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

[–] Overspark@piefed.social 11 points 2 months ago (1 children)

Podman automatically updates my containers for me.

[–] jeena@piefed.jeena.net 5 points 2 months ago* (last edited 2 months ago) (1 children)

Because you point to :latest and everything is dockerized and on one machine? How does it know when it's time to upgrade?

[–] Overspark@piefed.social 6 points 2 months ago (1 children)

Yeah only for :latest containers, that's true. It automatically runs a daily service to check whether there are newer images available. You can turn it off per container if you don't want it.

One of the nice things about it is that I have containers running under several different users (for security reasons) so that saves me a lot of effort switching to all these users all the time.

[–] melroy@kbin.melroy.org -2 points 2 months ago (2 children)

It's a bad practice to use latest tag

[–] prenatal_confusion@feddit.org 10 points 2 months ago* (last edited 2 months ago)

Depends on what you want to do. For production with sensitive data, yes it is. For my ytdl and jellyfin? Perfectly fine.

[–] Overspark@piefed.social 6 points 2 months ago

Depends. There are a few things I update by hand, but as long as you have proper backups it's generally safer to run the latest versions of things automatically if you don't mind the possibility of breakage (which is very rare in my experience). This is in the context of self-hosting of course, not a business environment.