Comment on Could somebody share a working Arr stack in docker with me?
plantsmakemehappy@lemmy.zip 3 weeks agowiki.servarr.com/radarr/tips-and-tricks#creating-…
I recommend being really specific on what issues you’re facing when you want help. Your post was pretty generic and so you’re getting a lot of different answers.
If discord is your thing, the servarr/sonarr/trash folks each have their own discord where you can get help.
Postmortal_Pop@lemmy.world 3 weeks ago
That’s actually what I was trying with the TLDR. As I understood it, docker is popular because once you get it running on one system you can use docker to make it run on any system. So my assumption was that someone who has the arr stuff working could just send me a copy of their config.yml and the directory it makes when you up and then I just tweak the locations and names on my side. I get that’s probably not possible but I’ll take literally anything at this point.
hirihit640@sh.itjust.works 3 weeks ago
You’re not wrong but when you use somebody else’s config you use somebody else’s…configuration. Like if they use ProtonVPN, you’ll need to use ProtonVPN as well. If they use Usenet instead of torrents, that’s what you’ll get as well. If somebody uses Podman instead of Docker, etc etc. So this is why it can be more difficult than just ripping configs from strangers.
This is the classic problem where the more flexibility a program has, the more fragmentation comes out of it. The *arr stack is complicated for this reason. It’s a million different pieces that can be configured in a million different ways. Something like Nextcloud is much more plug-and-play. I’ve been doing self-hosting for years now and even I find *arr a chore to deal with.
Though nothing wrong with referencing other people’s configs to get a sense of what it’s supposed to look like. Start simple, look for somebody who has a radarr + qbittorrent + gluetun stack working, and go from there.