NBN Co today launched a proposal to provide five times faster download speeds on its popular nbn Home Fast product, which would see wholesale download speeds accelerate from 100/20 Mbps to 500/50 Mbps1 at no extra wholesale cost to retailers.
Fair point, I've updated the readme now.
I hadn't planned on that specifically. An idea that's been in the back of my mind is to allow the configuration file be used to let users decide what command gets run, and with what arguments, so that you could use pretty much anything as the UI.
An interruption-free notification system for Linux - GitHub - ellsclytn/nofi: An interruption-free notification system for Linux
cross-posted from: https://aussie.zone/post/478031
> I wanted to improve my Rust knowledge a bit and solve how I approach notifications, so I made nofi. > > nofi is a desktop notification server, but instead of delivering realtime popups, it stores the notifications for you to view when you choose via a Rofi menu. It can also integrate with i3status-rust to show a pending notification count in your status bar. > > It's inspired by Rofication (the status bar integration follows the exact same protocol for drop-in compatibility).
An interruption-free notification system for Linux - GitHub - ellsclytn/nofi: An interruption-free notification system for Linux
I wanted to improve my Rust knowledge a bit and solve how I approach notifications, so I made nofi.
nofi is a desktop notification server, but instead of delivering realtime popups, it stores the notifications for you to view when you choose via a Rofi menu. It can also integrate with i3status-rust to show a pending notification count in your status bar.
It's inspired by Rofication (the status bar integration follows the exact same protocol for drop-in compatibility).
Honestly, I'd be surprised if static IPs fix it. Docker's default network type (bridge network) is very good at assigning IPs to containers without clashing, even with container restarts and replacements: it's been battle tested for years in production use. As others have said, standard DNS hostnames of containers should be sufficient. But I'll certainly be interested to hear your results.
networks:
app:
ipam:
config:
- subnet: 172.20.0.0/24
gateway: 172.20.0.1
services:
app:
image: my-app-image
networks:
app:
ipv4_address: 172.20.0.10
In the above example I've declared a Docker Bridge network with the range 172.20.0.0/24
and a gateway at 172.20.0.1
. I have a service named app
with a static IP of 172.20.0.10
.
The same is also possible with IPv6, though there are extra steps involved to make IPv6 networking work in Docker and it's not enabled by default so I won't go into detail in this comment.
Out of curiosity, what's the use case for a static IP in the Docker Bridge network? Docker compose assigns hostnames equal to the service name. That is, if you had another container in the app
network from my example above, it could just do a DNS lookup for app
and it would resolve to 172.20.0.10
.
Has anyone else experienced the -silent
launch option for Steam no longer working since the big client update? Hoping there might be a known fix/workaround out there.
Got a general interest in self hosted/open source software. Would love a podcast that talks about some of the trending applications out there.