Selfhosted

60482 readers

511 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.

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

103

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

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

66 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

[–] BlackEco@lemmy.blackeco.com 2 points 2 months ago (1 children)

I guess auto merge isn't enabled, since there's no way to check if an update doesn't break your deployment beforehand, am I right?

[–] tofu@lemmy.nocturnal.garden 2 points 2 months ago (1 children)

You can configure automerge per stack and also if it's allowed on patch, minor or major upgrades.

[–] BlackEco@lemmy.blackeco.com 2 points 2 months ago (1 children)

Yes, but usually when you use automerge you should have set up a CI to make sure new versions don't break your software or deployment. How are you supposed to do that in a self-hosting environment?

[–] tofu@lemmy.nocturnal.garden 2 points 2 months ago

Ideally, you have at least two systems, test updates in the dev system and only then allow it in prod. So no auto merge in prod in this case or somehow have it check if dev worked.

Seeing which services are usually fine to update without intervening and tuning your renovate config to it should be sufficient for homelab imho.

Given that most people are running :latest and just yolo the updates with watchtower or not automated at all, some granular control with renovate is already a big improvement.