We’re excited to announce a major update: the Jellyseerr and Overseerr teams are officially merging into a single team called Seerr. This unification marks an important step forward as we bring our efforts together under one banner.
For users, this means one shared codebase combining all existing Overseerr functionalities with the latest Jellyseerr features, along with Jellyfin and Emby support, allowing us to deliver updates more efficiently and keep the project moving forward.
Please check how to migrate to Seerr in our migration guide and stay tuned for more updates on the project!
I hate how so many of the arr apps don’t describe what they do in a way that people who don’t already know can understand.
Even the tutorials and guides are frustratingly vague.
Given it’s a suite of tools designed specifically to download copyrighted content, why are you surprised that descriptions are coy and elusive?
I’ll be honest, only the first setup gave me some trouble as I was tackling docker compose too. After you gain familiarity setting up a new arr is basically copying the provided yaml service then filling in the envs with yours
I hate how fragmented they are. I’ve given up on various guides out there for ‘setting up the arr stack’ because of getting bogged down in since miniature detail that, IMHO, shouldn’t even be a thing. I get that hosting seperate services has advantages. But the disadvantage of giving up on the whole thing because you have to sort out networking and file permission issues between the service that downloads video files over an hour long and the service that downloads video files under an hour outweighs those advantages.
What problems did you have? I just put the services I wanted in a compose file, configured sonarr/radarr to use prowlarr and my torrent client and done.
Later I added lidarr and readarr but ended up removing the last one. I found it easy enough, and the modularity makes it easy to use only what you need.
Spoiler: I am deeply into the arr “ecosystem” and love the shit out of it.
I think I finally understand Linux fans. Yes it’s confusing for new people, but because I’m so into the weeds on this stuff I love how much choice I have. And if one of the projects doesn’t have what we want, someone makes a fork.
To point: you really only need Sonarr and Radarr. Get those set up and working how you like. I recommend the Trash Guides. Once that’s working how you like, get Prowlarr for easy management of your usenet and torrent indexers. Most people should stop there.
You’re not alone. It’s super frustrating when things don’t work and you have to search through 4 apps to figure out what is wrong. This architecture makes the whole setup brittle.
Fortunately, there are all in one alternatives to the arr stack. I found a couple, but I think Cinephage is the most mature.
You said it’s the most mature, but it’s only about 2 months old and coded partially with AI.
I’m interested in this but paranoid about security, and don’t know how much I can trust something newish they also has some code the developer might not understand.
Huh. That sounds overly complicated. I just link everything with my torrent client. Tracker (prowlarr) into media managers (sonarr/radarr) into torrent client. That’s it.
I have jellyseer in there too but that’s a separate service that just works. The core stack is the other paragraph.
Everything is installed in my local server using the install script, no docker.
Either you misconfigured something or you are very new to this.
Keep it up.
As for good guides: Trash-guides
They provide a very in depth set-up that works really well.
The only thing you’ll need after this, is a source for the files.
Ikr like… Give me a docker compose file and tell me what env vars need to be set to what. Why is it so complicated?
Maybe thats by design. Some sort of gate keeping