Post #2132397

@domi before I forget completely 1) how do you arrange planned downtime when other users are logged in; like reboots-for-kernel-upgrades stuff? do you just wall <<< "reboot incoming, hold on to your tmuxes" or do you have a monthly schedule? (like you have some disdain for single-user selfhosting but one reason that keeps me from actively going out and Offering Services on my own systems is that I'd have no place to tinker with things anymore and get into situations where something breaks until reboot, or a security fix needs a reboot, etc. (another reason being that all my machines are kinda /old/ lol)) 2) already forgot what else I was going to ask I think it was about putting literally everything on one server vs multiple lower spec servers