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

[FEAT] Support for Jellyseerr (Emby) #34

Closed
1 task done
sgtcoder opened this issue Dec 29, 2023 · 3 comments
Closed
1 task done

[FEAT] Support for Jellyseerr (Emby) #34

sgtcoder opened this issue Dec 29, 2023 · 3 comments

Comments

@sgtcoder
Copy link

Is this a new feature request?

  • I have searched the existing issues

Wanted change

I read a forum from like 2021 about linuxserver not wanting to support Jellyseerr. I am considering on forking this overseerr project and refactoring it to use jellyseerr.

I wonder if I give access to the forked repository if it's possible to then support Jellyseerr since the skeleton work should be cut out and it literally functions mostly like Overseerr since it's a fork from overseerr.

Reason for change

Linuxserver has the best maintained docker containers and I would like to continue to stay in this ecosystem since Overseerr is already supported and I am simply wanting Emby (Jellyseerr) support.

Proposed code change

I can fork the code, refactor, test, and share the repository with you?

@sgtcoder sgtcoder added the enhancement New feature or request label Dec 29, 2023
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@LinuxServer-CI
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@LinuxServer-CI LinuxServer-CI closed this as not planned Won't fix, can't repro, duplicate, stale Mar 28, 2024
@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Mar 28, 2024
Copy link

This issue is locked due to inactivity

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

2 participants