search

Fallenbagel / jellyseerr

Fork of overseerr for jellyfin support.
https://docs.jellyseerr.dev/
MIT License
3.95k stars 249 forks source link

Prowlarr support #174

Open sunjam opened 2 years ago

sunjam commented 2 years ago

Description

Related to #96 and #134. Prowlarr is an indexer manager/proxy built on the popular *arr .net/reactjs base stack to integrate with your various PVR apps. Prowlarr supports management of both Torrent Trackers and Usenet Indexers. It integrates seamlessly with Lidarr, Mylar3, Radarr, Readarr, and Sonarr offering complete management of your indexers with no per app Indexer setup required (we do it all).

Desired Behavior

Prowlarr simplifies integration by serving as a proxy and manager for almost all existing *rr services, including those you currently support + those on your road map.

Thanks for considering either way!

Additional Context

No response

Code of Conduct

Fallenbagel commented 2 years ago

I'm not sure why you'd need prowlarr support on a request management software, could you care to explain more so I understand? 🤔

teambvd commented 2 years ago

For my own .02 - this is a lower priority 'nice-to-have'. The only difference this would make to the end user is saving them about 5 minutes during setup (one endpoing to connect to vs however many they're using), and a few additional minutes each time they make a change to one of their media management applications configuration (which should be a super rare occurrence).

It'd be kinda neat to have, I'd like it - I'd just prefer many other features be integrated prior, personally.

Fallenbagel commented 2 years ago

I'm still a little confused on the prowlarr support for request management because wouldn't just the sonarr and radarr need the indexers because they will be doing the indexing and sending releases to the download client? 🤔

Continous commented 1 year ago

I'm still a little confused on the prowlarr support for request management because wouldn't just the sonarr and radarr need the indexers because they will be doing the indexing and sending releases to the download client? 🤔

I think the idea is that the user already has sonarr/radarr set up through prowlarr, and instead wants jellyseerr to communicate to prowlarr instead of directly to sonarr/radarr. Perhaps too, the user may wish to use a service provided by prowlarr not supported directly by jellyseer, and so prowlarr can handle things, such as may be the case for music/audio where jellyseerr doesn't yet support a music/audio indexer.