There have been many improvements in making documentation more inclusive across the IT industry which shouldn’t be scoffed at. The first that comes to mind is changing “master” and “slave” to “primary” and “secondary” (or “replica” etc.) because references to slavery is inconsiderate to many.

I don’t think pile-ons are productive, but I think inclusive language and thinking is important.

I stand corrected, thank you. I’ll have to try that out.

The biggest issue I’ve had with I2P so far has been lack of content.

postman.i2p only permits torrents which includes its tracker in the torrent file, which means popular torrents from 1337x, TPB et al can’t be uploaded there (at least not without changing the infohash). Torrent clients like qBittorrent and BiglyBT can cross-seed on I2P and clearnet networks which is a recent development since libtorrent 2.0 came out (software packages take a while to bump to.the latest library), but from what I’ve tested nearly all of the infohashes I put into my client from “clearnet” torrent sites have stalled, probably because I2P is a little too bespoke at the moment.

The potential is definitely there IMO, but unless you’re just watching mainstream movies and TV it’s not a replacement for clearnet/VPN.

If I’m missing something I’d like to know :)

Bash scripts will only get you so far and I can wholly recommend Ansible for automation.

Basically the main advantage of Ansible is that its builtin tasks are “idempotent” which means you can re-run them and end up with the same result. Of course it is possible to do the same with bash scripts, but you may require more checks in place.

The other advantage of Ansible is that there are hundreds of modules for configuring a lot of different things on your system(s) and most are clear and easy to understand.

You could use HAProxy on the client side to load balance apps in multiple locations, but it really depends on the application.

I like to manage my software with Ansible but Docker stack files might make it simple enough for you.

Yeah, too frequent and too buggy. It got annoying having to do upgrades every six months and have to deal with all the new bugs that came with it.

Basically give me Debian-style biannual releases or Arch-style rolling releases.

I use Debian at home on my homeserver and a mix of Debian and Arch for my workstations. Most of my stuff is managed with Ansible to make rebuilding easier and most workloads in podman containers.

Personally I don’t overthink the distro thing. I recently started using Arch and quite like it. I’ve noticed packages that are available in Debian but not Arch and vice-versa. Debian Stable is nice because it’s just, well, stable.

Fedora has an annoying release cadence IMO. I have experienced desktop bugs in the early GA releases before which put me off. If I wanted instability I would sooner go with Arch (and I am yet to have many issues with Arch yet).

If I were to go with a BSD for a home server it would probably be OpenBSD or FreeBSD. OpenBSD has vmm and a bunch of tooling around it, and FreeBSD has bhyve and jails. I haven’t taken the plunge because Linux works and it’s what I know.

These days I hear about people using proxmox on their homeserver with LXC containers and/or VMs.