Selfhosted

59897 readers

521 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.

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

How to manage docker compose apps? (lemmy.today)

submitted 8 months ago by paequ2@lemmy.today to c/selfhosted@lemmy.world

56 comments fedilink hide all child comments

How do y'all manage all these Docker compose apps?

First I installed Jellyfin natively on Debian, which was nice because everything just worked with the normal package manager and systemd.

Then, Navidrome wasn't in the repos, but it's a simple Go binary and provides a systemd unit file, so that was not so bad just downloading a new binary every now and then.

Then... Immich came... and forced me to use Docker compose... :|

Now I'm looking at Frigate... and it also requires Docker compose... :|

Looking through the docs, looks like Jellyfin, Navidrome, Immich, and Frigate all require/support Docker compose...

At this point, I'm wondering if I should switch everything to Docker compose so I can keep everything straight.

But, how do folks manage this mess? Is there an analogue to apt update, apt upgrade, systemctl restart, journalctl for all these Docker compose apps? Or do I have to individually manage each app? I guess I could write a bash script... but... is this what other people do?

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

[–] sobchak@programming.dev 3 points 8 months ago (1 children)

I think compose files are usually pinned to a version, or use a .env file that needs to be changed to update to a new version.

I personally don't update very often; usually not until I'm forced to for some reason. I find that just checking the documentation for any upgrade/migration guides, and doing it manually is sufficient. I don't expose this kind of stuff publicly; if I did, I'd probably update regularly.

[–] SnotFlickerman@lemmy.blahaj.zone 4 points 8 months ago* (last edited 8 months ago)

Immich is a more touchy beast because it includes a mobile app and the mobile app and the docker container need to generally be either the same version, or within a few versions of one another. There was a while where I forgot to update the server for a while and the mobile app kept being updated on my phone and stopped backing up photos because it could no longer communicate with the server.

I don't expose services to the outside world either, but I still enjoy keeping things up to date. Gives me something to do.