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?

    • village604@adultswim.fanEnglish
      2·
      15 hours ago

      Hmm, I wonder if I can use this on my Synology to manage things until I get around to finishing my proxmox setup.

    • Kyle@lemmy.caEnglish
      3·
      22 hours ago

      Wow thank you for this. This looks so much nicer than portainer.

      Subscribing to these communities is so helpful because of discovery like this.

    • Lka1988@sh.itjust.worksEnglish
      2·
      22 hours ago

      Same here. Dockge is also developed by the Watchtower dev.

      It’s so much easier to use than Portainer: no weird licensing shit, uses standard Docker locations, and works even with existing stacks. Also helps me keep Docker stacks organized - each compose.yaml lives in it’s own folder under /opt/stacks/.

      I have 4 VMs on my cluster specifically for Docker, each with it’s own Dockge instance, which can be linked together so that any Dockge instance in my cluster can access all Docker stacks over all the VMs.