ByteSnap/channels-seerr
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: rebrand from Jellyseerr to Seerr across project (#2116)

Browse Source
This commit is contained in:
Gauvain
2025-11-18 22:51:20 +01:00
committed by GitHub
parent f4af6ed5f4
commit af083a3cd5
26 changed files with 51 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/getting-started/buildfromsource.mdx
View File

@@ -24,10 +24,10 @@ import TabItem from '@theme/TabItem';
```bash
sudo mkdir -p /opt/seerr && cd /opt/seerr
```
2. Clone the Seerr repository and checkout the develop branch:
2. Clone the Seerr repository and checkout the main branch:
```bash
git clone https://github.com/fallenbagel/jellyseerr.git
cd jellyseerr
git clone https://github.com/seerr-team/seerr.git
cd seerr
git checkout main
```
3. Install the dependencies:
@@ -199,9 +199,9 @@ pm2 status seerr
mkdir C:\seerr
cd C:\seerr
```
2. Clone the Seerr repository and checkout the develop branch:
2. Clone the Seerr repository and checkout the main branch:
```powershell
git clone https://github.com/fallenbagel/jellyseerr.git .
git clone https://github.com/seerr-team/seerr.git .
git checkout main
```
3. Install the dependencies:

2
docs/getting-started/docker.mdx
View File

@@ -18,7 +18,7 @@ An alternative Docker image is available on Docker Hub for this project. You can
:::info
All official Seerr images are cryptographically signed and include a verified [Software Bill of Materials (SBOM)](https://cyclonedx.org/).
To confirm that the container image you are using is authentic and unmodified, please refer to the [Verifying Signed Artifacts](/using-jellyseerr/advanced/verifying-signed-artifacts#verifying-signed-images) guide.
To confirm that the container image you are using is authentic and unmodified, please refer to the [Verifying Signed Artifacts](/using-seerr/advanced/verifying-signed-artifacts#verifying-signed-images) guide.
:::
## Unix (Linux, macOS)

7
docs/getting-started/kubernetes.mdx
View File

@@ -11,17 +11,16 @@ This method is not recommended for most users. It is intended for advanced users
:::info
All official Seerr charts are cryptographically signed and include a verified [Software Bill of Materials (SBOM)](https://cyclonedx.org/).
To confirm that the chart you are using is authentic and unmodified, please refer to the [Verifying Signed Artifacts](/using-jellyseerr/advanced/verifying-signed-artifacts#verifying-signed-helm-charts) guide.
To confirm that the chart you are using is authentic and unmodified, please refer to the [Verifying Signed Artifacts](/using-seerr/advanced/verifying-signed-artifacts#verifying-signed-helm-charts) guide.
:::
## Installation
```console
helm install seerr oci://ghcr.io/seerr-team/seerr/seerr-chart
```
Helm values can be found in the Seerr repository under [charts/seerr-chart/README.md](https://github.com/fallenbagel/jellyseerr/tree/develop/charts/seerr-chart).
Helm values can be found in the Seerr repository under [charts/seerr-chart/README.md](https://github.com/seerr-team/seerr/tree/develop/charts/seerr-chart).
Verify the signature with [cosign](https://docs.sigstore.dev/cosign/system_config/installation/) (replace [tag], with the TAG you want to verify) :
```console
cosign verify ghcr.io/seerr-team/seerr/seerr-chart:[tag] --certificate-identity=https://github.com/seerr-team/seerr/.github/workflows/helm.yml@refs/heads/main --certificate-oidc-issuer=https://token.ac
tions.githubusercontent.com
cosign verify ghcr.io/seerr-team/seerr/seerr-chart:[tag] --certificate-identity=https://github.com/seerr-team/seerr/.github/workflows/helm.yml@refs/heads/main --certificate-oidc-issuer=https://token.actions.githubusercontent.com
```

0
docs/using-jellyseerr/advanced/index.mdx → docs/using-seerr/advanced/index.mdx
View File

0
docs/using-jellyseerr/advanced/verifying-signed-artifacts.mdx → docs/using-seerr/advanced/verifying-signed-artifacts.mdx
View File

2
docs/using-seerr/notifications/index.mdx
View File

@@ -22,4 +22,4 @@ Users can customize their notification preferences in their own user notificatio
## Requesting New Notification Agents
If we do not currently support your preferred notification agent, feel free to [submit a feature request on GitHub](https://github.com/fallenbagel/jellyseerr/issues). However, please be sure to search first and confirm that there is not already an existing request for the agent!
If we do not currently support your preferred notification agent, feel free to [submit a feature request on GitHub](https://github.com/seerr-team/seerr/issues). However, please be sure to search first and confirm that there is not already an existing request for the agent!

2
docs/using-seerr/notifications/pushover.md
View File

@@ -16,7 +16,7 @@ User notifications are separate from system notifications, and the available not
### Application/API Token
[Register an application](https://pushover.net/apps/build) and enter the API token in this field. (You can use one of the [official icons in our GitHub repository](https://github.com/fallenbagel/jellyseerr/tree/develop/public) when configuring the application.)
[Register an application](https://pushover.net/apps/build) and enter the API token in this field. (You can use one of the [official icons in our GitHub repository](https://github.com/seerr-team/seerr/tree/develop/public) when configuring the application.)
For more details on registering applications or the API token, please see the [Pushover API documentation](https://pushover.net/api#registration).