docs(unraid): improve unraid migration guide

[blassley]

1. Create the config directory

:::note
Seerr is now rootless. Unraid typically runs Docker containers as nobody:users (UID 99, GID 100), but Seerr now runs internally as UID 1000, GID 1000. This creates a permission mismatch. :::

:::info
If migrating: Copy your existing Seerr files to the new folder, then apply the permissions below. :::

Open the Unraid terminal and run:

mkdir -p /mnt/user/appdata/seerr
chown -R 1000:1000 /mnt/user/appdata/seerr

Description

• Fixes Unraid migration documentation #2460

How Has This Been Tested?

Screenshots / Logs (if applicable)

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
  • Added notes for Unraid setup: Seerr runs rootless as UID 1000 / GID 1000 and may need permission adjustments.
  • Added migration guidance to copy existing Jellyseerr/Overseerr appdata into Seerr and set correct permissions.
  • Minor formatting improvements to info/note blocks.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates the Unraid guide to note Seerr now runs rootless as UID:GID 1000:1000, documents the UID/GID mismatch with Unraid’s nobody:users (99:100), adds migration instructions to copy existing Jellyseerr/Overseerr appdata to /mnt/user/appdata/seerr and chown, and adds formatting blocks for notes.

Changes

Cohort / File(s)	Summary
Unraid documentation docs/getting-started/third-parties/unraid.mdx	Added rootless operation note (Seerr runs as UID:GID 1000:1000), migration instructions to copy existing jellyseerr/overseerr appdata into seerr and chown to 1000:1000, and formatted notes with :::note/:::info blocks. Minor directive closure adjustment.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related issues

• Issue #2460: Covers Unraid migration/permissions and UID/GID mismatch; aligns with the documentation additions here.

Possibly related PRs

• PR #2440: Also modifies docs/getting-started/third-parties/unraid.mdx to add migration/permission guidance for Seerr running as 1000:1000.

Suggested reviewers

• M0NsTeRRR
• fallenbagel

Poem

🐰 A rootless hop into the night,
Files moved gently, owners set right,
From ninety-nine to thousand-one,
A tidy trail when work is done —
Chown and hop, the config’s bright. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly summarizes the main change: improving Unraid migration documentation with rootless operation guidance and permission setup instructions.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into develop
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ 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.}

[coderabbitai]

🤖 Fix all issues with AI agents

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


In `@docs/getting-started/third-parties/unraid.mdx`:
- Around line 28-30: Update the sentence that currently reads "Copy your
existing Seerr files to the new folder, then apply the permissions below." to
include example source locations so users know where to copy from; specifically,
mention common migration sources like Overseerr (its appdata directory) and the
previous Seerr config directory as typical locations and show one or two
concrete example source paths for each migration scenario so users can easily
locate their existing files.

🧹 Nitpick comments (1)

🤖 Fix all nitpicks with AI agents

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


In `@docs/getting-started/third-parties/unraid.mdx`:
- Around line 28-30: Update the sentence that currently reads "Copy your
existing Seerr files to the new folder, then apply the permissions below." to
include example source locations so users know where to copy from; specifically,
mention common migration sources like Overseerr (its appdata directory) and the
previous Seerr config directory as typical locations and show one or two
concrete example source paths for each migration scenario so users can easily
locate their existing files.

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

28-30: Consider specifying the typical source location for migrations.

The instruction to "copy your existing Seerr files" assumes users know where their current config is stored. For clarity, consider mentioning a typical source path (e.g., /mnt/user/appdata/overseerr if migrating from Overseerr, or the previous Seerr location).

📝 Suggested improvement

 :::info
-**If migrating**: Copy your existing Seerr files to the new folder, then apply the permissions below.
+**If migrating**: Copy your existing Seerr/Overseerr config files (e.g., from `/mnt/user/appdata/overseerr`) to `/mnt/user/appdata/seerr`, then apply the permissions below.
 :::

🤖 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 28 - 30, Update
the sentence that currently reads "Copy your existing Seerr files to the new
folder, then apply the permissions below." to include example source locations
so users know where to copy from; specifically, mention common migration sources
like Overseerr (its appdata directory) and the previous Seerr config directory
as typical locations and show one or two concrete example source paths for each
migration scenario so users can easily locate their existing files.