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

docs/getting-started/buildfromsource.mdx

@@ -230,7 +230,7 @@ You can now access Seerr by visiting `http://localhost:5055` in your web browser
   <TabItem value="task-scheduler" label="Task Scheduler">
 To run seerr as a bat script:
 1. Create a file named `start-seerr.bat` in the seerr directory:
-```bat
+```batch
 @echo off
 set PORT=5055
 set NODE_ENV=production

docs/getting-started/docker.mdx

@@ -168,36 +168,80 @@ or the Docker Desktop app:
 
 Then, create and start the Seerr container:
 <Tabs groupId="docker-methods" queryString>
-  <TabItem value="docker-cli" label="Docker CLI">
+  <TabItem value="docker-cli" label="Docker CLI (PowerShell)">
-```bash
+```powershell
-docker run -d \
+docker run -d `
-  --name seerr \
+  --name seerr `
-  --init \
+  --init `
-  -e LOG_LEVEL=debug \
+  -e LOG_LEVEL=debug `
-  -e TZ=Asia/Tashkent \
+  -e TZ=Asia/Tashkent `
-  -e PORT=5055 \
+  -e PORT=5055 `
-  -p 5055:5055 \
+  -p 5055:5055 `
-  -v seerr-data:/app/config \
+  -v seerr-data:/app/config `
-  --restart unless-stopped \
+  --restart unless-stopped `
-  --health-cmd "wget --no-verbose --tries=1 --spider http://localhost:5055/api/v1/status || exit 1" \
+  --health-cmd "wget --no-verbose --tries=1 --spider http://localhost:5055/api/v1/status || exit 1" `
-  --health-start-period 20s \
+  --health-start-period 20s `
-  --health-timeout 3s \
+  --health-timeout 3s `
-  --health-interval 15s \
+  --health-interval 15s `
-  --health-retries 3 \
+  --health-retries 3 `
   ghcr.io/seerr-team/seerr:latest
 ```
 
 The argument `-e PORT=5055` is optional.
 
 #### Updating:
+
+Stop and remove the existing container:
+```powershell
+docker stop seerr; docker rm seerr
+```
 Pull the latest image:
-```bash
+```powershell
-docker compose pull seerr
+docker pull ghcr.io/seerr-team/seerr:latest
 ```
-Then, restart all services defined in the Compose file:
+Finally, run the container with the same parameters originally used to create the container:
-```bash
+```powershell
-docker compose up -d
+docker run -d ...
 ```
+
+  </TabItem>
+
+  <TabItem value="docker-cli-cmd" label="Docker CLI (CMD)">
+```batch
+docker run -d ^
+  --name seerr ^
+  --init ^
+  -e LOG_LEVEL=debug ^
+  -e TZ=Asia/Tashkent ^
+  -e PORT=5055 ^
+  -p 5055:5055 ^
+  -v seerr-data:/app/config ^
+  --restart unless-stopped ^
+  --health-cmd "wget --no-verbose --tries=1 --spider http://localhost:5055/api/v1/status || exit 1" ^
+  --health-start-period 20s ^
+  --health-timeout 3s ^
+  --health-interval 15s ^
+  --health-retries 3 ^
+  ghcr.io/seerr-team/seerr:latest
+```
+
+The argument `-e PORT=5055` is optional.
+
+#### Updating:
+
+Stop and remove the existing container:
+```batch
+docker stop seerr && docker rm seerr
+```
+Pull the latest image:
+```batch
+docker pull ghcr.io/seerr-team/seerr:latest
+```
+Finally, run the container with the same parameters originally used to create the container:
+```batch
+docker run -d ...
+```
+
   </TabItem>
 
   <TabItem value="docker-compose" label="Docker Compose">

docs/migration-guide.mdx

@@ -53,6 +53,7 @@ Changes :
 Since the container now runs as the `node` user (UID 1000), you must ensure your config folder has the correct permissions. The `node` user must have read and write access to the `/app/config` directory.
 
 If you're migrating from a previous installation, you may need to update the ownership of your config folder:
+
 ```bash
 docker run --rm -v /path/to/appdata/config:/data alpine chown -R 1000:1000 /data
 ```
@@ -106,6 +107,7 @@ Summary of changes :
 </Tabs>
 
 ### Windows
+
 Summary of changes :
 <Tabs groupId="docker-methods" queryString>
   <TabItem value="docker-compose" label="Docker compose">
@@ -136,17 +138,32 @@ Summary of changes :
       external: true
   ```
   </TabItem>
-  <TabItem value="docker-cli" label="Docker CLI">
+  <TabItem value="docker-cli" label="Docker CLI (PowerShell)">
-  ```bash {2-3,8,10}
+  ```powershell {2-3,8,10}
-  docker run -d \
+  docker run -d `
-    --name seerr \
+    --name seerr `
-    --init \
+    --init `
-    -e LOG_LEVEL=debug \
+    -e LOG_LEVEL=debug `
-    -e TZ=Asia/Tashkent \
+    -e TZ=Asia/Tashkent `
-    -e PORT=5055 \
+    -e PORT=5055 `
-    -p 5055:5055 \
+    -p 5055:5055 `
-    -v seerr-data:/app/config \
+    -v seerr-data:/app/config `
-    --restart unless-stopped \
+    --restart unless-stopped `
+    ghcr.io/seerr-team/seerr:latest
+  ```
+  </TabItem>
+
+  <TabItem value="docker-cli-cmd" label="Docker CLI (CMD)">
+  ```batch {2-3,8,10}
+  docker run -d ^
+    --name seerr ^
+    --init ^
+    -e LOG_LEVEL=debug ^
+    -e TZ=Asia/Tashkent ^
+    -e PORT=5055 ^
+    -p 5055:5055 ^
+    -v seerr-data:/app/config ^
+    --restart unless-stopped ^
     ghcr.io/seerr-team/seerr:latest
   ```
   </TabItem>
@@ -277,4 +294,4 @@ Follow the [Unraid Installation Guide](/getting-started/third-parties/unraid#2-s
 Start the newly created Seerr container. Check the container logs to confirm the automatic migration completed successfully.
 
 **5. Remove the old app**
-Once you have confirmed Seerr is working properly and your data has successfully migrated, you can safely **Remove** the old Overseerr (or Jellyseerr) container from Unraid.
+Once you have confirmed Seerr is working properly and your data has successfully migrated, you can safely **Remove** the old Overseerr (or Jellyseerr) container from Unraid.

gen-docs/docusaurus.config.ts

@@ -133,7 +133,14 @@ const config: Config = {
     prism: {
       theme: prismThemes.shadesOfPurple,
       darkTheme: prismThemes.shadesOfPurple,
-      additionalLanguages: ['bash', 'powershell', 'yaml', 'nix', 'nginx'],
+      additionalLanguages: [
+        'bash',
+        'powershell',
+        'yaml',
+        'nix',
+        'nginx',
+        'batch',
+      ],
     },
   } satisfies Preset.ThemeConfig,
 };