The right way ™ is to have the application deployed with high availability. That is every component should have more than one server serving it. Then you can take them offline for a reboot sequentially so that there’s always a live one serving users. This is taken to an extreme in theatest cloud best practices where we don’t even update any servers. We update the versions of the packages we want in some source code file. A build job runs on that repo which produces a new OS image contains the updated things along with the application that the server will run and it’s ready to boot. Then in some sequence we kill server VMs running the old image and create news ones running the new.
Comment on Does "Selfhosted" mean you actually have a server at home?
nix@merv.news 9 months agoHow do you install security updates etc without restarting?
Linux servers prompt you do restart after certain updates do you just not restart?
avidamoeba@lemmy.ca 9 months ago
poVoq@slrpnk.net 9 months ago
You can just restart… with modern SSDs it takes less than a minute. No one is ging to have a problem with 1 minute downtime per month or so.
NeoNachtwaechter@lemmy.world 9 months ago
install security updates etc without restarting?
I am actually lazy with updates on the “bare metal” debian/proxmox. It does nothing else than host several vm’s. Even the hard disks belong to a vm that provides all the file shares.
VonReposti@feddit.dk 9 months ago
Enterprise distributuions can hot-swap kernels, making it unnecessary to reboot in order to make system updates.
Pringles@lemm.ee 9 months ago
Microsoft needs to get its shit together because reboots were a huge point of contention when I was setting up automated patching at my company.
Valmond@lemmy.mindoki.com 9 months ago
Good luck with that, I have all reboot options off but yesterday it just rebooted like that. Thanks MS.