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.
Arrs combined. Jellyfin alone. VPN with VPN stuff. Everything else alone. Unless it’s multiple of the same app.
i had arr in one stack and media in another.
Now in my kubernetes cluster everything is separated, but arr + torrent is in vpn and automatically uses the vpn-sidecar. And media (jellyfin + jellyseer) is separate.Same.
Jellyfin, Audiobookshelf, kavita = Media stack
Arr suite, Vpn, BitTorrent = Pirate stack
Edit:
CodeServer, git, esphome, home assistant = Code Stack
I have all of mine in their respective directories and have a master script that I run to bring them all up or take them down. Easier to exclude services from start up if I end up not needing them or something.
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.
There’s no point in having them in the same file
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.
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
I group them by network.
A mix - my *arrs, Plex, etc run in my “media” stack’s compose, but I have a handful of other stacks (“managing”, “monitoring”, “misc”, “games”, etc) for containers that aren’t related.
This also helps keep networks separate so the containers are only talking to the ones I want them to
I used to try to run arr stack together, but separately from jellyfin and transmission because I use them not only with arr things
But now I’m using nixos, and having the same dilemma with .nix files
Same. Never felt the need to do them separately.
Use to do it individually. Now I do it all from one Master compose.
Why separate it? It’s part of the same stack. Radar downloads, Jellyfin plays.
No Docker, because overhead and depending on a semi-closed ecosystem isn’t cool. Also systemd is perfectly capable of providing all the security docker does by itself.
