docs: add Unraid installation and migration guide

[mjonkus]

Description

Adds community documentation for installing Seerr on Unraid, replacing the
"awaiting community contribution" placeholder on the Unraid docs page.

Covers:

• Fresh installation via Unraid Docker UI (manual container setup)
• Migration from Overseerr/Jellyseerr (permissions fix, config path mapping)
• Reverse proxy notes for SWAG/Nginx users
• Update instructions

This was tested by successfully migrating a live Overseerr instance to Seerr
on Unraid following these exact steps.

AI Disclosure: This documentation was drafted with assistance from Claude Opus 4.6 (Anthropic), then verified against a real Overseerr-to-Seerr migration on Unraid.

How Has This Been Tested?

Tested on a live Unraid server by migrating from Overseerr (linuxserver image)
to Seerr. Verified automatic database migration, permissions fix (chown to UID 1000),
container startup, and reverse proxy (SWAG) connectivity.

Screenshots / Logs (if applicable)

N/A - documentation only

Checklist:

• I have read and followed the contribution guidelines.
• Disclosed any use of AI (see our policy)
• I have updated the documentation accordingly.
• All new and existing tests passed.
• Successful build pnpm build
• Translation keys pnpm i18n:extract
• Database migration (if required)

Summary by CodeRabbit

• Documentation
  • Replaced deprecated placeholder installer notes with a manual Unraid installation flow.
  • Added a full fresh-install guide: config setup, container creation with explicit field guidance, ports/paths and environment variable mappings, and access verification.
  • Highlighted use of the --init flag for proper shutdown handling.
  • Added a Unraid migration guide covering backup, old container removal, permissions fix, recreate steps, and a reverse-proxy tip.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Replaces the Unraid placeholder/internal installer docs with a manual Fresh Installation guide and a detailed Unraid migration procedure, adding explicit Docker container fields, port/volume/env mappings, backup and permission-fix steps, and an emphasized --init recommendation.

Changes

Cohort / File(s)	Summary
Unraid install doc docs/getting-started/third-parties/unraid.mdx	Full rewrite: removed deprecated/placeholder installer steps and commented installer flow; added manual Fresh Installation workflow with config directory creation, explicit Docker container fields (Name, Repository, Registry URL, Icon URL, WebUI, Extra Parameters including --init, Network Type, Privileged), port/path mappings, and TZ/LOG_LEVEL env vars; retained --init note and updated start/access instructions.
Migration guide (Unraid) docs/migration-guide.mdx	Added a detailed Unraid migration procedure: stop/remove old container, backup appdata, fix permissions, recreate container with explicit settings and mappings, apply/start, and a reverse-proxy tip; replaces prior single-line Unraid note.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• docs: fix migration guide title #2425 — edits to docs/migration-guide.mdx that adjust headings/section structure and overlap with this PR's migration content.

Suggested reviewers

• fallenbagel
• gauthier-th

Poem

🐇 I hopped through docs with carrot in paw,
Wrote steps for installs, backups, and more,
Containers tidy, permissions bright,
Click the WebUI, everything's right —
Hooray for clean starts and migrations galore!

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Merge Conflict Detection	⚠️ Warning	⚠️ Unable to check for merge conflicts: Failed to fetch base branch: fatal: cannot change to '/home/jailuser/git': No such file or directory

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changeset, which adds comprehensive Unraid installation and migration guides to the documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

⚔️ Resolve merge conflicts (beta)

• Auto-commit resolved conflicts to branch docs/unraid-installation-guide
• Post resolved changes as copyable diffs in a comment

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

docs/migration-guide.mdx (1)

243-243: Consider adding a brief note explaining the --init requirement.

Users navigating directly to the Unraid section may not see the explanation at line 49. A short inline note (or an admonition after step 5) would help clarify why --init is required—proper signal handling and clean container shutdowns.

📝 Suggested addition after line 276

 5. Click **Apply** to start the container. Check the container logs to confirm the automatic migration completed successfully.
+
+:::note
+The `--init` flag is required because Seerr no longer provides a built-in init process. This ensures proper signal handling and clean container shutdowns.
+:::

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@docs/getting-started/third-parties/unraid.mdx`:
- Around line 73-84: Replace the unsafe backup example that uses "cp -r
/mnt/user/appdata/overseerr /mnt/user/appdata/overseerr-backup" with a command
that preserves ownership and permissions (e.g., "cp -a
/mnt/user/appdata/overseerr /mnt/user/appdata/overseerr-backup" or an equivalent
"rsync -a" or "tar" approach); update the code block in the documentation to
show the safer command so appdata ownership/permissions are preserved during
backups.
- Around line 21-63: Add a brief clarification to the "Add the Docker container"
section explaining that the "Registry URL" field is optional in Unraid and does
not affect image pulling (the Repository field controls that); update the
paragraph/table around the Registry URL entry to include a short parenthetical
note like "(optional — image pull is controlled by Repository)" and ensure the
wording references the "Registry URL" field so readers encountering the field
won't be confused.

🧹 Nitpick comments (1)

docs/getting-started/third-parties/unraid.mdx (1)

4-8: Soften the time‑sensitive “no official template yet” claim.

This can become outdated quickly; consider conditional wording and confirm current CA availability.

💡 Suggested wording tweak

-Since there is no official Unraid Community Applications template for Seerr yet, you can install Seerr manually using Unraid's Docker UI.
+If an official Unraid Community Applications template for Seerr isn't available in your catalog, you can install Seerr manually using Unraid's Docker UI.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@docs/migration-guide.mdx`:
- Around line 219-225: Swap the order of the two migration steps so the
container is stopped/removed before taking the appdata backup (or explicitly
instruct to stop the container first), i.e. ensure the step that tells the user
to click the container icon and choose "Stop" then "Remove" (the Unraid Docker
container stop/remove action) comes before creating the backup of
/mnt/user/appdata/overseerr to /mnt/user/appdata/overseerr-backup so the cp -a
copy is taken with the container stopped to avoid an inconsistent SQLite
snapshot.

[M0NsTeRRR]

Otherwise LGTM :)

[M0NsTeRRR]

LGTM, thanks for your contribution !

[mjonkus]

LGTM, thanks for your contribution !

No problem. Thanks a lot for your patience :)

[Copilot]

Pull request overview

This PR adds comprehensive community-maintained documentation for installing and migrating Seerr on Unraid, replacing the previous placeholder that indicated the method was awaiting community contribution. The documentation provides step-by-step instructions for manual Docker container setup on Unraid systems.

Changes:

• Removed "Unraid app: Not maintained" notice from migration guide
• Added fresh installation guide with config directory setup, Docker container configuration, and detailed field-by-field instructions for Unraid's Docker UI
• Added migration guide from Overseerr/Jellyseerr with backup steps, permissions fixes, and reverse proxy configuration notes

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
docs/migration-guide.mdx	Removed deprecated notice; added comprehensive Unraid migration section with backup, permissions, and container setup instructions
docs/getting-started/third-parties/unraid.mdx	Replaced placeholder with complete fresh installation guide including directory setup, container configuration, and init flag explanation

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.