Well, you just saved me a bunch of time trying to figure out how to auto-update my humble little server. Granted, I only have Plex and Samba Share right now, but I like the principle. Hell, an update once blanked my smb config file for whatever reason
Now auto-backups are another thing; because I would like to use a .tar file, but then it leads me down a rabbit hole because I don’t know how to repair Grub if needed for a restore, or what Grub really even is vs Bios… I’ve just been learning as I go
I’m a few weeks away from getting a couple parts for an upgrade, and then it’ll be some fun. I want to redo it from scratch and maybe set up proxmox and change my file system to zfs, then start looking at docker, figure out Jellyfin and look at some ARR stuff… maybe tailscale or headscale. Idk, it’s just fun cause it’s a hobby. I just haven’t had the storage or ram really, but soon
cyclicircuit@lemmy.dbzer0.com 3 days ago
I don’t disagree with any of that, I’m merely making a different value judgement - namely that a breach that could’ve been prevented by automatic updates is worse than an outage caused by the same.
I will however make this choice more explicit in the articles and outline the risks.
ikidd@lemmy.world 2 days ago
Don’t expose anything outside of the tailnet and 99% of the potential problems are gone. Noobs should not expose services across a firewall. Period.
WhyJiffie@sh.itjust.works 3 days ago
with properly limited access the breach is much, much less likely, and an update bringing down an important service at the bad moment does not need to be a thing