15cb949f1f
* feat: add Media Server Selection to Setup Page Introduce the ability to select the media server type on the setup page. Users can now choose their preferred media server (e.g., Plex through the Plex sign-in or Emby/Jellyfin sign-in to select either Emby or Jellyfin). The selected media server type is then reflected in the application settings. This enhancement provides users with increased flexibility and customization options during the initial setup process, eliminating the need to rely on environment variables (which cannot be set if using platforms like snaps). Existing Emby users, who use the environment variable, should log out and log back in after updating to set their mediaServerType to Emby. BREAKING CHANGE: This commit deprecates the JELLYFIN_TYPE variable to identify Emby media server and instead rely on the mediaServerType that is set in the `settings.json`. Existing environment variable users can log out and log back in to set the mediaServerType to `3` (Emby). * feat(api): add severType to the api BREAKING CHANGE: This adds a serverType to the `/auth/jellyfin` which requires a serverType to be set (`jellyfin`/`emby`) * refactor: use enums for serverType and rename selectedservice to serverType * refactor(auth): jellyfin/emby authentication to set MediaServerType * fix: issue page formatMessage for 4k media * refactor: cleaner way of handling serverType change using MediaServerType instead of strings instead of using strings now it will use MediaServerType enums for serverType * revert: removed conditional render of the auto-request permission reverts the conditional render toshow the auto-request permission if the mediaServerType was set to Plex as this should be handled in a different PR and Cypress tests should be modified accordingly(currently cypress test would fail if this conditional check is there) * feat: add server type step to setup * feat: migrate existing emby setups to use emby mediaServerType * fix: scan jobs not running when media server type is emby * fix: emby media server type migration * refactor: change emby logo to full logo * style: decrease emby logo size in setup screen * refactor: use title case for servertype i18n message * refactor(i18n): fix a typo * refactor: use enums instead of numbers * fix: remove old references to JELLYFIN_TYPE environment variable * fix: go back to the last step when refresh the setup page * fix: move "scanning in background" tip next to the scanning section * fix: redirect the setup page when Jellyseerr is already setup --------- Co-authored-by: Gauthier <mail@gauthierth.fr>
Jellyseerr is a free and open source software application for managing requests for your media library. It is a fork of Overseerr built to bring support for Jellyfin & Emby media servers!
Current Features
-
Full Jellyfin/Emby/Plex integration including authentication with user import & management
-
Supports Movies, Shows and Mixed Libraries
-
Ability to change email addresses for smtp purposes
-
Easy integration with your existing services. Currently, Jellyseerr supports Sonarr and Radarr. More to come!
-
Jellyfin/Emby/Plex library scan, to keep track of the titles which are already available.
-
Customizable request system, which allows users to request individual seasons or movies in a friendly, easy-to-use interface.
-
Incredibly simple request management UI. Don't dig through the app to simply approve recent requests!
-
Granular permission system.
-
Support for various notification agents.
-
Mobile-friendly design, for when you need to approve requests on the go!
(Upcoming Features include: Multiple Server Instances, and much more!)
With more features on the way! Check out our issue tracker to see the features which have already been requested.
Getting Started
Check out our documentation for instructions on how to install and run Jellyseerr:
https://docs.jellyseerr.dev/getting-started/
Packages:
Archlinux: AUR
Nix: Nixpkg
Snap: Snap(Deprecated)
Preview
Support
- Check out the Jellyseerr Documentation before asking for help. Your question might already be in the docs!
- You can get support on Discord.
- You can ask questions in the Help category of our GitHub Discussions.
- Bug reports and feature requests can be submitted via GitHub Issues.
API Documentation
You can access the API documentation from your local Jellyseerr install at http://localhost:5055/api-docs
Community
You can ask questions, share ideas, and more in GitHub Discussions.
If you would like to chat with other members of our growing community, join the Jellyseerr Discord server!
Our Code of Conduct applies to all Jellyseerr community channels.
Contributing
You can help improve Jellyseerr too! Check out our Contribution Guide to get started.
Contributors ✨
Thanks goes to these wonderful people from Overseerr (emoji key) and all those that contributed directly to Jellyseerr:
