• 1 Post
  • 292 Comments
Joined 1 year ago
cake
Cake day: February 16th, 2025

help-circle



















  • I found the guides overwhelming too at the start, but then I skipped them and just went for it with a simple container in a compose file (doesn’t even have to be sonarr).

    The benefit of containerisation is that if you break it, it’s simple to remove the container, delete the config folder and start again without affecting your system. Give it fake data files to munch on and it’s unlikely to ruin anything if you muck it up.

    So I did that a few times until I got the basic relationship between the docker compose file and the functions of the program. THEN I looked up some guides on the arrs and saw I needed to structure the volumes better, but that’s fine because I could wipe clean and go again.

    Only when it worked predictably and I understood it did I let it loose on my library.

    The good news is that if you figure Sonarr out, Radarr is almost exactly the same. As are all the arrs.

    And then if you need some of them to route through a VPN container, that’s just one line in the file. And so on. Before you know it there are 20+ services and they’re easily managed.

    So from services on a single compose, I can mark a show to follow, it’ll automatically download on release, rename itself, any extraneous subtitles and audio tracks removed, ingest to the media server, and delete the files when they’ve been watched. Basically, all I do is ask for the show and watch it. Everything else is automatic.