this post was submitted on 07 Mar 2024
3 points (100.0% liked)

Selfhosted

39931 readers
463 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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?

top 5 comments
sorted by: hot top controversial new old
[–] zewm@lemmy.zip 2 points 8 months ago

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.

[–] anzo@programming.dev 0 points 7 months ago

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)

[–] thepaperpilot@incremental.social 0 points 8 months ago (1 children)

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?

[–] virku@lemmy.world 0 points 8 months ago (1 children)

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.

[–] thepaperpilot@incremental.social 1 points 8 months ago* (last edited 8 months ago)

Gotcha. In that case I've already set that all up in sonarr/radarr directly, using shared docker volumes.