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.
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
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 and independent services from an operational view.
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
You can interact with a single container if you need to, not just the whole compose group. docker compose restart jellyfin works 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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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 posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
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.
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
Convenience is the reason for a lot of people
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 and independent services from an operational view.
You can issue commands to singular services or group them under an alies if needed.
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
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.