feat: Overseerr to Jellyseerr migration #2019
Conversation
There was a problem hiding this comment.
Noticed some places where there were typos.
Also one thing I'm concerned with is, with this merge, the docs will reference images that are currently not out there yet. Maybe we should add a temporary thing until then? We could add tabs in the installation docs for jellyseerr and overseerr and seerr. We can remove the first two tabs once the merge is fully completed
Wdyt? @sct @gauthier-th
docs/README.md
Outdated
|
|
||
| ## We need your help! | ||
|
|
||
| [Jellyseerr](https://github.com/fallenbagel/jellyseerr) is an ambitious project where developers/contributors poured a lot of work into, and that builds on top of [Overseerr](https://github.com/sct/overseerr). And we have a lot more to do as well. |
There was a problem hiding this comment.
This needs to be reworked. We can say that seerr is the merge if these two projects etc
There was a problem hiding this comment.
| [Jellyseerr](https://github.com/fallenbagel/jellyseerr) is an ambitious project where developers/contributors poured a lot of work into, and that builds on top of [Overseerr](https://github.com/sct/overseerr). And we have a lot more to do as well. | |
| [Seerr](https://github.com/seerr-team/seerr) is an ambitious project developers/contributors poured a lot of work into, and we still have a lot more to do. |
There was a problem hiding this comment.
I previously reworked it like this:
Seerr is an ambitious project where developers/contributors poured a lot of work into, and we have a lot more to do as well. Seerr is the result of a collaborative effort between the original Overseerr project and the Jellyseerr fork, created to deliver an excellent request management solution for both Plex and Jellyfin users.
WDYT?
There was a problem hiding this comment.
Jellyin and emby users*
There was a problem hiding this comment.
@gauthier-th LGTM! Could you apply my edits to the first sentence though? The grammar is a bit odd in the original.
Yes that’s why I proposed releasing the 2.7.3 image (in seerr-team/seerr) on the same commit as Jellyseerr, so everything can be updated prior to the next (first) release without breaking anything for existing jellyseerr users. |
2.7.3 won't work though as it wont have the overseerr migration |
Would disabling the CI to publish the docs be a solution for now, until the merge is completed? |
That would work too |
No issue for me this image isn’t meant to handle the migration. The 3.0.0 release could be the first to do so. Currently, there’s no information confirming that the Seerr image is compatible with Overseerr, except for the preview-seerr tag from Jellyseerr. |
That reminds me @gauthier-th we should merge this pr as a "breaking change" commit with that added. This would allow semantic version bot to release next version as 3.0.0 |
@sudo-kraken and me gonna rework the release part. As we use convetionnal commit you just need to commit with a |
There was a problem hiding this comment.
Pull Request Overview
This pull request implements the migration from Overseerr to Seerr (the unification of Overseerr and Jellyseerr), including database migration logic and extensive rebranding throughout the codebase.
- Implements database migration logic to convert Overseerr instances to Seerr
- Replaces "Jellyseerr" references with "Seerr" throughout documentation and configuration
- Updates default database names, log file paths, and application titles
Reviewed Changes
Copilot reviewed 54 out of 60 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| server/lib/overseerrMerge.ts | Complete migration script for Overseerr to Seerr conversion |
| server/index.ts | Integrates migration check into application startup |
| server/logger.ts | Updates log file naming from jellyseerr to seerr |
| server/datasource.ts | Updates default PostgreSQL database name |
| docs/* | Comprehensive documentation updates from Jellyseerr to Seerr |
| compose.yaml | Updates service and database names |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Description
This PR includes the migration script to convert an Overseerr instance into a Jellyseerr one.
The database migration is included in the
server/lib/overseerrMerge.tsfile, and has been generated using TypeORM. This migration will always be run after theUpdateWebPush1745492372230migration, so that Overseerr users migrating much later doesn't run a new Seerr migration before the Overseerr->Seerr migration.It also includes some renames of Jellyseerr -> Seerr I wrote when creating the first version of the migration.
This is what have been used by beta-testers to migrate their Overseerr instance.
To-Dos
pnpm buildpnpm i18n:extract