I followed trash guides to set everything up blindly and my set up is working well. But, I feel like having jellyfin in the same docker compose as my “arr” services isn’t good. So, I’d be curious to see if I should split things up. I am even wondering if i should let portainer manage everything.

  • blicky_blank@lemmy.today
    link
    fedilink
    English
    arrow-up
    4
    ·
    11 months ago

    Yes splitting them up is much better.

    The only reason you should have secondary services there is if main service is using them exclusively.

    Having a single compose file for multiple unrelated services sounds like a nightmare to stop, start and debug if one of your containers is acting weird.


    Say for example you have something that needs a mysql server and you have no other use for it beyond that container, then it should go in there with the main seevice.

    But then you eventually add another service which also needs a mysql backend. Do you add another mysql instance for that specific service? Or you could separate your existing one into its own compose file and just connect the two separate apps to the single instance.


    Here’s the way I have mine setup. https://github.com/DanTheMinotaur/HomeHost/tree/main/apps

    I use an ansible job to deploy and run them.

    • Kusimulkku@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      Having a single compose file for multiple unrelated services sounds like a nightmare to stop, start and debug if one of your containers is acting weird.

      You can do “docker compose (servive) start/stop/restart” and so on