I have bought my first proper home server and am setting up a full stack of media services on truenas scale after years of doing everything manually. In that regard I have set up jellyfin, sabnzbd and radarr, and the next step is to add jellyserr it seems. But then I stumble across prowlarr and cannot figure out if it is a contender to or a supplement to jellyserr. Can somebody tell me what the difference is, if I should use both if they are complementing each other or which you are using if they are competing?
They are two different programs. Prowlarr is an index manager and overserr/jellyserr are requesters.
Indexer pulls a listing of available files from as many indexing services as you add. 1337x, NZBgeek, etc.
Overserr is like a front end for your entire stack. You just tell it what you want media you want and it sends the requests to the stack to figure out.
Overserr talks to -> radar/sonarr talks to -> prowlarr talks to -> sabnzbd/qbit.
Beware of radarr, if you remove a library there it clears all files without warning! (That’s why I came back to manual. Setup was a hassle, and having to come to a backup was the last drop in my glass)
I never heard of those tools, but I have a jellyfin server. By “support” for jellyfin, does that mean it has like a plugin or something to request media from within jellyfin?
I haven’t set up jellyserr yet, so I haven’t seen it in action yet, but if it works the way I understand it should, it is that when media is downloaded it is automatically updated into your jellyfin server.
See the reply by @zewm@zewm@lemmy.zip. Jellyserr is the gui where you search for the media. It then sends radarr/sonarr/… the request which works along prowlarr to download the usenet or torrent file and makes your usenet/torrent client download it. When the download is complete it is moved to the correct place, renamed by your rules etc and inserted into your media server.
Radarr is for movies, Sonarr is for shows, you have one for audiobooks, one for music, comics etc.
Gotcha. In that case I’ve already set that all up in sonarr/radarr directly, using shared docker volumes.
