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.
I created them in the same compose but will probably split them up soon. There’s no point in having them in the same file: *arr services and jacket interact with each other, but Jellyfin is its own thing and I often want/need to restart it alone. They’re best as 2 separate stacks imo.
You can interact with a single container if you need to, not just the whole compose group.
docker compose restart jellyfinworks 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.
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.
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