revert(perf): drop the dockerode and docker-modem pnpm patches

Both patches came out of this work and both are removed at the maintainer's
request. The finding was real - ssh2's WASM heap costs +14.0 MiB RSS on require,
and @grpc/grpc-js another 14.6 MiB across 61 files, neither of which a
socket-based Docker install ever uses - but patching a dependency means every
future dockerode or docker-modem bump fails until someone regenerates the patch,
and that recurring cost is not worth roughly 25 MiB.

The finding stays on record in SERVER-MEMORY.md because the fix belongs upstream:
both packages require a module at file scope while using it in exactly one
already-guarded branch, so a PR to each would fix it for every consumer with no
patch to maintain here.

The two remaining patches, @types/node-unifi and trpc-to-openapi, predate this
work and are untouched. allowUnusedPatches was already set on dev and is left
alone. Lockfile regenerated: patchedDependencies now lists only those two.

Also sharpens the Cache Components entry. The SqliteError was simply an unmigrated
build database, which is fixable - but feeding the build a database would be the
wrong fix, because serverSetting is per-installation data on the user's volume and
a shell prerendered against the build machine's database would bake one install's
settings into every other install's first paint. The error was Next.js correctly
reporting a request-time read sitting in the shell path.

.agents/skills/homarr-custom-widget/SKILL.md

@@ -1,28 +0,0 @@
----
-name: homarr-custom-widget
-description: Author safe Homarr Custom JSX v2 widgets from API documentation.
----
-
-# Homarr Custom Widget
-
-Author one widget at a time. When connected to Homarr, retrieve `homarr://custom-widgets/schema` and only the component resources needed for the design. The live resources are authoritative for the installed release.
-
-1. Read the API documentation.
-2. Create one credential-free widget with keyed `sources`, keyed `requests`, optional keyed `options`, and safe JSX `template`.
-3. Validate, preview, test queries and simulated actions, visually inspect, and iterate.
-4. Configure deployment-specific source URLs and request credentials through Homarr; never repeat plaintext.
-5. Save only after narrow/wide, light/dark, loading, empty, error, and success states work.
-
-Use `{option:name}` or `$option` for saved options. Use `{param:name}` or `$param` for values supplied by `SubFetch`, `ActionButton`, or `ToggleSwitch`. Load queries cannot use invocation parameters. Templates read `data`, `status`, `options`, and temporary `inputs`.
-
-`SubFetch` with `trigger="manual"` renders its own load button. Pass a card or image through `triggerContent` with `triggerAriaLabel` when that content should launch the request. Its callback is `(result, meta)`; never author `onClick` or a fetch callback.
-
-Use standard Mantine compound names and deliberate visual hierarchy, spacing, restrained semantic color, and responsive layouts. Avoid excessive nested cards.
-
-Do not use imports, hooks, refs, raw HTML, raw event callbacks, browser requests, arbitrary functions, eval, bigint, npm packages, authored statement blocks, IIFEs, or recursion. Do not pretend MCP tools exist in an offline chat session.
-
-To install an existing widget, use `customWidget_workshopSearch`, inspect it with `customWidget_workshopGet`, then use `customWidget_workshopInstall`. Configure each self-hosted source afterward with `customWidget_sourceConfigure`, or call `customWidget_configurationRequestUser` so the user can enter the server URL and credentials directly in Homarr.
-
-Preview-scoped configuration expires with the preview. To persist user-entered values for a new widget, create the widget first, request configuration for its definition ID, then create a final preview with that definition ID so Homarr loads the stored credentials.
-
-When this skill is installed from the repository, optional offline details are in `references/schema.md`, `references/runtime.md`, and `references/security.md`. MCP-only clients should use the live Homarr resources instead.

.agents/skills/homarr-custom-widget/references/runtime.md

@@ -1,16 +0,0 @@
-# Runtime
-
-Templates read `data.requestId`, `status.requestId`, `options.name`, and temporary `inputs.name`. Status contains `loading`, `ok`, `status`, `statusText`, and `error`.
-
-`bind="search"` creates an in-memory input. It is never persisted. Supply invocation values only through `params`, for example:
-
-```jsx
-<TextInput bind="search" label="Search" />
-<SubFetch requestId="search" params={{ query: inputs.search }}>
-  {(items) => <Stack>{(items ?? []).map(item => <Text key={item.id}>{item.name}</Text>)}</Stack>}
-</SubFetch>
-```
-
-`SubFetch` with `trigger="manual"` renders its own load button. To make a card or image launch the request, pass that node through `triggerContent` and provide `triggerAriaLabel`; Homarr supplies the click and keyboard behavior. Its optional second callback argument contains `{ ok, status, statusText, loading: false }`; loading and request failures are rendered by `SubFetch` before the callback runs. Do not author `onClick` or a fetch callback.
-
-Use expression callbacks for supported collection methods and trusted slots. Do not use callback blocks, IIFEs, authored recursion, or raw events. Bounded regex literals work only with safe string matching/replacement operations.

.agents/skills/homarr-custom-widget/references/schema.md

@@ -1,22 +0,0 @@
-# Schema
-
-```ts
-interface HomarrCustomWidgetV2 {
-  $schema: "homarr-custom-widget-v2";
-  name: string;
-  description?: string;
-  iconUrl?: string;
-  sources: Record<string, CustomWidgetSource>;
-  requests: Record<string, CustomWidgetRequest>;
-  options?: Record<string, CustomWidgetOption>;
-  template: string;
-}
-```
-
-Sources require `default`. A request defaults to the default source, query, GET, load, inherited auth, and view permission. An action defaults to manual and modify permission. DELETE uses full permission and confirmation.
-
-Use stable real URLs for public APIs and clear suggested URLs for self-hosted services. Homarr collects the installer's server URL, network scope, and credentials as source setup; credentials remain outside the manifest.
-
-Paths use `{option:name}` and `{param:name}`. Query/body data uses `{ "$option": "name" }` and `{ "$param": "name" }`. Load queries cannot use params. Runtime parameter names and primitive values are inferred from references.
-
-Every option has `label`, `control`, and `default`. Optional fields are `description`, `choices`, `choicesFrom`, `min`, `max`, `step`, `advanced`, and `group`.

.agents/skills/homarr-custom-widget/references/security.md

@@ -1,7 +0,0 @@
-# Security
-
-All requests use Homarr's protected server executor. Source origin, network scope, DNS, redirects, SSRF, rate limits, permissions, size limits, timeouts, and encrypted credential injection remain enforced.
-
-The JSX interpreter blocks imports, hooks, refs, raw event callbacks, browser requests, eval, arbitrary functions, prototype access, unsafe URLs, global CSS escape, arbitrary portals, bigint, statement blocks, IIFEs, and recursion. Regex literals must be bounded and reject backreferences, lookbehind, nested quantifiers, excessive length, and unsupported flags.
-
-Credentials are stored separately and never exported or returned to an agent. A published self-hosted source URL is only a suggestion: installers must confirm or replace private and loopback URLs for their own Homarr deployment. Source origins cannot be controlled through widget options.

.env.example

@@ -55,36 +55,19 @@ TURBO_TELEMETRY_DISABLED=1
 # Example: DOCKER_SOCKET_PATHS=/var/run/docker.sock,/run/user/1000/podman/podman.sock
 # DOCKER_SOCKET_PATHS=
 
+# Redis DB index for the Next.js cache handler (default: 1).
+# Must differ from REDIS_DATABASE_INDEX (default: 0) to avoid cache ops affecting app data.
+# REDIS_CACHE_DB=1
+
 # Enable kubernetes tool
 # ENABLE_KUBERNETES=true
 
 # Enable mock integration
 UNSAFE_ENABLE_MOCK_INTEGRATION=true
 
-# Public URL contract. Values must be absolute HTTP(S) URLs without credentials,
-# query strings, or fragments. Trailing slashes are normalized at startup.
-HOMARR_WEBSITE_URL=https://homarr.dev
-# PocketBase API used by Homarr and by the standalone documentation site.
-# Defaults to HOMARR_WEBSITE_URL.
-# WORKSHOP_API_URL=https://homarr.dev
-# Public Workshop page opened from Homarr. Defaults to HOMARR_WEBSITE_URL/workshop.
-# WORKSHOP_WEB_URL=https://homarr.dev/workshop
-
-# Documentation and PocketBase deployment settings.
-# WORKSHOP_PUBLIC_ORIGIN=https://homarr.dev
-# PB_ALLOWED_ORIGINS=*
-
-# Local Workshop stack:
-# HOMARR_WEBSITE_URL=http://127.0.0.1:3003
-# WORKSHOP_API_URL=http://127.0.0.1:8090
-# WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop
-# WORKSHOP_PUBLIC_ORIGIN=http://127.0.0.1:3003
-# Optional: GITHUB_CLIENT_ID=
-# Optional: GITHUB_CLIENT_SECRET=
-
 # Enable demo mode (seeds a demo user "demo"/"demo", a sample board and a mock integration)
 # DEMO_MODE=true
 
 # Whether demo mode is read-only. Defaults to true (the public demo blocks all mutations).
 # Set to false for writable preview deployments so the demo user can modify the dashboard.
-# DEMO_READ_ONLY=false
+# DEMO_READ_ONLY=false

.github/pull_request_template.md

@@ -16,6 +16,6 @@
 **When contributing a new integration or widget:**
 
 - [ ] I confirmed manually that the integration or widget is working with a real system and performed basic smoke
-      tests (e.g. what happens if it is offline)
+  tests (e.g. what happens if it is offline)
 - [ ] Optional but recommended: I confirm that I am willing to be added to the `CODEOWNERS` of this feature and will
-      provide support and maintain the integration (e.g. in case of breaking or failure)
+  provide support and maintain the integration (e.g. in case of breaking or failure)

.github/workflows/autofix.yml

@@ -1,4 +1,4 @@
-name: Formatting
+name: Auto-fix lint and format
 
 on:
   pull_request:
@@ -6,30 +6,42 @@ on:
     branches: ["*"]
 
 permissions:
-  contents: read
+  contents: write
 
 concurrency:
   group: ${{ github.workflow }}-${{ github.event.pull_request.number }}
   cancel-in-progress: true
 
 jobs:
-  format:
-    name: Check formatting
+  autofix:
+    name: Auto-fix
+    if: github.event.pull_request.head.repo.id == github.repository_id
     runs-on: ubuntu-latest
     timeout-minutes: 5
     steps:
       - uses: actions/checkout@v7
         with:
           fetch-depth: 0
-          persist-credentials: false
+          ref: ${{ github.head_ref }}
 
       - name: Setup
         uses: ./tooling/github/setup
 
-      - name: Check changed files
+      - name: Get changed files
+        id: changed
         env:
           BASE_REF: ${{ github.base_ref }}
         run: |
-          git diff --name-only --diff-filter=ACMR -z "origin/${BASE_REF}...HEAD" -- \
-            '*.css' '*.js' '*.json' '*.jsonc' '*.jsx' '*.md' '*.mdx' '*.scss' '*.ts' '*.tsx' '*.yaml' '*.yml' \
-            | xargs -0 -r pnpm exec oxfmt --check --
+          git diff --name-only --diff-filter=ACMR "origin/${BASE_REF}...HEAD" -- '*.ts' '*.tsx' '*.js' '*.jsx' > /tmp/changed-files
+          echo "count=$(wc -l < /tmp/changed-files | tr -d '[:space:]')" >> $GITHUB_OUTPUT
+
+      - name: Auto-fix lint + format
+        if: steps.changed.outputs.count != '0'
+        run: |
+          xargs -r -a /tmp/changed-files pnpm exec oxlint --fix || true
+          xargs -r -a /tmp/changed-files pnpm exec oxfmt --write
+
+      - name: Commit fixes
+        uses: stefanzweifel/git-auto-commit-action@v7
+        with:
+          commit_message: "style: auto-fix lint and format"

.github/workflows/ci.yml

@@ -8,7 +8,7 @@ on:
     types: [closed]
     branches: ["*"]
   push:
-    branches: [main, dev, beta, next, v2]
+    branches: [main, dev, beta, next]
   merge_group:
   workflow_dispatch:
     inputs:
@@ -34,10 +34,8 @@ permissions:
   contents: read
 
 concurrency:
-  # Every event for a PR shares one group so a close event cancels stale image
-  # publication and a newer synchronize run cannot be overwritten by an older run.
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || inputs.pr_number || github.ref }}
-  cancel-in-progress: ${{ github.event_name == 'pull_request' || github.event_name == 'pull_request_target' || github.event_name == 'workflow_dispatch' || github.ref != 'refs/heads/main' }}
+  group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.event.pull_request.number || inputs.pr_number || github.ref }}
+  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
 
 env:
   FORCE_COLOR: 3
@@ -89,17 +87,6 @@ jobs:
       - name: Validate workspace configuration
         run: pnpm lint:ws
 
-      - name: Validate Custom Widget architecture
-        run: pnpm check:custom-widgets
-
-      - name: Validate checked-in OpenAPI schema
-        run: pnpm check:openapi
-
-      - name: Validate Custom Widget bundle budget
-        run: |
-          pnpm --filter nextjs build
-          pnpm check:custom-widget-bundle
-
       - name: Run unit tests
         run: pnpm test
 
@@ -115,8 +102,6 @@ jobs:
     permissions:
       contents: read
       packages: write
-    outputs:
-      digest: ${{ steps.preview-build.outputs.digest }}
     steps:
       - uses: actions/checkout@v7
         if: "!env.ACT"
@@ -199,166 +184,38 @@ jobs:
           path: e2e/test-results/
           retention-days: 7
 
-      - name: Log in to GHCR for preview publication
+      - name: Determine preview tag
+        id: preview
         if: |
           !env.ACT &&
           (
             (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
             (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
           )
+        env:
+          PR_NUMBER: ${{ github.event.pull_request.number || inputs.pr_number }}
+        run: echo "tag=pr-${PR_NUMBER}" >> "$GITHUB_OUTPUT"
+
+      - name: Log in to GHCR
+        if: steps.preview.outputs.tag != ''
         uses: docker/login-action@v4
         with:
           registry: ${{ env.REGISTRY }}
           username: ${{ github.actor }}
           password: ${{ secrets.GITHUB_TOKEN }}
 
-      - name: Push amd64 preview image by digest
-        id: preview-build
-        if: |
-          !env.ACT &&
-          (
-            (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
-            (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
-          )
-        uses: docker/build-push-action@v7
-        with:
-          context: .
-          network: host
-          platforms: linux/amd64
-          outputs: type=image,"name=${{ env.PREVIEW_IMAGE }}",push-by-digest=true,name-canonical=true,push=true
-          cache-from: type=gha,scope=homarr-linux-amd64
-          secrets: |
-            TURBO_API=${{ secrets.TURBO_API }}
-            TURBO_TEAM=${{ secrets.TURBO_TEAM }}
-            TURBO_TOKEN=${{ secrets.TURBO_TOKEN }}
-            TURBO_REMOTE_CACHE_SIGNATURE_KEY=${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
+      - name: Push preview image
+        if: steps.preview.outputs.tag != ''
+        env:
+          PREVIEW_TAG: ${{ steps.preview.outputs.tag }}
+        run: |
+          docker tag homarr-ci "${PREVIEW_IMAGE}:${PREVIEW_TAG}"
+          docker push "${PREVIEW_IMAGE}:${PREVIEW_TAG}"
 
       - name: Show Act publication result
         if: env.ACT
         run: echo "Act validated the publication path; external GHCR writes are disabled locally."
 
-  preview-arm64:
-    name: Build arm64 preview image
-    needs: fast-gate
-    if: |
-      (
-        (github.event_name == 'pull_request' && github.event.pull_request.draft == false && github.event.pull_request.head.repo.full_name == github.repository) ||
-        (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
-      )
-    runs-on: ubuntu-24.04-arm
-    timeout-minutes: 20
-    permissions:
-      contents: read
-      packages: write
-    outputs:
-      digest: ${{ steps.preview-build.outputs.digest }}
-    steps:
-      - uses: actions/checkout@v7
-        if: "!env.ACT"
-        with:
-          persist-credentials: false
-          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || '' }}
-
-      - name: Log in to GHCR
-        if: "!env.ACT"
-        uses: docker/login-action@v4
-        with:
-          registry: ${{ env.REGISTRY }}
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Set up Docker Buildx
-        if: "!env.ACT"
-        uses: docker/setup-buildx-action@v4
-
-      - name: Build and push arm64 preview image by digest
-        id: preview-build
-        if: "!env.ACT"
-        uses: docker/build-push-action@v7
-        with:
-          context: .
-          network: host
-          platforms: linux/arm64
-          outputs: type=image,"name=${{ env.PREVIEW_IMAGE }}",push-by-digest=true,name-canonical=true,push=true
-          cache-from: type=gha,scope=homarr-linux-arm64
-          cache-to: type=gha,scope=homarr-linux-arm64,mode=max
-          secrets: |
-            TURBO_API=${{ secrets.TURBO_API }}
-            TURBO_TEAM=${{ secrets.TURBO_TEAM }}
-            TURBO_TOKEN=${{ secrets.TURBO_TOKEN }}
-            TURBO_REMOTE_CACHE_SIGNATURE_KEY=${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
-
-  publish-preview:
-    name: Publish multi-platform preview image
-    needs: [container, preview-arm64]
-    if: |
-      (
-        (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
-        (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
-      )
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    permissions:
-      contents: read
-      packages: write
-      pull-requests: read
-    env:
-      PREVIEW_TAG: pr-${{ github.event.pull_request.number || inputs.pr_number }}
-    steps:
-      - name: Log in to GHCR
-        if: "!env.ACT"
-        uses: docker/login-action@v4
-        with:
-          registry: ${{ env.REGISTRY }}
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Set up Docker Buildx
-        if: "!env.ACT"
-        uses: docker/setup-buildx-action@v4
-
-      - name: Verify PR head before publication
-        if: github.event_name == 'pull_request'
-        uses: actions/github-script@v8
-        env:
-          EXPECTED_HEAD_SHA: ${{ github.event.pull_request.head.sha }}
-        with:
-          script: |
-            const { data: pull } = await github.rest.pulls.get({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              pull_number: context.payload.pull_request.number,
-            });
-            if (pull.state !== "open") {
-              core.setFailed(`PR #${pull.number} is ${pull.state}; refusing to publish its preview.`);
-              return;
-            }
-            if (pull.head.sha !== process.env.EXPECTED_HEAD_SHA) {
-              core.setFailed(`PR #${pull.number} moved from ${process.env.EXPECTED_HEAD_SHA} to ${pull.head.sha}.`);
-            }
-
-      - name: Publish preview manifest
-        if: "!env.ACT"
-        env:
-          AMD64_DIGEST: ${{ needs.container.outputs.digest }}
-          ARM64_DIGEST: ${{ needs.preview-arm64.outputs.digest }}
-        run: |
-          docker buildx imagetools create -t "${PREVIEW_IMAGE}:${PREVIEW_TAG}" \
-            "${PREVIEW_IMAGE}@${AMD64_DIGEST}" \
-            "${PREVIEW_IMAGE}@${ARM64_DIGEST}"
-
-      - name: Verify preview manifest platforms
-        if: "!env.ACT"
-        run: |
-          image="${PREVIEW_IMAGE}:${PREVIEW_TAG}"
-          manifest="$(docker buildx imagetools inspect "$image" --raw)"
-          for architecture in amd64 arm64; do
-            jq --exit-status --arg architecture "$architecture" \
-              'any(.manifests[]; .platform.os == "linux" and .platform.architecture == $architecture)' \
-              <<<"$manifest" >/dev/null
-          done
-          docker buildx imagetools inspect "$image"
-
   cleanup:
     name: Clean up preview image
     if: github.event_name == 'pull_request_target' || (github.event_name == 'workflow_dispatch' && inputs.operation == 'cleanup')

.github/workflows/workshop.yml

@@ -1,63 +0,0 @@
-name: Workshop
-
-on:
-  pull_request:
-  push:
-    branches: [dev, v2, main]
-
-permissions:
-  contents: read
-
-jobs:
-  validate:
-    runs-on: ubuntu-24.04
-    timeout-minutes: 30
-    steps:
-      - uses: actions/checkout@v7
-      - uses: actions/setup-node@v6
-        with:
-          node-version: 24.18.0
-      - uses: pnpm/action-setup@v6
-        with:
-          run_install: false
-      - run: pnpm install --frozen-lockfile
-      - run: pnpm --filter @homarr/workshop typecheck
-      - run: pnpm --filter @homarr/docs typecheck
-      - run: docker compose --env-file apps/workshop/.env.staging.example -f apps/workshop/docker-compose.staging.yml config --quiet
-      - run: pnpm test:workshop
-      - run: pnpm test:workshop-image
-
-  publish:
-    if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'main')
-    needs: validate
-    runs-on: ubuntu-24.04
-    timeout-minutes: 30
-    permissions:
-      contents: read
-      packages: write
-    steps:
-      - uses: actions/checkout@v7
-      - uses: docker/setup-qemu-action@v4
-      - uses: docker/setup-buildx-action@v4
-      - uses: docker/login-action@v4
-        with:
-          registry: ghcr.io
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-      - uses: docker/metadata-action@v6
-        id: metadata
-        with:
-          images: ghcr.io/homarr-labs/workshop
-          tags: |
-            type=sha,prefix=sha-,format=long
-            type=raw,value=v2,enable=${{ github.ref_name == 'v2' }}
-            type=raw,value=latest,enable=${{ github.ref_name == 'main' }}
-      - uses: docker/build-push-action@v7
-        with:
-          context: .
-          file: apps/workshop/Dockerfile
-          target: production
-          platforms: linux/amd64,linux/arm64
-          push: true
-          tags: ${{ steps.metadata.outputs.tags }}
-          labels: ${{ steps.metadata.outputs.labels }}

.gitignore

@@ -16,7 +16,6 @@ out/
 next-env.d.ts
 
 # artifacts
-.ai-evaluations/
 packages/db/migrations/*/migrate.cjs
 
 # nitro
@@ -72,11 +71,7 @@ apps/nextjs/public/images/background.png
 
 # personal agent config
 .opencode
-.agents/*
-!.agents/skills/
-.agents/skills/*
-!.agents/skills/homarr-custom-widget/
-!.agents/skills/homarr-custom-widget/**
+.agents/
 skills-lock.json
 
 # docusaurus
@@ -84,3 +79,11 @@ apps/docs/.docusaurus
 apps/docs/build
 .pnpm-store
 benchmark-results
+.bench/
+
+# Homarr backups used by scripts/benchmarks/stress-restore.mts. These contain
+# real integration secrets and an encryption key — never commit one.
+homarr-backup*.zip
+*.sqlite
+*.sqlite-wal
+*.sqlite-shm

.impeccable/critique/2026-07-21T11-32-50Z__apps-docs-src-components-workshop.md

@@ -1,116 +0,0 @@
----
-target: Workshop store in the docs
-total_score: 20
-p0_count: 1
-p1_count: 3
-timestamp: 2026-07-21T11-32-50Z
-slug: apps-docs-src-components-workshop
----
-
-# Workshop Store Critique
-
-## Design Health Score
-
-| #         | Heuristic                           |     Score | Key issue                                                                                                                                                        |
-| --------- | ----------------------------------- | --------: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 1         | Visibility of system status         |       1/4 | Fetch failure can show beside an empty-store message, so the system communicates two incompatible states.                                                        |
-| 2         | Match between system and real world |       3/4 | Widget, CSS, voting, revisions, and comments use familiar language.                                                                                              |
-| 3         | User control and freedom            |       2/4 | Filters are reversible, but the crashed route and failed fetch state offer no useful recovery.                                                                   |
-| 4         | Consistency and standards           |       2/4 | The submission editor uses CodeMirror, while revision editing falls back to a textarea; several tiny custom controls do not follow the shared button vocabulary. |
-| 5         | Error prevention                    |       2/4 | Submission validation exists, but disabled progression does not explain what is missing and destructive actions use a brief inline confirmation.                 |
-| 6         | Recognition rather than recall      |       3/4 | Labels, type choices, and the submission stepper are understandable without documentation.                                                                       |
-| 7         | Flexibility and efficiency          |       2/4 | Search covers titles only, signed-out users can select Yours, and installation is reduced to ambiguous Copy and Download actions.                                |
-| 8         | Aesthetic and minimalist design     |       3/4 | The restrained visual system is clean, but the browse toolbar and card action rows become dense.                                                                 |
-| 9         | Help users recover from errors      |       0/4 | The production route crashes with React error 130; the fetch error has no retry action or useful context.                                                        |
-| 10        | Help and documentation              |       2/4 | The editor explains its fields, but the store does not teach the full inspect, trust, download, and install journey.                                             |
-| **Total** |                                     | **20/40** | **Needs work before release**                                                                                                                                    |
-
-## Anti-Patterns Verdict
-
-The surface does not look like obvious AI-generated decoration. Its visual restraint, familiar controls, and practical editor are credible product UI. The weakness is product behavior rather than styling: contradictory states, tiny action controls, an overloaded responsive toolbar, and a primary installation journey that is not explicit.
-
-The deterministic Impeccable scan returned zero findings for `apps/docs/src/components/workshop`. This is useful but incomplete. The detector did not catch runtime failures, semantic state conflicts, touch-target sizing, or responsive grouping. Browser evidence found a full route crash, React error 130, and an earlier state that rendered both `Something went wrong.` and `No submissions yet`.
-
-No visual overlay was injected because the available browser evaluation surface is read-only. Screenshots, DOM snapshots, console logs, and source inspection were used instead.
-
-## Overall Impression
-
-The submission modal is now one of the stronger parts of the Workshop. The store around it is not release-ready. The single biggest opportunity is to make discovery and installation a dependable, explicit path: load reliably, show one truthful state, help users evaluate a submission, and give them one obvious next action.
-
-## What Is Working
-
-1. The visual system is restrained and consistent with the Homarr documentation. Typography, color, radii, and spacing do not compete with the content.
-2. The submission flow chunks a complex task into Type, Details, and Media. The shared JSON/CSS editor, drag-and-drop import, metadata autofill, and capped media previews reduce creator effort.
-3. The detail design exposes revision, author, reports, changelog, source content, and comments. This supports inspection rather than treating community code as a blind install.
-
-## Priority Issues
-
-### P0: The Workshop route crashes in the production docs build
-
-**Why it matters:** No visual polish matters if the store becomes a Docusaurus error page. A fresh independent tab consistently reached `This page crashed` with React error 130. The console attributed the thrown error to the Kapa widget bundle.
-
-**Fix:** Isolate or disable the Kapa script on Workshop routes, prevent third-party widget failures from reaching the Docusaurus route boundary, and add a route-level Workshop boundary that preserves navigation and retry. Reproduce against the built Docker docs image, not only the development server.
-
-**Suggested command:** `$impeccable harden`
-
-### P1: Failure and empty states contradict each other
-
-**Why it matters:** Showing `Something went wrong.` followed by `No submissions yet` makes users believe the store is both broken and empty. The generic message gives no cause and no recovery.
-
-**Fix:** Make loading, failure, empty, and results mutually exclusive. The failure state should say that listings could not be loaded, preserve the current filters, and provide `Try loading again`. Do not render filters or an empty store as authoritative data after the initial request fails.
-
-**Suggested command:** `$impeccable harden`
-
-### P1: Mobile discovery controls are too dense and do not form a responsive hierarchy
-
-**Why it matters:** The toolbar's inner row contains four type choices, sorting, and outdated visibility without wrapping. Most controls are 24 to 28 pixels tall. At narrow widths this is difficult to scan, easy to clip, and below a comfortable touch target.
-
-**Fix:** Put a full-width search first on mobile, keep All, Widgets, and CSS as the primary segmented choice, move sorting and outdated visibility into a compact secondary row or popover, and hide Yours when signed out or make it a sign-in affordance. Use at least 40 to 44 pixel touch targets. Add `aria-pressed` or proper tab semantics to the type filter.
-
-**Suggested command:** `$impeccable adapt`
-
-### P1: The store does not make the install journey obvious
-
-**Why it matters:** A first-time user sees Copy and Download without knowing which is recommended, what will be copied, how to inspect safety, or where the file goes in Homarr. This weakens the store's main purpose.
-
-**Fix:** Make the detail page the decision surface. Use one primary action named for its result, such as `Download widget JSON` or `Copy CSS`, with a short `Install in Homarr` explanation linked to the correct in-app flow. Cards should prioritize title, preview, compatibility, score, and `View details`; secondary utilities should not compete with evaluation.
-
-**Suggested command:** `$impeccable clarify`
-
-### P2: Card and moderation actions are too small and too numerous
-
-**Why it matters:** Vote, copy, download, comment, delete, and report controls compete in a compact footer. Low-contrast icon buttons are hard to discover and hard to use by touch. CSS columns also create a top-to-bottom visual reading order that can differ from the expected row order.
-
-**Fix:** Use a regular responsive grid, remove hover scaling, keep one or two visible card actions, and move owner/moderation actions to a menu. Keep voting visible but increase its target size. Correct the report copy: reports and reporter identities are moderation data, not public social proof.
-
-**Suggested command:** `$impeccable distill`
-
-## Persona Red Flags
-
-### Jordan, first-time self-hoster
-
-Jordan opens Workshop to install a widget. The route can crash before any listing appears. In the partial failure state, Jordan sees both an error and an empty store. If listings load, Copy and Download do not explain the Homarr destination or recommended path. Jordan is likely to leave before installing anything.
-
-### Alex, experienced Homarr administrator
-
-Alex can understand the JSON and appreciates the source viewer, but title-only search and limited filtering make a larger catalog inefficient. Compatibility and required secret information are not prominent at browse time. Tiny moderation and owner controls slow repeated management tasks.
-
-### Morgan, mobile user
-
-Morgan encounters a toolbar with more controls than fit comfortably in one decision group, 24 to 28 pixel targets, and a signed-out Yours filter that leads to an unhelpful no-results state. Submission cards add another dense row of small actions.
-
-## Minor Observations
-
-- Future submission steps are focusable buttons even when clicking them does nothing. Disable them or render non-interactive progress markers.
-- The report textarea relies on placeholder text and needs a persistent accessible label.
-- The revision editor should reuse the same JSON/CSS CodeMirror component as creation.
-- Search should include title, description, and author at minimum.
-- The timed inline `Confirm?` deletion pattern is easy to miss and weak for keyboard and touch users.
-- The detail-page changelog uses an uppercase tracked label, which is unnecessary in this otherwise restrained interface.
-- Loading comments should use the same skeleton vocabulary as listings rather than centered status text.
-
-## Questions to Consider
-
-1. Is Workshop primarily a catalog for discovery, or a technical exchange for copying source? The primary card and detail actions should commit to one answer.
-2. Should users evaluate compatibility and required secrets before opening a listing, or only on the detail page?
-3. Does Workshop need every moderation and ownership action visible inline, or should those actions live behind a menu?

.impeccable/critique/2026-07-21T12-29-41Z__apps-docs-src-components-workshop.md

@@ -1,64 +0,0 @@
----
-target: Workshop store in the docs
-total_score: 38
-p0_count: 0
-p1_count: 0
-timestamp: 2026-07-21T12-29-41Z
-slug: apps-docs-src-components-workshop
----
-
-# Workshop Store Critique — Post-Polish
-
-## Design Health Score
-
-| #         | Heuristic                           |     Score | Evidence                                                                                                                                                         |
-| --------- | ----------------------------------- | --------: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 1         | Visibility of system status         |       4/4 | Loading, initial failure, stale refresh failure, empty, and results states are mutually exclusive; recovery actions are visible.                                 |
-| 2         | Match between system and real world |       4/4 | Actions describe their result: Download widget JSON, Copy CSS, View details, and Install in Homarr.                                                              |
-| 3         | User control and freedom            |       4/4 | Filters can be cleared, errors retried, dialogs cancelled, and destructive submission deletion requires explicit confirmation.                                   |
-| 4         | Consistency and standards           |       4/4 | Creation and revision editing share CodeMirror, buttons follow the shared system, and cards use a predictable responsive grid.                                   |
-| 5         | Error prevention                    |       3/4 | Validation, disabled progression, pending states, RLS, and confirmations are strong; disabled form progression could explain unmet requirements more explicitly. |
-| 6         | Recognition rather than recall      |       4/4 | Persistent labels, type descriptions, step status, source previews, and installation instructions minimize recall.                                               |
-| 7         | Flexibility and efficiency          |       4/4 | Search spans title, description, and author; signed-in filtering, sorting, responsive controls, and direct detail actions support repeat use.                    |
-| 8         | Aesthetic and minimalist design     |       3/4 | The catalog is restrained and scannable; long source documents and the complete creator form necessarily remain dense on small screens.                          |
-| 9         | Help users recover from errors      |       4/4 | Route, listing, edit, report, copy, OAuth, and detail failures remain local and provide a clear next action.                                                     |
-| 10        | Help and documentation              |       4/4 | The detail page explains the exact Homarr destination and links to updated Workshop documentation.                                                               |
-| **Total** |                                     | **38/40** | **Release-quality; minor polish remains**                                                                                                                        |
-
-## Anti-Patterns Verdict
-
-The surface is product-led rather than decorative. The redesign removes the overloaded card footer, hover scaling, tiny touch controls, public moderation details, contradictory states, and ambiguous install actions. The deterministic Impeccable detector reports zero findings.
-
-## What Improved
-
-1. The production route no longer collapses into the Docusaurus crash screen without recovery. A route-local boundary protects navigation, and the fresh-volume production path renders without console errors.
-2. Loading, failure, empty, stale-results, and populated states are truthful and mutually exclusive.
-3. Search and filters form a clear responsive hierarchy. Mobile targets are 40–44 pixels, signed-out users do not see Yours, and cards no longer overflow at 390 pixels.
-4. Cards prioritize evaluation: title, author, type, score, description, comments, and View details. Copy, download, reporting, editing, and deletion moved to the detail page.
-5. The detail page now teaches the installation journey and names its primary action precisely.
-6. Reports and reporter identities are admin-only through PocketBase rules. Public catalog UI no longer turns reports into social proof.
-7. The creator and revision dialogs share the CodeMirror editor, use bounded internal scrolling, expose pending/error states, and avoid step-selection layout shifts.
-
-## Remaining Minor Opportunities
-
-### P2: Explain disabled progression inline
-
-The Type and Details steps are understandable, but a disabled Next button could state the missing requirement for keyboard and first-time users. This is a refinement, not a blocker, because required fields and validation messages are already present.
-
-### P2: Consider a compact source summary on very small screens
-
-The read-only source viewer is intentionally complete and horizontally scrollable. A future collapse/expand summary could reduce page length for nontechnical visitors without hiding inspection entirely.
-
-## Verification Evidence
-
-- Fresh Docker Compose PocketBase volume and production docs image.
-- Populated catalog with widget, CSS, and outdated examples.
-- Desktop and 390px mobile layouts in light and dark themes.
-- Widget detail, installation instructions, CodeMirror source view, and comments.
-- Signed-in submission wizard through Type and Details, including the shared editor.
-- Zero browser console errors after the final fixes.
-- Impeccable deterministic detector: zero findings.
-
-## Compatibility Note
-
-An existing local development volume created from an earlier unreleased version of the reset migration still has a stale Workshop view. It is intentionally not migrated or deleted. A fresh volume created from the current unreleased migration is the supported validation target and works correctly.

.impeccable/critique/2026-07-22T15-58-15Z__apps-docs-src-components-workshop.md

@@ -1,106 +0,0 @@
----
-target: Homarr Workshop docs UI
-total_score: 27
-p0_count: 0
-p1_count: 2
-timestamp: 2026-07-22T15-58-15Z
-slug: apps-docs-src-components-workshop
----
-
-## Design Health Score
-
-| #         | Heuristic                       |     Score | Key Issue                                                                                                                                     |
-| --------- | ------------------------------- | --------: | --------------------------------------------------------------------------------------------------------------------------------------------- |
-| 1         | Visibility of System Status     |         3 | Strong loading, retry, stale-data, pending, and copy states; successful report/edit actions still end silently.                               |
-| 2         | Match System / Real World       |         3 | Core Workshop language is clear, but `networkScope`, query/action, and schema terminology assumes technical fluency.                          |
-| 3         | User Control and Freedom        |         3 | Back, cancel, clear filters, vote toggling, and destructive confirmations are present; destructive actions have no undo.                      |
-| 4         | Consistency and Standards       |         3 | Shared primitives are coherent, though Docusaurus chrome and the denser app-store vocabulary still feel slightly stitched together.           |
-| 5         | Error Prevention                |         2 | Validation and confirmations are good, but install safety and credential context appears after download/copy actions on small screens.        |
-| 6         | Recognition Rather Than Recall  |         3 | Author, revision, source, filters, and capabilities are visible; installation still asks users to remember a separate Homarr navigation path. |
-| 7         | Flexibility and Efficiency      |         2 | Search, filters, sort, drag-and-drop, autofill, and comment shortcuts help; the install handoff remains manual.                               |
-| 8         | Aesthetic and Minimalist Design |         2 | Hierarchy is clear, but repeated panels, badges, uppercase metadata labels, and overlapping install actions add noise.                        |
-| 9         | Error Recognition and Recovery  |         3 | Errors are plain-language and usually preserve work; the global action error can be detached from the failed control.                         |
-| 10        | Help and Documentation          |         3 | The installation guide and source explanation are useful; security terminology lacks inline definitions.                                      |
-| **Total** |                                 | **27/40** | **Acceptable, significant improvements needed**                                                                                               |
-
-## Anti-Patterns Verdict
-
-**LLM assessment:** Moderate AI-assisted feel, not outright slop. Domain-specific copy, extensive state coverage, and transparent source/capability information make the feature credible. The generic card grid, repeated rounded panels, icon tiles, uppercase tracked labels, and decorative changelog stripe still expose a component-recipe grammar. It looks competent but not fully edited into a distinctive Homarr store.
-
-**Deterministic scan:** `detect.mjs --json apps/docs/src/components/workshop` exited 0 with exact output `[]`: zero findings, zero triggered rules, and no false positives. The scan found none of Impeccable's deterministic anti-patterns.
-
-**Visual overlays:** No reliable user-visible overlay is available. The independent detector agent had no browser backend. The parent fallback opened a fresh browser tab and visually inspected the listing, but the browser API did not expose a mutable evaluation method for the required preflight, so injection and `[Human]` visibility were correctly skipped. Browser/source evidence was used instead.
-
-## Overall Impression
-
-The Workshop is already substantially better than a generic gallery: it communicates authorship, source code, API capabilities, secrets, revision history, reports, and discussion. The biggest opportunity is to turn that information into a deliberate trust sequence. Today the interface lets the user act first and understand safety later, especially on mobile.
-
-## What's Working
-
-- **State coverage is unusually strong.** Listing failures, stale data, loading skeletons, empty results, filter recovery, comment errors, pending actions, and destructive confirmations have explicit UI.
-- **Pre-install transparency is excellent.** API hosts, methods, configurable options, network scope, and credential requirements are visible instead of hidden behind a download.
-- **The new primitive layer is coherent.** Search, filters, menus, switches, dialogs, and code presentation share one restrained interaction vocabulary across light and dark themes.
-
-## Priority Issues
-
-### [P1] Safety context arrives after the install action on mobile
-
-**Why it matters:** Download and copy actions appear in the header, while source capabilities, credential requirements, and installation guidance live in an aside that drops below the long source and discussion sections under the desktop breakpoint. A first-time mobile user can commit before understanding what the widget contacts or what secrets it needs.
-
-**Fix:** Put a compact “Before you install” summary immediately below the header on small screens: API hosts, network scopes, credential count, and action/query counts. Keep the full sticky details panel on desktop.
-
-**Suggested command:** `$impeccable layout`
-
-### [P1] Primary button and own-comment contrast misses AA
-
-**Why it matters:** The requested theme's primary red with white foreground is about 3.4:1, below 4.5:1 for small text. The same pairing affects primary buttons and the author's comment bubbles.
-
-**Fix:** Darken the primary red or use a dark foreground in light mode, then verify default buttons and comment bubbles in both themes.
-
-**Suggested command:** `$impeccable colorize`
-
-### [P2] The listing's server-rendered fallback is blank
-
-**Why it matters:** Before hydration, the listing renders an empty block instead of preserving the page's hierarchy and indicating progress. This creates a visible dead zone on slower self-hosted deployments.
-
-**Fix:** Render the listing heading, toolbar silhouette, and shared skeleton cards as the `BrowserOnly` fallback, matching the detail page's loading treatment.
-
-**Suggested command:** `$impeccable harden`
-
-### [P2] Download, copy, source, and install compete for the same task
-
-**Why it matters:** “Download widget,” “Copy JSON,” a full source viewer, and a separate installation panel all appear as parallel paths. Users must infer the recommended workflow.
-
-**Fix:** Make “Download widget JSON” the single primary header action. Keep copy beside the source viewer and place the next import step directly beside or immediately after download.
-
-**Suggested command:** `$impeccable clarify`
-
-### [P2] Repeated metadata scaffolding creates visual noise
-
-**Why it matters:** Card shells, badges, icon tiles, uppercase tracked labels, and the changelog stripe make the detail page feel assembled from recipes and slow scanning.
-
-**Fix:** Flatten the widget details into a compact definition list, reserve badges for status, and remove the decorative changelog stripe.
-
-**Suggested command:** `$impeccable distill`
-
-## Persona Red Flags
-
-**Jordan, first-timer:** “Network scope,” queries, actions, options, and the manifest schema appear without inline explanation. Download versus copy has no stated recommendation. On mobile, credential and installation context arrives after source and discussion.
-
-**Sam, accessibility-dependent user:** Primary controls and author comment bubbles miss small-text contrast. Copy, optimistic votes, filter result changes, and successful report/edit completion do not expose explicit live-region behavior. Gallery controls and dots are below comfortable touch-target sizes.
-
-**Casey, distracted mobile user:** The most important safety panel falls to the bottom, while primary actions stay at the top. Long source and discussion content separate the decision from its explanation. The submit type selector remains dense at narrow widths.
-
-## Minor Observations
-
-- The internal installation guide uses an external-link icon.
-- The final publication action says “Submit” rather than “Publish submission.”
-- Dark-theme tokens are declared in two blocks, increasing drift risk.
-- Screenshot dots rely on opacity alone and lack `aria-current`.
-- Successful report and edit actions deserve a small confirmation instead of silent dismissal.
-
-## Questions to Consider
-
-- If source review is important enough to say “Review exactly what will be installed,” why can users download before seeing the capability and credential summary?
-- Is Workshop primarily a code catalog or a safety-conscious app store? The current action hierarchy tries to be both.
-- Should the successful end state be a downloaded file, or a confident handoff into Homarr with the next step already visible?

.oxfmtrc.json

@@ -3,15 +3,5 @@
   "printWidth": 120,
   "endOfLine": "lf",
   "sortPackageJson": true,
-  "ignorePatterns": [
-    "**/*.cjs",
-    "**/lang/**",
-    "static-data/**",
-    "CHANGELOG.md",
-    "apps/docs/.docusaurus/**",
-    "apps/docs/build/**",
-    "apps/docs/blog/**",
-    "packages/custom-widgets/src/core/component-catalog.generated.json",
-    "apps/docs/static/custom-widgets/component-catalog-v1.json"
-  ]
+  "ignorePatterns": ["**/*.cjs", "**/lang/**", "static-data/**", "CHANGELOG.md", "apps/docs/.docusaurus/**", "apps/docs/build/**", "apps/docs/blog/**"]
 }

.oxlintrc.json

@@ -30,15 +30,7 @@
   "options": {
     "reportUnusedDisableDirectives": "off"
   },
-  "ignorePatterns": [
-    "**/*.config.js",
-    "**/*.config.mjs",
-    "**/*.cjs",
-    "**/lang/*.d.json.ts",
-    ".next/**",
-    "apps/docs/.docusaurus/**",
-    "apps/docs/build/**"
-  ],
+  "ignorePatterns": ["**/*.config.js", "**/*.config.mjs", "**/*.cjs", "**/lang/*.d.json.ts", ".next/**", "apps/docs/.docusaurus/**", "apps/docs/build/**"],
   "settings": {
     "react": { "version": "19" }
   }

Dockerfile

@@ -22,7 +22,7 @@ COPY --parents ./packages/definitions/src ./
 # isolated linker, patches apply inside the virtual store (node_modules/.pnpm/...)
 # which IS created by pnpm fetch. The original hoisted linker is restored
 # before the install step so the final node_modules layout stays flat.
-RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store,sharing=locked \
+RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
     pnpm config set store-dir /pnpm/store && \
     sed -i 's/nodeLinker: hoisted/nodeLinker: isolated/' pnpm-workspace.yaml && \
     pnpm fetch --ignore-scripts && \
@@ -31,7 +31,7 @@ RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store,sharing=locked \
 # Install only from the fetched, committed lockfile so local and Docker builds
 # resolve the same dependency graph. Serial lifecycle builds avoid esbuild's
 # atomic binary replacement racing across the hoisted workspace (pnpm/pnpm#8200).
-RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store,sharing=locked \
+RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
     npm_config_nodedir=/usr/local pnpm install --recursive --offline --frozen-lockfile --child-concurrency=1
 
 COPY . .
@@ -40,6 +40,25 @@ ARG SKIP_ENV_VALIDATION='true'
 ARG CI='true'
 ARG DISABLE_REDIS_LOGS='true'
 ARG TARGETPLATFORM
+# Opt-in React profiling build + browser source maps, for React DevTools' Profiler
+# and for readable names in heap snapshots. See next.config.ts.
+ARG HOMARR_PROFILING='false'
+ENV HOMARR_PROFILING=${HOMARR_PROFILING}
+
+# React ships a separate profiling renderer; the production one omits the hooks
+# DevTools needs, which is what makes it report "Profiling not supported". Next only
+# swaps it via a webpack alias (create-compiler-aliases.js), so under Turbopack both
+# `next build --profile` and `reactProductionProfiling` silently produce a normal
+# build. Point the vendored client entry at the profiling bundle instead — the same
+# swap webpack's alias performs, done where Turbopack cannot miss it.
+RUN if [ "$HOMARR_PROFILING" = "true" ]; then \
+      set -e; \
+      entry=node_modules/next/dist/compiled/react-dom/client.js; \
+      grep -q "react-dom-client.production.js" "$entry" || { echo "profiling patch: unexpected $entry"; exit 1; }; \
+      sed -i "s#./cjs/react-dom-client.production.js#./cjs/react-dom-profiling.profiling.js#" "$entry"; \
+      grep -q "react-dom-profiling.profiling.js" "$entry" || { echo "profiling patch failed"; exit 1; }; \
+      echo "profiling patch applied to $entry"; \
+    fi
 
 RUN --mount=type=secret,id=TURBO_API,env=TURBO_API \
     --mount=type=secret,id=TURBO_TEAM,env=TURBO_TEAM \

PHASE2-FINDINGS.md

@@ -0,0 +1,28 @@
+# Performance findings
+
+This file grew past 1,200 lines covering server memory, client rendering, methodology and a long
+list of rejected ideas at once. It has been split by subject under [`docs/perf/`](./docs/perf/):
+
+| document | subject |
+| --- | --- |
+| [docs/perf/README.md](./docs/perf/README.md) | Headline results and the change-by-change ratio table |
+| [docs/perf/SERVER-MEMORY.md](./docs/perf/SERVER-MEMORY.md) | What the container's RAM is made of, layer by layer, and what reduced it |
+| [docs/perf/CLIENT-PERFORMANCE.md](./docs/perf/CLIENT-PERFORMANCE.md) | Dashboard cost in Chrome: DOM, fibers, images, paint |
+| [docs/perf/REJECTED.md](./docs/perf/REJECTED.md) | Ideas implemented, measured, and abandoned — with their numbers |
+| [docs/perf/METHODOLOGY.md](./docs/perf/METHODOLOGY.md) | The tools, and the measurement traps that produced wrong answers |
+
+## Result in one table
+
+Server RAM, merge-base `06724cfeb` vs this branch, two alternated runs per side, cgroup **anonymous**
+memory — the figure that counts against a container limit:
+
+| stage | before | after | change |
+| --- | --- | --- | --- |
+| **peak** | 376.6 MiB | **279.3 MiB** | **−26%** |
+| boot idle | 130.5 MiB | **62.4 MiB** | **−52%** |
+| after sign-in | 247.4 MiB | **142.9 MiB** | **−42%** |
+| dashboard loaded | 293.4 MiB | **170.4 MiB** | **−42%** |
+| 4 tabs, 2 boards | 366.5 MiB | **258.2 MiB** | **−30%** |
+| after 2 min idle soak | 323.7 MiB | **200.8 MiB** | **−38%** |
+
+No before/after range overlaps at any stage. Cost: **+18% CPU**, solid and non-overlapping.

PRODUCT.md

@@ -1,33 +0,0 @@
-# Product
-
-## Register
-
-product
-
-## Users
-
-Homarr is used by self-hosters and administrators who assemble dashboards for services running across home labs and private infrastructure. They need dense, reliable controls and status at a glance, with enough guidance to configure advanced features without hiding how they work.
-
-## Product Purpose
-
-Homarr provides one place to organize, observe, and operate self-hosted services. Success means a user can build a useful dashboard quickly, understand its state, recover from configuration errors, and extend it without requiring a bespoke Homarr feature for every service.
-
-## Brand Personality
-
-Direct, capable, and approachable. Copy should be concise and technical when precision matters, while the interface should remain familiar to users who are not developers.
-
-## Anti-references
-
-Avoid decorative admin dashboards, wizard flows that fight ordinary scrolling, hidden configuration magic, inconsistent controls, excessive modal usage, and interfaces that expose implementation complexity before the user needs it.
-
-## Design Principles
-
-1. Keep the user in control by making configuration and consequences visible.
-2. Prefer familiar product patterns and progressive disclosure over custom interaction concepts.
-3. Make simple tasks short without limiting advanced use cases.
-4. Isolate failures so one service or widget cannot disrupt the dashboard.
-5. Use the existing Mantine design language consistently across management and board surfaces.
-
-## Accessibility & Inclusion
-
-Target WCAG 2.2 AA. Support keyboard navigation, screen readers, visible focus, sufficient contrast, reduced motion, non-color status cues, responsive layouts, and actionable error messages.

apps/docs/.vscode/settings.json

@@ -1,3 +1,10 @@
 {
-  "cSpell.words": ["Homarr", "Lidarr", "Nextcloud", "Radarr", "Readarr", "Sonarr"]
-}
+    "cSpell.words": [
+        "Homarr",
+        "Lidarr",
+        "Nextcloud",
+        "Radarr",
+        "Readarr",
+        "Sonarr"
+    ]
+}

apps/docs/README.md

@@ -21,14 +21,8 @@ pnpm dev:docs
 
 # Or from within this directory
 pnpm dev
-
-# Point the docs at a local PocketBase instance
-WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs
 ```
 
-The standalone docs use `WORKSHOP_API_URL` for PocketBase and `HOMARR_WEBSITE_URL` for the public site origin. The old
-`WORKSHOP_URL` name is a deprecated one-release alias.
-
 ## Build
 
 ```bash
@@ -46,7 +40,7 @@ Uses oxlint and oxfmt (same as the rest of the monorepo):
 ```bash
 pnpm lint        # oxlint
 pnpm format      # oxfmt (check)
-pnpm format:fix    # oxfmt (fix)
+pnpm format -- --write  # oxfmt (fix)
 ```
 
 ## Typecheck
@@ -77,7 +71,7 @@ Each integration/widget doc follows a consistent pattern:
 The docs app has `@homarr/definitions` as a workspace dependency. You can import integration kinds, widget kinds, and other definitions directly:
 
 ```typescript
-import { IntegrationKind } from "@homarr/definitions";
+import { IntegrationKind } from '@homarr/definitions';
 ```
 
 This enables type-safe references to homarr domain concepts within documentation code.
@@ -96,15 +90,15 @@ pnpm verify:search
 
 ## Tech Stack
 
-| Layer          | Technology                                  |
-| -------------- | ------------------------------------------- |
+| Layer | Technology |
+|---|---|
 | Site generator | Docusaurus 3 (`@docusaurus/preset-classic`) |
-| Styling        | Tailwind CSS 4 + Docusaurus Infima          |
-| Icons          | `@tabler/icons-react`                       |
-| Diagrams       | Mermaid (`@docusaurus/theme-mermaid`)       |
-| Search         | Algolia DocSearch                           |
-| Analytics      | PostHog                                     |
-| Charts         | @nivo/line                                  |
+| Styling | Tailwind CSS 3 + Docusaurus Infima |
+| Icons | `@tabler/icons-react` |
+| Diagrams | Mermaid (`@docusaurus/theme-mermaid`) |
+| Search | Algolia DocSearch |
+| Analytics | PostHog |
+| Charts | @nivo/line |
 
 ## Contributing
 

apps/docs/components.json

@@ -1,24 +0,0 @@
-{
-  "$schema": "https://ui.shadcn.com/schema.json",
-  "style": "base-nova",
-  "rsc": false,
-  "tsx": true,
-  "tailwind": {
-    "config": "",
-    "css": "src/css/custom.css",
-    "baseColor": "mist",
-    "cssVariables": true,
-    "prefix": ""
-  },
-  "aliases": {
-    "components": "@/components",
-    "utils": "@/lib/utils",
-    "ui": "@/components/ui",
-    "lib": "@/lib",
-    "hooks": "@/hooks"
-  },
-  "iconLibrary": "tabler",
-  "rtl": false,
-  "menuColor": "default",
-  "menuAccent": "subtle"
-}

apps/docs/docs/advanced/command-line/_category_.json

@@ -1,4 +1,4 @@
 {
   "collapsed": true,
   "label": "Command line interface"
-}
+}

apps/docs/docs/advanced/command-line/fix-usernames/index.mdx

@@ -14,4 +14,4 @@ homarr fix-usernames
 
 This will convert all credential usernames to lowercase and update the database accordingly.
 
-![](./img/screenshot-cli.png)
+![](./img/screenshot-cli.png)

apps/docs/docs/advanced/command-line/index.mdx

@@ -1,7 +1,7 @@
 # Command line interface
 
 The Homarr image ships with a built-in recovery tool. This can be useful, if you do not have access to Homarr or if something is not working.
-Please note that the CLI is an _emergency tool_, not an API tool.
+Please note that the CLI is an *emergency tool*, not an API tool.
 
 :::caution
 
@@ -12,10 +12,10 @@ You should also create a backup of the database, in case you break something.
 
 ## Execute CLI with Docker
 
-1. Execute `docker ps | grep homarr` on the root system with Docker to find the container ID of your Homarr container.
-2. Run `docker exec -it <container-id> /bin/bash homarr <your-command-goes-here>`. \
-   Replace `<container-id>` with your container ID from step 1. \
-   Replace `<your-command-goes-here>` with the command you want to execute (see sub-pages).
+1. Execute ``docker ps | grep homarr`` on the root system with Docker to find the container ID of your Homarr container.
+2. Run ``docker exec -it <container-id> homarr <your-command-goes-here>``. \
+Replace ``<container-id>`` with your container ID from step 1. \
+Replace ``<your-command-goes-here>`` with the command you want to execute (see sub-pages).
 
 ## Execute CLI with QNAP
 

apps/docs/docs/advanced/command-line/integrations/index.mdx

@@ -7,7 +7,6 @@ This guide requires that you understand [how to access the CLI](../).
 :::
 
 Using these commands, you can manage the integrations from the CLI:
-
 ```bash
 Group of commands to manage integrations
 
@@ -44,7 +43,7 @@ Flags:
 ## Delete Integration
 
 - Requires a database connection
-- Requires one parameter: `id` or `name`
+- Requires one parameter: ``id`` or ``name``
 - Deletes an integration permanently from the database
 
 ```bash
@@ -58,4 +57,4 @@ Flags:
   -n, --name string   Name of the integration
   -h, --help          help for integrations delete
   -v, --version       version for homarr-cli
-```
+```

apps/docs/docs/advanced/command-line/password-recovery/index.mdx

@@ -12,8 +12,8 @@ All sessions for that user will be terminated and the user must re-login.
 
 ![](./img/screenshot-cli.png)
 
-Using the `--username` parameter, you can specify who you want to reset the password for.
+Using the ``--username`` parameter, you can specify who you want to reset the password for.
 Executing the command will create a new random password, update the database and display the new password.
 All sessions for this user will be terminated and they must re-login.
 
-![](./img/screenshot-cli-result.png)
+![](./img/screenshot-cli-result.png)

apps/docs/docs/advanced/command-line/users/index.mdx

@@ -7,7 +7,6 @@ This guide requires that you understand [how to access the CLI](../).
 :::
 
 Using these commands, you can manage the users from the CLI:
-
 ```bash
 Group of commands to manage users
 
@@ -43,7 +42,7 @@ yj52ek5cyb6du4bp4osbkjry        admin           xxxx@example.com
 ## Delete User
 
 - Requires a database connection
-- Requires one parameter: `id` or `username`
+- Requires one parameter: ``id`` or ``username``
 
 ```bash
 Delete a user by id or username
@@ -77,4 +76,4 @@ Flags:
   -p, --password          New password
   -h, --help              help for users update-password
   -v, --version           version for homarr-cli
-```
+```

apps/docs/docs/advanced/development/_category_.json

@@ -1,8 +1,9 @@
 {
-  "label": "Developer guides",
-  "position": 6,
-  "collapsed": true,
-  "link": {
-    "type": "generated-index"
+    "label": "Developer guides",
+    "position": 6,
+    "collapsed": true,
+    "link": {
+      "type": "generated-index"
+    }
   }
-}
+  

apps/docs/docs/advanced/development/getting-started.mdx

@@ -8,121 +8,74 @@ tags:
 sidebar_position: 1
 ---
 
-## Set up your development environment
+## Setting up your development environment
+
+This guide will help you set up your development environment to start contributing to homarr.
 
 ### Prerequisites
 
 - **Node.js 24.18 or newer**: You can download it from the [official website](https://nodejs.org/).
-- **Corepack**: Run `corepack enable` so the repository selects its pinned pnpm 11 version.
+- **Corepack**: Run `corepack enable` so the repository selects its pinned pnpm version.
 - **Git**: You can download it from the [official website](https://git-scm.com/).
 - **Docker or Docker Desktop**: Required for the Redis service and the developer Docker CLI.
 - **Go 1.25+**: Required only for the developer Docker CLI. You can download it from the [official website](https://go.dev/).
 - **GitHub CLI**: Required only for pull-request image features. Install it from the [official website](https://cli.github.com/), then authenticate with `gh auth login`.
 
-The versions in the root `package.json` are the supported baseline. Let Corepack select the repository version instead
-of installing an unrelated global pnpm:
+### Setting up the project
 
-```sh
-corepack enable
-corepack install
-pnpm install --frozen-lockfile
-```
+1. Fork the repository by clicking on the "Fork" button on the top right corner of the repository page.
 
-### Run the Homarr application
+![Fork button](./img/fork.png)
 
-1. Copy `.env.example` to `.env`.
-2. Set `DB_URL` to an absolute writable SQLite file path.
-3. Keep Redis and the optional local databases running in one terminal.
-4. Apply migrations and start Next.js in another terminal.
+2. Clone the repository to your local machine with `git clone`. You can find the url to use by clicking on the "Code" button on the top right corner of your forks repository page.
 
-```sh
-cp .env.example .env
-```
+![Clone button](./img/clone.png)
 
-Terminal 1:
+3. Change directory to the project folder with `cd homarr`.
 
-```sh
-pnpm docker:dev
-```
+4. Install the dependencies with `pnpm install`.
 
-Terminal 2:
+5. Create `.env` from `.env.example`. In a POSIX shell, run `cp .env.example .env`; in PowerShell, run `Copy-Item .env.example .env`. Set `DB_URL` to an absolute path for your SQLite file.
 
-```sh
-pnpm db:migration:sqlite:run
-pnpm dev
-```
+6. Start Redis in the background with `pnpm docker:dev:up` if your development workflow needs it.
 
-The infrastructure command remains in the foreground. Open `http://127.0.0.1:3000`; the first user created through
-Homarr becomes the instance administrator.
-Use `pnpm docker:dev:up` instead when you only need Redis in the background. Running the migration also seeds the
-default data; use `pnpm db:seed` to seed it explicitly later.
+7. Create or update the database with `pnpm db:migration:sqlite:run`. This also seeds the default data. To run the seed explicitly later, use `pnpm db:seed`.
 
-### Run PocketBase and documentation
+8. Start the development server with `pnpm dev` and wait for a message that says `✓ Ready in 10.7s`
 
-Start PocketBase in another terminal:
+9. Open your browser and navigate to [http://localhost:3000](http://localhost:3000). (Loading the page might take up to 2 minutes the first time)
 
-```sh
-cp apps/workshop/.env.example apps/workshop/.env
-docker compose --env-file apps/workshop/.env -f apps/workshop/docker-compose.yml up --build workshop
-```
+### Useful npm scripts
 
-Then start Docusaurus in a third terminal:
+#### During development
 
-```sh
-WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs
-```
+- `pnpm dev`: Start the Next.js development server.
+- `pnpm dev:benchmark`: Run the local authenticated-board benchmark. Set `DEV_BENCHMARK_BOARD_URL` and
+  `DEV_BENCHMARK_STORAGE_STATE`; readiness-only measurements require the explicit `--smoke` flag and are not
+  suitable for performance claims.
+- `pnpm dev:cli -- dev`: Browse and run local images and remote pull-request images.
+- `pnpm dev:cli -- build <name>`: Build the current checkout as `homarr:<name>`.
+- `pnpm dev:cli -- build --pr <number>`: Build a pull request locally from a temporary checkout.
+- `pnpm dev:cli -- rebuild <name>`: Rebuild a local image from its recorded checkout or pull request.
+- `pnpm dev:cli:install`: Optionally install the developer CLI as a `homarr` binary.
+- `pnpm cli`: Run cli commands.
+- `pnpm db:migration:sqlite:run`: Run the migrations to create or update the sqlite db file.
+- `pnpm db:seed`: Explicitly seed the default database data.
+- `pnpm docker:dev:up`: Start the Redis development service in the background.
+- `pnpm db:migration:sqlite:generate`: Generate a new migration file for the sqlite db. Also works with `mysql`.
+- `pnpm db:studio`: Open a visual studio for the database.
+- `pnpm package:new`: Create a new package in the monorepo.
 
-PocketBase runs on port 8090 and Docusaurus on port 3003. Stopping the services preserves the PocketBase volume.
+#### Checking code quality
 
-Open `http://127.0.0.1:8090/_/` and create the first PocketBase superuser. The Workshop UI is available at
-`http://127.0.0.1:3003/workshop`.
+- `pnpm lint`: Run the linter to check for code quality issues.
+- `pnpm format:fix`: Run the formatter to fix code style issues.
+- `pnpm test`: Run the tests. You can also use `pnpm test:ui` to get a UI for the tests.
+- `pnpm typecheck`: Run the typescript type checker.
 
-Point Homarr at the local services with:
+#### Building the project
 
-```dotenv
-HOMARR_WEBSITE_URL=http://127.0.0.1:3003
-WORKSHOP_API_URL=http://127.0.0.1:8090
-WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop
-```
-
-Restart `pnpm dev` after changing `.env`. GitHub OAuth is optional locally. See
-[`apps/workshop/README.md`](https://github.com/homarr-labs/homarr/blob/HEAD/apps/workshop/README.md) for OAuth,
-Workshop moderator promotion, logs, tests, backup, restore, stopping, and intentional volume reset.
-
-### URL testing
-
-Docusaurus reads `HOMARR_WEBSITE_URL` and `WORKSHOP_API_URL` when it starts or builds. Homarr also reads
-`WORKSHOP_WEB_URL` when its server starts, so these values do not rely on `NEXT_PUBLIC_*` build variables. Test a
-separate API origin before release:
-
-```sh
-HOMARR_WEBSITE_URL=http://127.0.0.1:3003 \
-WORKSHOP_API_URL=http://127.0.0.1:8090 \
-WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop \
-pnpm dev:docs
-```
-
-### Useful commands
-
-- `pnpm dev` — Next.js on port 3000.
-- `pnpm dev:benchmark` — authenticated-board benchmark; readiness-only `--smoke` runs are not performance claims.
-- `pnpm dev:cli -- dev` — browse and run local images and remote pull-request images.
-- `pnpm dev:cli -- build <name>` — build the current checkout as `homarr:<name>`.
-- `pnpm dev:cli -- build --pr <number>` — build a pull request from a temporary checkout.
-- `pnpm dev:cli -- rebuild <name>` — rebuild an image from its recorded checkout or pull request.
-- `pnpm dev:cli:install` — optionally install the developer CLI as a `homarr` binary.
-- `pnpm dev:docs` — Docusaurus only on port 3003.
-- `pnpm docker:workshop` — local PocketBase through Docker Compose.
-- `pnpm docker:dev:up` — Redis development service in the background.
-- `pnpm cli` — Homarr operations CLI.
-- `pnpm db:migration:sqlite:run` — create or update a SQLite database.
-- `pnpm db:seed` — seed the default database data explicitly.
-- `pnpm db:studio` — inspect the database.
-- `pnpm format` / `pnpm format:fix` — check or apply oxfmt.
-- `pnpm lint` / `pnpm lint:fix` — check or apply oxlint.
-- `pnpm typecheck` — typecheck all workspaces.
-- `pnpm test` — unit and contract suites.
-- `pnpm test:workshop` — disposable Workshop integration suite.
-- `pnpm build` — production monorepo build.
-- `docker build -t homarr .` — build a production Docker image.
-- `docker run -p 7575:7575 -e SECRET_ENCRYPTION_KEY='your_64_character_hex_string' homarr:<name>` — run it.
+- `pnpm build`: Build the project for production.
+- `pnpm dev:cli -- build <name>`: Build a `homarr:<name>` image and record its checkout for later rebuilds.
+- `docker build -t homarr .`: Build a docker image for the project.
+- `docker run -p 7575:7575 -e SECRET_ENCRYPTION_KEY='your_64_character_hex_string' homarr:<name>`: Run the created docker image.

apps/docs/docs/advanced/development/kubernetes.mdx

@@ -132,4 +132,4 @@ This command should return CPU and memory usage statistics for each node.
 
 ## Conclusion
 
-You have successfully set up a multi-node Kubernetes cluster using kind and installed the Metrics Server for monitoring resource usage. This setup is useful for local development and testing Kubernetes workloads before deploying them to a production environment.
+You have successfully set up a multi-node Kubernetes cluster using kind and installed the Metrics Server for monitoring resource usage. This setup is useful for local development and testing Kubernetes workloads before deploying them to a production environment.

apps/docs/docs/advanced/environment-variables/index.mdx

@@ -25,17 +25,14 @@ This is especially useful for [docker secrets](https://docs.docker.com/engine/sw
 Using the `PUID` and `PGID` will require you to set the correct permissions on the mounted volumes and if used the docker socket. See more in the [Running as a different user](/docs/advanced/running-as-different-user) documentation.
 :::
 
-| Environment Variable     | Description                                                                                                                                                                                                                            | Possible values                     | Default                       |
-| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ----------------------------- |
-| `PUID`                   | User ID to run the container as                                                                                                                                                                                                        | Any valid user ID                   | `0`                           |
-| `PGID`                   | Group ID to run the container as                                                                                                                                                                                                       | Any valid group ID                  | `0`                           |
-| `LOG_LEVEL`              | Log level to use                                                                                                                                                                                                                       | `debug` / `info` / `warn` / `error` | `info`                        |
-| `NO_EXTERNAL_CONNECTION` | Disables Homarr's internet-backed requests, including update checks, weather, and RSS feeds                                                                                                                                            | `true` or `false`                   | `false`                       |
-| `ENABLE_DNS_CACHING`     | Enables dns caching. Enabled by default, but if you experience issues with IPv6 or static IPs, see [#4006](https://github.com/homarr-labs/homarr/issues/4006) or disable this flag                                                     | `true` or `false`                   | `true`                        |
-| `HOMARR_DISABLE_IPV6`    | Disables the IPv6 listener of the internal nginx proxy, even when the host supports IPv6. IPv6 is normally disabled automatically when the host has no IPv6 configured. See [#4596](https://github.com/homarr-labs/homarr/issues/4596) | `true` or `false`                   | `false`                       |
-| `HOMARR_WEBSITE_URL`     | Main Homarr documentation/site base used by runtime links. Must be an absolute HTTP(S) URL.                                                                                                                                            | HTTP(S) URL                         | `https://homarr.dev`          |
-| `WORKSHOP_API_URL`       | PocketBase API used by Homarr and standalone documentation.                                                                                                                                                                            | HTTP(S) URL                         | `HOMARR_WEBSITE_URL`          |
-| `WORKSHOP_WEB_URL`       | Public Workshop page opened from Homarr.                                                                                                                                                                                               | HTTP(S) URL                         | `HOMARR_WEBSITE_URL/workshop` |
+| Environment Variable     | Description                                                                                                                                                                                                                            | Possible values                     | Default |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ------- |
+| `PUID`                   | User ID to run the container as                                                                                                                                                                                                        | Any valid user ID                   | `0`     |
+| `PGID`                   | Group ID to run the container as                                                                                                                                                                                                       | Any valid group ID                  | `0`     |
+| `LOG_LEVEL`              | Log level to use                                                                                                                                                                                                                       | `debug` / `info` / `warn` / `error` | `info`  |
+| `NO_EXTERNAL_CONNECTION` | Disables Homarr's internet-backed requests, including update checks, weather, and RSS feeds                                                                                                                                            | `true` or `false`                   | `false` |
+| `ENABLE_DNS_CACHING`     | Enables dns caching. Enabled by default, but if you experience issues with IPv6 or static IPs, see [#4006](https://github.com/homarr-labs/homarr/issues/4006) or disable this flag                                                     | `true` or `false`                   | `true`  |
+| `HOMARR_DISABLE_IPV6`    | Disables the IPv6 listener of the internal nginx proxy, even when the host supports IPv6. IPv6 is normally disabled automatically when the host has no IPv6 configured. See [#4596](https://github.com/homarr-labs/homarr/issues/4596) | `true` or `false`                   | `false` |
 
 ## Authentication
 
@@ -109,12 +106,6 @@ External redis is currently not supported with Proxmox Community Scripts
 The advanced deployments environment variables should only be used if you know what you are doing.
 :::
 
-| Environment Variable     | Description                                                                                                                                                                                                       |
-| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `DB_MIGRATIONS_DISABLED` | Disable db migrations. For example for helm charts.                                                                                                                                                               |
-| `WORKSHOP_PUBLIC_ORIGIN` | Origin used in PocketBase-generated links and email. It must be set explicitly in production and must match the externally reachable Workshop origin.                                                             |
-| `PB_ALLOWED_ORIGINS`     | Browser origins accepted by PocketBase. Use `*` for the central public community so arbitrary self-hosted Homarr instances can use the API and OAuth; private staging may use a comma-separated origin allowlist. |
-
-All public URL variables reject non-HTTP protocols, embedded credentials, query strings, and fragments, and normalize
-trailing slashes when Homarr or Docusaurus starts. The Docusaurus-only `WORKSHOP_URL` name is accepted as a deprecated alias for
-`WORKSHOP_API_URL` for one release. `WORKSHOP_API_URL` takes precedence.
+| Environment Variable     | Description                                        |
+| ------------------------ | -------------------------------------------------- |
+| `DB_MIGRATIONS_DISABLED` | Disable db migrations. For example for helm charts |

apps/docs/docs/advanced/keyboard-shortcuts/index.mdx

@@ -6,11 +6,11 @@ tags:
 
 Homarr has the following keyboard shortcuts:
 
-| Shortcut    | Description          |
-| ----------- | -------------------- |
+| Shortcut | Description |
+| -------- | ----------- |
 | `MOD` + `K` | Opens the search bar |
-| `MOD` + `J` | Toggles Dark Mode    |
-| `MOD` + `E` | Toggles Edit Mode    |
+| `MOD` + `J` | Toggles Dark Mode |
+| `MOD` + `E` | Toggles Edit Mode |
 
 :::tip
 

apps/docs/docs/advanced/proxy/index.mdx

@@ -9,17 +9,16 @@ tags:
   - Security
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
 
 ## Allowing self-signed certificates
-
 Some users may come across a barrier, where they're unable to receive a 200 response from the Ping widget for some apps, while using self-signed certificates or a local certificate authory.
 
 :::note What's going on?
 
 Homarr is trying to communicate to your apps via the integrations.
-It usually doesn't matter if Homarr is running on `http` or `https`.
+It usually doesn't matter if Homarr is running on ``http`` or ``https``.
 Your apps have a self-signed certificate - Homarr will recognize that the certificate was signed by an unknown authority and requests will be blocked.
 
 :::
@@ -29,9 +28,8 @@ To allow self-signed certificates, you can configure them on the certificates ma
 ## Securing Homarr with Traefik
 
 Copying the configuration straight from the docker-compose file won't work if you are running Homarr behind Traefik, such as a Portainer setup, or docker-swarm. In that case, you should use the following slightly modified configuration:
-
 ```yaml
-version: "3"
+version: '3'
 services:
   homarr:
     container_name: homarr
@@ -55,12 +53,11 @@ networks:
     external: true
 ```
 
-<br />
+<br/>
 
 A sample Traefik docker-compose.yml using Cloudflare for certificate generation that works with the configuration above would be:
-
 ```yaml
-version: "3"
+version: '3'
 
 apps:
   traefik:
@@ -106,6 +103,7 @@ networks:
     external: true
 ```
 
+
 :::tip
 Of particular note here is that both configurations explicitly define which network they are using, in this case "proxy", but it can be named anything. It just has to be the same across all apps for which Traefik is serving as a proxy. These are marked as external because the proxy network was manually created by running: `docker network create proxy` but this might be unnecessary depending on HOW exactly you are running Traefik. For example, if running [Traefik with Portainer](https://docs.portainer.io/advanced/reverse-proxy/traefik#deploying-in-a-docker-standalone-scenario), you can follow their official docs on how to set up Traefik and Portainer together, and you can just focus on the Homarr docker labels instead.
 :::
@@ -116,6 +114,7 @@ If you are using Caddy as the reverse proxy for your setup, your `docker-compose
 
 ```yaml
 services:
+  
   # <-- [Homarr installation]
 
   caddy:
@@ -141,17 +140,14 @@ networks:
   proxy:
     external: true
 ```
-
 :::important
 Homarr needs to be on the same network so you will need to add the following property to your homarr install:
-
 ```yaml
 homarr:
   ...
   networks:
     - proxy
 ```
-
 :::
 
 Next, create a file named `Caddyfile` at the same level as your `docker-compose.yml` file with the following content:

apps/docs/docs/advanced/running-as-different-user/index.mdx

@@ -8,7 +8,7 @@ tags:
   - PUID
 ---
 
-By default the container is running with user `root` and group `root`.
+By default the container is running with user `root` and group `root`. 
 You can change the user and group by using the `PUID` and `PGID` environment variables.
 Important to note is, that you'll also need to change the permissions for the mounted directories accordingly.
 
@@ -32,11 +32,11 @@ services:
     volumes:
       - ./homarr/appdata:/appdata
     environment:
-      - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
-      - PUID=1000
-      - PGID=1000
+        - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
+        - PUID=1000
+        - PGID=1000
     ports:
-      - "7575:7575"
+      - '7575:7575'
 ```
 
 After that you'll need to create the appdata directory and set the correct permissions:
@@ -76,11 +76,11 @@ services:
       - /var/run/docker.sock:/var/run/docker.sock
       - ./homarr/appdata:/appdata
     environment:
-      - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
-      - PUID=1000
-      - PGID=999
+        - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
+        - PUID=1000
+        - PGID=999
     ports:
-      - "7575:7575"
+      - '7575:7575'
 ```
 
 And set the permissions for the mounted directories:
@@ -90,4 +90,4 @@ mkdir -p ./homarr/appdata
 chown -R 1000:999 ./homarr/appdata
 ```
 
-Important here is that the group ID is set to `999` as we created the `docker` group with this ID.
+Important here is that the group ID is set to `999` as we created the `docker` group with this ID.

apps/docs/docs/advanced/single-sign-on/index.mdx

@@ -10,21 +10,20 @@ tags:
   - Active Directory
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
 
 # Single Sign On
 
 Homarr supports multiple authentication options, from internal userbase (credentials), to LDAP (with Active directory support), and OIDC.
 
 ### Auth configuration common variables
-
-| Environment Variable     | Description                                                                                                                                                                                                                                                                                                             | Default Value |
-| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- |
-| AUTH_PROVIDERS           | Select Which provider to use between _credentials_, _ldap_ and _oidc_. <br /> Multiple providers can be enabled with by separating them with `,`, (ex. `AUTH_PROVIDERS=credentials,oidc`, it is highly recommended to just enable one provider).                                                                        | credentials   |
-| AUTH_LOGOUT_REDIRECT_URL | URL to redirect to after clicking logging out.                                                                                                                                                                                                                                                                          | ---           |
-| AUTH_SESSION_EXPIRY_TIME | Time for the session to time out. Can be set as pure number, which will automatically be used in seconds, or followed by s, m, h or d for seconds, minutes, hours or days. (ex: "30m")                                                                                                                                  | "30d"         |
-| AUTH_COOKIE_PREFIX       | Prefix used for all authentication cookies (session, csrf, callback, pkce, state, nonce). Change this if you run another Auth.js/NextAuth app on the same hostname as Homarr (browsers scope cookies by host, not by port) to avoid cookie name collisions. Only letters, numbers, hyphens and underscores are allowed. | `homarr`      |
+| Environment Variable      | Description | Default Value |
+|---------------------------|-------------|---------------|
+| AUTH_PROVIDERS             | Select Which provider to use between *credentials*, *ldap* and *oidc*. <br /> Multiple providers can be enabled with by separating them with `,`, (ex. `AUTH_PROVIDERS=credentials,oidc`, it is highly recommended to just enable one provider).  |  credentials  |
+| AUTH_LOGOUT_REDIRECT_URL  | URL to redirect to after clicking logging out.  | --- |
+| AUTH_SESSION_EXPIRY_TIME  | Time for the session to time out. Can be set as pure number, which will automatically be used in seconds, or followed by s, m, h or d for seconds, minutes, hours or days. (ex: "30m") | "30d"  |
+| AUTH_COOKIE_PREFIX  | Prefix used for all authentication cookies (session, csrf, callback, pkce, state, nonce). Change this if you run another Auth.js/NextAuth app on the same hostname as Homarr (browsers scope cookies by host, not by port) to avoid cookie name collisions. Only letters, numbers, hyphens and underscores are allowed. | `homarr`  |
 
 <Tabs>
   <TabItem value="credentials" label="Credentials Provider" default>

apps/docs/docs/advanced/styling/index.mdx

@@ -19,14 +19,12 @@ Homarr uses https://mantine.dev/ under the hood. You can change the look & feel
 using custom CSS, that extends or overwrites the styles from Mantine.
 
 ## Getting into CSS
-
 If you don't have any experience with CSS,
 we strongly recommend you to go through the courses here: https://www.w3schools.com/css/.
 Due to the infinite scenarios and setups possible with custom CSS,
 our support team will not provide any support with your own written CSS.
 
 ## Limitations and dangers
-
 When using custom CSS, you can break the page or certain functionalities.
 Although CSS can improve the design & feel of the page, it **<ins>cannot do any of the following</ins>**:
 
@@ -35,23 +33,21 @@ Although CSS can improve the design & feel of the page, it **<ins>cannot do any
 - Completely revamp the design of the page, only smaller changes are possible
 
 Here are some dangers of using custom CSS:
-
 - Updates may contain breaking changes in the structure, built-in styling or how styling is processed. Therefore,
-  custom CSS may break unexpectedly without any warning
+custom CSS may break unexpectedly without any warning
 - Custom CSS may make certain elements invisible or not possible to click / interact with
 - Custom CSS could make readability and accessibility worse for impaired people
 
 ## How to inspect the page
-
-When styling the page, you can use the `Inspector` to inspect elements on the page and try out styles.
+When styling the page, you can use the ``Inspector`` to inspect elements on the page and try out styles.
 This may vary depending on your browser and operating system, but the workflow usually goes like this:
 
 - Open the Homarr page
-- Press `Ctrl` + `Shift` + `I` at the same time.
-  Alternatively, right-click on the page and choose `Inspect` or `Inspect element`.
-- Open the tab `Elements` if it isn't open yet.
+- Press ``Ctrl`` + ``Shift`` + ``I`` at the same time.
+Alternatively, right-click on the page and choose ``Inspect`` or ``Inspect element``.
+- Open the tab ``Elements`` if it isn't open yet.
 - Search the element you want to change in the DOM tree or use the element picker (usually at the top left)
-  to select it by clicking on the page.
+to select it by clicking on the page.
 - Experiment by changing the CSS code on the right side
 
 When writing custom CSS, it is important to also remember or create a selector, which tells the browser
@@ -59,19 +55,17 @@ which element to apply the styles to. If you accidentally broke something or wan
 simply reload the page.
 
 ## Using Homarr's classes
-
 Homarr's elements will already have a lot of classes and styles pre-applied.
 You can reuse those classes to apply additional styles or overwrite them.
-When overwriting, remember to add the `!important` flag to your CSS property to tell the browser to use our instruction instead.
+When overwriting, remember to add the ``!important`` flag  to your CSS property to tell the browser to use our instruction instead.
 
-Classes with random number suffixes, such as `mantine-Card-x2fske`, should be avoided, since those are dynamic
+Classes with random number suffixes, such as ``mantine-Card-x2fske``, should be avoided, since those are dynamic
 CSS classes that will change with every build. This means, every time you update Homarr,
 your styles will no longer apply to them
 
 ## Defining custom classes for widgets
-
 If you want to apply the styles only for one widget, you can define custom class names only for that widget.
-To do that, enter edit mode on your board, click the three dots of your widget, click `Edit item` and click `Advanced options`.
+To do that, enter edit mode on your board, click the three dots of your widget, click ``Edit item`` and click ``Advanced options``.
 Then, you can enter as many custom classes as you'd like:
 
 ![](./img/widget-custom-classes.png)
@@ -79,7 +73,6 @@ Then, you can enter as many custom classes as you'd like:
 To save them, click `Save changes` on both modals and exit edit mode.
 
 ## Where to enter custom CSS
-
 After you wrote your custom CSS, it is time to permanently save it, so you don't need to use the inspector anymore.
 To do this, enter the board settings:
 
@@ -91,12 +84,11 @@ Here you can enter your CSS code, which will be applied on the respective board
 ![](./img/custom-css-setting.png)
 
 ## Using variables
-
 You can also change the values of the theme variables, which are located here: https://mantine.dev/styles/css-variables-list/.
 To do this, see the following example CSS:
 
 ```css
 :root {
-  --mantine-primary-color-filled: #ffbb00;
+    --mantine-primary-color-filled: #ffbb00;
 }
-```
+```

apps/docs/docs/community/donate.mdx

@@ -7,15 +7,12 @@ tags:
 ---
 
 # Donate
-
 ## Why to donate
-
 Our team of 4 developers is working on Homarr in their free time.
 Homarr has become a big part of our daily things we work on - and therefore we invest a lot of time into maintaining Homarr,
 providing support and implementing new features.
 We also incur monetary costs while developing Homarr for the tools that we need.
 A few examples include:
-
 - Renting for a Cloud VPS for our cloud services (status page, monitoring, email, analytics, [demo instance](https://demo.homarr.dev/), ...)
 - Paying for (IDE-) licenses
 
@@ -23,7 +20,6 @@ Using a donation, you help us to cover these expenses and enable the development
 Homarr is completely free to use. We'd highly appreciate if you consider donating, especially if you use Homarr in a commercial environment.
 
 ## Where to donate
-
 We accept donations on our official [OpenCollective](https://opencollective.com/homarr).
 You may also sponsor us directly by providing a useful service / product to us other means.
-You can get into contact with us [here](/docs/community/get-in-touch).
+You can get into contact with us [here](/docs/community/get-in-touch).

apps/docs/docs/community/faq.mdx

@@ -5,57 +5,43 @@ tags:
   - Help
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
 
 ### Can I install Homarr on a Raspberry Pi?
-
 Yes, Homarr is compatible with the architecture of the Raspberry Pi. Have a look in our <a href="/docs/category/installation-1">installation guide</a> on how to do so.
 
 ### I have a suggestion / idea for improvement or want to report a bug
-
 You can report issues, suggestions, or ideas for improvements <a href="https://github.com/homarr-labs/homarr/issues/new/choose">here</a>.
 
 ### Can I use my own custom icons for apps?
-
 Yes, check out our guide on <a href="/docs/advanced/customizations/icons">how to add your custom icons</a>.
 
 ### Some of my online icons are not working (anymore)
-
 It seems the `cdn.jsdelivr.net` database of icon sometimes appear in the lists for DNS-Holes (PiHole, AdGuard Home...). <br />
 So make sure to manually whitelist this address.
 
 ### Can I add my own widgets? Do I need programming skills?
+We have decided, not to support custom widgets, until Homarr is in a stable and highly polished state.
+Enabling users to write their own widgets is easy at the first glance, but there are some major issues with it:
 
-Yes. A [Custom Widget](/docs/management/custom-widgets) can read a public or private HTTP API.
+- There are mainly two options for adding plugins or custom widgets to Homarr. The first option is, to allow and inject custom code in Homarr. Apps like Nextcloud can do this easily, because they use the Runtime to render all components of the application (In reality, the process is still a bit more complicated). In contrast, Homarr is using Next.js - a framework that needs to be compiled in production. That means, that each time you would modify a custom widget or plugin, the app would have to be restarted. There are options to avoid this, but they are quite flakey and bring disadvantages in our experience. The second option is, to write widgets declaratively instead of imperatively. This way, we would be able to render and modify widgets without any restarting at all. However, we'd have to write our own interpreter for said declarative schema. This is totally possible, but requires a lot of planning and architecture design to function properly. The required work to implement either option is therefore quite substantial.
+- Custom widgets would need to be able to request data, so they work properly. We use tRPC for this. Many APIs use different formats and we'd have to convert and read those.
+- Using custom widgets, one could easily create harmful widgets, leak your personal data (potentially including your tokens) and trick your users. A proper implementation (eg. official plugin store, where we can ban harmful widgets from) would resolve this problem to a certain extent, but again requires additional work and time to be put in.
 
-It can show responsive Mantine JSX. It can also use widget options and actions with board permission checks.
-
-Custom JSX v2 is the only Custom Widget format. Write the JSON and JSX in the workbench.
-
-You can also use the AI copy prompt. An MCP agent can validate and preview a definition before it saves the definition.
-
-The workbench reads a pasted AI response. It shows request capabilities and redacted diagnostics.
-
-A template cannot import packages or run arbitrary JavaScript. It cannot call browser `fetch`.
-
-Named requests use the Homarr server. The server applies board permissions and the network policy.
-
-Before installation, examine the origins, methods, permissions, and actions. Use the same review before publication.
+If you still want to add a widget, please consider to contribute it directly to Homarr. For that, basic programming skills are required. Our [Developer Guides](/docs/advanced/development/getting-started) explain this even more detailed.
 
 ### Is it secure to expose Homarr to the web?
 
-Yes, since v0.14.0, we are confident that Homarr is secure enough to be exposed to the web.
+Yes, since v0.14.0, we are confident that Homarr is secure enough to be exposed to the web. 
 Make sure to enable the "allow anonymous access" [option in the settings](/docs/management/boards#access-control), if you want to allow people without an account to be able to see your dashboard (not edit)
 
 ### How do I open the console / log?
-
 There are two different sources of information:
-
 - console: This is your client (browser). It can tell us, if there is an issue on the client (crash, bug, ...).
 - log: This is your server. It will tell us, if there are issues with connections for the integrations, crashes and errors.
 
-Both variants _can_ contain personal data. It's recommended, that you don't post them publicly or remove personal data from it.
+Both variants *can* contain personal data. It's recommended, that you don't post them publicly or remove personal data from it.
 
 <Tabs>
   <TabItem value="apple" label="Read console" default>
@@ -63,45 +49,39 @@ Both variants _can_ contain personal data. It's recommended, that you don't post
 > Note: This will not work on most mobile browsers.
 
 Open your browser and ensure, that Homarr is your current tab.
-Press `CTRL` + `SHIFT` + `I` on your keyboard. If this shortcut doesn't work, please use one of the alternatives: https://developer.chrome.com/docs/devtools/open/.
-Click on `Console` in the new window, that opened. There, you should see white, orange and sometimes red messages. You can use the Windows Snip & Sketch tool (or your respective tool on Linux / MacOS) to screenshot those messages.
+Press ``CTRL`` + ``SHIFT`` + ``I`` on your keyboard. If this shortcut doesn't work, please use one of the alternatives: https://developer.chrome.com/docs/devtools/open/.
+Click on ``Console`` in the new window, that opened. There, you should see white, orange and sometimes red messages. You can use the Windows Snip & Sketch tool (or your respective tool on Linux / MacOS) to screenshot those messages.
 
 > Please never execute any commands in the console. Scammers are using the console to let you execute harmful commands. If you want to resolve an issue in Homarr, **you'll never have to execute any commands here**
 
   </TabItem>
   <TabItem value="orange" label="Read log">
 
-This depends on your installation method. If you use Unraid, you can simply click on the App and on `Log`. If you have a bare Docker install, use `docker container logs homarr`. If you used a different name than `homarr` for your container, you need to replace said argument. Here is some additional information about the command: https://geekflare.com/check-docker-logs/.
+This depends on your installation method. If you use Unraid, you can simply click on the App and on ``Log``. If you have a bare Docker install, use ``docker container logs homarr``. If you used a different name than ``homarr`` for your container, you need to replace said argument. Here is some additional information about the command: https://geekflare.com/check-docker-logs/.
 
   </TabItem>
 </Tabs>
 
 ### How do I post logs?
-
 Please check [the section above](#how-do-i-open-the-console--log), on how to obtain logs. Logs should always be posted to https://pastebin.com/ or https://rentry.co/.
 
 ### Can I use Homarr at my company?
-
 Yes, you can! But please consider a donation, if our work has been useful to you.
 
 ### I think I found a bug. What can I do?
-
 If you think, that you found a bug, please create an issue <a href="https://github.com/homarr-labs/homarr/issues/new/choose">here</a>.
 
 ### Why can't I use my custom icons?
-
 You need to restart the Homarr Docker container after adding icons.
 
 ### Why can't homarr see/ping containers running locally behind GluetunVPN?
-
 This is because GluetunVPN, and many other docker VPN services, secure their VPN connections with strict firewalls. These firewalls often block access to local containers, even on the same docker network. The workaround for <a href="https://github.com/qdm12/gluetun-wiki/blob/main/setup/options/firewall.md">GluetunVPN</a> is to add "- FIREWALL_OUTBOUND_SUBNETS=192.168.1.0/24" into the environmental variables of the docker compose file. If you are using a firewall on your system, you will need to add a rule that allows requests from ip's in the range of 192.168.xxx.xxx . If you are using UFW the command would be "sudo ufw allow from 192.168.0.0/16".
 Tip: If you are running your torrent client behind a VPN, and running Sonarr (or something similar) normally, make sure to open your torrent client's port in your firewall. If you don't, Sonarr will not be able to see it. Furthermore, use your machines IP (192.168.x.x) rather then 127.0.0.1 or localhost.
 
 ### Can I get in touch with you?
-
 Yes, go <a href="/docs/community/get-in-touch">here</a> to get with us in touch.
 
-<hr />
+<hr/>
 
 :::tip
 

apps/docs/docs/community/get-in-touch.mdx

@@ -9,16 +9,16 @@ tags:
 We're happy to talk with you! Shoot us a message at the following places:
 
 ## E-Mail
-
 We are open to discuss sponsorships, security vulnerabilities and other private requests through our email.
 Please do not report any bugs / feature requests here - they will be ignored and deleted.
 
 [homarr-labs@proton.me](mailto:homarr-labs@proton.me)
 
 ## Discord
-
 We have a Discord Server, where we announce new releases, discuss features and bugs and show off our dashboards.
 There are over 4'000 members and we're happy to answer your questions or concerns.
 You're also open to discuss new / upcoming features and any offtopic selfhosting content.
 
 [_![](https://discordapp.com/api/guilds/972958686051962910/widget.png?style=banner2)_](https://discord.gg/aCsmEV5RgA)
+
+

apps/docs/docs/community/license.mdx

@@ -7,7 +7,6 @@ tags:
 Homarr is licensed under [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0).
 
 ## TL;DR
-
 | Action         | Allowed |
 | -------------- | ------- |
 | Copy           | ✅      |
@@ -25,6 +24,8 @@ Please consider [making a donation](/docs/community/donate) to Homarr, if this p
 
 :::
 
+
+
 ## Full License
 
 ```txt

apps/docs/docs/community/translations.mdx

@@ -5,31 +5,30 @@ tags:
   - Translations
 ---
 
-We want to make Homarr accessible for everyone.
-But to do that, we need your help.
-We are running a community program that enables everyone to translate Homarr into their language – no programming required.
-We are using [Crowdin](https://crowdin.com/) to manage our translations.
+We want to make Homarr accessible for everyone. 
+But to do that, we need your help. 
+We are running a community program that enables everyone to translate Homarr into their language – no programming required. 
+We are using [Crowdin](https://crowdin.com/) to manage our translations. 
 You can find the translations [here](https://translate.homarr.dev/).
 
 ## How to translate
 
-### Using crowdin's online platform
 
-Go to the [Crowdin translations](https://translate.homarr.dev/) and select a language you want to translate.
-You can then enter the translation mode and start translating.
-After you've submitted your translations, a Proofreader will review your changes.
-After a translation has been approved, it will be merged to the language development branch.
-We merge this one periodically to the development branch.
+### Using crowdin's online platform
+Go to the [Crowdin translations](https://translate.homarr.dev/) and select a language you want to translate. 
+You can then enter the translation mode and start translating. 
+After you've submitted your translations, a Proofreader will review your changes. 
+After a translation has been approved, it will be merged to the language development branch. 
+We merge this one periodically to the development branch. 
 After the next update of Homarr, all changes from the development branch will be merged, including the changes in the translations.
 
 ### Using live translate
-
 You can also help translate homarr directly from the app!
 For this you can simply change your language to "Crowdin (live translations)"
 
 ![](./img/crowdin-language-select.png)
 
-Then you'll be prompted to connect to your Crowdin account and choose the language in which you want to transalte.
+Then you'll be prompted to connect to your Crowdin account and choose the language in which you want to transalte. 
 You can then start translating directly from the app by selecting some text on the app.
 If some text cannot be selected to be edited with the live translation tool, you can still translate it inside of the In-Context popup at the Home tab, it will be red if it's not translated yet.
 
@@ -48,8 +47,7 @@ Do you want to become a proofreader? [Let us know on our Discord](/docs/communit
 :::
 
 ## Guidelines
-
 1. Translate with context: Some translations can't be translated 1:1 - they need context. Ensure that your translations make sense in the context.
 2. Keep things simple and original - no additional characters are needed.
 3. Don't translate the same thing twice - if you see a translation that is already translated, don't translate it again unless you have a better translation.
-4. Keep your translations as close to the original as possible.
+5. Keep your translations as close to the original as possible.

apps/docs/docs/getting-started/after-the-installation.mdx

@@ -54,7 +54,11 @@ You must choose a username and password (both can later be changed).
 We enforce strict password requirements when you enter your password to protect your instance if you accidentally
 expose it to the internet.
 
-<img src={imageStartFromScratchStepAdminUser} alt={"Screenshot form to create admin user"} width={300} />
+<img
+  src={imageStartFromScratchStepAdminUser}
+  alt={"Screenshot form to create admin user"}
+  width={300}
+/>
 
 If you selected external providers (such as LDAP or OIDC), you'll be prompted to create an admin group.
 This group will be used to synchronize users from your provider to Homarr.
@@ -112,14 +116,22 @@ The onboarding can no longer be started again.
 From here you can click on one of the provided links to continue your journey.
 We recommend you to continue with the section [creating your first board on this page](#creating-your-first-board).
 
-<img src={imageStartFromScratchStepFinish} alt={"Screenshot of the finish onboarding process with links"} width={300} />
+<img
+  src={imageStartFromScratchStepFinish}
+  alt={"Screenshot of the finish onboarding process with links"}
+  width={300}
+/>
 
 ### Importing a ZIP from version before 1.0.0
 
 This is recommended when you used Homarr before and want to re-import your data.
 It is important that you first migrate correctly using [the list of breaking changes for 1.0](/blog/2024/09/23/version-1.0).
 
-<img src={manageExportOldHomarr} alt="Export from old Homarr" style={{ maxWidth: 500 }} />
+<img
+  src={manageExportOldHomarr}
+  alt="Export from old Homarr"
+  style={{ maxWidth: 500 }}
+/>
 
 **How to export and import data**
 
@@ -185,23 +197,38 @@ Here you have the following options in the header:
 
 When entering the edit mode, you'll get some additional buttons to work with:
 
-<img src={manageBoardHeaderEditMode} alt={"Screenshot of buttons in the edit mode"} width={200} />
+<img
+  src={manageBoardHeaderEditMode}
+  alt={"Screenshot of buttons in the edit mode"}
+  width={200}
+/>
 
 - **Add item**: Click this button to add new elements to your page.
 - **Exit edit mode**: Click this btuton to save your changes and exit edit mode.
 
 To continue, click the option "New Item":
 
-<img src={manageBoardHeaderAddItem} alt={"Screenshot of the add item menu"} width={200} />
+<img
+  src={manageBoardHeaderAddItem}
+  alt={"Screenshot of the add item menu"}
+  width={200}
+/>
 
 Next, you can choose what item you'd like to add.
 We will discuss the other options in the following sections - for now choose "App" to continue.
 
-<img src={manageBoardHeaderChooseItem} alt={"Screenshot of choosing the app item in the modal"} width={300} />
+<img
+  src={manageBoardHeaderChooseItem}
+  alt={"Screenshot of choosing the app item in the modal"}
+  width={300}
+/>
 
 As soon as you chose the app, the modal will close and you'll get the following item on your board:
 
-<img src={manageBoardNoApp} alt="Screenshot of the No app element on the board" />
+<img
+  src={manageBoardNoApp}
+  alt="Screenshot of the No app element on the board"
+/>
 
 This is expected, because you haven't told Homarr what app it should show in this item.
 To configure this, click on the small 3 dots at the top of the item in the edit mode and choose "Edit item" in the menu.

apps/docs/docs/getting-started/glossary.mdx

@@ -1,9 +1,8 @@
 # Glossary
-
 In the glossary, you'll learn the different components and their names of Homarr.
 
 | Term            | Definition                                                                                                     |
-| --------------- | -------------------------------------------------------------------------------------------------------------- |
+|-----------------|----------------------------------------------------------------------------------------------------------------|
 | Apps            | An piece of software that you or a third party hosts (eg. Google)                                              |
 | Integration     | A connection to a service outside of Homarr                                                                    |
 | Dynamic section | Resizeable area where items on your board can be placed and grouped                                            |

apps/docs/docs/getting-started/index.mdx

@@ -8,14 +8,13 @@ tags:
   - Unraid
 ---
 
-import Link from "@docusaurus/Link";
-import { IconArrowRight } from "@tabler/icons-react";
+import Link from '@docusaurus/Link';
+import { IconArrowRight } from '@tabler/icons-react';
 
 Before you try to install Homarr, please review if your device meets the requirements.
 Installing on an unsupported device may lead to unstable behaviour and no support will be provided.
 
 ## Hardware
-
 - At least 500MB RAM
 - At least 600MB of free disk space for the Docker image. SSD is preferred.
 - Single or dual core CPU
@@ -25,8 +24,8 @@ Installing on an unsupported device may lead to unstable behaviour and no suppor
 
 We build Homarr for a bunch of different architectures, including ARM. Please ensure that your device architecture is supported by Homarr. We won't be able to provide support for unusual or outdated architectures.
 
-| Architecture | Supported        |
-| ------------ | ---------------- |
+| Architecture | Supported       |
+|--------------|-----------------|
 | linux/amd64  | ✅ Supported     |
 | linux/arm64  | ✅ Supported     |
 | linux/arm/v7 | ❌ Not supported |
@@ -35,10 +34,10 @@ We build Homarr for a bunch of different architectures, including ARM. Please en
 
 <Link
   data-attr="Go to installation"
-  className={"button button--secondary button--lg rounded-3xl dark:border-zinc-600 dark:bg-zinc-800"}
+  className={'button button--secondary button--lg rounded-3xl dark:border-zinc-600 dark:bg-zinc-800'}
   to="/docs/category/installation-1"
 >
-  <div className={"flex items-center gap-3"}>
+  <div className={'flex items-center gap-3'}>
     <span className={"dark:text-gray-200"}>Go to Installation</span>
     <IconArrowRight className={"dark:text-gray-200"} size={20} />
   </div>

apps/docs/docs/getting-started/installation/docker.mdx

@@ -1,23 +1,21 @@
-import { DockerInstallSnippet } from "@site/src/components/pages/installation/docker/dynamic-docker-install";
+import { DockerInstallSnippet } from '@site/src/components/pages/installation/docker/dynamic-docker-install'
 
 # Docker
-
 Docker is our recommended installation method for beginners and professionals.
 It is easy to use, ships with all dependencies inside a single container and is easy to use and maintain.
 It requires at least some basic knowledge of [Docker](https://www.docker.com/).
 We recommend [NetworkChuck's Docker Containers 101](https://www.youtube.com/watch?v=eGz9DS-aIeY) as a good start for complete beginners.
 
 ## Docker compose
-
 ### Prerequisites
 
 - A Linux or Windows based system that meets the [hardware prerequisites](/docs/getting-started/#hardware) and [architecture prerequisites](/docs/getting-started/#architecture).
 - [Docker](https://docs.docker.com/get-docker/)
-- [Docker Compose](https://docs.docker.com/compose/install/) - _preinstalled on many systems nowadays_
+- [Docker Compose](https://docs.docker.com/compose/install/) - *preinstalled on many systems nowadays*
 
 ### Installation
 
-<DockerInstallSnippet data-visual-test="blackout" />
+<DockerInstallSnippet data-visual-test="blackout"/>
 Finally, run ``docker compose up -d`` in the same directory. This will start the Homarr container in the background.
 
 :::caution
@@ -28,26 +26,27 @@ Docker compose creates a network by default. Some integrations may not work (spe
 
 ### Updating
 
-To update, navigate to the directory with the `docker-compose.yaml` located.
+To update, navigate to the directory with the ``docker-compose.yaml`` located.
 
-- Stop Homarr using `docker compose down`
-- Pull the newest image of Homarr using `docker compose pull`
-- Start Homarr again using `docker compose up -d` (`-d` for detached mode - start in background)
-- Delete the old image using `docker image prune` (_Warning: this also removes you other unused images - not just Homarr_)
+- Stop Homarr using ``docker compose down``
+- Pull the newest image of Homarr using ``docker compose pull``
+- Start Homarr again using ``docker compose up -d`` (``-d`` for detached mode - start in background)
+- Delete the old image using ``docker image prune`` (*Warning: this also removes you other unused images - not just Homarr*)
 
 You can automate this process using [Watchtower](https://containrrr.dev/watchtower/).
 
 ### Uninstalling
 
-To uninstall, navigate to the directory with the `docker-compose.yaml` located.
+To uninstall, navigate to the directory with the ``docker-compose.yaml`` located.
 
-- Stop Homarr using `docker compose down`
-- Delete the created directories & files on your root file system (check `docker-compose.yaml` file for your specific locations)
-- Delete compose file using `rm docker-compose.yaml`
-- Prune unused Docker images using `docker image prune` (_Warning: this also removes you other unused images - not just Homarr_)
+- Stop Homarr using ``docker compose down``
+- Delete the created directories & files on your root file system (check ``docker-compose.yaml`` file for your specific locations)
+- Delete compose file using ``rm docker-compose.yaml``
+- Prune unused Docker images using ``docker image prune`` (*Warning: this also removes you other unused images - not just Homarr*)
 - (Optional): Prune any network or volumes if you use any.
 - (Optional): Remove Homarr from your reverse proxy, VPNs or tunnels if you use any.
 
+
 ## Docker standalone
 
 :::caution
@@ -78,16 +77,15 @@ docker run  \
 
 :::note
 
-Docker will mount the configuration files and icons to your host machine. Please make sure to replace `<your-path>` from the docker run command with your desired storage location. The path must be absolute.
+Docker will mount the configuration files and icons to your host machine. Please make sure to replace ``<your-path>`` from the docker run command with your desired storage location. The path must be absolute.
 
 :::
 
 ### Updating
-
 To update Homarr, you must remove your container first. Make sure that you've mounted your data and that you have access to it, so your configuration doesn't get lost.
 
-1. Run `docker rm homarr` to remove the container.
-2. Pull the latest Homarr image `docker pull ghcr.io/homarr-labs/homarr:latest`.
+1. Run ``docker rm -f homarr`` to stop and remove the container.
+2. Pull the latest Homarr image ``docker pull ghcr.io/homarr-labs/homarr:latest``.
 3. Re-run the command you used to install Homarr.
 
 This process can get tideous, if you update frequently. Thus, we recommend [using docker-compose](#docker-compose)
@@ -100,8 +98,8 @@ Want to update all your containers automatically? Checkout [Watchtower](https://
 
 ### Uninstalling
 
-1. Obtain the container ID of your Homarr container using `docker ps | grep homarr`.
-2. Delete the container using `docker rm <your-container-id>`
-3. Prune unused Docker images using `docker image prune` (_Warning: this also removes you other unused images - not just Homarr_)
+1. Obtain the container ID of your Homarr container using ``docker ps -a | grep homarr``.
+2. Delete the container using ``docker rm -f <your-container-id>``
+3. Prune unused Docker images using ``docker image prune`` (*Warning: this also removes you other unused images - not just Homarr*)
 4. (Optional): Prune any network or volumes if you use any.
 5. (Optional): Remove Homarr from your reverse proxy, VPNs or tunnels if you use any.

apps/docs/docs/getting-started/installation/helm.md

@@ -12,7 +12,7 @@ A Helm chart to deploy homarr for Kubernetes
 
 ## Source Code
 
-- <https://github.com/homarr-labs/homarr>
+* <https://github.com/homarr-labs/homarr>
 
 ## Requirements
 
@@ -76,38 +76,38 @@ To avoid including sensitive information in plain text within your version contr
 
 Below is an exhaustive list of all secrets:
 
-| FEATURE  | SECRET NAME      | SECRET KEYS                          | Required |
-| -------- | ---------------- | ------------------------------------ | -------- |
-| OIDC     | auth-oidc-secret | oidc-client-id<br>oidc-client-secret | No       |
-| LDAP     | auth-ldap-secret | bind-password                        | No       |
-| DATABASE | db-secret        | db-url                               | No       |
-| DATABASE | db-encryption    | db-encryption-key                    | yes      |
+| FEATURE   | SECRET NAME             | SECRET KEYS                             | Required |
+|-----------|-------------------------|-----------------------------------------|----------|
+| OIDC      | auth-oidc-secret        | oidc-client-id<br>oidc-client-secret    | No       |
+| LDAP      | auth-ldap-secret        | bind-password                           | No       |
+| DATABASE  | db-secret               | db-url                                  | No       |
+| DATABASE  | db-encryption           | db-encryption-key                       | yes      |
 
 ### Database
 
 You have multiple options for configuring the database:
 
-| DRIVER TYPE    | Persistence mode             |
-| -------------- | ---------------------------- |
-| better-sqlite3 | Pod disk                     |
-| better-sqlite3 | homarr-database PVC          |
-| mysql2         | External MySql database      |
-| node-postgres  | External Postgresql database |
+| DRIVER TYPE    | Persistence mode                |
+|----------------|---------------------------------|
+| better-sqlite3 | Pod disk                        |
+| better-sqlite3 | homarr-database PVC             |
+| mysql2         | External MySql database         |
+| node-postgres  | External Postgresql database    |
 
 #### Pod disk
 
-No additional configuration is required. However, keep in mind that if the pod restarts, all data will be lost. This setup is not _recommended_ for production use.
+No additional configuration is required. However, keep in mind that if the pod restarts, all data will be lost. This setup is not *recommended* for production use.
 
 To create the necessary database secret, execute the following command:
 
 <details>
 <summary>Required Secrets</summary>
 
-```yaml
+````yaml
 kubectl create secret generic db-encryption \
 --from-literal=db-encryption-key='<SECRET_ENCRYPTION_KEY_SECRET_TO_CHANGE>' \
 --namespace homarr
-```
+````
 
 </details>
 
@@ -120,11 +120,11 @@ Associated secret to create :
 <details>
 <summary>DB Required Secrets</summary>
 
-```yaml
+````yaml
 kubectl create secret generic db-encryption \
 --from-literal=db-encryption-key='<SECRET_ENCRYPTION_KEY_SECRET_TO_CHANGE>' \
 --namespace homarr
-```
+````
 
 </details>
 
@@ -133,13 +133,13 @@ Bellow an example of the override value file :
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 persistence:
   homarrDatabase:
     enabled: true
     storageClassName: "default"
     size: "1Gi"
-```
+````
 
 </details>
 
@@ -150,18 +150,17 @@ To create the necessary database secrets, execute the following command:
 <details>
 <summary>Required Secrets</summary>
 
-```yaml
+````yaml
 kubectl create secret generic db-encryption \
 --from-literal=db-encryption-key='<SECRET_ENCRYPTION_KEY_SECRET_TO_CHANGE>' \
 --namespace homarr
-```
+````
 
-```yaml
+````yaml
 kubectl create secret generic db-secret \
 --from-literal=db-url='mysql://user:password@host:port/homarrdb' \
 --namespace homarr
-```
-
+````
 </details>
 
 Below is an example of the override values file:
@@ -169,11 +168,10 @@ Below is an example of the override values file:
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 database:
   type: mysql
-```
-
+````
 </details>
 
 #### External Postgresql database
@@ -183,17 +181,17 @@ To create the necessary database secrets, execute the following command:
 <details>
 <summary>Required Secrets</summary>
 
-```yaml
+````yaml
 kubectl create secret generic db-encryption \
 --from-literal=db-encryption-key='<SECRET_ENCRYPTION_KEY_SECRET_TO_CHANGE>' \
 --namespace homarr
-```
+````
 
-```yaml
+````yaml
 kubectl create secret generic db-secret \
 --from-literal=db-url='postgresql://user:password@host:port/homarrdb' \
 --namespace homarr
-```
+````
 
 </details>
 
@@ -202,11 +200,10 @@ Below is an example of the override values file:
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 database:
   type: postgresql
-```
-
+````
 </details>
 
 ### Ingress
@@ -216,7 +213,7 @@ The ingress section in the values.yaml file allows you to configure how external
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 service:
   enabled: true # Ensure the service is enabled for Ingress to route traffic
 ingress:
@@ -234,8 +231,7 @@ ingress:
         - "homarr.homelab.dev"
         - "www.homarr.homelab.dev"
       secretName: homelab-tls
-```
-
+````
 </details>
 
 ### HTTPRoute (Gateway API)
@@ -246,9 +242,9 @@ This provides a more expressive and future-proof alternative to Ingress, with su
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 service:
-  enabled: true # must be enabled for HTTPRoute to forward traffic
+  enabled: true  # must be enabled for HTTPRoute to forward traffic
 httproute:
   enabled: true
   parentRefs:
@@ -264,15 +260,14 @@ httproute:
       backendRefs:
         - name: homarr
           port: 7575
-```
-
+````
 </details>
 
 #### Notes:
 
 - parentRefs: the Gateway(s) this route attaches to. Gateways must already exist.
 - hostnames: domain names this route applies to.
-- rules: each rule can define matches (paths, headers, queries), optional filters, and backendRefs to services
+- rules:  each rule can define matches (paths, headers, queries), optional filters, and backendRefs to services
 - TLS must be configured on the Gateway (not on HTTPRoute). For example, the Gateway can have a TLS listener for homarr.homelab.dev, and this route will automatically apply once matched.
 
 ### Certificates
@@ -289,7 +284,7 @@ Use inline certificates to generate a ConfigMap, mounted as individual files.
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 persistence:
   homarrTrustedCerts:
     enabled: true
@@ -303,8 +298,7 @@ persistence:
         -----BEGIN CERTIFICATE-----
         MIID...EFGH==
         -----END CERTIFICATE-----
-```
-
+````
 </details>
 
 Behavior:
@@ -319,7 +313,7 @@ Use inline certificates to generate a Kubernetes Secret, mounted as files.
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 persistence:
   homarrTrustedCerts:
     enabled: true
@@ -333,8 +327,7 @@ persistence:
         -----BEGIN CERTIFICATE-----
         MIIC...XYZ==
         -----END CERTIFICATE-----
-```
-
+````
 </details>
 
 Behavior:
@@ -349,17 +342,16 @@ Use an existing Kubernetes Secret, assuming its keys are filenames.
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 persistence:
   homarrTrustedCerts:
     enabled: true
     type: existingSecret
     existingSecretName: "existingSecretName"
     existingSecretKeys:
-      - cert3.crt
-      - cert4.crt
-```
-
+        - cert3.crt
+        - cert4.crt
+````
 </details>
 
 Behavior:
@@ -380,115 +372,114 @@ All available values are listed on the [artifacthub](https://artifacthub.io/pack
 
 ## Values
 
-| Key                                                | Type   | Default                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| -------------------------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| additionalObjects                                  | list   | `[]`                                                                                                                                                                                                                                             | Additional resources to deploy. These objects are templated.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| affinity                                           | object | `{}`                                                                                                                                                                                                                                             | Node affinity for pod scheduling                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| autoscaling.enabled                                | bool   | `false`                                                                                                                                                                                                                                          | Enable autoscaling                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| autoscaling.maxReplicas                            | int    | `100`                                                                                                                                                                                                                                            | Maximum replicas                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| autoscaling.minReplicas                            | int    | `1`                                                                                                                                                                                                                                              | Minimum replicas                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| autoscaling.targetCPUUtilizationPercentage         | int    | `80`                                                                                                                                                                                                                                             | Target CPU utilization for autoscaling                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| containerPorts                                     | object | `{"http":{"port":7575,"protocol":"TCP"}}`                                                                                                                                                                                                        | containerPorts defines the ports to open on the container. It is a map where each entry specifies: - `port` (int) (required): The port number to expose inside the container. - `protocol` (string) (required): The network protocol (TCP or UDP) used for the port. - `disabled` (bool) : Optional flag to disable this port (defaults to false). Can be overridden via Helm values. By default, this configuration exposes TCP port 7575 with the name `http`.                                                                                         |
-| database.migrationEnabled                          | bool   | `true`                                                                                                                                                                                                                                           | Database migration configuration. DB_MIGRATIONS_DISABLED Set to `true` to disable database migrations. Migrations are enabled by default (`false`).                                                                                                                                                                                                                                                                                                                                                                                                      |
-| database.type                                      | string | `"sqlite"`                                                                                                                                                                                                                                       | Database type: sqlite, mysql or postgresql                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| env.AUTH_COOKIE_PREFIX                             | string | `"homarr"`                                                                                                                                                                                                                                       | Prefix used for all authentication cookies. Change if you run another Auth.js/NextAuth app on the same hostname to avoid cookie name collisions. Only letters, numbers, hyphens and underscores.                                                                                                                                                                                                                                                                                                                                                         |
-| env.AUTH_LDAP_BASE                                 | string | `nil`                                                                                                                                                                                                                                            | Base dn of your LDAP server                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| env.AUTH_LDAP_BIND_DN                              | string | `nil`                                                                                                                                                                                                                                            | User used for finding users and groups                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| env.AUTH_LDAP_GROUP_CLASS                          | string | `"groupOfUniqueNames"`                                                                                                                                                                                                                           | Class used for querying groups                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| env.AUTH_LDAP_GROUP_FILTER_EXTRA_ARG               | string | `nil`                                                                                                                                                                                                                                            | Extra arguments for user's groups search filter (& based)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| env.AUTH_LDAP_GROUP_MEMBER_ATTRIBUTE               | string | `"member"`                                                                                                                                                                                                                                       | Attribute used for querying group member                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| env.AUTH_LDAP_GROUP_MEMBER_USER_ATTRIBUTE          | string | `"dn"`                                                                                                                                                                                                                                           | User attribute used for comparing with group member                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| env.AUTH_LDAP_SEARCH_SCOPE                         | string | `"base"`                                                                                                                                                                                                                                         | LDAP search scope between base, one or sub                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| env.AUTH_LDAP_URI                                  | string | `nil`                                                                                                                                                                                                                                            | URI of your LDAP server                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| env.AUTH_LDAP_USERNAME_ATTRIBUTE                   | string | `"uid"`                                                                                                                                                                                                                                          | Attribute used for username                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| env.AUTH_LDAP_USERNAME_FILTER_EXTRA_ARG            | string | `nil`                                                                                                                                                                                                                                            | Extra arguments for user search filter (& based)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| env.AUTH_LDAP_USER_MAIL_ATTRIBUTE                  | string | `"mail"`                                                                                                                                                                                                                                         | Attribute used for mail field                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| env.AUTH_LOGOUT_REDIRECT_URL                       | string | `nil`                                                                                                                                                                                                                                            | URL to redirect to after clicking logging out.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| env.AUTH_OIDC_AUTO_LOGIN                           | string | `"false"`                                                                                                                                                                                                                                        | Automatically redirect to OIDC login                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| env.AUTH_OIDC_CLIENT_NAME                          | string | `"OIDC"`                                                                                                                                                                                                                                         | Display name of provider (in login screen)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| env.AUTH_OIDC_GROUPS_ATTRIBUTE                     | string | `"groups"`                                                                                                                                                                                                                                       | Attribute used for groups (roles) claim                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| env.AUTH_OIDC_ISSUER                               | string | `nil`                                                                                                                                                                                                                                            | Issuer URI of OIDC provider without trailing slash (/)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| env.AUTH_OIDC_NAME_ATTRIBUTE_OVERWRITE             | string | `nil`                                                                                                                                                                                                                                            | Overwrite name attribute. By default, it will use preferred_username if it does not contain a @ and otherwise name.                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| env.AUTH_OIDC_SCOPE_OVERWRITE                      | string | `"openid email profile groups"`                                                                                                                                                                                                                  | Override the OIDC scopes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| env.AUTH_PROVIDERS                                 | string | `"credentials"`                                                                                                                                                                                                                                  | Enabled authentication methods. Multiple providers can be enabled with by separating them with , (ex. AUTH_PROVIDERS=credentials,oidc, it is highly recommended to just enable one provider).                                                                                                                                                                                                                                                                                                                                                            |
-| env.AUTH_SESSION_EXPIRY_TIME                       | string | `"30d"`                                                                                                                                                                                                                                          | Time for the session to time out. Can be set as pure number, which will automatically be used in seconds, or followed by s, m, h or d for seconds, minutes, hours or days. (ex: "30m")                                                                                                                                                                                                                                                                                                                                                                   |
-| env.ENABLE_DNS_CACHING                             | string | `"false"`                                                                                                                                                                                                                                        | Enables dns caching. This is not yet working for all users. See #4006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| env.LOG_LEVEL                                      | string | `"info"`                                                                                                                                                                                                                                         | Log level to use. Possible values: debug/info/warn/error                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| env.NO_EXTERNAL_CONNECTION                         | string | `"false"`                                                                                                                                                                                                                                        | Disables some requests that need internet connection                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| env.TZ                                             | string | `"Europe/Paris"`                                                                                                                                                                                                                                 | Your local time zone                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| envSecrets.authLdapCredentials.existingSecret      | string | `"auth-ldap-secret"`                                                                                                                                                                                                                             | Name of existing secret containing LDAP credentials                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| envSecrets.authLdapCredentials.ldapBindingPassword | string | `"bind-password"`                                                                                                                                                                                                                                | Password for bind user secret key                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| envSecrets.authOidcCredentials.existingSecret      | string | `"auth-oidc-secret"`                                                                                                                                                                                                                             | Name of existing secret containing OIDC credentials                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| envSecrets.authOidcCredentials.oidcClientId        | string | `"oidc-client-id"`                                                                                                                                                                                                                               | ID of OIDC client (application) secret key                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| envSecrets.authOidcCredentials.oidcClientSecret    | string | `"oidc-client-secret"`                                                                                                                                                                                                                           | Secret of OIDC client (application) secret key                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| envSecrets.dbCredentials.dbUrlKey                  | string | `"db-url"`                                                                                                                                                                                                                                       | Secret key for DB_URL Example for external database: `mysql://username:password@host:port/homarrdb` or `postgresql://username:password@host:port/homarrdb`                                                                                                                                                                                                                                                                                                                                                                                               |
-| envSecrets.dbCredentials.existingSecret            | string | `"db-secret"`                                                                                                                                                                                                                                    | Name of existing secret containing DB credentials                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| envSecrets.dbEncryption.existingSecret             | string | `"db-encryption"`                                                                                                                                                                                                                                | Name of existing secret containing DB encryption                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| envSecrets.dbEncryption.key                        | string | `"db-encryption-key"`                                                                                                                                                                                                                            | Secret key for SECRET_ENCRYPTION_KEY can be generated with `openssl rand -hex 32`                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| fullnameOverride                                   | string | `""`                                                                                                                                                                                                                                             | Overrides chart's fullname                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| hostAliases                                        | list   | `[]`                                                                                                                                                                                                                                             | Add static entries to /etc/hosts in the Pod. This is useful in the following cases: - You are running in a dual-stack cluster (IPv4 + IPv6) and want to force usage of IPv4 for specific hostnames - Your application is having DNS resolution issues or IPv6 preference issues - You need to override or simulate DNS entries without changing global DNS - You are running in an air-gapped or isolated environment without external DNS Example: hostAliases: - ip: "192.168.1.10" hostnames: - "example.com" - "example.internal"                    |
-| httproute                                          | object | `{"enabled":false,"hostnames":["chart-example.local"],"parentRefs":[{"name":"my-gateway","namespace":"default"}],"rules":[{"backendRefs":[{"name":"homarr","port":7575}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]}` | Gateway API HTTPRoute configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| httproute.enabled                                  | bool   | `false`                                                                                                                                                                                                                                          | Enable HTTPRoute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| httproute.hostnames                                | list   | `["chart-example.local"]`                                                                                                                                                                                                                        | Hostnames this route matches (similar to ingress.hosts.host)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| httproute.parentRefs                               | list   | `[{"name":"my-gateway","namespace":"default"}]`                                                                                                                                                                                                  | References to the parent Gateway(s) this route attaches to. Each item must include at least a `name`, and optionally a `namespace`.                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| httproute.rules                                    | list   | `[{"backendRefs":[{"name":"homarr","port":7575}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]`                                                                                                                          | List of routing rules. Each rule can include: - matches: path/header/query matching - filters: optional transformations (redirects, header modifications, etc.) - backendRefs: one or more Kubernetes Services to forward traffic to                                                                                                                                                                                                                                                                                                                     |
-| httproute.rules[0].filters                         | list   | `[]`                                                                                                                                                                                                                                             | Optional filters for this rule (default: empty)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| httproute.rules[0].matches[0].path.type            | string | `"PathPrefix"`                                                                                                                                                                                                                                   | Path match type. One of: Exact, PathPrefix, RegularExpression                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| httproute.rules[0].matches[0].path.value           | string | `"/"`                                                                                                                                                                                                                                            | Path value to match                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| image.pullPolicy                                   | string | `"IfNotPresent"`                                                                                                                                                                                                                                 | Image pull policy                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| image.repository                                   | string | `"ghcr.io/homarr-labs/homarr"`                                                                                                                                                                                                                   | Image repository                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| image.tag                                          | string | `"v1.74.0"`                                                                                                                                                                                                                                      | Overrides the image tag whose default is the chart appVersion                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| imagePullSecrets                                   | list   | `[]`                                                                                                                                                                                                                                             | Secrets for Docker registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| ingress.annotations                                | object | `{}`                                                                                                                                                                                                                                             | Ingress annotations                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| ingress.enabled                                    | bool   | `false`                                                                                                                                                                                                                                          | Enable ingress                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| ingress.hosts                                      | list   | `[{"host":"chart-example.local","paths":[{"path":"/"}]}]`                                                                                                                                                                                        | Ingress hosts configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| ingress.ingressClassName                           | string | `""`                                                                                                                                                                                                                                             | Ingress class name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| ingress.tls                                        | list   | `[]`                                                                                                                                                                                                                                             | Ingress TLS configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| livenessProbe.failureThreshold                     | int    | `3`                                                                                                                                                                                                                                              | Failure threshold for liveness probe - number of consecutive failures before pod is restarted                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| livenessProbe.httpGet.path                         | string | `"/api/health/live"`                                                                                                                                                                                                                             | This is the liveness check endpoint used by Kubernetes to determine if the application is still running.                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| livenessProbe.httpGet.port                         | int    | `7575`                                                                                                                                                                                                                                           | The port on which the liveness check will be performed. This must be the same as the container port exposed by the application.                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| livenessProbe.initialDelaySeconds                  | int    | `10`                                                                                                                                                                                                                                             | Initial delay in seconds before the liveness probe starts                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| livenessProbe.periodSeconds                        | int    | `10`                                                                                                                                                                                                                                             | Period in seconds between liveness probe checks                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| livenessProbe.timeoutSeconds                       | int    | `1`                                                                                                                                                                                                                                              | Timeout in seconds for each liveness probe check                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| nameOverride                                       | string | `""`                                                                                                                                                                                                                                             | Overrides chart's name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| nodeSelector                                       | object | `{}`                                                                                                                                                                                                                                             | Node selectors for pod scheduling                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| persistence.homarrDatabase.accessMode              | string | `"ReadWriteOnce"`                                                                                                                                                                                                                                | homarr-database access mode                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| persistence.homarrDatabase.enabled                 | bool   | `false`                                                                                                                                                                                                                                          | Enable homarr-database persistent storage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| persistence.homarrDatabase.mountPath               | string | `"/appdata"`                                                                                                                                                                                                                                     | homarr-database mount path inside the pod                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| persistence.homarrDatabase.name                    | string | `"homarr-database"`                                                                                                                                                                                                                              | homarr-database persistent storage name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| persistence.homarrDatabase.size                    | string | `"50Mi"`                                                                                                                                                                                                                                         | homarr-database storage size                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| persistence.homarrDatabase.storageClassName        | string | `"local-path"`                                                                                                                                                                                                                                   | homarr-database storage class name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| persistence.homarrDatabase.volumeClaimName         | string | `""`                                                                                                                                                                                                                                             | homarr-database optional volumeClaimName to target specific PV                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| persistence.homarrTrustedCerts.certificates        | string | `nil`                                                                                                                                                                                                                                            | homarr-trusted-certificates certificates, each entry will become a new trusted certificate as a dedicated file (works only for "configmap" and "secret" mode)                                                                                                                                                                                                                                                                                                                                                                                            |
-| persistence.homarrTrustedCerts.enabled             | bool   | `false`                                                                                                                                                                                                                                          | Enable trusted certificates persistence                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| persistence.homarrTrustedCerts.existingSecretKeys  | string | `nil`                                                                                                                                                                                                                                            | List of keys (filenames) to mount from the existing secret (used only when type is "existingSecret")                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| persistence.homarrTrustedCerts.existingSecretName  | string | `""`                                                                                                                                                                                                                                             | Name of the existing Kubernetes Secret to mount (required if type is "existingSecret")                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| persistence.homarrTrustedCerts.mountPath           | string | `"/appdata/trusted-certificates"`                                                                                                                                                                                                                | homarr-trusted-certificates mount path inside the pod                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| persistence.homarrTrustedCerts.type                | string | `"configmap"`                                                                                                                                                                                                                                    | Persistence mode can be : configmap (declarative), secret (declarative) or existingSecret (mount an existing Kubernetes Secret by name and specify which keys to mount as files)                                                                                                                                                                                                                                                                                                                                                                         |
-| podAnnotations                                     | object | `{}`                                                                                                                                                                                                                                             | Pod annotations                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| podLabels                                          | object | `{}`                                                                                                                                                                                                                                             | Pod labels                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| podSecurityContext                                 | object | `{}`                                                                                                                                                                                                                                             | Pod security context                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| rbac                                               | object | `{"enabled":false}`                                                                                                                                                                                                                              | Enable RBAC resources for Kubernetes integration Creates Role, ClusterRole, and associated bindings for Homarr's Kubernetes features                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| rbac.enabled                                       | bool   | `false`                                                                                                                                                                                                                                          | Enable to create RBAC resources and activate Kubernetes integration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| readinessProbe.failureThreshold                    | int    | `3`                                                                                                                                                                                                                                              | Failure threshold for readiness probe - number of consecutive failures before pod is considered unready                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| readinessProbe.httpGet.path                        | string | `"/api/health/ready"`                                                                                                                                                                                                                            | This is the readiness check endpoint used by Kubernetes to determine if the application is ready to handle traffic.                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| readinessProbe.httpGet.port                        | int    | `7575`                                                                                                                                                                                                                                           | The port on which the readiness check will be performed. This must match the container's exposed port.                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| readinessProbe.initialDelaySeconds                 | int    | `10`                                                                                                                                                                                                                                             | Initial delay in seconds before the readiness probe starts. increase this value if the pod is slow to fully start.                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| readinessProbe.periodSeconds                       | int    | `10`                                                                                                                                                                                                                                             | Period in seconds between readiness probe checks                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| readinessProbe.timeoutSeconds                      | int    | `1`                                                                                                                                                                                                                                              | Timeout in seconds for each readiness probe check                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| replicaCount                                       | int    | `1`                                                                                                                                                                                                                                              | Number of replicas                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| resources                                          | object | `{}`                                                                                                                                                                                                                                             | Resource configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| securityContext                                    | object | `{}`                                                                                                                                                                                                                                             | Security context                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| service.enabled                                    | bool   | `true`                                                                                                                                                                                                                                           | Enable service                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| service.ipFamilies                                 | list   | `[]`                                                                                                                                                                                                                                             | List of IP families to use for the service. Examples: - ["IPv4"] - ["IPv6"] - ["IPv4", "IPv6"] for dual-stack Leave empty to use cluster default behavior                                                                                                                                                                                                                                                                                                                                                                                                |
-| service.ipFamilyPolicy                             | string | `"SingleStack"`                                                                                                                                                                                                                                  | Defines how the service assigns IP families (IPv4/IPv6) Possible values: - SingleStack (default): Only one IP family, usually IPv4 - PreferDualStack: Use dual-stack if the cluster supports it, fallback to single - RequireDualStack: Fail if dual-stack cannot be assigned                                                                                                                                                                                                                                                                            |
-| service.ports.app.port                             | int    | `7575`                                                                                                                                                                                                                                           | Service port                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| service.ports.app.protocol                         | string | `"TCP"`                                                                                                                                                                                                                                          | Service protocol                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| service.ports.app.targetPort                       | string | `"http"`                                                                                                                                                                                                                                         | Service target port                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| service.type                                       | string | `"ClusterIP"`                                                                                                                                                                                                                                    | Service type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| strategyType                                       | string | `"RollingUpdate"`                                                                                                                                                                                                                                | `strategyType` specifies the strategy used to replace old Pods by new ones. `strategyType` can be `"Recreate"` or `"RollingUpdate"`. `"RollingUpdate"` is the default value and updates Pods in a rolling update fashion. `"Recreate"` will kill all existing Pods before new ones are created. The `"Recreate"` strategy is necessary when persistent volume's `accessMode` is set to `"ReadWriteOnce"` when using `helm upgrade`, as pod volume attachments to an existing PersistentVolumeClaim need to be cleared before a new pod can attach to it. |
-| tolerations                                        | list   | `[]`                                                                                                                                                                                                                                             | Node tolerations for pod scheduling                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Key | Type | Default | Description |
+|-----|------|---------|-------------|
+| additionalObjects | list | `[]` | Additional resources to deploy. These objects are templated. |
+| affinity | object | `{}` | Node affinity for pod scheduling |
+| autoscaling.enabled | bool | `false` | Enable autoscaling |
+| autoscaling.maxReplicas | int | `100` | Maximum replicas |
+| autoscaling.minReplicas | int | `1` | Minimum replicas |
+| autoscaling.targetCPUUtilizationPercentage | int | `80` | Target CPU utilization for autoscaling |
+| containerPorts | object | `{"http":{"port":7575,"protocol":"TCP"}}` | containerPorts defines the ports to open on the container. It is a map where each entry specifies:    - `port`     (int)    (required): The port number to expose inside the container.    - `protocol` (string) (required): The network protocol (TCP or UDP) used for the port.    - `disabled` (bool)              : Optional flag to disable this port (defaults to false). Can be overridden via Helm values.  By default, this configuration exposes TCP port 7575 with the name `http`. |
+| database.migrationEnabled | bool | `true` | Database migration configuration. DB_MIGRATIONS_DISABLED Set to `true` to disable database migrations. Migrations are enabled by default (`false`). |
+| database.type | string | `"sqlite"` | Database type: sqlite, mysql or postgresql |
+| env.AUTH_COOKIE_PREFIX | string | `"homarr"` | Prefix used for all authentication cookies. Change if you run another Auth.js/NextAuth app on the same hostname to avoid cookie name collisions. Only letters, numbers, hyphens and underscores. |
+| env.AUTH_LDAP_BASE | string | `nil` | Base dn of your LDAP server |
+| env.AUTH_LDAP_BIND_DN | string | `nil` | User used for finding users and groups |
+| env.AUTH_LDAP_GROUP_CLASS | string | `"groupOfUniqueNames"` | Class used for querying groups |
+| env.AUTH_LDAP_GROUP_FILTER_EXTRA_ARG | string | `nil` | Extra arguments for user's groups search filter (& based) |
+| env.AUTH_LDAP_GROUP_MEMBER_ATTRIBUTE | string | `"member"` | Attribute used for querying group member |
+| env.AUTH_LDAP_GROUP_MEMBER_USER_ATTRIBUTE | string | `"dn"` | User attribute used for comparing with group member |
+| env.AUTH_LDAP_SEARCH_SCOPE | string | `"base"` | LDAP search scope between base, one or sub |
+| env.AUTH_LDAP_URI | string | `nil` | URI of your LDAP server |
+| env.AUTH_LDAP_USERNAME_ATTRIBUTE | string | `"uid"` | Attribute used for username |
+| env.AUTH_LDAP_USERNAME_FILTER_EXTRA_ARG | string | `nil` | Extra arguments for user search filter (& based) |
+| env.AUTH_LDAP_USER_MAIL_ATTRIBUTE | string | `"mail"` | Attribute used for mail field |
+| env.AUTH_LOGOUT_REDIRECT_URL | string | `nil` | URL to redirect to after clicking logging out. |
+| env.AUTH_OIDC_AUTO_LOGIN | string | `"false"` | Automatically redirect to OIDC login |
+| env.AUTH_OIDC_CLIENT_NAME | string | `"OIDC"` | Display name of provider (in login screen) |
+| env.AUTH_OIDC_GROUPS_ATTRIBUTE | string | `"groups"` | Attribute used for groups (roles) claim |
+| env.AUTH_OIDC_ISSUER | string | `nil` | Issuer URI of OIDC provider without trailing slash (/) |
+| env.AUTH_OIDC_NAME_ATTRIBUTE_OVERWRITE | string | `nil` | Overwrite name attribute. By default, it will use preferred_username if it does not contain a @ and otherwise name. |
+| env.AUTH_OIDC_SCOPE_OVERWRITE | string | `"openid email profile groups"` | Override the OIDC scopes |
+| env.AUTH_PROVIDERS | string | `"credentials"` | Enabled authentication methods. Multiple providers can be enabled with by separating them with , (ex. AUTH_PROVIDERS=credentials,oidc, it is highly recommended to just enable one provider). |
+| env.AUTH_SESSION_EXPIRY_TIME | string | `"30d"` | Time for the session to time out. Can be set as pure number, which will automatically be used in seconds, or followed by s, m, h or d for seconds, minutes, hours or days. (ex: "30m") |
+| env.ENABLE_DNS_CACHING | string | `"false"` | Enables dns caching. This is not yet working for all users. See #4006 |
+| env.LOG_LEVEL | string | `"info"` | Log level to use. Possible values: debug/info/warn/error |
+| env.NO_EXTERNAL_CONNECTION | string | `"false"` | Disables some requests that need internet connection |
+| env.TZ | string | `"Europe/Paris"` | Your local time zone |
+| envSecrets.authLdapCredentials.existingSecret | string | `"auth-ldap-secret"` | Name of existing secret containing LDAP credentials |
+| envSecrets.authLdapCredentials.ldapBindingPassword | string | `"bind-password"` | Password for bind user secret key |
+| envSecrets.authOidcCredentials.existingSecret | string | `"auth-oidc-secret"` | Name of existing secret containing OIDC credentials |
+| envSecrets.authOidcCredentials.oidcClientId | string | `"oidc-client-id"` | ID of OIDC client (application) secret key |
+| envSecrets.authOidcCredentials.oidcClientSecret | string | `"oidc-client-secret"` | Secret of OIDC client (application) secret key |
+| envSecrets.dbCredentials.dbUrlKey | string | `"db-url"` | Secret key for DB_URL Example for external database: `mysql://username:password@host:port/homarrdb` or `postgresql://username:password@host:port/homarrdb` |
+| envSecrets.dbCredentials.existingSecret | string | `"db-secret"` | Name of existing secret containing DB credentials |
+| envSecrets.dbEncryption.existingSecret | string | `"db-encryption"` | Name of existing secret containing DB encryption |
+| envSecrets.dbEncryption.key | string | `"db-encryption-key"` | Secret key for SECRET_ENCRYPTION_KEY can be generated with `openssl rand -hex 32` |
+| fullnameOverride | string | `""` | Overrides chart's fullname |
+| hostAliases | list | `[]` | Add static entries to /etc/hosts in the Pod. This is useful in the following cases: - You are running in a dual-stack cluster (IPv4 + IPv6) and want to force usage of IPv4 for specific hostnames - Your application is having DNS resolution issues or IPv6 preference issues - You need to override or simulate DNS entries without changing global DNS - You are running in an air-gapped or isolated environment without external DNS Example: hostAliases:   - ip: "192.168.1.10"     hostnames:       - "example.com"       - "example.internal" |
+| httproute | object | `{"enabled":false,"hostnames":["chart-example.local"],"parentRefs":[{"name":"my-gateway","namespace":"default"}],"rules":[{"backendRefs":[{"name":"homarr","port":7575}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]}` | Gateway API HTTPRoute configuration |
+| httproute.enabled | bool | `false` | Enable HTTPRoute |
+| httproute.hostnames | list | `["chart-example.local"]` | Hostnames this route matches (similar to ingress.hosts.host) |
+| httproute.parentRefs | list | `[{"name":"my-gateway","namespace":"default"}]` | References to the parent Gateway(s) this route attaches to. Each item must include at least a `name`, and optionally a `namespace`. |
+| httproute.rules | list | `[{"backendRefs":[{"name":"homarr","port":7575}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]` | List of routing rules. Each rule can include: - matches: path/header/query matching - filters: optional transformations (redirects, header modifications, etc.) - backendRefs: one or more Kubernetes Services to forward traffic to |
+| httproute.rules[0].filters | list | `[]` | Optional filters for this rule (default: empty) |
+| httproute.rules[0].matches[0].path.type | string | `"PathPrefix"` | Path match type. One of: Exact, PathPrefix, RegularExpression |
+| httproute.rules[0].matches[0].path.value | string | `"/"` | Path value to match |
+| image.pullPolicy | string | `"IfNotPresent"` | Image pull policy |
+| image.repository | string | `"ghcr.io/homarr-labs/homarr"` | Image repository |
+| image.tag | string | `"v1.74.0"` | Overrides the image tag whose default is the chart appVersion |
+| imagePullSecrets | list | `[]` | Secrets for Docker registry |
+| ingress.annotations | object | `{}` | Ingress annotations |
+| ingress.enabled | bool | `false` | Enable ingress |
+| ingress.hosts | list | `[{"host":"chart-example.local","paths":[{"path":"/"}]}]` | Ingress hosts configuration |
+| ingress.ingressClassName | string | `""` | Ingress class name |
+| ingress.tls | list | `[]` | Ingress TLS configuration |
+| livenessProbe.failureThreshold | int | `3` | Failure threshold for liveness probe - number of consecutive failures before pod is restarted |
+| livenessProbe.httpGet.path | string | `"/api/health/live"` | This is the liveness check endpoint used by Kubernetes to determine if the application is still running. |
+| livenessProbe.httpGet.port | int | `7575` | The port on which the liveness check will be performed. This must be the same as the container port exposed by the application. |
+| livenessProbe.initialDelaySeconds | int | `10` | Initial delay in seconds before the liveness probe starts |
+| livenessProbe.periodSeconds | int | `10` | Period in seconds between liveness probe checks |
+| livenessProbe.timeoutSeconds | int | `1` | Timeout in seconds for each liveness probe check |
+| nameOverride | string | `""` | Overrides chart's name |
+| nodeSelector | object | `{}` | Node selectors for pod scheduling |
+| persistence.homarrDatabase.accessMode | string | `"ReadWriteOnce"` | homarr-database access mode |
+| persistence.homarrDatabase.enabled | bool | `false` | Enable homarr-database persistent storage |
+| persistence.homarrDatabase.mountPath | string | `"/appdata"` | homarr-database mount path inside the pod |
+| persistence.homarrDatabase.name | string | `"homarr-database"` | homarr-database persistent storage name |
+| persistence.homarrDatabase.size | string | `"50Mi"` | homarr-database storage size |
+| persistence.homarrDatabase.storageClassName | string | `"local-path"` | homarr-database storage class name |
+| persistence.homarrDatabase.volumeClaimName | string | `""` | homarr-database optional volumeClaimName to target specific PV |
+| persistence.homarrTrustedCerts.certificates | string | `nil` | homarr-trusted-certificates certificates, each entry will become a new trusted certificate as a dedicated file (works only for "configmap" and "secret" mode) |
+| persistence.homarrTrustedCerts.enabled | bool | `false` | Enable trusted certificates persistence |
+| persistence.homarrTrustedCerts.existingSecretKeys | string | `nil` | List of keys (filenames) to mount from the existing secret (used only when type is "existingSecret") |
+| persistence.homarrTrustedCerts.existingSecretName | string | `""` | Name of the existing Kubernetes Secret to mount (required if type is "existingSecret") |
+| persistence.homarrTrustedCerts.mountPath | string | `"/appdata/trusted-certificates"` | homarr-trusted-certificates  mount path inside the pod |
+| persistence.homarrTrustedCerts.type | string | `"configmap"` | Persistence mode can be : configmap (declarative), secret (declarative) or existingSecret (mount an existing Kubernetes Secret by name and specify which keys to mount as files) |
+| podAnnotations | object | `{}` | Pod annotations |
+| podLabels | object | `{}` | Pod labels |
+| podSecurityContext | object | `{}` | Pod security context |
+| rbac | object | `{"enabled":false}` | Enable RBAC resources for Kubernetes integration Creates Role, ClusterRole, and associated bindings for Homarr's Kubernetes features |
+| rbac.enabled | bool | `false` | Enable to create RBAC resources and activate Kubernetes integration |
+| readinessProbe.failureThreshold | int | `3` | Failure threshold for readiness probe - number of consecutive failures before pod is considered unready |
+| readinessProbe.httpGet.path | string | `"/api/health/ready"` | This is the readiness check endpoint used by Kubernetes to determine if the application is ready to handle traffic. |
+| readinessProbe.httpGet.port | int | `7575` | The port on which the readiness check will be performed. This must match the container's exposed port. |
+| readinessProbe.initialDelaySeconds | int | `10` | Initial delay in seconds before the readiness probe starts. increase this value if the pod is slow to fully start. |
+| readinessProbe.periodSeconds | int | `10` | Period in seconds between readiness probe checks |
+| readinessProbe.timeoutSeconds | int | `1` | Timeout in seconds for each readiness probe check |
+| replicaCount | int | `1` | Number of replicas |
+| resources | object | `{}` | Resource configuration |
+| securityContext | object | `{}` | Security context |
+| service.enabled | bool | `true` | Enable service |
+| service.ipFamilies | list | `[]` | List of IP families to use for the service. Examples: - ["IPv4"] - ["IPv6"] - ["IPv4", "IPv6"] for dual-stack Leave empty to use cluster default behavior |
+| service.ipFamilyPolicy | string | `"SingleStack"` | Defines how the service assigns IP families (IPv4/IPv6) Possible values: - SingleStack (default): Only one IP family, usually IPv4 - PreferDualStack: Use dual-stack if the cluster supports it, fallback to single - RequireDualStack: Fail if dual-stack cannot be assigned |
+| service.ports.app.port | int | `7575` | Service port |
+| service.ports.app.protocol | string | `"TCP"` | Service protocol |
+| service.ports.app.targetPort | string | `"http"` | Service target port |
+| service.type | string | `"ClusterIP"` | Service type |
+| strategyType | string | `"RollingUpdate"` | `strategyType` specifies the strategy used to replace old Pods by new ones. `strategyType` can be `"Recreate"` or `"RollingUpdate"`. `"RollingUpdate"` is the default value and updates Pods in a rolling update fashion. `"Recreate"` will kill all existing Pods before new ones are created. The `"Recreate"` strategy is necessary when persistent volume's `accessMode` is set to `"ReadWriteOnce"` when using `helm upgrade`, as pod volume attachments to an existing PersistentVolumeClaim need to be cleared before a new pod can attach to it. |
+| tolerations | list | `[]` | Node tolerations for pod scheduling |
 
 ---
-
 Autogenerated from chart metadata using [helm-docs](https://github.com/norwoodj/helm-docs)

apps/docs/docs/getting-started/installation/home-assistant.mdx

@@ -14,7 +14,7 @@ Homarr can be seamlessly integrated into your Home Assistant setup with this add
 ## Installation
 
 1. **Add Repository**: Navigate to your Home Assistant Supervisor panel, and go to the Add-on Store. Add the following repository URL: `https://github.com/Wiggen94/ha-homarr-v1-server` or click this button
-   [![Open your Home Assistant instance and show the add add-on repository dialog with a specific repository URL pre-filled.](https://my.home-assistant.io/badges/supervisor_add_addon_repository.svg)](https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgithub.com%2FWiggen94%2Fha-homarr-v1-server)
+[![Open your Home Assistant instance and show the add add-on repository dialog with a specific repository URL pre-filled.](https://my.home-assistant.io/badges/supervisor_add_addon_repository.svg)](https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgithub.com%2FWiggen94%2Fha-homarr-v1-server)
 
 2. **Install the Add-on**: Search for "Homarr Server" in the Add-on Store and select it. Click on "Install" to start the installation process.
 

apps/docs/docs/getting-started/installation/portainer.mdx

@@ -1,7 +1,5 @@
 # Portainer
-
 ## Portainer Stacks
-
 ### Prerequisites
 
 - [Portainer Stacks](https://www.portainer.io/blog/stacks-docker-compose-the-portainer-way)
@@ -25,14 +23,15 @@ services:
     environment:
       - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
     ports:
-      - "7575:7575"
+      - '7575:7575'
 ```
 
+
 :::note
-Portainer will mount the files to your host machine. Please make sure to replace `<your-path>` from the docker run command with your desired storage location. The path must be absolute.
+Portainer will mount the files to your host machine. Please make sure to replace ``<your-path>`` from the docker run command with your desired storage location. The path must be absolute.
 :::
 
-Then, click on `Deploy the stack` and wait until the container has started.
+Then, click on ``Deploy the stack`` and wait until the container has started.
 
 :::tip
 
@@ -44,5 +43,5 @@ If you're unsure how to create a stack, checkout the [Portainer Documentation](h
 
 To update Homarr using Docker Compose or Portainer Stacks, simply pull the latest image and restart the container.
 
-1. Run `docker pull ghcr.io/homarr-labs/homarr:latest` to pull the latest image.
-2. Re-run `docker-compose up -d` or re-deploy the stack in Portainer.
+1. Run ``docker pull ghcr.io/homarr-labs/homarr:latest`` to pull the latest image.
+2. Re-run ``docker-compose up -d`` or re-deploy the stack in Portainer.

apps/docs/docs/getting-started/installation/proxmox.mdx

@@ -31,7 +31,7 @@ After you've installed Homarr, you can find a new LXC "homarr".
 
 # Updating
 
-Updating is as simple as executing
+Updating is as simple as executing 
 
 ```bash
 update
@@ -49,19 +49,17 @@ Some Homarr features require setting environment variables. When installing Homa
 
 # Troubleshooting
 
-If something does not work after an update, please first try rebooting the LXC or the homarr Service with
+If something does not work after an update, please first try rebooting the LXC or the homarr Service with 
 
 ```bash
 systemctl restart homarr
 ```
 
 # Getting help
-
 - If you are looking for help with the script, updating the LXC or troubleshooting the installer, please get in contact with the support of the community scripts. They provide support on their [Discord](https://discord.gg/2wvnMDgdnU). If you found vulnerabilities, bugs or have a request for the script, [create a new issue here](https://github.com/community-scripts/ProxmoxVE/issues/new/choose).
 - If you are looking to report a bug, vulnerability or request a new feature, use https://github.com/homarr-labs/homarr . You can ask for help on our Discord.
 
 # How to find logs
-
 Homarr runs under a system service called `homarr`, so getting the logs is a simple as using the following command inside the LXC (Container) Shell
 
 ```bash

apps/docs/docs/getting-started/installation/qnap.mdx

@@ -4,6 +4,6 @@
 QNAP installation guide has not updated to 1.0 yet. There guide is still for 0.15.10.
 :::
 
-When installing on QNAP, we recommend you to install Homarr using [Container Station](https://www.qnap.com/en/software/container-station) or [this third-party image](https://www.myqnap.org/product/homarr/).
+When installing on QNAP, we recommend you to install Homarr using [Container Station]( https://www.qnap.com/en/software/container-station) or [this third-party image](https://www.myqnap.org/product/homarr/).
 
 There is also a guide available, but note that it is written in Chinese: https://post.smzdm.com/p/awzm7op2/

apps/docs/docs/getting-started/installation/runtipi.mdx

@@ -1,4 +1,4 @@
-# Runtipi
+#  Runtipi
 
 Runtipi is a self-hosted orchestrator that makes it easy to manage and run multiple services on a single server. It is based on Docker and comes with a simple web interface to manage your services. Runtipi is designed to be easy to use, so you don't have to worry about manual configuration or networking.
 
@@ -11,7 +11,6 @@ https://runtipi.io
 # Installation
 
 Installing Homarr is pretty untuitive, the app is available in the default appstore :
-
 1. Search for **"Homarr"** in the App-Store page and select it
 2. Click on **"Install"**.
 3. Choose the method you want to access Homarr, through any port or domain name then select **"Install"**
@@ -19,15 +18,13 @@ Installing Homarr is pretty untuitive, the app is available in the default appst
 # Maintenance
 
 After installation, all you need is available from the WebUI in **"My apps"** > **"Homarr"** :
-
-- Start/Stop
-- Update
-- Backup
-- Logs
-
+ - Start/Stop
+ - Update
+ - Backup
+ - Logs
+ 
 If you like to tinker with your apps, you can also edit your app's docker-compose with a [user-config](https://runtipi.io/docs/guides/customize-app-config).
 
 # Getting help
-
 - If you are looking for help with anything in Runtipi. They provide support on their [Discord](https://discord.gg/Bu9qEPnHsc) and [forums](https://forums.runtipi.io/). If you found vulnerabilities or bugs, [create a new issue here](https://github.com/runtipi/runtipi-appstore/issues).
-- If you are looking to report a bug, vulnerability or request a new feature for Homarr, use https://github.com/homarr-labs/homarr . You can ask for help on our Discord.
+- If you are looking to report a bug, vulnerability or request a new feature for Homarr, use https://github.com/homarr-labs/homarr . You can ask for help on our Discord.

apps/docs/docs/getting-started/installation/saltbox.mdx

@@ -5,7 +5,6 @@ Saltbox installation command has not updated to 1.0 yet. There command still run
 :::
 
 You can also use this to install on Saltbox:
-
 ```bash
 sb install sandbox-homarr
-```
+```

apps/docs/docs/getting-started/installation/source.mdx

@@ -28,29 +28,15 @@ This method is only useful, when you want to develop on Homarr or extend it with
 ## Steps
 
 <ol>
-  <li>
-    Clone the Repository using <code>git clone https://github.com/homarr-labs/homarr.git</code>
-  </li>
-  <li>
-    Enter the created directory using <code>cd homarr</code>
-  </li>
-  <li>
-    Install all dependencies using <code>pnpm install</code>
-  </li>
-  <li>
-    Copy the `.env.example` file to `.env` and replace `DB_URL` with the full path you want to use for the sqlite
-    database file. For example `DB_URL='/home/username/homarr/db.sqlite`
-  </li>
-  <li>
-    Replace `AUTH_SECRET` and `SECRET_ENCRYPTION_KEY` both with a secure random string by using `openssl rand -hex 32`
-  </li>
+  <li>Clone the Repository using <code>git clone https://github.com/homarr-labs/homarr.git</code></li>
+  <li>Enter the created directory using <code>cd homarr</code></li>
+  <li>Install all dependencies using <code>pnpm install</code></li>
+  <li>Copy the `.env.example` file to `.env` and replace `DB_URL` with the full path you want to use for the sqlite database file. For example `DB_URL='/home/username/homarr/db.sqlite`</li>
+  <li>Replace `AUTH_SECRET` and `SECRET_ENCRYPTION_KEY` both with a secure random string by using `openssl rand -hex 32`</li>
   <li>Replace `CRON_JOB_API_KEY` with a secure random string by using `openssl rand -base64 32`</li>
   <li>Run `pnpm run db:migration:sqlite:run` and wait that it completes</li>
   <li>Build the source using `pnpm build`</li>
-  <li>
-    Copy better-sqlite3.node files with `mkdir build` and `cp
-    ./node_modules/better-sqlite3/build/Release/better_sqlite3.node ./build/better_sqlite3.node`
-  </li>
+  <li>Copy better-sqlite3.node files with `mkdir build` and `cp ./node_modules/better-sqlite3/build/Release/better_sqlite3.node ./build/better_sqlite3.node`</li>
   <li>Start a redis server using `redis-server`</li>
   <li>Run the server using `pnpm start`</li>
   <li>Open `http://localhost:3000` in your browser</li>

apps/docs/docs/getting-started/installation/unraid.mdx

@@ -1,5 +1,5 @@
-import Link from "@docusaurus/Link";
-import { IconDownload } from "@tabler/icons-react";
+import Link from '@docusaurus/Link';
+import { IconDownload } from '@tabler/icons-react';
 
 # Unraid
 
@@ -14,17 +14,17 @@ You can install Homarr directly from your Unraid Dashboard, no terminal required
 
 <Link
   data-attr="Install Unraid Community Apps"
-  className={"button button--secondary button--lg rounded-3xl dark:border-zinc-600 dark:bg-zinc-800"}
+  className={'button button--secondary button--lg rounded-3xl dark:border-zinc-600 dark:bg-zinc-800'}
   to="https://forums.unraid.net/topic/38582-plug-in-community-applications/"
 >
-  <div className={"flex items-center gap-3"}>
+  <div className={'flex items-center gap-3'}>
     <span className={"dark:text-gray-200"}>Install community applications plugin</span>
     <IconDownload className={"dark:text-gray-200"} size={20} />
   </div>
 </Link>
 
-<br />
-<br />
+<br/>
+<br/>
 
 :::tip
 
@@ -46,3 +46,4 @@ After you've installed the Community Apps Plugin, you can install Homarr from th
 After you've installed Homarr, you can find it under the tab "Docker".
 
 The official support thread is located [here](https://forums.unraid.net/topic/123478-support-smartphonelover-homarr/), but we prefer to communicate over GitHub and Discord instead.
+

apps/docs/docs/integrations/adguard-home/index.mdx

@@ -1,44 +1,37 @@
 ---
-title: "AdGuard Home"
+title: 'AdGuard Home'
 description: "AdGuard Home is a network-wide software for blocking ads and trackers, providing a safer and faster internet experience."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconAd, IconDeviceGamepad } from "@tabler/icons-react";
-import { adguardHomeIntegration } from ".";
-import { dnsHoleSummaryWidget } from "@site/docs/widgets/dns-hole-summary";
-import { dnsHoleControlsWidget } from "@site/docs/widgets/dns-hole-controls";
+import { adguardHomeIntegration } from '.';
+import { dnsHoleSummaryWidget } from '@site/docs/widgets/dns-hole-summary';
+import { dnsHoleControlsWidget } from '@site/docs/widgets/dns-hole-controls';
 
-<IntegrationHeader integration={adguardHomeIntegration} categories={["DNS Hole"]} />
+<IntegrationHeader
+    integration={adguardHomeIntegration}
+    categories={['DNS Hole']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: dnsHoleSummaryWidget,
-    },
-    {
-      widget: dnsHoleControlsWidget,
-    },
-  ]}
+    items={[{
+        widget: dnsHoleSummaryWidget,
+    },{
+        widget: dnsHoleControlsWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['username', 'password'],
+    steps: []
+}]} />

apps/docs/docs/integrations/anchor/index.mdx

@@ -1,45 +1,40 @@
 ---
-title: "Anchor"
+title: 'Anchor'
 description: "Anchor is a self-hosted note-taking application."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { anchorIntegration } from ".";
-import { anchorNoteWidget } from "@site/docs/widgets/anchor-note";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { anchorIntegration } from '.';
+import { anchorNoteWidget } from '@site/docs/widgets/anchor-note';
 
-<IntegrationHeader integration={anchorIntegration} categories={["Notes"]} />
+
+<IntegrationHeader
+  integration={anchorIntegration}
+  categories={['Notes']}
+/>
 
 The Anchor integration lets Homarr connect to your Anchor instance so you can display and edit selected notes directly from your dashboard.
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: anchorNoteWidget,
-    },
-  ]}
+  items={[{
+    widget: anchorNoteWidget
+  }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [
-        "Open your Anchor instance.",
-        "Generate or copy an API key from Anchor settings.",
-        "Paste that key into the API Key secret field in Homarr.",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+  credentials: ['apiKey'],
+  steps: [
+    'Open your Anchor instance.',
+    'Generate or copy an API key from Anchor settings.',
+    'Paste that key into the API Key secret field in Homarr.'
+  ]
+}]} />

apps/docs/docs/integrations/aria2/index.mdx

@@ -1,43 +1,38 @@
 ---
-title: "Aria2"
+title: 'Aria2'
 description: "Lightweight multiprotocol & multi-source command-line download utility. It supports HTTP/HTTPS, FTP, SFTP, BitTorrent and Metalink"
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { aria2Integration } from ".";
-import { downloadsWidget } from "@site/docs/widgets/downloads";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { aria2Integration } from '.';
+import { downloadsWidget } from '@site/docs/widgets/downloads';
 
-<IntegrationHeader integration={aria2Integration} categories={["Download", "Multiprotocol", "Multi-source"]} />
+<IntegrationHeader
+  integration={aria2Integration}
+  categories={['Download', 'Multiprotocol', 'Multi-source']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: downloadsWidget,
-    },
-  ]}
+  items={[{
+    widget: downloadsWidget,
+  }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-    {
-      credentials: [],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[
+  {
+    credentials: ['apiKey'],
+    steps: []
+  },
+  {
+    credentials: [],
+    steps: []
+  }]} />

apps/docs/docs/integrations/audiobookshelf/index.mdx

@@ -1,40 +1,41 @@
 ---
-title: "Audiobookshelf"
+title: 'Audiobookshelf'
 description: "Audiobookshelf is a self-hosted audiobook and podcast server that lets you manage and stream your audio library."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { audiobookshelfIntegration } from ".";
-import { audioStatsWidget } from "@site/docs/widgets/audio-stats";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { audiobookshelfIntegration } from '.';
+import { audioStatsWidget } from '@site/docs/widgets/audio-stats';
 
-<IntegrationHeader integration={audiobookshelfIntegration} categories={["Media"]} />
+
+<IntegrationHeader
+    integration={audiobookshelfIntegration}
+    categories={['Media']}
+/>
 
 Audiobookshelf provides library statistics including audiobook and podcast counts, listening time, and active sessions.
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: audioStatsWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: audioStatsWidget },
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [
-        "Open your Audiobookshelf instance",
-        "Go to Settings → Users",
-        "Click on your user account",
-        "Copy the API token from the user details",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: [
+        'Open your Audiobookshelf instance',
+        'Go to Settings → Users',
+        'Click on your user account',
+        'Copy the API token from the user details',
+    ]
+}]} />

apps/docs/docs/integrations/bazarr/index.mdx

@@ -1,30 +1,31 @@
 ---
-title: "Bazarr"
+title: 'Bazarr'
 description: "Bazarr is a companion application to Sonarr and Radarr that manages and downloads subtitles."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { bazarrIntegration } from ".";
-import { bazarrWidget } from "@site/docs/widgets/bazarr";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { bazarrIntegration } from '.';
+import { bazarrWidget } from '@site/docs/widgets/bazarr';
 
-<IntegrationHeader integration={bazarrIntegration} categories={["Subtitles", "Media"]} />
+<IntegrationHeader
+  integration={bazarrIntegration}
+  categories={['Subtitles', 'Media']}
+/>
 
 Bazarr complements Sonarr and Radarr by managing subtitle downloads. The Homarr integration uses your Bazarr API key to fetch missing subtitle counts and health badges.
 
 ### Screenshots
 
-import apiKeySettings from "./img/api-key-settings.png";
-import widgetOverview from "@site/docs/widgets/bazarr/img/widget-overview.png";
+import apiKeySettings from './img/api-key-settings.png';
+import widgetOverview from '@site/docs/widgets/bazarr/img/widget-overview.png';
 
 <div className="flex flex-col gap-4">
   <div>
-    <p>
-      API key location in Bazarr (<strong>Settings → General → Security</strong>):
-    </p>
+    <p>API key location in Bazarr (<strong>Settings → General → Security</strong>):</p>
     <img src={apiKeySettings} alt="bazarr-api-key-settings" width={128 * 4} />
   </div>
   <div>
@@ -34,25 +35,20 @@ import widgetOverview from "@site/docs/widgets/bazarr/img/widget-overview.png";
 </div>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: bazarrWidget }]} />
+<IntegrationCapabilites
+    items={[{ widget: bazarrWidget }]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
 You can find your Bazarr API key under **Settings → General → Security**.
 
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [
-        "Open Bazarr and go to Settings → General → Security.",
-        "Copy the API key and paste it into Homarr when creating the integration.",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: [
+      "Open Bazarr and go to Settings → General → Security.",
+      "Copy the API key and paste it into Homarr when creating the integration.",
+    ],
+}]} />

apps/docs/docs/integrations/beszel/index.mdx

@@ -1,22 +1,25 @@
 ---
-title: "Beszel"
+title: 'Beszel'
 description: "Beszel is a lightweight server monitoring platform with Docker stats, historical data, and alert functions."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { beszelIntegration } from ".";
-import { beszelSystemStatsWidget } from "@site/docs/widgets/beszel-system-stats";
-import { beszelSystemGridWidget } from "@site/docs/widgets/beszel-system-grid";
-import { beszelSystemTableWidget } from "@site/docs/widgets/beszel-system-table";
-import { beszelAlertsWidget } from "@site/docs/widgets/beszel-alerts";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { beszelIntegration } from '.';
+import { beszelSystemStatsWidget } from '@site/docs/widgets/beszel-system-stats';
+import { beszelSystemGridWidget } from '@site/docs/widgets/beszel-system-grid';
+import { beszelSystemTableWidget } from '@site/docs/widgets/beszel-system-table';
+import { beszelAlertsWidget } from '@site/docs/widgets/beszel-alerts';
 
-import beszelDashboard from "./img/beszel-dashboard.png";
+import beszelDashboard from './img/beszel-dashboard.png';
 
-<IntegrationHeader integration={beszelIntegration} categories={["System Monitoring"]} />
+<IntegrationHeader
+    integration={beszelIntegration}
+    categories={['System Monitoring']}
+/>
 
 Beszel monitors your servers in real time via lightweight agents, collecting CPU, memory, disk, network, GPU, temperature, and Docker container metrics. It stores historical data and supports configurable alerts.
 
@@ -25,33 +28,26 @@ Beszel monitors your servers in real time via lightweight agents, collecting CPU
 <img src={beszelDashboard} alt="Beszel dashboard overview showing all four widgets" />
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    { widget: beszelSystemStatsWidget },
-    { widget: beszelSystemGridWidget },
-    { widget: beszelSystemTableWidget },
-    { widget: beszelAlertsWidget },
-  ]}
+    items={[
+        { widget: beszelSystemStatsWidget },
+        { widget: beszelSystemGridWidget },
+        { widget: beszelSystemTableWidget },
+        { widget: beszelAlertsWidget },
+    ]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [
-        "Open your Beszel hub instance (default port 8090)",
-        "Use the same credentials you use to log in to the Beszel web UI",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['username', 'password'],
+    steps: [
+        'Open your Beszel hub instance (default port 8090)',
+        'Use the same credentials you use to log in to the Beszel web UI',
+    ]
+}]} />
 
 :::tip
 Beszel uses PocketBase under the hood. The default admin credentials are set during the initial Beszel setup.

apps/docs/docs/integrations/coolify/index.mdx

@@ -1,24 +1,29 @@
 ---
-title: "Coolify"
-description: "Self-hosted PaaS and deployment platform"
+title: 'Coolify'
+description: 'Self-hosted PaaS and deployment platform'
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { coolifyIntegration } from ".";
-import { coolifyWidget } from "../../widgets/coolify";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { coolifyIntegration } from '.';
+import { coolifyWidget } from '../../widgets/coolify';
 
-<IntegrationHeader integration={coolifyIntegration} categories={["System monitoring", "Deployment"]} />
+<IntegrationHeader
+  integration={coolifyIntegration}
+  categories={['System monitoring', 'Deployment']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: coolifyWidget }]} />
+<IntegrationCapabilites
+  items={[
+    { widget: coolifyWidget }
+  ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 :::info URL configuration
@@ -26,28 +31,16 @@ Use the root URL of your Coolify instance, for example `https://coolify.example.
 :::
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [
-        "Open your Coolify instance and make sure you are in the team you want Homarr to monitor.",
-        <span>
-          Enable API access under <strong>Settings &gt; Advanced</strong> if it is disabled.
-        </span>,
-        <span>
-          Go to <strong>Security &gt; API Tokens</strong>.
-        </span>,
-        'Enter a name, e.g. "Homarr".',
-        <span>
-          Select the <code>read</code> permission. The Coolify widget only reads version, server, project, application,
-          and service data.
-        </span>,
-        'Click "Create".',
-        "Copy the generated token immediately. Coolify only shows it once.",
-        "Paste the token into the API Key field in Homarr.",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+  credentials: ['apiKey'],
+  steps: [
+    'Open your Coolify instance and make sure you are in the team you want Homarr to monitor.',
+    (<span>Enable API access under <strong>Settings &gt; Advanced</strong> if it is disabled.</span>),
+    (<span>Go to <strong>Security &gt; API Tokens</strong>.</span>),
+    'Enter a name, e.g. "Homarr".',
+    (<span>Select the <code>read</code> permission. The Coolify widget only reads version, server, project, application, and service data.</span>),
+    'Click "Create".',
+    'Copy the generated token immediately. Coolify only shows it once.',
+    'Paste the token into the API Key field in Homarr.'
+  ]
+}]} />

apps/docs/docs/integrations/dash-dot/index.mdx

@@ -1,33 +1,32 @@
 ---
-title: "Dash."
+title: 'Dash.'
 description: "Dash. is a system performance and resource monitoring tool"
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconHeartRateMonitor } from "@tabler/icons-react";
-import { dashDotIntegration } from ".";
-import { healthMonitoringWidget } from "@site/docs/widgets/health-monitoring";
-import { systemResourcesWidget } from "@site/docs/widgets/system-resources";
+import { dashDotIntegration } from '.';
+import { healthMonitoringWidget } from '@site/docs/widgets/health-monitoring';
+import { systemResourcesWidget } from '@site/docs/widgets/system-resources';
 
-<IntegrationHeader integration={dashDotIntegration} categories={["System monitoring"]} />
+
+<IntegrationHeader
+  integration={dashDotIntegration}
+  categories={['System monitoring']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: healthMonitoringWidget,
-    },
-    {
-      widget: systemResourcesWidget,
-    },
-  ]}
+    items={[{
+      widget: healthMonitoringWidget
+    }, {
+      widget: systemResourcesWidget
+    }]}
 />
 
 ### Adding the integration
-
-<AddingIntegration />
+<AddingIntegration />

apps/docs/docs/integrations/deluge/index.mdx

@@ -1,41 +1,36 @@
 ---
-title: "Deluge"
+title: 'Deluge'
 description: "Deluge is a lightweight, Free Software, cross-platform BitTorrent client."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
 import { IconDownload } from "@tabler/icons-react";
-import Alert from "@theme/Admonition";
-import { delugeIntegration } from ".";
-import { downloadsWidget } from "@site/docs/widgets/downloads";
+import Alert from '@theme/Admonition';
+import { delugeIntegration } from '.';
+import { downloadsWidget } from '@site/docs/widgets/downloads';
 
-<IntegrationHeader integration={delugeIntegration} categories={["Torrent client"]} />
+
+<IntegrationHeader
+    integration={delugeIntegration}
+    categories={['Torrent client']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: downloadsWidget,
-    },
-  ]}
+    items={[{
+        widget: downloadsWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["password"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['password'],
+    steps: [],
+}]} />

apps/docs/docs/integrations/docker/index.mdx

@@ -1,31 +1,32 @@
 ---
-title: "Docker"
+title: 'Docker'
 description: "Docker is a platform where you can run your applications in containers, allowing for easy deployment and management of applications."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconBrandDocker, IconTool } from "@tabler/icons-react";
-import { dockerIntegration } from ".";
-import { dockerContainersWidget } from "@site/docs/widgets/docker-containers";
+import { dockerIntegration } from '.';
+import { dockerContainersWidget } from '@site/docs/widgets/docker-containers';
 
-<IntegrationHeader integration={dockerIntegration} categories={["Containers"]} />
 
-### Widgets & Capabilities
-
-<IntegrationCapabilites
-  items={[
-    {
-      widget: dockerContainersWidget,
-      note: "This widget can only be used with administrator privileges",
-    },
-  ]}
+<IntegrationHeader
+  integration={dockerIntegration}
+  categories={['Containers']}
 />
 
-## Enabling the Docker integration
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+      widget: dockerContainersWidget,
+      note: "This widget can only be used with administrator privileges"
+    }]}
+/>
 
+
+## Enabling the Docker integration
 This integration must first be enabled.
 If you directly run on the host system and you have docker installed, it will be enabled by default.
 Otherwise, you'll need to mount the [docker socket](https://docs.docker.com/engine/security/protect-access/) to the Homarr container,
@@ -48,7 +49,7 @@ services:
     environment:
       - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
     ports:
-      - "7575:7575"
+      - '7575:7575'
 ```
 
 With docker run, add this parameter: `-v /var/run/docker.sock:/var/run/docker.sock`.
@@ -123,10 +124,8 @@ services:
 ```
 
 ### Managing your Docker containers within Homarr
-
 Homarr allows you to interact with Docker containers running on your system.
 Each container row has an action menu with the following options:
-
 - **View logs** - opens a dedicated logs page with a live terminal
 - **Start** - start a stopped container
 - **Stop** - stop a running container
@@ -167,13 +166,11 @@ Currently Homarr supports one label for configuration of the containers:
 - **homarr.hide:** If set to any value, the container will be hidden from the Docker Containers widget and tools page.
 
 ### Security
-
 Mounting docker sockets can be risky, as they permit full control over your docker service.
 As an example, a thread actor could abuse Homarr use the socket to start, stop or delete containers on your system.
 
 Therefore we recommend the usage of a socket proxy, which can prohibit certain actions.
 A few examples include:
-
 - https://github.com/linuxserver/docker-socket-proxy
 - https://github.com/Tecnativa/docker-socket-proxy
 
@@ -181,44 +178,36 @@ See documentation of the respective proxies on how to configure them.
 Homarr may behave in unexpected ways when you use proxies.
 
 #### Permissions
-
 Homarr needs the following permissions from the Docker API:
-
 - Containers/Start
 - Containers/Stop
 - Containers/Restart
 - Containers/Remove
 
 For socket proxies, you will need these permissions:
-
 - `CONTAINERS=1`
 - `POST=1`
 
 **Caution:** `POST` access is security critical as it provides extensive capabilities to modify your docker environment. Please leave it disabled if you're concerned about this.
 
 As a workaround, you can use [LSIO's socket proxy](https://github.com/linuxserver/docker-socket-proxy) and set the following:
-
 - ALLOW_START=1
 - ALLOW_STOP=1
 - ALLOW_RESTARTS=1
 
-These will work even with `POST=0`.
+These will work even with `POST=0`. 
 
 You lose the ability to remove containers, but start, stop and restarts should work just fine.
 
 #### Connecting to Docker via Socket Proxies
-
 To connect to Docker via a socket proxy, you'll need to add these two environment variables in the compose file:
-
 - `DOCKER_HOSTNAMES=<name of the socket proxy container>`
 - `DOCKER_PORTS=<socket proxy port, usually 2375>`
 
 Refer: https://homarr.dev/docs/advanced/environment-variables/
 
 You will also need to add Homarr to the network of your socket proxy. You can do it like this:
-
 1. Add the network to your compose file (with appropriate changes):
-
 ```yaml
 networks:
   socket-proxy:
@@ -227,7 +216,6 @@ networks:
 ```
 
 2. Add the network to the homarr service in the compose file:
-
 ```yaml
 networks:
   - socket-proxy

apps/docs/docs/integrations/emby/index.mdx

@@ -1,35 +1,37 @@
 ---
-title: "Emby"
+title: 'Emby'
 description: "Emby is a media server platform that allows you to organize, manage, and stream your personal media collection."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconVideo, IconTicket } from "@tabler/icons-react";
-import { embyIntegration } from ".";
-import { mediaServerWidget } from "@site/docs/widgets/media-server";
-import { mediaReleasesWidget } from "@site/docs/widgets/media-releases";
+import { embyIntegration } from '.';
+import { mediaServerWidget } from '@site/docs/widgets/media-server';
+import { mediaReleasesWidget } from '@site/docs/widgets/media-releases';
 
-<IntegrationHeader integration={embyIntegration} categories={["Media server"]} />
+
+<IntegrationHeader
+    integration={embyIntegration}
+    categories={['Media server']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: mediaServerWidget }, { widget: mediaReleasesWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: mediaServerWidget }, 
+        { widget: mediaReleasesWidget }
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/glances/index.mdx

@@ -1,43 +1,37 @@
 ---
-title: "Glances"
+title: 'Glances'
 description: "Glances is a cross-platform system monitoring tool."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { glancesIntegration } from ".";
-import { systemResourcesWidget } from "@site/docs/widgets/system-resources";
-import { healthMonitoringWidget } from "@site/docs/widgets/health-monitoring";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { glancesIntegration } from '.';
+import { systemResourcesWidget } from '@site/docs/widgets/system-resources';
+import { healthMonitoringWidget } from '@site/docs/widgets/health-monitoring';
 
-<IntegrationHeader integration={glancesIntegration} categories={["System Monitoring"]} />
+
+<IntegrationHeader
+    integration={glancesIntegration}
+    categories={['System Monitoring']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: systemResourcesWidget,
-    },
-    {
-      widget: healthMonitoringWidget,
-    },
-  ]}
+    items={[{
+        widget: systemResourcesWidget
+    }, {
+        widget: healthMonitoringWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: [],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}]} />

apps/docs/docs/integrations/gluetun/index.mdx

@@ -1,17 +1,20 @@
 ---
-title: "Gluetun"
-description: "Connect Gluetun to Homarr as a VPN integration."
+title: 'Gluetun'
+description: 'Connect Gluetun to Homarr as a VPN integration.'
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { gluetunIntegration } from ".";
-import { vpnWidget } from "@site/docs/widgets/vpn";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { gluetunIntegration } from '.';
+import { vpnWidget } from '@site/docs/widgets/vpn';
 
-<IntegrationHeader integration={gluetunIntegration} categories={["VPN", "Network"]} />
+<IntegrationHeader
+  integration={gluetunIntegration}
+  categories={['VPN', 'Network']}
+/>
 
 [Gluetun](https://github.com/qdm12/gluetun) exposes a control server that Homarr can query to report the VPN tunnel
 status, DNS status, public IP address, and active provider details in the VPN widget.
@@ -19,11 +22,9 @@ status, DNS status, public IP address, and active provider details in the VPN wi
 ### Widgets & Capabilities
 
 <IntegrationCapabilites
-  items={[
-    {
-      widget: vpnWidget,
-    },
-  ]}
+  items={[{
+    widget: vpnWidget,
+  }]}
 />
 
 ### Setting up the Gluetun control server
@@ -39,20 +40,13 @@ Refer to the [Gluetun control server documentation](https://github.com/qdm12/glu
 Gluetun's control server can be left unprotected or secured with either an API key or HTTP Basic authentication.
 Choose the option that matches how your Gluetun instance integration is set up.
 
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: [],
-      steps: [],
-    },
-    {
-      credentials: ["username", "password"],
-      steps: [],
-    },
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-    ,
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+  credentials: [],
+  steps: [],
+},{
+  credentials: ['username', 'password'],
+  steps: [],
+},{
+  credentials: ['apiKey'],
+  steps: [],
+},,]} />

apps/docs/docs/integrations/gotify/index.mdx

@@ -1,39 +1,33 @@
 ---
-title: "Gotify"
+title: 'Gotify'
 description: "Gotify is a simple, self-hosted server for sending and receiving messages in real time."
 hide_title: true
 ---
 
-import { notificationsWidget } from "@site/docs/widgets/notifications";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { gotifyIntegration } from ".";
+import { notificationsWidget } from '@site/docs/widgets/notifications';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { gotifyIntegration } from '.';
 
-<IntegrationHeader integration={gotifyIntegration} categories={["Notifications", "Messaging"]} />
+<IntegrationHeader
+    integration={gotifyIntegration}
+    categories={['Notifications', 'Messaging']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: notificationsWidget,
-    },
-  ]}
+    items={[{
+        widget: notificationsWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['username', 'password'],
+    steps: []
+}]} />

apps/docs/docs/integrations/home-assistant/index.mdx

@@ -1,51 +1,45 @@
 ---
-title: "Home Assistant"
+title: 'Home Assistant'
 description: "Home Assistant is an open-source home automation platform that focuses on privacy and local control, allowing you to automate and control your smart home devices."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconBinaryTree } from "@tabler/icons-react";
-import { homeAssistantIntegration } from ".";
-import { smartHomeEntityStateWidget } from "@site/docs/widgets/smart-home-entity-state";
-import { smartHomeExecuteAutomationWidget } from "@site/docs/widgets/smart-home-execute-automation";
+import { homeAssistantIntegration } from '.';
+import { smartHomeEntityStateWidget } from '@site/docs/widgets/smart-home-entity-state';
+import { smartHomeExecuteAutomationWidget } from '@site/docs/widgets/smart-home-execute-automation';
 
-<IntegrationHeader integration={homeAssistantIntegration} categories={["Smart Home", "Automation"]} />
+
+<IntegrationHeader
+    integration={homeAssistantIntegration}
+    categories={['Smart Home', 'Automation']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: smartHomeEntityStateWidget,
-    },
-    {
-      widget: smartHomeExecuteAutomationWidget,
-    },
-  ]}
+    items={[{
+        widget: smartHomeEntityStateWidget
+    }, {
+        widget: smartHomeExecuteAutomationWidget,
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: [
         "Click on your profile in the bottom left corner of Home Assistant.",
         "Switch to the Security tab.",
         "Scroll down to the Long-lived access tokens section.",
         "Click on the Create Token button.",
         "Enter a name for the token (e.g., 'Homarr Integration') and click Create.",
         "Copy the generated token and paste it into the Homarr integration settings.",
-      ],
-    },
-  ]}
-/>
+    ]
+}]} />

apps/docs/docs/integrations/ical/index.mdx

@@ -1,44 +1,38 @@
 ---
-title: "iCal"
+title: 'iCal'
 description: "iCal is a standard for calendar data exchange, allowing users to share and manage calendar events across different platforms."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconZoomQuestion, IconChartBar, IconSearch } from "@tabler/icons-react";
-import { icalIntegration } from ".";
-import { calendarWidget } from "@site/docs/widgets/calendar";
+import { icalIntegration } from '.';
+import { calendarWidget } from '@site/docs/widgets/calendar';
 
-<IntegrationHeader integration={icalIntegration} categories={["Calendar"]} />
+<IntegrationHeader
+  integration={icalIntegration}
+  categories={['Calendar']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: calendarWidget,
-    },
-  ]}
+    items={[{
+      widget: calendarWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["url"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['url'],
+    steps: []
+}]} />
 
 ## Using the iCal integration
 
-The iCal integration allows you to add external calendars to Homarr. Any calendar that provides a public iCal URL can be integrated, such as Google Calendar, Apple Calendar, or Outlook.
+The iCal integration allows you to add external calendars to Homarr. Any calendar that provides a public iCal URL can be integrated, such as Google Calendar, Apple Calendar, or Outlook.

apps/docs/docs/integrations/immich/index.mdx

@@ -1,29 +1,36 @@
 ---
-title: "Immich"
+title: 'Immich'
 description: "Self-hosted photo and video management solution"
 hide_title: true
 ---
 
-import { immichAlbumCarouselWidget } from "../../widgets/immich-album-carousel";
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { immichIntegration } from ".";
-import { immichServerStatsWidget } from "../../widgets/immich-server-stats";
+import { immichAlbumCarouselWidget } from '../../widgets/immich-album-carousel';import {
+  IntegrationHeader
+} from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { immichIntegration } from '.';
+import { immichServerStatsWidget } from '../../widgets/immich-server-stats';
 
-<IntegrationHeader integration={immichIntegration} categories={["Photo server"]} />
+
+<IntegrationHeader
+  integration={immichIntegration}
+  categories={['Photo server']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: immichAlbumCarouselWidget }, { widget: immichServerStatsWidget }]} />
+<IntegrationCapabilites
+  items={[
+    { widget: immichAlbumCarouselWidget },
+    { widget: immichServerStatsWidget }
+  ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
 <IntegrationSecrets secrets={[{
   credentials: ['apiKey'],
   steps: [
@@ -48,10 +55,9 @@ import { immichServerStatsWidget } from "../../widgets/immich-server-stats";
     <code>asset.statistics</code>,{" "}
     <code>server.statistics</code>,{" "}
     <code>server.about</code>.
-
   </span>
 
 ),
-'Create the integration in Homarr and copy the API key to there'
-]
+    'Create the integration in Homarr and copy the API key to there'
+    ]
 }]} />

apps/docs/docs/integrations/jellyfin/index.mdx

@@ -1,39 +1,40 @@
 ---
-title: "Jellyfin"
+title: 'Jellyfin'
 description: "Jellyfin is a free and open-source media server software that allows you to organize, manage, and share your media files."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconVideo, IconTicket } from "@tabler/icons-react";
-import { jellyfinIntegration } from ".";
-import { mediaServerWidget } from "@site/docs/widgets/media-server";
-import { mediaReleasesWidget } from "@site/docs/widgets/media-releases";
+import { jellyfinIntegration } from '.';
+import { mediaServerWidget } from '@site/docs/widgets/media-server';
+import { mediaReleasesWidget } from '@site/docs/widgets/media-releases';
 
-<IntegrationHeader integration={jellyfinIntegration} categories={["Media server"]} />
+
+<IntegrationHeader
+    integration={jellyfinIntegration}
+    categories={['Media server']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: mediaServerWidget }, { widget: mediaReleasesWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: mediaServerWidget }, 
+        { widget: mediaReleasesWidget }
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-    {
-      credentials: ["username", "password"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+},{
+    credentials: ['username', 'password'],
+    steps: []
+}]} />

apps/docs/docs/integrations/jellyseerr/index.mdx

@@ -1,52 +1,45 @@
 ---
-title: "Jellyseerr"
+title: 'Jellyseerr'
 description: "Jellyseerr is a self-hosted media request management system that integrates with Jellyfin and other media servers."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconZoomQuestion, IconChartBar, IconSearch } from "@tabler/icons-react";
-import { jellyseerrIntegration } from ".";
-import { mediaRequestListWidget } from "@site/docs/widgets/media-request-list";
-import { mediaRequestStatsWidget } from "@site/docs/widgets/media-request-stats";
+import { jellyseerrIntegration } from '.';
+import { mediaRequestListWidget } from '@site/docs/widgets/media-request-list';
+import { mediaRequestStatsWidget } from '@site/docs/widgets/media-request-stats';
 
-<IntegrationHeader integration={jellyseerrIntegration} categories={["Media requests"]} />
+
+<IntegrationHeader
+  integration={jellyseerrIntegration}
+  categories={['Media requests']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: mediaRequestListWidget,
-    },
-    {
-      widget: mediaRequestStatsWidget,
-    },
-    {
-      capability: {
-        icon: IconSearch,
-        name: "Media Search",
-        description: "Search for movies and TV shows directly from Spotlight and request them.",
-        path: "../../management/search-engines/#media-request-search",
-      },
-    },
-  ]}
+    items={[{
+        widget: mediaRequestListWidget,
+    },{
+        widget: mediaRequestStatsWidget,
+    }, {
+        capability: {
+            icon: IconSearch,
+            name: "Media Search",
+            description: "Search for movies and TV shows directly from Spotlight and request them.",
+            path: "../../management/search-engines/#media-request-search"
+        }
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/kubernetes/index.mdx

@@ -1,16 +1,20 @@
 ---
-title: "Kubernetes"
+title: 'Kubernetes'
 description: "Kubernetes is a powerful container orchestration platform that automates the deployment, scaling, and management of containerized applications."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconBrandDocker, IconTool } from "@tabler/icons-react";
-import { kubernetesIntegration } from ".";
+import { kubernetesIntegration } from '.';
 
-<IntegrationHeader integration={kubernetesIntegration} categories={["Containers"]} />
+
+<IntegrationHeader
+  integration={kubernetesIntegration}
+  categories={['Containers']}
+/>
 
 Homarr provides a user-friendly Kubernetes dashboard that offers an overview of your cluster’s resources in a clear and structured interface. It allows users to view key Kubernetes objects, including `Pods`, `Services`, `Ingresses`, `Nodes`, `ConfigMaps`, `Secrets`, `Namespaces`, and `Volumes`, as well as basic metrics when the Kubernetes Metrics Server is enabled.
 
@@ -43,7 +47,7 @@ Enabling RBAC in the Helm chart creates the necessary Kubernetes Role-Based Acce
 - Service Account: A dedicated service account for Homarr.
 - Role & RoleBinding: Grants permissions within a specific namespace to list, watch, and get pods, services, secrets, configmaps, and more.
 - ClusterRole & ClusterRoleBinding: Extends the same permissions cluster-wide for additional flexibility.
-  :::
+:::
 
 ### Homarr Dashboard Overview
 

apps/docs/docs/integrations/lidarr/index.mdx

@@ -1,40 +1,35 @@
 ---
-title: "Lidarr"
+title: 'Lidarr'
 description: "Lidarr is a music management tool that automates the process of downloading, sorting, and renaming music."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconCalendar } from "@tabler/icons-react";
-import { lidarrIntegration } from ".";
-import { calendarWidget } from "@site/docs/widgets/calendar";
+import { lidarrIntegration } from '.';
+import { calendarWidget } from '@site/docs/widgets/calendar';
 
-<IntegrationHeader integration={lidarrIntegration} categories={["Media manager", "Servarr"]} />
+
+<IntegrationHeader
+    integration={lidarrIntegration}
+    categories={['Media manager', "Servarr"]}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: calendarWidget,
-    },
-  ]}
+    items={[{
+        widget: calendarWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/navidrome/index.mdx

@@ -1,39 +1,41 @@
 ---
-title: "Navidrome"
+title: 'Navidrome'
 description: "Navidrome is a self-hosted music server and streamer compatible with the Subsonic API."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { navidromeIntegration } from ".";
-import { audioStatsWidget } from "@site/docs/widgets/audio-stats";
-import { mediaServerWidget } from "@site/docs/widgets/media-server";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { navidromeIntegration } from '.';
+import { audioStatsWidget } from '@site/docs/widgets/audio-stats';
+import { mediaServerWidget } from '@site/docs/widgets/media-server';
 
-<IntegrationHeader integration={navidromeIntegration} categories={["Media", "Media server"]} />
+
+<IntegrationHeader
+    integration={navidromeIntegration}
+    categories={['Media', 'Media server']}
+/>
 
 Navidrome provides music library statistics including artist, album, and song counts, as well as now playing audio streams via the Subsonic API.
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: audioStatsWidget }, { widget: mediaServerWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: audioStatsWidget },
+        { widget: mediaServerWidget },
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [
-        "Use the same credentials you use to log in to Navidrome",
-        "The user must have access to the Subsonic API (enabled by default)",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['username', 'password'],
+    steps: [
+        'Use the same credentials you use to log in to Navidrome',
+        'The user must have access to the Subsonic API (enabled by default)',
+    ]
+}]} />

apps/docs/docs/integrations/nextcloud/index.mdx

@@ -1,43 +1,40 @@
 ---
-title: "Nextcloud"
+title: 'Nextcloud'
 description: "Nextcloud is a self-hosted productivity platform that provides file storage, collaboration tools, and more."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconCalendar } from "@tabler/icons-react";
-import Alert from "@theme/Admonition";
-import { nextcloudIntegration } from ".";
-import { calendarWidget } from "@site/docs/widgets/calendar";
-import { notificationsWidget } from "@site/docs/widgets/notifications";
+import Alert from '@theme/Admonition';
+import { nextcloudIntegration } from '.';
+import { calendarWidget } from '@site/docs/widgets/calendar';
+import { notificationsWidget } from '@site/docs/widgets/notifications';
 
-<IntegrationHeader integration={nextcloudIntegration} categories={["Calendar", "Notifications"]} />
+<IntegrationHeader
+  integration={nextcloudIntegration}
+  categories={['Calendar', 'Notifications']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: calendarWidget }, { widget: notificationsWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: calendarWidget },
+        { widget: notificationsWidget }
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [],
-      header: (
-        <Alert type="info">
-          Users who use 2FA will have to use Nextcloud's App Password tool to grant Homarr access, as 2FA breaks the
-          traditional process. For more information, see [Nextcloud's
-          Documentation](https://docs.nextcloud.com/server/stable/admin_manual/configuration_user/authentication.html#app-passwords)
-        </Alert>
-      ),
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['username', 'password'],
+    steps: [],
+    header: <Alert type="info">
+      Users who use 2FA will have to use Nextcloud's App Password tool to grant Homarr access, as 2FA breaks the traditional process. For more information, see [Nextcloud's Documentation](https://docs.nextcloud.com/server/stable/admin_manual/configuration_user/authentication.html#app-passwords)
+    </Alert>,
+}]} />

apps/docs/docs/integrations/ntfy/index.mdx

@@ -1,44 +1,37 @@
 ---
-title: "Ntfy"
+title: 'Ntfy'
 description: "Ntfy is a simple, open-source notification service that allows you to send and receive notifications across devices."
 hide_title: true
 ---
 
-import { notificationsWidget } from "@site/docs/widgets/notifications";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
+import { notificationsWidget } from '@site/docs/widgets/notifications';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { IconMessage } from "@tabler/icons-react";
-import { ntfyIntegration } from ".";
+import { ntfyIntegration } from '.';
 
-<IntegrationHeader integration={ntfyIntegration} categories={["Notifications", "Messaging"]} />
+<IntegrationHeader
+    integration={ntfyIntegration}
+    categories={['Notifications', 'Messaging']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: notificationsWidget,
-    },
-  ]}
+    items={[{
+        widget: notificationsWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["topic"],
-      steps: [],
-    },
-    {
-      credentials: ["topic", "apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['topic'],
+    steps: []
+}, {
+    credentials: ['topic', 'apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/nzbget/index.mdx

@@ -1,41 +1,36 @@
 ---
-title: "NZBGet"
+title: 'NZBGet'
 description: "NZBGet is a lightweight and efficient Usenet downloader."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
 import { IconDownload } from "@tabler/icons-react";
-import { nzbgetIntegration } from ".";
-import Alert from "@theme/Admonition";
-import { downloadsWidget } from "@site/docs/widgets/downloads";
+import { nzbgetIntegration } from '.';
+import Alert from '@theme/Admonition';
+import { downloadsWidget } from '@site/docs/widgets/downloads';
 
-<IntegrationHeader integration={nzbgetIntegration} categories={["Usenet client"]} />
+
+<IntegrationHeader
+  integration={nzbgetIntegration}
+  categories={['Usenet client']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: downloadsWidget,
-    },
-  ]}
+    items={[{
+        widget: downloadsWidget,
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['username', 'password'],
+    steps: [],
+}]} />

apps/docs/docs/integrations/open-media-vault/index.mdx

@@ -1,52 +1,42 @@
 ---
-title: "Open Media Vault"
+title: 'Open Media Vault'
 description: "Open Media Vault is a free network-attached storage server based on the Debian operating system."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconHeartRateMonitor } from "@tabler/icons-react";
-import { openMediaVaultIntegration } from ".";
-import Alert from "@theme/Admonition";
-import { healthMonitoringWidget } from "@site/docs/widgets/health-monitoring";
-import { systemResourcesWidget } from "@site/docs/widgets/system-resources";
+import { openMediaVaultIntegration } from '.';
+import Alert from '@theme/Admonition'
+import { healthMonitoringWidget } from '@site/docs/widgets/health-monitoring';
+import { systemResourcesWidget } from '@site/docs/widgets/system-resources';
 
-<IntegrationHeader integration={openMediaVaultIntegration} categories={["System monitoring"]} />
+<IntegrationHeader
+  integration={openMediaVaultIntegration}
+  categories={['System monitoring']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: healthMonitoringWidget,
-      note: "To use this widget, you must have the OpenMediaVault plugin openmediavault-cputemp installed.",
-    },
-    {
-      widget: systemResourcesWidget,
-    },
-  ]}
+    items={[{
+        widget: healthMonitoringWidget,
+        note: "To use this widget, you must have the OpenMediaVault plugin openmediavault-cputemp installed.",
+    }, {
+      widget: systemResourcesWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [],
-      body: (
-        <Alert type="caution">
-          The user used here must have administrative permissions or Homarr won't be able to read the system performance
-          and resource data.
-        </Alert>
-      ),
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['username', 'password'],
+    steps: [],
+    body: <Alert type="caution">
+        The user used here must have administrative permissions or Homarr won't be able to read the system performance and resource data.
+    </Alert>
+}]} />

apps/docs/docs/integrations/opnsense/index.mdx

@@ -1,75 +1,65 @@
 ---
-title: "OPNsense"
+title: 'OPNsense'
 description: "OPNsense is an open-source, easy-to-use, and easy-to-build firewall and routing platform."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconHeartRateMonitor } from "@tabler/icons-react";
-import { opnsenseIntegration } from ".";
-import Alert from "@theme/Admonition";
-import { firewallWidget } from "../../widgets/firewall";
+import { opnsenseIntegration } from '.';
+import Alert from '@theme/Admonition'
+import { firewallWidget } from '../../widgets/firewall';
 
-<IntegrationHeader integration={opnsenseIntegration} categories={["Firewall"]} />
+<IntegrationHeader
+  integration={opnsenseIntegration}
+  categories={['Firewall']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: firewallWidget,
-    },
-  ]}
+    items={[{
+        widget: firewallWidget,
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      tabLabel: "ApiKey (Key & Secret)",
-      credentials: ["opnsenseApiKey", "opnsenseApiSecret"],
-      header: (
-        <Alert type="info">
-          This integration does not require full API access to the firewall. The following guide outlines the process
-          for creating a restricted OPNsense user with a scrambled password, designed exclusively for API access. This
-          ensures minimal permissions and prevents local login capability.
-        </Alert>
-      ),
-      steps: [
+<IntegrationSecrets secrets={[{
+    tabLabel: "ApiKey (Key & Secret)",
+    credentials: ['opnsenseApiKey', 'opnsenseApiSecret'],
+    header: <Alert type="info">
+                This integration does not require full API access to the firewall. The following guide outlines the process for creating a restricted OPNsense user with a scrambled password, designed exclusively for API access. This ensures minimal permissions and prevents local login capability.
+    </Alert>,
+    steps: [
         "Log in to the OPNsense web interface as an administrator",
         "Navigate to System → Access → Users",
         "Click the + (Add) button to create a new user",
         <>
-          Fill in the user details:
-          <ul>
-            <li>Username: Enter a unique name</li>
-            <li>Password: Leave empty</li>
-            <li>Scrambled Password: Enable this option</li>
-            <li>Full name: (Optional) Add a descriptive name</li>
-          </ul>
+        Fill in the user details:
+            <ul>
+                <li>Username: Enter a unique name</li>
+                <li>Password: Leave empty</li>
+                <li>Scrambled Password: Enable this option</li>
+                <li>Full name: (Optional) Add a descriptive name</li>
+            </ul>
         </>,
         <>
-          In Privileges section → Select the option below:
-          <ul>
-            <li>Lobby: Dashboard</li>
-            <li>Reporting: Traffic</li>
-          </ul>
+        In Privileges section → Select the option below:
+            <ul>
+                <li>Lobby: Dashboard</li>
+                <li>Reporting: Traffic</li>
+            </ul>
         </>,
         "Click Save",
         "Return to the Users list",
         "Find the user and click the ticket icon in the Commands column",
         "Click Yes in the popup to confirm",
         "A txt file will download automatically, containing: Key and Secret",
-        "Save this file securely—this information will only be shown once",
-      ],
-    },
-  ]}
-/>
+        "Save this file securely—this information will only be shown once"
+    ],
+}]} />

apps/docs/docs/integrations/overseerr/index.mdx

@@ -1,52 +1,45 @@
 ---
-title: "Overseerr"
+title: 'Overseerr'
 description: "Overseerr is a self-hosted media request management system that integrates with Plex."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconZoomQuestion, IconChartBar, IconSearch } from "@tabler/icons-react";
-import { overseerrIntegration } from ".";
-import { mediaRequestListWidget } from "@site/docs/widgets/media-request-list";
-import { mediaRequestStatsWidget } from "@site/docs/widgets/media-request-stats";
+import { overseerrIntegration } from '.';
+import { mediaRequestListWidget } from '@site/docs/widgets/media-request-list';
+import { mediaRequestStatsWidget } from '@site/docs/widgets/media-request-stats';
 
-<IntegrationHeader integration={overseerrIntegration} categories={["Media requests"]} />
+
+<IntegrationHeader
+  integration={overseerrIntegration}
+  categories={['Media requests']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: mediaRequestListWidget,
-    },
-    {
-      widget: mediaRequestStatsWidget,
-    },
-    {
-      capability: {
-        icon: IconSearch,
-        name: "Media Search",
-        description: "Search for movies and TV shows directly from Spotlight and request them.",
-        path: "../../management/search-engines/#media-request-search",
-      },
-    },
-  ]}
+    items={[{
+        widget: mediaRequestListWidget
+    }, {
+        widget: mediaRequestStatsWidget
+    }, {
+        capability: {
+            icon: IconSearch,
+            name: "Media Search",
+            description: "Search for movies and TV shows directly from Spotlight and request them.",
+            path: "../../management/search-engines/#media-request-search"
+        }
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/paperless-ngx/index.mdx

@@ -1,40 +1,41 @@
 ---
-title: "Paperless-ngx"
+title: 'Paperless-ngx'
 description: "Paperless-ngx is a document management system that transforms your physical documents into a searchable online archive."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { paperlessNgxIntegration } from ".";
-import { paperlessNgxWidget } from "@site/docs/widgets/paperless-ngx";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { paperlessNgxIntegration } from '.';
+import { paperlessNgxWidget } from '@site/docs/widgets/paperless-ngx';
 
-<IntegrationHeader integration={paperlessNgxIntegration} categories={["Documents"]} />
+
+<IntegrationHeader
+    integration={paperlessNgxIntegration}
+    categories={['Documents']}
+/>
 
 Paperless-ngx provides document statistics including total documents, inbox count, correspondents, tags, and document types.
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: paperlessNgxWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: paperlessNgxWidget },
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [
-        "Open your Paperless-ngx instance",
-        "Navigate to Settings → Django Admin → Tokens",
-        "Create a new token for your user",
-        "Copy the token value",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: [
+        'Open your Paperless-ngx instance',
+        'Navigate to Settings → Django Admin → Tokens',
+        'Create a new token for your user',
+        'Copy the token value',
+    ]
+}]} />

apps/docs/docs/integrations/patchmon/index.mdx

@@ -1,42 +1,43 @@
 ---
-title: "PatchMon"
+title: 'PatchMon'
 description: "PatchMon is a patch management and monitoring solution for Linux hosts."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { patchmonIntegration } from ".";
-import { patchmonWidget } from "@site/docs/widgets/patchmon";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { patchmonIntegration } from '.';
+import { patchmonWidget } from '@site/docs/widgets/patchmon';
 
-<IntegrationHeader integration={patchmonIntegration} categories={["Health Monitoring"]} />
+
+<IntegrationHeader
+    integration={patchmonIntegration}
+    categories={['Health Monitoring']}
+/>
 
 PatchMon provides host and package update statistics including total hosts, hosts needing updates, and security update counts.
 
 The PatchMon widget requires users to be **signed in to Homarr**; see the [PatchMon widget documentation](/docs/widgets/patchmon#authentication) for details on authentication and public boards.
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: patchmonWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: patchmonWidget },
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["patchmonApiKey", "patchmonApiSecret"],
-      steps: [
-        "Open your PatchMon instance",
-        "Navigate to Settings and create a new GetHomepage API key",
-        "Copy the API key and secret from the success dialog",
-        "Paste them into Homarr — Basic authentication is handled automatically",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['patchmonApiKey', 'patchmonApiSecret'],
+    steps: [
+        'Open your PatchMon instance',
+        'Navigate to Settings and create a new GetHomepage API key',
+        'Copy the API key and secret from the success dialog',
+        'Paste them into Homarr — Basic authentication is handled automatically',
+    ]
+}]} />

apps/docs/docs/integrations/peanut/index.mdx

@@ -1,53 +1,48 @@
 ---
-title: "PeaNUT"
-description: "A tiny dashboard for Network UPS Tools (NUT) servers."
+title: 'PeaNUT'
+description: 'A tiny dashboard for Network UPS Tools (NUT) servers.'
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { peaNutIntegration } from ".";
-import { upsWidget } from "@site/docs/widgets/ups";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { peaNutIntegration } from '.';
+import { upsWidget } from '@site/docs/widgets/ups';
 
-<IntegrationHeader integration={peaNutIntegration} categories={["UPS", "Hardware"]} />
+<IntegrationHeader
+  integration={peaNutIntegration}
+  categories={['UPS', 'Hardware']}
+/>
 
 [PeaNUT](https://github.com/Brandawg93/PeaNUT) exposes the data of your [Network UPS Tools](https://networkupstools.org/) servers
 over a REST API, which Homarr reads to display the status of your UPS devices.
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
+    items={[{
       widget: upsWidget,
-    },
-  ]}
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
 PeaNUT secures its API with HTTP Basic authentication when the `WEB_USERNAME` and `WEB_PASSWORD` environment variables
 are set on the PeaNUT instance. Provide the same credentials here. If the instance runs with `AUTH_DISABLED=true`, no
 secrets are required.
 
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [
-        "Set WEB_USERNAME and WEB_PASSWORD on your PeaNUT instance.",
-        "Create an integration in Homarr with the PeaNUT URL and those credentials.",
-      ],
-    },
-    {
-      credentials: [],
-      steps: ["If PeaNUT runs with AUTH_DISABLED=true, create the integration with no credentials."],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['username', 'password'],
+    steps: [
+      "Set WEB_USERNAME and WEB_PASSWORD on your PeaNUT instance.",
+      "Create an integration in Homarr with the PeaNUT URL and those credentials.",
+    ],
+},{
+    credentials: [],
+    steps: [
+      "If PeaNUT runs with AUTH_DISABLED=true, create the integration with no credentials.",
+    ],
+}]} />

apps/docs/docs/integrations/pi-hole/index.mdx

@@ -1,54 +1,47 @@
 ---
-title: "Pi-hole"
+title: 'Pi-hole'
 description: "Pi-hole is a network-wide ad blocker that acts as a DNS sinkhole, blocking unwanted content and improving your browsing experience."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
 import { IconAd, IconDeviceGamepad } from "@tabler/icons-react";
-import Alert from "@theme/Admonition";
-import { dnsHoleSummaryWidget } from "@site/docs/widgets/dns-hole-summary";
-import { dnsHoleControlsWidget } from "@site/docs/widgets/dns-hole-controls";
-import { piHoleIntegration } from ".";
+import Alert from '@theme/Admonition';
+import { dnsHoleSummaryWidget } from '@site/docs/widgets/dns-hole-summary';
+import { dnsHoleControlsWidget } from '@site/docs/widgets/dns-hole-controls';
+import { piHoleIntegration } from '.';
 
-<IntegrationHeader integration={piHoleIntegration} categories={["DNS Hole"]} />
 
-<Alert type="note" className="my-2">
-  Homarr supports both Pi-hole v5 and v6. It automatically detects the version and uses the correct API.
+<IntegrationHeader
+    integration={piHoleIntegration}
+    categories={['DNS Hole']}
+/>
+
+<Alert type="note" className='my-2'>
+    Homarr supports both Pi-hole v5 and v6. It automatically detects the version and uses the correct API.
 </Alert>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: dnsHoleSummaryWidget,
-    },
-    {
-      widget: dnsHoleControlsWidget,
-    },
-  ]}
+    items={[{
+        widget: dnsHoleSummaryWidget,
+    },{
+        widget: dnsHoleControlsWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-      body: "Please note, that in v6 of Pi-hole you no longer specify an API key, but instead either a password or application password. We suggest to use the application password when possible.",
-    },
-    {
-      credentials: [],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: [],
+    body: "Please note, that in v6 of Pi-hole you no longer specify an API key, but instead either a password or application password. We suggest to use the application password when possible."
+}, {
+    credentials: [],
+    steps: []
+}]} />

apps/docs/docs/integrations/plex/index.mdx

@@ -1,47 +1,41 @@
 ---
-title: "Plex"
+title: 'Plex'
 description: "Plex is a media server platform that allows you to organize, manage, and stream your personal media collection."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconVideo, IconTicket } from "@tabler/icons-react";
-import { plexIntegration } from ".";
-import { mediaServerWidget } from "@site/docs/widgets/media-server";
-import { mediaReleasesWidget } from "@site/docs/widgets/media-releases";
+import { plexIntegration } from '.';
+import { mediaServerWidget } from '@site/docs/widgets/media-server';
+import { mediaReleasesWidget } from '@site/docs/widgets/media-releases';
 
-<IntegrationHeader integration={plexIntegration} categories={["Media server"]} />
+
+<IntegrationHeader
+  integration={plexIntegration}
+  categories={['Media server']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: mediaServerWidget }, { widget: mediaReleasesWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: mediaServerWidget }, 
+        { widget: mediaReleasesWidget }
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: [
         <span>
-          Follow the official{" "}
-          <a
-            href="https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/"
-            target="_blank"
-            rel="noopener noreferrer"
-          >
-            Plex documentation
-          </a>{" "}
-          to find your authentication token.
-        </span>,
-      ],
-    },
-  ]}
-/>
+            Follow the official <a href="https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/" target="_blank" rel="noopener noreferrer">Plex documentation</a> to find your authentication token.
+        </span>
+    ]
+}]} />

apps/docs/docs/integrations/prowlarr/index.mdx

@@ -1,34 +1,32 @@
 ---
-title: "Prowlarr"
+title: 'Prowlarr'
 description: "Prowlarr is an indexer manager for Usenet and BitTorrent, providing a unified interface to manage your indexers."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconHeartRateMonitor } from "@tabler/icons-react";
-import { prowlarrIntegration } from ".";
-import { indexerManagerWidget } from "@site/docs/widgets/indexer-manager";
+import { prowlarrIntegration } from '.';
+import { indexerManagerWidget } from '@site/docs/widgets/indexer-manager';
 
-<IntegrationHeader integration={prowlarrIntegration} categories={["Indexer"]} />
+<IntegrationHeader
+  integration={prowlarrIntegration}
+  categories={['Indexer']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: indexerManagerWidget }]} />
+<IntegrationCapabilites
+    items={[{ widget: indexerManagerWidget }]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/proxmox/index.mdx

@@ -1,107 +1,103 @@
 ---
-title: "Proxmox"
+title: 'Proxmox'
 description: "Proxmox is a powerful open-source virtualization platform that allows you to run virtual machines and containers."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconHeartRateMonitor } from "@tabler/icons-react";
-import { proxmoxIntegration } from ".";
-import Alert from "@theme/Admonition";
-import { healthMonitoringWidget } from "@site/docs/widgets/health-monitoring";
-import { systemResourcesWidget } from "@site/docs/widgets/system-resources";
+import { proxmoxIntegration } from '.';
+import Alert from '@theme/Admonition'
+import { healthMonitoringWidget } from '@site/docs/widgets/health-monitoring';
+import { systemResourcesWidget } from '@site/docs/widgets/system-resources';
 
-<IntegrationHeader integration={proxmoxIntegration} categories={["System monitoring"]} />
+<IntegrationHeader
+  integration={proxmoxIntegration}
+  categories={['System monitoring']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: healthMonitoringWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: healthMonitoringWidget },
+        
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      header: (
-        <Alert type="caution">
-          The Proxmox API may not work with Linux PAM standard authentication. It is strongly recommended to use the
-          Proxmox VE authentication server realm when creating your API user.
-        </Alert>
-      ),
-      credentials: ["username", "tokenId", "realm", "apiKey"],
-      steps: [
+<IntegrationSecrets secrets={[{
+    header: <Alert type="caution">
+        The Proxmox API may not work with Linux PAM standard authentication. It is strongly recommended to use the Proxmox VE authentication server realm when creating your API user.
+    </Alert>,
+    credentials: ['username', 'tokenId', 'realm', 'apiKey'],
+    steps: [
         "Navigate to the Proxmox portal, click on Datacenter",
         "Expand Permissions, click on Groups",
         "Click the Create button",
         "Name the group something informative, like api-users",
         "Click on the Permissions 'folder'",
         <>
-          Click Add {"->"} Group Permission
-          <ul>
-            <li>Path: /</li>
-            <li>Group: group from Step 4 above</li>
-            <li>Role: PVEAuditor</li>
-            <li>Propagate: Checked</li>
-          </ul>
+            Click Add {"->"} Group Permission
+            <ul>
+                <li>Path: /</li>
+                <li>Group: group from Step 4 above</li>
+                <li>Role: PVEAuditor</li>
+                <li>Propagate: Checked</li>
+            </ul>
         </>,
         "Expand Permissions, click on Users",
         <>
-          Click the Add button
-          <ul>
-            <li>User name: something informative like api</li>
-            <li>Realm: Proxmox VE authentication server</li>
-            <li>Password: create a secure password for the user</li>
-            <li>Confirm Password: re-enter the password</li>
-            <li>Group: group from Step 4 above</li>
-          </ul>
+            Click the Add button
+            <ul>
+                <li>User name: something informative like api</li>
+                <li>Realm: Proxmox VE authentication server</li>
+                <li>Password: create a secure password for the user</li>
+                <li>Confirm Password: re-enter the password</li>
+                <li>Group: group from Step 4 above</li>
+            </ul>
         </>,
         "Expand Permissions, click on API Tokens",
         <>
-          Click the Add button
-          <ul>
-            <li>User: user from Step 8 above</li>
-            <li>Token ID: something informative like the application or purpose like homarr</li>
-            <li>Privilege Separation: unchecked</li>
-          </ul>
+            Click the Add button
+            <ul>
+                <li>User: user from Step 8 above</li>
+                <li>Token ID: something informative like the application or purpose like homarr</li>
+                <li>Privilege Separation: unchecked</li>
+            </ul>
         </>,
         "Copy the Secret that is shown in Step 10 because it is only shown once",
         "Go back to the 'Permissions' menu",
         <>
-          Click Add {"->"} API Token Permission
-          <ul>
-            <li>Path: /</li>
-            <li>API Token: select the API token created in Step 10</li>
-            <li>Role: PVE Auditor</li>
-            <li>Propagate: Checked</li>
-          </ul>
+            Click Add {"->"} API Token Permission
+            <ul>
+                <li>Path: /</li>
+                <li>API Token: select the API token created in Step 10</li>
+                <li>Role: PVE Auditor</li>
+                <li>Propagate: Checked</li>
+            </ul>
         </>,
-      ],
-      body: (
-        <>
-          <span>
-            Sometimes you'll also find the <code>api@pve!homarr</code> format, within Homarr you'll have to split it up
-            into:
-          </span>
-          <ul>
+        ],
+    body: <>
+        <span>
+            Sometimes you'll also find the <code>api@pve!homarr</code> format, 
+            within Homarr you'll have to split it up into:
+        </span>
+        <ul>
             <li>
-              <b>Username:</b> api
+                <b>Username:</b> api
             </li>
             <li>
-              <b>Realm:</b> pve
+                <b>Realm:</b> pve
             </li>
             <li>
-              <b>Token ID:</b> homarr
+                <b>Token ID:</b> homarr
             </li>
-          </ul>
-        </>
-      ),
-    },
-  ]}
-/>
+        </ul>
+    </>
+}]} />

apps/docs/docs/integrations/q-bittorent/index.mdx

@@ -1,39 +1,37 @@
 ---
-title: "qBittorrent"
+title: 'qBittorrent'
 description: "qBittorrent is a free and open-source BitTorrent client."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
 import { IconDownload } from "@tabler/icons-react";
-import { qBittorentIntegration } from ".";
-import Alert from "@theme/Admonition";
-import { downloadsWidget } from "@site/docs/widgets/downloads";
+import { qBittorentIntegration } from '.';
+import Alert from '@theme/Admonition';
+import { downloadsWidget } from '@site/docs/widgets/downloads';
 
-<IntegrationHeader integration={qBittorentIntegration} categories={["Torrent client"]} />
+
+<IntegrationHeader
+  integration={qBittorentIntegration}
+  categories={['Torrent client']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: downloadsWidget }]} />
+<IntegrationCapabilites
+    items={[{ widget: downloadsWidget }]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-    {
-      credentials: ["username", "password"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+},{
+    credentials: ['username', 'password'],
+    steps: [],
+}]} />

apps/docs/docs/integrations/radarr/index.mdx

@@ -1,34 +1,33 @@
 ---
-title: "Radarr"
+title: 'Radarr'
 description: "Radarr is a movie management tool that automates the process of downloading, sorting, and renaming movies."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconCalendar } from "@tabler/icons-react";
-import { radarrIntegration } from ".";
-import { calendarWidget } from "@site/docs/widgets/calendar";
+import { radarrIntegration } from '.';
+import { calendarWidget } from '@site/docs/widgets/calendar';
 
-<IntegrationHeader integration={radarrIntegration} categories={["Media manager", "Servarr"]} />
+
+<IntegrationHeader
+  integration={radarrIntegration}
+  categories={['Media manager', "Servarr"]}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: calendarWidget }]} />
+<IntegrationCapabilites
+    items={[{ widget: calendarWidget }]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/readarr/index.mdx

@@ -1,34 +1,33 @@
 ---
-title: "Readarr"
+title: 'Readarr'
 description: "Readarr is a book management tool that automates the process of downloading, sorting, and renaming books."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconCalendar } from "@tabler/icons-react";
-import { readarrIntegration } from ".";
-import { calendarWidget } from "@site/docs/widgets/calendar";
+import { readarrIntegration } from '.';
+import { calendarWidget } from '@site/docs/widgets/calendar';
 
-<IntegrationHeader integration={readarrIntegration} categories={["Media manager", "Servarr"]} />
+
+<IntegrationHeader
+  integration={readarrIntegration}
+  categories={['Media manager', "Servarr"]}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: calendarWidget }]} />
+<IntegrationCapabilites
+    items={[{ widget: calendarWidget }]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/sabnzbd/index.mdx

@@ -1,35 +1,34 @@
 ---
-title: "SABnzbd"
+title: 'SABnzbd'
 description: "SABnzbd is an Open Source Binary Newsreader."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
 import { IconDownload } from "@tabler/icons-react";
-import { sabnzbdIntegration } from ".";
-import Alert from "@theme/Admonition";
-import { downloadsWidget } from "@site/docs/widgets/downloads";
+import { sabnzbdIntegration } from '.';
+import Alert from '@theme/Admonition';
+import { downloadsWidget } from '@site/docs/widgets/downloads';
 
-<IntegrationHeader integration={sabnzbdIntegration} categories={["Usenet client"]} />
+
+<IntegrationHeader
+  integration={sabnzbdIntegration}
+  categories={['Usenet client']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: downloadsWidget }]} />
+<IntegrationCapabilites
+    items={[{ widget: downloadsWidget}]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: [],
+}]} />

apps/docs/docs/integrations/seerr/index.mdx

@@ -1,52 +1,45 @@
 ---
-title: "Seerr"
+title: 'Seerr'
 description: "Seerr is a self-hosted media request management system that integrates with various media servers."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconZoomQuestion, IconChartBar, IconSearch } from "@tabler/icons-react";
-import { seerrIntegration } from ".";
-import { mediaRequestListWidget } from "@site/docs/widgets/media-request-list";
-import { mediaRequestStatsWidget } from "@site/docs/widgets/media-request-stats";
+import { seerrIntegration } from '.';
+import { mediaRequestListWidget } from '@site/docs/widgets/media-request-list';
+import { mediaRequestStatsWidget } from '@site/docs/widgets/media-request-stats';
 
-<IntegrationHeader integration={seerrIntegration} categories={["Media requests"]} />
+
+<IntegrationHeader
+  integration={seerrIntegration}
+  categories={['Media requests']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: mediaRequestListWidget,
-    },
-    {
-      widget: mediaRequestStatsWidget,
-    },
-    {
-      capability: {
-        icon: IconSearch,
-        name: "Media Search",
-        description: "Search for movies and TV shows directly from Spotlight and request them.",
-        path: "../../management/search-engines/#media-request-search",
-      },
-    },
-  ]}
+    items={[{
+        widget: mediaRequestListWidget
+    }, {
+        widget: mediaRequestStatsWidget
+    }, {
+        capability: {
+            icon: IconSearch,
+            name: "Media Search",
+            description: "Search for movies and TV shows directly from Spotlight and request them.",
+            path: "../../management/search-engines/#media-request-search"
+        }
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/slskd/index.mdx

@@ -1,39 +1,34 @@
 ---
-title: "Slskd"
+title: 'Slskd'
 description: "A modern client-server application for the Soulseek file sharing network."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { slskdIntegration } from ".";
-import { downloadsWidget } from "@site/docs/widgets/downloads";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { slskdIntegration } from '.';
+import { downloadsWidget } from '@site/docs/widgets/downloads';
 
-<IntegrationHeader integration={slskdIntegration} categories={["System Monitoring"]} />
+
+<IntegrationHeader
+    integration={slskdIntegration}
+    categories={['System Monitoring']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: downloadsWidget,
-    },
-  ]}
+    items={[{
+        widget: downloadsWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ["apiKey"],
+    steps: []
+}]} />

apps/docs/docs/integrations/sonarr/index.mdx

@@ -1,34 +1,33 @@
 ---
-title: "Sonarr"
+title: 'Sonarr'
 description: "Sonarr is a TV series management tool that automates the process of downloading, sorting, and renaming episodes."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconCalendar } from "@tabler/icons-react";
-import { sonarrIntegration } from ".";
-import { calendarWidget } from "@site/docs/widgets/calendar";
+import { sonarrIntegration } from '.';
+import { calendarWidget } from '@site/docs/widgets/calendar';
 
-<IntegrationHeader integration={sonarrIntegration} categories={["Media manager", "Servarr"]} />
+
+<IntegrationHeader
+  integration={sonarrIntegration}
+  categories={['Media manager', "Servarr"]}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: calendarWidget }]} />
+<IntegrationCapabilites
+    items={[{ widget: calendarWidget }]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/speedtest-tracker/index.mdx

@@ -1,39 +1,34 @@
 ---
-title: "Speedtest Tracker"
-description: "Speedtest Tracker is a self-hosted internet performance tracking application."
+title: 'Speedtest Tracker'
+description: 'Speedtest Tracker is a self-hosted internet performance tracking application.'
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { speedtestTrackerIntegration } from ".";
-import { speedtestTrackerWidget } from "@site/docs/widgets/speedtest-tracker";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { speedtestTrackerIntegration } from '.';
+import { speedtestTrackerWidget } from '@site/docs/widgets/speedtest-tracker';
 
-<IntegrationHeader integration={speedtestTrackerIntegration} categories={["Speedtest"]} />
+
+<IntegrationHeader
+    integration={speedtestTrackerIntegration}
+    categories={['Speedtest']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: speedtestTrackerWidget,
-    },
-  ]}
+    items={[{
+        widget: speedtestTrackerWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/synology/index.mdx

@@ -19,7 +19,11 @@ import Alert from "@theme/Admonition";
 ### Widgets & Capabilities
 
 <IntegrationCapabilites
-  items={[{ widget: healthMonitoringWidget }, { widget: systemResourcesWidget }, { widget: systemDisksWidget }]}
+  items={[
+    { widget: healthMonitoringWidget },
+    { widget: systemResourcesWidget },
+    { widget: systemDisksWidget },
+  ]}
 />
 
 ### Supported metrics

apps/docs/docs/integrations/tdarr/index.mdx

@@ -1,38 +1,36 @@
 ---
-title: "Tdarr"
+title: 'Tdarr'
 description: "Tdarr is a distributed media transcoding system that allows you to process and optimize your media files across multiple nodes."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconTransform } from "@tabler/icons-react";
-import { tdarrIntegration } from ".";
-import { mediaTranscodingWidget } from "@site/docs/widgets/media-transcoding";
+import { tdarrIntegration } from '.';
+import { mediaTranscodingWidget } from '@site/docs/widgets/media-transcoding';
 
-<IntegrationHeader integration={tdarrIntegration} categories={["Media Transcoding"]} />
+
+<IntegrationHeader
+  integration={tdarrIntegration}
+  categories={['Media Transcoding']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: mediaTranscodingWidget }]} />
+<IntegrationCapabilites
+    items={[{ widget: mediaTranscodingWidget }]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-    {
-      credentials: [],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}, {
+    credentials: [],
+    steps: []
+}]} />

apps/docs/docs/integrations/technitium-dns/index.mdx

@@ -1,72 +1,62 @@
 ---
-title: "Technitium DNS"
+title: 'Technitium DNS'
 description: "Technitium DNS Server is a self-hosted DNS server with ad-blocking and network-wide filtering capabilities."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import Alert from "@theme/Admonition";
-import { technitiumDnsIntegration } from ".";
-import { dnsHoleSummaryWidget } from "@site/docs/widgets/dns-hole-summary";
-import { dnsHoleControlsWidget } from "@site/docs/widgets/dns-hole-controls";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import Alert from '@theme/Admonition';
+import { technitiumDnsIntegration } from '.';
+import { dnsHoleSummaryWidget } from '@site/docs/widgets/dns-hole-summary';
+import { dnsHoleControlsWidget } from '@site/docs/widgets/dns-hole-controls';
 
-<IntegrationHeader integration={technitiumDnsIntegration} categories={["DNS Hole"]} />
+<IntegrationHeader
+    integration={technitiumDnsIntegration}
+    categories={['DNS Hole']}
+/>
 
-<Alert type="note" className="my-2">
-  Homarr supports Technitium DNS v11 and above. The correct API version is detected automatically - no manual
-  configuration is required.
+<Alert type="note" className='my-2'>
+    Homarr supports Technitium DNS v11 and above. The correct API version is detected automatically - no manual configuration is required.
 </Alert>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: dnsHoleSummaryWidget,
-    },
-    {
-      widget: dnsHoleControlsWidget,
-    },
-  ]}
+    items={[{
+        widget: dnsHoleSummaryWidget,
+    },{
+        widget: dnsHoleControlsWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
 
-<Alert type="info" className="my-2">
-  The **API token** option is recommended. API tokens are non-expiring and do not require storing your admin password in
-  Homarr. Username and password authentication uses a session token that expires after inactivity, triggering a silent
-  re-login on the next request.
+<Alert type="info" className='my-2'>
+    The **API token** option is recommended. API tokens are non-expiring and do not require storing your admin password in Homarr.
+    Username and password authentication uses a session token that expires after inactivity, triggering a silent re-login on the next request.
 </Alert>
 
-<Alert type="warning" className="my-2">
-  The **DNS Hole Controls** widget (enabling, disabling, and timed disabling of blocking) requires the token to have
-  settings-level permissions. The **DNS Hole Summary** widget (stats only) works with any valid token. If Homarr cannot
-  read the blocking status due to insufficient permissions, the status indicator will be hidden but statistics will
-  still be shown.
+<Alert type="warning" className='my-2'>
+    The **DNS Hole Controls** widget (enabling, disabling, and timed disabling of blocking) requires the token to have settings-level permissions.
+    The **DNS Hole Summary** widget (stats only) works with any valid token.
+    If Homarr cannot read the blocking status due to insufficient permissions, the status indicator will be hidden but statistics will still be shown.
 </Alert>
 
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: [
         "Open the Technitium DNS web console and sign in.",
-        'Click on your username in the top-right corner and select "Create API Token".',
-        'Give the token a name (e.g. "Homarr") and click "Create Token".',
-        "Copy the generated token and paste it into the API Key field in Homarr.",
-      ],
-    },
-    {
-      credentials: ["username", "password"],
-      steps: [],
-      body: "Enter your Technitium DNS admin credentials. Homarr will exchange them for a session token and transparently re-authenticate when the session expires.",
-    },
-  ]}
-/>
+        "Click on your username in the top-right corner and select \"Create API Token\".",
+        "Give the token a name (e.g. \"Homarr\") and click \"Create Token\".",
+        "Copy the generated token and paste it into the API Key field in Homarr."
+    ]
+}, {
+    credentials: ['username', 'password'],
+    steps: [],
+    body: "Enter your Technitium DNS admin credentials. Homarr will exchange them for a session token and transparently re-authenticate when the session expires."
+}]} />