How do you keep up?
-
[email protected]replied to [email protected] last edited by
Constant maintenance? What's that?
Here's my setup:
- OS - openSUSE Leap - I upgrade when I remember
- software - Docker images in a docker compose file; upgrading is a simple docker command, and I'll only do it if I need something in the update
- hardware - old desktop; I'll upgrade when I have extra hardware
I honestly don't think about it. I run updates when I get to it (every month or so), and I'll do an OS upgrade a little while after a new release is available (every couple years?).
I don't even know what TrueCharts is. Maybe that's your issue?
-
[email protected]replied to [email protected] last edited by
Same, but openSUSE. Tumbleweed on my desktop and laptop, Leap on my servers.
And yeah, if I need to babysit something, I'll use an alternative. I'll upgrade when I'm ready to, which is usually over holidays when I'm bored and looking for a project.
-
[email protected]replied to [email protected] last edited by
How does that help here?
-
[email protected]replied to [email protected] last edited by
For automating maintenance and updates? How exactly does it not?
-
[email protected]replied to [email protected] last edited by
They are complaining because of the number of updates and breaking changes. Ansible just a tool for bulk changes
-
[email protected]replied to [email protected] last edited by
Yeah, everything that's already been said, except that I specifically chose an off-the-shelf Synology NAS with Docker support to run my core setup for this exact reason. It needs a reboot maybe once or twice a year for critical updates but is otherwise rock solid.
I have since added a small N100 box for things that need a little extra grunt (Plex mainly) but I run Ubuntu Server LTS with Docker on that and do maintenance on it about as often as I reboot the NAS.
-
[email protected]replied to [email protected] last edited by
Debian, baby.
-
[email protected]replied to [email protected] last edited by
You can choose a slower train for scale. Go for the stable release or even the enterprise release. Update once in a few months or so.
I went with Talos OS for my apps after the mess from IX-systems and for the most part it has been set and forget.
-
[email protected]replied to [email protected] last edited by
Docker: More or less automatically upgraded (compose)
Proxmox/TrueNas: My setup breaks so often I want to do something that I will check it every once in a while and run updates
Main Debian NAS: Automatic updates. (apt)
Raspberry Pi: Automatic Updates (apt)
Windows: If it prompts me and I am shutting it down amyway: Fine. Thanks for notifying.I stopped chassing updates quite some time ago.
-
[email protected]replied to [email protected] last edited by
Release: stable
Keep the updates as hands off as possible. Docker compose, TTecks lxc updater.
I come through once a week or so to update the stacks, I come through once a month or so to update the machines. Total time updating is 3hrs a month, I could drop that a lot when I get around to writing some scripts to update docker images.
Minimise attack surface and outsource security. I have nothing at all open to the internet, I use Tailscale to create tunnels. I'm trusting my security to Tailscale but they are much, much, better at it than I am.
-
[email protected]replied to [email protected] last edited by
Release: stable
Keep the updates as hands off as possible. Docker compose, TTeck's LXC updater, automatic upgrades.
I come through once a week or so to update the stacks (dockge > stack > update), I come through once a month or so to update the machines (I have 5 total). Total time updating is 3hrs a month. I could drop that time a lot when I get around to writing some scripts to update docker images, then I'd just have to "apt update && apt upgrade"
Minimise attack surface and outsource security. I have nothing at all open to the internet, I use Tailscale to create tunnels. I'm trusting my security to Tailscale, Pihole and my ISP's firewall, but they are much, much better at it than I am.
-
[email protected]replied to [email protected] last edited by
Same here. I spent last month transitioning all my servers to NixOS and it feels so comfy! I do a small test on my desktop when I do something that might break stuff first, and then add it to server's config later.
--target-host
and--use-remote-sudo
makes it even better too. -
[email protected]replied to [email protected] last edited by
I run a Fedora server.
All of my apps are in docker containers set to restart unless stopped by me.
Then I run a cron job that is scheduled at like 3 or 4am that runs docker pull on all containers and restarts them. Then it runs all system uldtwa and restarts the server.
Every week or so I just spot check to make sure it is still working. This has been my process for like 6 months without issue.
-
[email protected]replied to [email protected] last edited by
Try watchtower instead of cron jobs
-
[email protected]replied to [email protected] last edited by
I'll check it out! Thanks!