docs(docker): replace backslashes by backticks in windows docker run commands [skip-ci]

[0xSysR3ll]

Description

This fixes the docker run commands for Windows in the documentation. PowerShell does not support backslashes (\) for line continuation; instead, it requires backticks (`).
Same thing has been done for batch (CMD) commands. \ have been replaced with ^.
Additionally, also fixed the wrong use of bat instead of batch for correct syntax highlighting.

• Fixes #XXXX

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
  • Split Windows Docker examples into separate "Docker CLI (PowerShell)" and "Docker CLI (CMD)" tabs; moved and expanded update/stop/remove/pull/re-run steps into each tab
  • Added Docker config ownership command to migration guide
  • Improved spacing and wording in migration and Unraid installation steps
  • Updated Windows Task Scheduler examples to use batch fencing and run the built app
  • Added 'batch' to syntax highlighting languages

[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

Windows Docker CLI examples were split into PowerShell and CMD variants with their respective line-continuation syntax; a chown ownership-correction snippet and minor spacing/Unraid phrasing edits were added to migration docs. The Windows Task Scheduler example fence language changed and now runs node dist/index.js. No runtime behavior changed. (50 words)

Changes

Cohort / File(s)	Summary
Getting-started: Docker CLI tabs docs/getting-started/docker.mdx	Replaced single Windows Docker CLI block with two tabs: Docker CLI (PowerShell) using backtick continuations and Docker CLI (CMD) using caret continuations; updated update/stop/remove steps per tab; Docker Compose tab unchanged.
Migration guide: Windows CLI & permissions docs/migration-guide.mdx	Added chown snippet to set config ownership during migration; split Windows Docker CLI examples into PowerShell and CMD variants; minor spacing/formatting and Unraid "Remove the old app" wording changes.
Build-from-source: Task Scheduler & start command docs/getting-started/buildfromsource.mdx	Changed Task Scheduler code fence language from bat to batch; added node dist/index.js to the start command in the example.
Docs config: syntax highlighting gen-docs/docusaurus.config.ts	Expanded Prism additionalLanguages array to include 'batch' for syntax highlighting.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

• fallenbagel
• M0NsTeRRR

Poem

🐰 I hopped through docs with nimble paws,
Split PowerShell and CMD in tidy laws,
Backticks and carets now dance in line,
A tiny chown hop — permissions align,
Off to nibble carrots and watch builds shine ✨

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 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 primary change: replacing backslashes with backticks in Windows Docker run commands documentation. It directly corresponds to the main focus of the changeset across multiple documentation files.

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

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

docs/getting-started/docker.mdx (1)

195-203: ⚠️ Potential issue | 🟡 Minor

Inconsistent update instructions for Docker CLI tab.

The "Updating" section under the Docker CLI tab shows docker compose commands, but this tab is for users who installed via docker run. The update instructions should match the Unix Docker CLI pattern (stop container, remove it, pull latest image, then re-run with docker run).

Compare with the Unix Docker CLI updating section (lines 76-89) which correctly uses docker stop, docker rm, docker pull, and docker run.

📝 Suggested fix

 #### Updating:
-Pull the latest image:
-```bash
-docker compose pull seerr
-```
-Then, restart all services defined in the Compose file:
-```bash
-docker compose up -d
-```
+Stop and remove the existing container:
+```powershell
+docker stop seerr; docker rm seerr
+```
+Pull the latest image:
+```powershell
+docker pull ghcr.io/seerr-team/seerr:latest
+```
+Finally, run the container with the same parameters originally used to create the container:
+```powershell
+docker run -d ...
+```

🤖 Prompt for AI Agents

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

In `@docs/getting-started/docker.mdx` around lines 195 - 203, The Docker CLI tab's
"Updating" section currently shows docker compose commands but should present
the Unix Docker CLI flow for the docker run installation; update the "Updating"
subsection in the Docker CLI tab to replace the docker compose commands with the
stop/remove -> pull -> run sequence (stop and remove the existing seerr
container, docker pull the ghcr.io/seerr-team/seerr:latest image, then re-run
the container with the original docker run parameters) so it mirrors the Unix
Docker CLI pattern used earlier.

🤖 Prompt for all review comments with AI agents

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

Outside diff comments:
In `@docs/getting-started/docker.mdx`:
- Around line 195-203: The Docker CLI tab's "Updating" section currently shows
docker compose commands but should present the Unix Docker CLI flow for the
docker run installation; update the "Updating" subsection in the Docker CLI tab
to replace the docker compose commands with the stop/remove -> pull -> run
sequence (stop and remove the existing seerr container, docker pull the
ghcr.io/seerr-team/seerr:latest image, then re-run the container with the
original docker run parameters) so it mirrors the Unix Docker CLI pattern used
earlier.

[Copilot]

Pull request overview

This PR updates the Windows Docker CLI examples in the documentation to use PowerShell-correct line continuation (backticks) instead of Unix-style backslashes, preventing copy/paste failures for Windows users.

Changes:

• Replace \ line continuations with PowerShell backticks (`) in Windows docker run examples.
• Add short guidance notes in Windows sections explaining the correct PowerShell continuation syntax.
• Minor formatting tweaks (blank lines) to improve readability around code blocks.

Reviewed changes

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

File	Description
docs/migration-guide.mdx	Updates Windows Docker CLI snippet to PowerShell backticks and adds a brief PowerShell note; small formatting spacing adjustments.
docs/getting-started/docker.mdx	Updates the Windows Docker CLI installation command to a PowerShell multi-line example using backticks and adds PowerShell guidance text.

---

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

[Copilot]

Pull request overview

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

---

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

[coderabbitai]

Actionable comments posted: 2

🤖 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`:
- Line 142: The CMD code block uses the Prism language id 'bat' but the
Docusaurus Prism config's additionalLanguages array (additionalLanguages) does
not include 'batch', so add 'batch' to the additionalLanguages array in the
Docusaurus config (e.g., where additionalLanguages:
['bash','powershell','yaml','nix','nginx', ...] is defined) so that 'bat' code
blocks render with syntax highlighting; ensure the array becomes
...,'nginx','batch'....
- Line 157: Replace the Prism language identifier `bat` with `batch` in code
fences (e.g., change the triple-backtick specifiers in docs/migration-guide.mdx
and also update docs/getting-started/docker.mdx and
docs/getting-started/buildfromsource.mdx) and then register the language by
adding "batch" to the additionalLanguages array in gen-docs/docusaurus.config.ts
(update the value used by Prism loader such as the additionalLanguages export or
plugins config so Prism includes prism-batch).

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9255be5 and e82fa89.

📒 Files selected for processing (2)

• docs/getting-started/docker.mdx
• docs/migration-guide.mdx

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/getting-started/docker.mdx

[0xSysR3ll]

Commit as-is and replace all bat occurrences to batch + add batch highlighting support to docusaurus in another PR ? Or do it now ? IMO it's just cosmetic.

[M0NsTeRRR]

Commit as-is and replace all bat occurrences to batch + add batch highlighting support to docusaurus in another PR ? Or do it now ? IMO it's just cosmetic.

For me you can do it now if you are lazy ahah

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

docs/getting-started/docker.mdx (1)

192-200: ⚠️ Potential issue | 🟡 Minor

Wrong updating commands in the "Docker CLI (PowerShell)" tab — these are Docker Compose commands.

Lines 194–200 show docker compose pull seerr / docker compose up -d with the text "restart all services defined in the Compose file," which is copy-pasted from the Docker Compose tab. This tab is for Docker CLI users who don't have a compose.yaml; the equivalent updating flow should mirror what the Unix Docker CLI tab does.

📝 Suggested fix

 #### Updating:
-Pull the latest image:
-```bash
-docker compose pull seerr
-```
-Then, restart all services defined in the Compose file:
-```bash
-docker compose up -d
-```
+Stop and remove the existing container:
+```powershell
+docker stop seerr; docker rm seerr
+```
+Pull the latest image:
+```powershell
+docker pull ghcr.io/seerr-team/seerr:latest
+```
+Finally, run the container with the same parameters originally used to create the container:
+```powershell
+docker run -d `
+  ...
+```

🤖 Prompt for AI Agents

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

In `@docs/getting-started/docker.mdx` around lines 192 - 200, In the "Docker CLI
(PowerShell)" tab replace the incorrect Docker Compose commands (`docker compose
pull seerr` / `docker compose up -d`) with the PowerShell-specific update flow:
stop and remove the existing container, pull the latest image from
ghcr.io/seerr-team/seerr:latest, and then re-run the container with the same
docker run parameters originally used; locate the block that currently contains
`docker compose pull seerr` and `docker compose up -d` and swap it for the
three-step sequence (stop+rm, docker pull, docker run) described in the review
suggestion.

🤖 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/docker.mdx`:
- Around line 203-221: Add an "Updating" subsection under the TabItem with value
"docker-cli-cmd" to match the PowerShell tab; include a docker pull and
container recreate sequence using the same caret (^) line-continuation style as
the existing docker run block and reference the image
ghcr.io/seerr-team/seerr:latest and container name seerr so users can
stop/remove the old container and run the updated image (docker pull
ghcr.io/seerr-team/seerr:latest, docker stop seerr, docker rm seerr, then the
docker run command with the same ^ continuations).

---

Outside diff comments:
In `@docs/getting-started/docker.mdx`:
- Around line 192-200: In the "Docker CLI (PowerShell)" tab replace the
incorrect Docker Compose commands (`docker compose pull seerr` / `docker compose
up -d`) with the PowerShell-specific update flow: stop and remove the existing
container, pull the latest image from ghcr.io/seerr-team/seerr:latest, and then
re-run the container with the same docker run parameters originally used; locate
the block that currently contains `docker compose pull seerr` and `docker
compose up -d` and swap it for the three-step sequence (stop+rm, docker pull,
docker run) described in the review suggestion.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e82fa89 and 2516646.

📒 Files selected for processing (4)

• docs/getting-started/buildfromsource.mdx
• docs/getting-started/docker.mdx
• docs/migration-guide.mdx
• gen-docs/docusaurus.config.ts

[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/getting-started/docker.mdx`:
- Line 196: Replace the PowerShell chain "docker stop seerr && docker rm seerr"
with a PowerShell-5.1–compatible form by either using two separate commands
("docker stop seerr" then "docker rm seerr") or using a semicolon separator,
ensuring the docs no longer rely on the PowerShell 7+ && operator; update the
line containing the exact string "docker stop seerr && docker rm seerr"
accordingly.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2516646 and 91e5a6e.

📒 Files selected for processing (4)

• docs/getting-started/buildfromsource.mdx
• docs/getting-started/docker.mdx
• docs/migration-guide.mdx
• gen-docs/docusaurus.config.ts

🚧 Files skipped from review as they are similar to previous changes (3)

• gen-docs/docusaurus.config.ts
• docs/getting-started/buildfromsource.mdx
• docs/migration-guide.mdx