Go with docker images and save your setup files/commands, so you can always redeploy on a NAS/new server later. Go with lscr.io/linuxserver images.
It probably took me a good 20 hours to setup. Then dozens more hours to get my existing library imported, but that's just part of the process.
Initially it is time intensive, but it's totally worth it. Make sure you make proper backups, so you don't lose your work.
Tbh, setting things up the second time is a lot faster than the first time.
It can be a good bit less than 20 hours. I did my very first setup and it took maybe 5-6 hours total, possibly less. But to be fair, I already had the computer assembled and the operating system and docker were already installed. I use Gentoo so building everything from scratch would've taken 20+ hours for sure.
Couple of tips for anyone just getting started: Use docker compose and copy the YAML from sonarr, radarr, prowlarr and (overseerr or jellyseerr) docker registry pages (or github readme). If they don't want to connect to eachother, try using the container name (defined in docker compose file) instead of localhost. Docker will set up those as hostnames for communication between containers on the same machine. Luckily I knew this from having worked with docker previously, could've been a pain to figure out otherwise (I mean sure, you could also use your machine's local (not 127.0.0.1) IP, but that can change, if you don't have a static one set up).
Also, the configs usually mount a path (a fictional one you change) for config. This makes reusing your config easier. If you omit that part, the config files will live on an ephemeral volume.
I was having trouble adding my Prowlarr indexers to Radarr and Sonarr. Then I googled around a bit and discovered that it should be done the other way around - add Radarr and Sonarr as apps to Prowlarr.
Next step for me is to buy some used hardware and a bunch of big shiny new drives and set up an actual server instead of running it on my Linux desktop PC (which to be fair, runs 24/7 anyway). Thinking NVMe boot drive and 18 TB drives for storage, start with 3 in RAID 5 and then add a couple more over time. I THINK that's a good idea, but if someone wants to tell me why it's not, please do.
Go with docker images and save your setup files/commands, so you can always redeploy on a NAS/new server later. Go with lscr.io/linuxserver images.
It probably took me a good 20 hours to setup. Then dozens more hours to get my existing library imported, but that's just part of the process.
Initially it is time intensive, but it's totally worth it. Make sure you make proper backups, so you don't lose your work.
Tbh, setting things up the second time is a lot faster than the first time.
It can be a good bit less than 20 hours. I did my very first setup and it took maybe 5-6 hours total, possibly less. But to be fair, I already had the computer assembled and the operating system and docker were already installed. I use Gentoo so building everything from scratch would've taken 20+ hours for sure.
Couple of tips for anyone just getting started: Use docker compose and copy the YAML from sonarr, radarr, prowlarr and (overseerr or jellyseerr) docker registry pages (or github readme). If they don't want to connect to eachother, try using the container name (defined in docker compose file) instead of localhost. Docker will set up those as hostnames for communication between containers on the same machine. Luckily I knew this from having worked with docker previously, could've been a pain to figure out otherwise (I mean sure, you could also use your machine's local (not 127.0.0.1) IP, but that can change, if you don't have a static one set up).
Also, the configs usually mount a path (a fictional one you change) for config. This makes reusing your config easier. If you omit that part, the config files will live on an ephemeral volume.
I was having trouble adding my Prowlarr indexers to Radarr and Sonarr. Then I googled around a bit and discovered that it should be done the other way around - add Radarr and Sonarr as apps to Prowlarr.
Next step for me is to buy some used hardware and a bunch of big shiny new drives and set up an actual server instead of running it on my Linux desktop PC (which to be fair, runs 24/7 anyway). Thinking NVMe boot drive and 18 TB drives for storage, start with 3 in RAID 5 and then add a couple more over time. I THINK that's a good idea, but if someone wants to tell me why it's not, please do.