docs: update Unraid install and migration guides with dual permission methods

[mjonkus]

Description

Update the Unraid installation and migration guides to offer two permission methods: Seerr Default (UID 1000) and Unraid Default (UID 99:100), with trade-off disclaimers for each.

• Restructure unraid.mdx with tabbed install instructions and a Template Installation section
• Replace duplicated Docker setup tables in migration-guide.mdx with a link to the install guide
• Add extra parameters guidance (--init, --restart=unless-stopped)
• Remove unused Registry URL field
• Add disclaimers for both methods explaining their trade-offs

This PR was authored with the assistance of Claude Code, under human direction and review throughout.

• Fixes [Docs]: Unraid improve install/migration guide #2460

How Has This Been Tested?

Documentation-only changes — verified MDX syntax and structure manually.

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 (docs only)
• Successful build (docs only)
• Translation keys (docs only)
• Database migration (not required)

Summary by CodeRabbit

• Documentation
  • Restructured Unraid setup into a tabbed UI with two deployment paths: Seerr Default and Unraid Default.
  • Added a Template installation section and renamed Fresh Installation to Manual Installation with an initial method-choice preface.
  • Converted step-by-step install content into tabbed steps with clearer ownership/permission guidance, UID/GID notes, and warnings about init/restart behavior.
  • Simplified migration instructions, deferring detailed container configuration to the Unraid installation guide.

[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

Restructures Unraid install and migration docs into a tabbed Seerr Default vs Unraid Default flow, adds a Template installation section, converts linear steps into tabbed steps, and adds explicit mkdir/chown, UID/GID/rootless guidance and required Docker extra-parameter notes.

Changes

Cohort / File(s)	Summary
Getting-started — Unraid docs docs/getting-started/third-parties/unraid.mdx	Replaced linear Unraid install guide with tabbed UI (Seerr Default / Unraid Default). Added Template installation section, reorganized steps into tabbed step blocks, added mkdir/chown commands, host ownership/UID:GID notes, and emphasized --init --restart (and optional --user 99:100).
Migration guide — Unraid docs/migration-guide.mdx	Simplified migration flow to instruct setting permissions and following the Unraid install guide, collapsed detailed container-creation UI steps, updated step titles/order, and preserved the warning to not delete appdata until verification.

Sequence Diagram(s)

(omitted — changes are documentation restructure without new multi-component control flow)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• docs(unraid): improve unraid migration guide  #2470: Similar Unraid docs updates adding mkdir/chown and UID/GID rootless guidance.
• docs: add Unraid installation and migration guide #2440: Prior edits to the same Unraid docs that overlap with this reorganization.
• docs(truenas): update install/migration guide #2491: Related changes to Unraid migration/install instructions and flow.

Suggested reviewers

• fallenbagel
• 0xSysR3ll
• M0NsTeRRR

Poem

🐇 I hopped through tabs and tidy lines,
Two paths unfolded, clear designs.
I nudged the folders, set the rights,
Guided UIDs through gentle nights.
Seerr on Unraid — cosy bytes and light. ✨

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating Unraid documentation to present dual permission methods (Seerr Default and Unraid Default) with improved installation and migration guidance.
Linked Issues check	✅ Passed	The PR addresses all coding requirements from issue #2460: documents Unraid's user setup (99:100), provides --user 99:100 parameter guidance, includes migration instructions, and offers dual permission methods with trade-off disclaimers.
Out of Scope Changes check	✅ Passed	All changes are scoped to Unraid documentation updates addressing issue #2460; no unrelated modifications to other systems or files are present.

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

---

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

[Copilot]

Pull request overview

This PR updates the Unraid installation and migration documentation to present two supported permissions approaches (Seerr default UID/GID 1000:1000 vs Unraid default 99:100), including trade-off disclaimers and streamlined migration instructions.

Changes:

• Restructures the Unraid install guide into tabbed instructions for “Seerr Default” vs “Unraid Default”, including extra parameters guidance.
• Simplifies the Unraid migration section by linking to the install guide and adding a permissions decision step with tabs.
• Removes/avoids duplicated Docker setup tables in the migration guide in favor of the install guide link.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
docs/migration-guide.mdx	Reworks Unraid migration steps and adds tabbed permission/ownership options.
docs/getting-started/third-parties/unraid.mdx	Adds tabbed manual install paths for the two permission models plus disclaimers and extra-params guidance.

Comments suppressed due to low confidence (1)

docs/getting-started/third-parties/unraid.mdx:23

• “Several templates from Unraid Community are available right now” reads as an incomplete sentence. Consider adding an article and punctuation (e.g., “Several templates from the Unraid community are available:” ) so the following list reads correctly.

Several templates from Unraid Community are available right now
- [Unraid Community Apps](https://unraid.net/community/apps#community-apps-iframe)

---

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

[fallenbagel]

Just two small changes and this should be good to merge

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/migration-guide.mdx`:
- Around line 263-267: The current cp command copies the overseerr directory
into seerr and will create a nested /mnt/user/appdata/seerr/overseerr if the
destination exists; update the command that currently uses "cp -a
/mnt/user/appdata/overseerr /mnt/user/appdata/seerr" to copy the contents of the
overseerr folder into the existing seerr folder (e.g., use a trailing slash on
the source or otherwise copy the directory contents) so the files land directly
under /mnt/user/appdata/seerr and preserve the intended /app/config mapping.

[M0NsTeRRR]

I’ve posted some comments let me know what you think. When I add a command for one install method, it often applies to the other installation methods as well, so be sure to update both.
I’ll try running the documentation later to check how it looks! :)

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

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

22-23: Minor grammar refinement.

"are available right now" reads casually; consider tightening for technical documentation.

✏️ Suggested rewording

-Several templates from Unraid Community are available right now
+Several templates are available from Unraid Community Apps:
 - [Unraid Community Apps](https://unraid.net/community/apps#community-apps-iframe)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/getting-started/third-parties/unraid.mdx` around lines 22 - 23, The
sentence "Several templates from Unraid Community are available right now" is
too casual; replace it with a tighter, more technical phrasing such as "Several
templates from the Unraid Community are available" or "Several Unraid Community
templates are available" in the docs/getting-started/third-parties/unraid.mdx
content (look for the exact sentence and the Unraid Community Apps link) so the
wording is concise and formal.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/getting-started/third-parties/unraid.mdx`:
- Around line 122-136: The note text contradicts the following instructions: the
note says "Keep current host ownership" and "avoids changing host permissions"
while the command `chown -R 99:100 /mnt/user/appdata/seerr` immediately changes
ownership; update the documentation to be consistent by either (A) rewording the
note to state that we recommend setting the config folder to Unraid's standard
nobody:users (UID 99, GID 100) so the subsequent `chown -R 99:100
/mnt/user/appdata/seerr` makes the ownership explicit, or (B) remove/replace the
`chown` command if the intent is truly to preserve existing ownership; ensure
the note/reference to Unraid UID/GID and the `mkdir`/`chown` instructions (the
`chown -R 99:100 ...` line) clearly reflect the chosen approach.

---

Nitpick comments:
In `@docs/getting-started/third-parties/unraid.mdx`:
- Around line 22-23: The sentence "Several templates from Unraid Community are
available right now" is too casual; replace it with a tighter, more technical
phrasing such as "Several templates from the Unraid Community are available" or
"Several Unraid Community templates are available" in the
docs/getting-started/third-parties/unraid.mdx content (look for the exact
sentence and the Unraid Community Apps link) so the wording is concise and
formal.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

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

124-128: Consider clarifying "without changing host folder ownership" phrasing.

Line 125 states --user 99:100 "avoids permission errors accessing your shares without changing host folder ownership," but step 2 explicitly changes ownership of the config directory via chown -R 99:100. The intent appears to be that users don't need to change ownership of other shares (media libraries, etc.), but the current phrasing could confuse readers.

Suggested clarification

-  The `--user 99:100` parameter runs the container process with Unraid's default UID/GID and avoids permission errors accessing your shares without changing host folder ownership.
+  The `--user 99:100` parameter runs the container process with Unraid's default UID/GID, allowing access to your existing shares without needing to change their ownership.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/getting-started/third-parties/unraid.mdx` around lines 124 - 128,
Clarify the sentence about `--user 99:100` to remove ambiguity: update the
phrasing around `--user 99:100` so it explicitly notes that the guide does
instruct changing ownership of the container's config directory via `chown -R
99:100` earlier, but `--user 99:100` prevents needing to change ownership on
other host shares (e.g., media libraries); mention both the earlier `chown -R
99:100` action and that `--user 99:100` is intended to avoid altering ownership
of other host folders to prevent reader confusion.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/migration-guide.mdx`:
- Around line 273-274: Update the "**3. Set permissions and install Seerr**"
paragraph to explicitly tell migration users which permission tab to use in the
referenced Unraid Installation Guide: recommend following the "Unraid Default"
tab (UID 99:100) rather than "Seerr Default" (UID 1000) because existing
Overseerr/Jellyseerr appdata on Unraid is typically owned by 99:100; keep the
instruction to "start from step 2" and briefly note the UID guidance so readers
know which tab to pick when following the linked guide.

---

Duplicate comments:
In `@docs/migration-guide.mdx`:
- Around line 265-269: The cp example under the "**2. Copy existing data to
Seerr appdata**" step will create a nested overseerr/ folder when the
destination exists; update the command shown (`cp -a /mnt/user/appdata/overseerr
/mnt/user/appdata/seerr`) to use the trailing-dot form so it copies the contents
into the target directory (i.e., replace the shown command with the equivalent
that uses the source directory's trailing dot to avoid creating an extra
overseerr subdirectory).

---

Nitpick comments:
In `@docs/getting-started/third-parties/unraid.mdx`:
- Around line 124-128: Clarify the sentence about `--user 99:100` to remove
ambiguity: update the phrasing around `--user 99:100` so it explicitly notes
that the guide does instruct changing ownership of the container's config
directory via `chown -R 99:100` earlier, but `--user 99:100` prevents needing to
change ownership on other host shares (e.g., media libraries); mention both the
earlier `chown -R 99:100` action and that `--user 99:100` is intended to avoid
altering ownership of other host folders to prevent reader confusion.

[coderabbitai]

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@docs/migration-guide.mdx`:
- Around line 265-269: Replace the existing example copy command that copies the
entire overseerr directory into seerr (the line containing "cp -a
/mnt/user/appdata/overseerr /mnt/user/appdata/seerr") with a content-copy
variant so files land directly in /mnt/user/appdata/seerr instead of creating a
nested /mnt/user/appdata/seerr/overseerr; update the docs to recommend using a
content-copy form (or rsync equivalent) that targets the contents of
/mnt/user/appdata/overseerr into /mnt/user/appdata/seerr and mention why (to
avoid nesting when the destination already exists).

[M0NsTeRRR]

Otherwise, lgtm good work !

[M0NsTeRRR]

Thanks for your contribution !