Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request] Support for Jellyseerr #132

Open
iamronr opened this issue Dec 8, 2023 · 4 comments
Open

[Request] Support for Jellyseerr #132

iamronr opened this issue Dec 8, 2023 · 4 comments

Comments

@iamronr
Copy link

iamronr commented Dec 8, 2023

Is your feature request related to a problem? Please describe.
No. Overseerr only supports Plex, not Emby. A lot of Plex users are starting to move to Emby with the recent Plex news, and the direction Plex is going. Jellyseerr is a fork of Overseerr, but supports Emby.

Describe the solution you'd like
Being able to use Doplarr to submit requests to Jellyseerr. I'm no dev, but I imagine since Jellyseerr is a fork of Overseerr, the coding might be the same, if not VERY similar.

Describe alternatives you've considered
Just allowing those I share my Emby library with to request via Jellyseerr, but also providing a way through Discord would be great as well.

Additional context
None at the moment. I tried using Doplarr with Jellyseerr, but it's not working.

@kiranshila
Copy link
Owner

I tried using Doplarr with Jellyseerr, but it's not working.

I wonder how different the API is, if you give doplarr the jellyseerr API key pretending it's overseer, what are the errors?

@Permanently
Copy link

Just tested with Jellyseerr. No issues whatsoever from my end.

Requesting a movie and TV show with Doplarr, hooked to Jellyseerr

Jellyseerr reporting back that it has received the requests from Doplarr

@iuliandita
Copy link

Yup, works just fine with Jellyseer.

image
image

@kiranshila Maybe you can add this info to the README, that it works with both?
Also, changing from OVERSEER__ to just SEER__ for the env vars would be too much, right? Then maybe they all work in parallel, OVERSEER__, JELLYSEER__ or just SEER__ :)

@kiranshila
Copy link
Owner

@kiranshila Maybe you can add this info to the README, that it works with both?

Yep will do!

Also, changing from OVERSEER__ to just SEER__ for the env vars would be too much, right? Then maybe they all work in parallel, OVERSEER__, JELLYSEER__ or just SEER__ :)

Yeah I don't want to make any changes that break people's config, only adding new features. It's easy enough to add those as aliases, maybe just JELLYSEERR__ though?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants