Comment on Do you configure your servarr docker containers from one docker-compose file, or individual ones?

eager_eagle@lemmy.world ⁨11⁩ ⁨months⁩ ago

• CalicoJack@lemmy.dbzer0.com ⁨11⁩ ⁨months⁩ ago

  You can interact with a single container if you need to, not just the whole compose group. docker compose restart jellyfin for your example, and “restart” can be swapped for stop or start as needed.

  Splitting compose files can be a good idea, but it isn’t always necessary.

  source

  • eager_eagle@lemmy.world ⁨11⁩ ⁨months⁩ ago

    yes, but I use one alias for all stacks to down, pull, up as a daemon, and watch its logs, so I’d rather split the stack than have a special treatment for it.

    source
• Kusimulkku@lemm.ee ⁨11⁩ ⁨months⁩ ago

  There’s no point in having them in the same file

  Convenience is the reason for a lot of people

  source

  • eager_eagle@lemmy.world ⁨11⁩ ⁨months⁩ ago

    if these are the only services one is self hosting, I can see that.

    But I have around a dozen stacks atm and I never came across a situation that I wanted to trigger an *arr stack restart with Jellyfin’s. They’re pretty much unrelated services from an operational view.

    source

    • Kusimulkku@lemm.ee ⁨11⁩ ⁨months⁩ ago

      You can issue commands to singular services or group them under an alies if needed.

      But I have around a dozen stacks atm and I never came across a situation that I wanted to trigger an *arr stack restart with Jellyfin’s. They’re pretty much unrelated and independent services from an operational view.

      I’m more talking about pull, up -d. It’s convenient having it all behind a single command, unless there’s a special need to have them separated

      source
• offspec@lemmy.nicknakin.com ⁨11⁩ ⁨months⁩ ago

  I use individual files with some like-services grouped together, but you interface with specific services withing a compose file by just specifying the name at the end o the command

  source