this post was submitted on 01 Dec 2023
38 points (95.2% liked)

Selfhosted

39964 readers
298 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
38
Do you configure your servarr docker containers from one docker-compose file, or individual ones? (lemmy.world)
submitted 11 months ago by [email protected] to c/[email protected]
29 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 11 months ago* (last edited 11 months ago) (3 children)

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.

[–] [email protected] 4 points 11 months ago* (last edited 11 months ago) (1 children)

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.

[–] [email protected] 1 points 11 months ago* (last edited 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.

[–] [email protected] 1 points 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

[–] [email protected] 1 points 11 months ago (1 children)

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

Convenience is the reason for a lot of people

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago) (1 children)

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.

[–] [email protected] 1 points 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