Selfhosted

58442 readers

1007 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 posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

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

submitted 1 day ago by jeena@piefed.jeena.net to c/selfhosted@lemmy.world

56 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

[–] iamthetot@piefed.ca 3 points 1 day ago* (last edited 19 hours ago) (2 children)

cd appname && dockup && cd ..

Dockup being an alias for docker compose pull && docker compose up -d

Repeat for the few services I have.

[–] jeena@piefed.jeena.net 5 points 1 day ago (1 children)

So everything is dockerized and points to :latest?

What about the necessary changes to the docker compose files? What about changes necessary in nginx configs?

I guess you also read each release notes manually?

[–] iamthetot@piefed.ca 1 points 19 hours ago

Not running anything that I've had to alter compose files. Also never had change nginx configs. Maybe I'm just running particularly stable stuff.

I usually read update notes yes, but I'd be lying if I said I was always thorough.

[–] probable_possum@leminal.space 2 points 23 hours ago* (last edited 23 hours ago) (1 children)

I don't understand. docker compose up starts the container. When does the docker compose pull happen? Or is there an update directive in the compose file?

[–] iamthetot@piefed.ca 2 points 19 hours ago (1 children)

Whoops, I forgot that the alias includes a pull for the latest versions.

[–] probable_possum@leminal.space 1 points 17 hours ago* (last edited 17 hours ago) (1 children)

Ah. I thought there is an option in docker compose I could use.

And a docker image prune - a while the containers are running? :)

[–] iamthetot@piefed.ca 1 points 16 hours ago

Yes, I usually do that after I check all the services are running okay.