feat: Overseerr to Jellyseerr migration (#2019)

* feat: add Overseerr migration

* refactor: rename to Seerr

* refactor: more rename to Seerr

* feat: update the value of the MediaStatus.DELETED enum

* fix: add more details in migration logs

* fix: replace .update by .save for TypeORM hooks

* fix: add fake migration to skip the duplicated UpdateWebPush migration

* fix: rewrite the AddUserAvatarCacheFields migration for Overseerr merge

* fix: replace jellyseerr migrations with a dedicated one for overseerr

* fix: update overseerr migration

* fix: update overseerr migration

* fix: remove irrelevant changes

* fix: typos

* docs: update jsdoc comment

* docs: update seerr description

* docs: fix the contributing.md link

* fix: remove unwanterd change on postgres dev datasource

* docs: add latest tag to docker image

* fix: migrate old deleted status for 4k media

* fix: update Seerr version check

Author: gauthier-th

CONTRIBUTING.md

@@ -115,7 +115,7 @@ Steps:
 
 1. Make the necessary changes.
 2. Test your changes.
-3. Update the `version` in `charts/jellyseerr-chart/Chart.yaml` following [Semantic Versioning (SemVer)](https://semver.org/).
+3. Update the `version` in `charts/seerr-chart/Chart.yaml` following [Semantic Versioning (SemVer)](https://semver.org/).
 4. Run the `helm-docs` command to regenerate the chart's README.
 
 ### Contributing Code
@@ -162,16 +162,16 @@ If you are adding a new feature that requires a database migration, you will nee
 1. Create a PostgreSQL database or use an existing one:
 
 ```bash
-sudo docker run --name postgres-jellyseerr -e POSTGRES_PASSWORD=postgres -d -p 127.0.0.1:5432:5432/tcp postgres:latest
+sudo docker run --name postgres-seerr -e POSTGRES_PASSWORD=postgres -d -p 127.0.0.1:5432:5432/tcp postgres:latest
 ```
 
 2. Reset the SQLite database and the PostgreSQL database:
 
 ```bash
 rm config/db/db.*
 rm config/settings.*
-PGPASSWORD=postgres sudo docker exec -it postgres-jellyseerr /usr/bin/psql -h 127.0.0.1 -U postgres -c "DROP DATABASE IF EXISTS jellyseerr;"
-PGPASSWORD=postgres sudo docker exec -it postgres-jellyseerr /usr/bin/psql -h 127.0.0.1 -U postgres -c "CREATE DATABASE jellyseerr;"
+PGPASSWORD=postgres sudo docker exec -it postgres-seerr /usr/bin/psql -h 127.0.0.1 -U postgres -c "DROP DATABASE IF EXISTS seerr;"
+PGPASSWORD=postgres sudo docker exec -it postgres-seerr /usr/bin/psql -h 127.0.0.1 -U postgres -c "CREATE DATABASE seerr;"
 ```
 
 3. Checkout the `develop` branch and create the original database for SQLite and PostgreSQL so that TypeORM can automatically generate the migrations:

charts/seerr-chart/README.md

@@ -55,7 +55,7 @@ If `replicaCount` value was used - remove it. Helm update should work fine after
 | fullnameOverride | string | `""` |  |
 | image.pullPolicy | string | `"IfNotPresent"` |  |
 | image.registry | string | `"ghcr.io"` |  |
-| image.repository | string | `"fallenbagel/jellyseerr"` |  |
+| image.repository | string | `"seerr-team/seerr"` |  |
 | image.sha | string | `""` |  |
 | image.tag | string | `""` | Overrides the image tag whose default is the chart appVersion. |
 | imagePullSecrets | list | `[]` |  |

charts/seerr-chart/values.yaml

@@ -1,6 +1,6 @@
 image:
   registry: ghcr.io
-  repository: fallenbagel/jellyseerr
+  repository: seerr-team/seerr
   pullPolicy: IfNotPresent
   # -- Overrides the image tag whose default is the chart appVersion.
   tag: ''

compose.postgres.yaml

@@ -1,5 +1,5 @@
 services:
-  jellyseerr:
+  seerr:
     build:
       context: .
       dockerfile: Dockerfile.local
@@ -9,9 +9,9 @@ services:
       DB_TYPE: 'postgres' # Which DB engine to use. The default is "sqlite". To use postgres, this needs to be set to "postgres"
       DB_HOST: 'postgres' # The host (url) of the database
       DB_PORT: '5432' # The port to connect to
-      DB_USER: 'jellyseerr' # Username used to connect to the database
-      DB_PASS: 'jellyseerr' # Password of the user used to connect to the database
-      DB_NAME: 'jellyseerr' # The name of the database to connect to
+      DB_USER: 'seerr' # Username used to connect to the database
+      DB_PASS: 'seerr' # Password of the user used to connect to the database
+      DB_NAME: 'seerr' # The name of the database to connect to
       DB_LOG_QUERIES: 'false' # Whether to log the DB queries for debugging
       DB_USE_SSL: 'false' # Whether to enable ssl for database connection
     volumes:
@@ -25,9 +25,9 @@ services:
   postgres:
     image: postgres:18
     environment:
-      POSTGRES_USER: jellyseerr
-      POSTGRES_PASSWORD: jellyseerr
-      POSTGRES_DB: jellyseerr
+      POSTGRES_USER: seerr
+      POSTGRES_PASSWORD: seerr
+      POSTGRES_DB: seerr
     ports:
       - '5432:5432'
     volumes:

compose.yaml

@@ -1,5 +1,5 @@
 services:
-  jellyseerr:
+  seerr:
     build:
       context: .
       dockerfile: Dockerfile.local

docs/README.md

@@ -5,9 +5,9 @@ sidebar_position: 1
 
 # Introduction
 
-Welcome to the Jellyseerr Documentation.
+Welcome to the Seerr Documentation.
 
-**Jellyseerr** is a free and open source software application for managing requests for your media library. It integrates with the media server of your choice: [Jellyfin](https://jellyfin.org), [Plex](https://plex.tv), and [Emby](https://emby.media/). In addition, it integrates with your existing services, such as **[Sonarr](https://sonarr.tv/)**, **[Radarr](https://radarr.video/)**.
+**Seerr** is a free and open source software application for managing requests for your media library. It integrates with the media server of your choice: [Jellyfin](https://jellyfin.org), [Plex](https://plex.tv), and [Emby](https://emby.media/). In addition, it integrates with your existing services, such as **[Sonarr](https://sonarr.tv/)**, **[Radarr](https://radarr.video/)**.
 
 ## Features
 
@@ -26,16 +26,10 @@ Welcome to the Jellyseerr Documentation.
 - Easily **Watchlist** or **Blacklist** media.
 - More features to come!
 
-## Motivation
-
-The primary motivation for starting Jellyseerr was to bring Jellyfin and Emby support to Overseerr. However, over time, **Jellyseerr** has evolved into its own distinct application with unique features. Designed as a one-stop shop for media requests, it offers a simple, easy-to-use experience for managing requests on Jellyfin, Emby, and Plex servers.
-
 ## 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.
-
-We value your feedback and support in identifying and fixing bugs to make Jellyseerr even better. As an open-source project, we welcome contributions from everyone. While Jellyseerr has diverged from Overseerr and evolved into its own unique application, we still encourage contributions to Overseerr, as it played a crucial role in inspiring what Jellyseerr has become today.
+[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. 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 Plex, Jellyfin and Emby users.
 
-Contribution includes building new features, patching bugs, translating the application, or even just writing documentation.
+We value your feedback and support in identifying and fixing bugs to make Seerr even better. As an open-source project, we welcome contributions from everyone. Contribution includes building new features, patching bugs, translating the application, or even just writing documentation.
 
-If you would like to contribute, please be sure to review our [contribution guidelines](https://github.com/fallenbagel/jellyseerr/blob/develop/CONTRIBUTING.md).
+If you would like to contribute, please be sure to review our [contribution guidelines](https://github.com/seerr-team/seerr/blob/develop/CONTRIBUTING.md).

docs/extending-jellyseerr/_category_.json

@@ -0,0 +1,9 @@
+{
+  "label": "Extending Seerr",
+  "position": 3,
+  "link": {
+    "type": "generated-index",
+    "title": "Extending Seerr",
+    "description": "Extend Seerr to your liking"
+  }
+}

docs/extending-seerr/_category_.json

@@ -1,11 +1,11 @@
 ---
 title: Configuring the Database (Advanced)
-description: Configure the database for Jellyseerr
+description: Configure the database for Seerr
 sidebar_position: 2
 ---
 # Configuring the Database
 
-Jellyseerr supports SQLite and PostgreSQL. The database connection can be configured using the following environment variables:
+Seerr supports SQLite and PostgreSQL. The database connection can be configured using the following environment variables:
 
 ## SQLite Options
 
@@ -34,7 +34,7 @@ DB_HOST="localhost" # (optional) The host (URL) of the database. The default is
 DB_PORT="5432" # (optional) The port to connect to. The default is "5432".
 DB_USER= # (required) Username used to connect to the database.
 DB_PASS= # (required) Password of the user used to connect to the database.
-DB_NAME="jellyseerr" # (optional) The name of the database to connect to. The default is "jellyseerr".
+DB_NAME="seerr" # (optional) The name of the database to connect to. The default is "seerr".
 DB_LOG_QUERIES="false" # (optional) Whether to log the DB queries for debugging. The default is "false".
 ```
 
@@ -47,7 +47,7 @@ DB_TYPE=postgres # Which DB engine to use, either sqlite or postgres. The defaul
 DB_SOCKET_PATH="/var/run/postgresql" # (required) The path to the PostgreSQL Unix socket directory.
 DB_USER= # (required) Username used to connect to the database.
 DB_PASS= # (optional) Password of the user used to connect to the database, depending on the server's authentication configuration.
-DB_NAME="jellyseerr" # (optional) The name of the database to connect to. The default is "jellyseerr".
+DB_NAME="seerr" # (optional) The name of the database to connect to. The default is "seerr".
 DB_LOG_QUERIES="false" # (optional) Whether to log the DB queries for debugging. The default is "false".
 ```
 
@@ -91,9 +91,9 @@ DB_SSL_CERT_FILE= # (optional) Path to certificate chain in pem format for the p
 
 ### Migrating from SQLite to PostgreSQL
 
-1. Set up your PostgreSQL database and configure Jellyseerr to use it
-2. Run Jellyseerr to create the tables in the PostgreSQL database
-3. Stop Jellyseerr
+1. Set up your PostgreSQL database and configure Seerr to use it
+2. Run Seerr to create the tables in the PostgreSQL database
+3. Stop Seerr
 4. Run the following command to export the data from the SQLite database and import it into the PostgreSQL database:
 
 :::info
@@ -112,7 +112,7 @@ import TabItem from '@theme/TabItem';
 <Tabs>
 <TabItem value="docker" label="Using pgloader Container (Recommended)" default>
 
-**Recommended method**: Use the pgloader container even for standalone Jellyseerr installations. This avoids building from source and ensures compatibility.
+**Recommended method**: Use the pgloader container even for standalone Seerr installations. This avoids building from source and ensures compatibility.
 
 ```bash
 # For standalone installations (no Docker network needed)
@@ -126,7 +126,7 @@ docker run --rm \
 **For Docker Compose setups**: Add the network parameter if your PostgreSQL is also in a container:
 ```bash
 docker run --rm \
-  --network your-jellyseerr-network \
+  --network your-seerr-network \
   -v /path/to/your/config/db.sqlite3:/db.sqlite3:ro \
   ghcr.io/ralgar/pgloader:pr-1531 \
   pgloader --with "quote identifiers" --with "data only" \
@@ -167,4 +167,4 @@ Once pgloader is built, run the migration:
 </TabItem>
 </Tabs>
 
-5. Start Jellyseerr
+5. Start Seerr