Selfhosted

60093 readers

958 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 7 days old, your post is exempt from this rule as long as you continue to engage in comments.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

112

How Do you keep your services updated? (piefed.jeena.net)

submitted 2 months ago by jeena@piefed.jeena.net to c/selfhosted@lemmy.world

67 comments fedilink hide all child comments

Back in the day it was nice, apt get update && apt get upgrade and you were done.

But today every tool/service has it's own way to being installed and updated:

docker:latest
docker:v1.2.3
custom script
git checkout v1.2.3
same but with custom migration commands afterwards
custom commands change from release to release
expect to do update as a specific user
update nginx config
update own default config and service has dependencies on the config changes
expect new versions of tools
etc.

I selfhost around 20 services like PieFed, Mastodon, PeerTube, Paperless-ngx, Immich, open-webui, Grafana, etc. And all of them have some dependencies which need to be updated too.

And nowadays you can't really keep running on an older version especially when it's internet facing.

So anyway, what are your strategies how to keep sanity while keeping all your self hosted services up to date?

you are viewing a single comment's thread
view the rest of the comments

[–] mlfh@lm.mlfh.org 28 points 2 months ago (2 children)

Everything I run, I deploy and manage with ansible.

When I'm building out the role/playbook for a new service, I make sure to build in any special upgrade tasks it might have and tag them. When it's time to run infrastructure-wide updates, I can run my single upgrade playbook and pull in the upgrade tasks for everything everywhere - new packages, container images, git releases, and all the service restart steps to load them.

It's more work at the beginning to set the role/playbook up properly, but it makes maintaining everything so much nicer (which I think is vital to keep it all fun and manageable).

[–] non_burglar@lemmy.world 10 points 2 months ago

+1 for ansible.There's a module for almost everything out there.

[–] jeena@piefed.jeena.net 7 points 2 months ago (1 children)

Yeah, For some reason I didn't think of ansible even though I use it at work regularly. Thanks for pointing it out!

[–] Cyber@feddit.uk 5 points 2 months ago

Just a word of caution...

I try to upgrade 1 (of a similar group) manually first to check it'a not foobarred after the update, then crack on with the rest. Testing a restore is 1 thing, but restoring the whole system...?