@fastfinge I think especially with #snac /#snac2 many test, homelabs and nerdy spaces came up which are only reachable by v6. While im also running several v6 only things, public facing things should always be dual-stack.
@fastfinge I'm surprised at how many instances don't actually use IPV6 considering the software itself is pretty stack independent. I didn't have to do anything special when setting this thing up and it runs just fine over IPV6.
@quanin I have absolutely everything dockerized. Literally nothing at all runs on the host directly. In theory, that makes it super easy to move servers. And it would have been, too, if only I’d remembered to back up the config files for my instance, not just assume that it kept everything important in the database. Everything else moved as fast as I could transfer the data.
@fastfinge In theory, yes. In practice that's just one more point of failure. And unless you're changing your configs daily, nothing stops you from keeping a copy of them local. I've got a script that dumps the database into my userspace, then that and the configs are pulled local. Plus I have automatic daily image snapshots happening. Something catches fire I can be back online in 20 minutes. I may be missing the most recent data this way, but if it's important it can be replaced.
@quanin Right, but i run 20 other things on this server. Docker lets me stick it all behind a reverse proxy. And it’s not an issue that one app wants postgresql 15 and another wants 16 and nobody wants the same version of Python.
@fastfinge Ah. See generally speaking I prefer my servers a little more specialized. The server that runs this instance runs only this instance. The tradeoff there is of course that means more servers, but if for some reason this one explodes it only takes down this instance.
@fastfinge Nothing on these servers pays me. They're all projects I fired up at some point because I had the bandwidth. But also because none of these things are paying me, if I can't support them further they die in 5 seconds.
@fastfinge Oh I get it. In the last long-term gig I had one of these servers was also where I tested things so I could stick the developers' noses in what was broken, so I mean technically that server paid for itself. But since that's also my primary web server I already planned to pay for that.
@fastfinge@quanin I did not know that about Docker. Surprises me a little bit because I would have thought there would be ways to use the large IPv6 address space to make it easier to make network connections in and out of containers, but that's just an offhand thought, not an especially deep dive into containers.
@soaproot@quanin I wonder if that’s the reason it’s off? To run my fedi server, I have a container for the backend, one for the front end, one for email, one for backups, and one for the reverse proxy. The only one I want to have a public IP is the reverse proxy.
