I got a used mini pc to run as a media center, running the arr stack and torrent client that's bound to the VPN interface. For usenet stuff I don't care is it on VPN or not. Its running headless.
If you make sure that the torrent client is set to be bound on the VPN interface, you are fine, if VPN is not up, it should not start, since the interface is not up. For VPN I use wireguard and set the VPN to be brought up by via wg-quick command and use systemd to start it during boot.
You'll be fine using it for personal stuff along with pulling stuff from high seas.
At least, for me, Nix was never attractive, and it should be by all means, the features it provides. I still see this as an alternative, where I'm more than satisfied with my bash scripts and git repos, syncthing backups to rebuild the whole system.
And, on the second part, this schism that happened in Nix is the same recipie that happened in other projects. I just find it funny.
Yeah, I'm looking at it, will probably rewrite the logic using Pingora. or maybe I did something wrong. Not sure if its something using the hyper legacy client, that has connection pooling, maybe there's something there to improve.
or maybe the use of RwLock to share the config struct is reaching some limits. Will try using parking_lot to see if anything changes.
reverse proxy using tokio and hyper, there are few things to figure out on high traffic sites, it doesn't work as well compared to nginx after a certain threshold.
@green_dot
@le.fduck.net