docs: add docs details

2026-07-01 18:49:13 +02:00
894 changed files with 19323 additions and 52612 deletions
@@ -6,14 +6,7 @@ npm-debug.log
 README.md
 .next
 .turbo
-.pnpm-store
-**/.pnpm-store
-coverage
-**/coverage
-**/.docusaurus
-**/build
 .git
-.github
 dev
 .build
 e2e
@@ -59,11 +59,4 @@ TURBO_TELEMETRY_DISABLED=1
 # ENABLE_KUBERNETES=true

 # Enable mock integration
-UNSAFE_ENABLE_MOCK_INTEGRATION=true
-
-# 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
+UNSAFE_ENABLE_MOCK_INTEGRATION=true
@@ -33,9 +33,6 @@ body:
      options:
        # The below comment is used to insert a new version with on-release.yml
        #NEXT_VERSION#
-        - 1.70.0
-        - 1.69.2
-        - 1.69.0
        - 1.68.0
        - 1.67.0
        - 1.66.1
@@ -1,2 +0,0 @@
-.secrets
-!.secrets.example
@@ -1,4 +0,0 @@
-TURBO_API=
-TURBO_TEAM=
-TURBO_TOKEN=
-TURBO_REMOTE_CACHE_SIGNATURE_KEY=
@@ -1,36 +0,0 @@
-# Running CI locally
-
-Install [Act](https://nektosact.com/installation/index.html) and ensure Docker is running, then use:
-
-```bash
-pnpm ci:act:fast
-pnpm ci:act:docker
-pnpm ci:act:all
-pnpm ci:act:cleanup
-```
-
-`fast` runs the quality gate. `docker` and `all` run the gate followed by the single container build, E2E suite, and memory regression test. `cleanup` validates the manual cleanup path without calling GitHub. The wrapper supports regular clones and Git worktrees, including non-default Docker contexts. Linux dependencies are kept in Docker volumes instead of overwriting host `node_modules`. The first run downloads the Act runner and Playwright browser dependencies.
-
-Remote caching is optional locally. Copy `.github/act/.secrets.example` to `.github/act/.secrets`, populate it with rotated credentials, and run with:
-
-```bash
-ACT_SECRET_FILE=.github/act/.secrets pnpm ci:act:all
-```
-
-Act never publishes or deletes GHCR images. The secret file is ignored by Git.
-
-## PR preview images
-
-Successful non-draft pull requests from this repository publish an amd64 image:
-
-```bash
-docker pull ghcr.io/homarr-labs/homarr-test:pr-<number>
-```
-
-The tag is replaced when the pull request is updated and deleted when it closes. Production Homarr images remain the supported multi-architecture releases. The `homarr-test` package must be configured as public in GHCR for unauthenticated testers.
-
-## Dokploy preview cache
-
-Keep `needs-demo` as the Dokploy preview label. Under the application's **Preview Build-time Secrets**, configure `TURBO_API`, `TURBO_TEAM`, `TURBO_TOKEN`, and `TURBO_REMOTE_CACHE_SIGNATURE_KEY`. Dokploy passes these to the Dockerfile as BuildKit secrets. Do not configure the token or signature key as Docker build arguments.
-
-Rotate any credentials that have appeared in chat, logs, or committed configuration before enabling the cache.
@@ -11,7 +11,7 @@ outputs:
 runs:
  using: "composite"
  steps:
-    - uses: actions/checkout@v7
+    - uses: actions/checkout@v6
      with:
        persist-credentials: false
    - name: Set up Docker Buildx
@@ -11,11 +11,3 @@
 - [ ] Commits follow the [conventional commits guideline](https://www.conventionalcommits.org/en/v1.0.0/)
 - [ ] No shorthand variable names are used (eg. `x`, `y`, `i` or any abbrevation)
 - [ ] Documentation is up to date. Create a pull request [here](https://github.com/homarr-labs/documentation/).
- [ ] When using AI; No temp files are checked in, the code style follows the rest of the project
-
-**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)
- [ ] 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)
@@ -1,47 +0,0 @@
-name: Auto-fix lint and format
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened]
-    branches: ["*"]
-
-permissions:
-  contents: write
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number }}
-  cancel-in-progress: true
-
-jobs:
-  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
-          ref: ${{ github.head_ref }}
-
-      - name: Setup
-        uses: ./tooling/github/setup
-
-      - name: Get changed files
-        id: changed
-        env:
-          BASE_REF: ${{ github.base_ref }}
-        run: |
-          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"
@@ -17,7 +17,7 @@ jobs:
    if: github.actor_id == 158783068 || github.actor_id == 190541745 || github.actor_id == 210161987 || github.actor_id == 175486441
    steps:
      - name: Checkout code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
      - name: Obtain token
        id: obtainToken
        uses: actions/create-github-app-token@v3
@@ -1,347 +0,0 @@
-name: CI
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened, ready_for_review]
-    branches: ["*"]
-  pull_request_target:
-    types: [closed]
-    branches: ["*"]
-  push:
-    branches: [main, dev, beta, next]
-  merge_group:
-  workflow_dispatch:
-    inputs:
-      operation:
-        description: Operation to run
-        required: true
-        default: validate
-        type: choice
-        options:
-          - validate
-          - publish
-          - cleanup
-      pr_number:
-        description: PR number for publish or cleanup
-        required: false
-        type: number
-      ref:
-        description: Git ref to validate or publish
-        required: false
-        type: string
-
-permissions:
-  contents: read
-
-concurrency:
-  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
-  SKIP_ENV_VALIDATION: true
-  TURBO_TELEMETRY_DISABLED: 1
-  REGISTRY: ghcr.io
-  PREVIEW_IMAGE: ghcr.io/homarr-labs/homarr-test
-
-jobs:
-  fast-gate:
-    name: Fast gate
-    if: github.event_name != 'pull_request_target' && (github.event_name != 'workflow_dispatch' || inputs.operation != 'cleanup')
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-    env:
-      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 }}
-      TURBO_SCM_BASE: ${{ github.event.pull_request.base.sha || github.event.merge_group.base_sha || github.event.before || 'HEAD~1' }}
-      TURBO_SCM_HEAD: ${{ github.sha }}
-      TURBO_PLATFORM: linux/amd64
-    steps:
-      - uses: actions/checkout@v7
-        if: '!env.ACT'
-        with:
-          fetch-depth: 0
-          persist-credentials: false
-          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || '' }}
-
-      - name: Validate manual inputs
-        if: github.event_name == 'workflow_dispatch' && inputs.operation == 'publish'
-        env:
-          PR_NUMBER: ${{ inputs.pr_number }}
-          BUILD_REF: ${{ inputs.ref }}
-        run: |
-          test -n "$PR_NUMBER" || { echo "pr_number is required for publish"; exit 1; }
-          test -n "$BUILD_REF" || { echo "ref is required for publish"; exit 1; }
-
-      - name: Setup
-        uses: ./tooling/github/setup
-
-      - name: Copy environment defaults
-        run: cp .env.example .env
-
-      - name: Check formatting in affected workspaces
-        run: pnpm turbo run format --affected --continue -- --check
-
-      - name: Lint, typecheck, and build affected workspaces
-        run: pnpm turbo run lint typecheck build --affected --continue=dependencies-successful
-
-      - name: Validate workspace configuration
-        run: pnpm lint:ws
-
-      - name: Run unit tests
-        run: pnpm test
-
-      - name: Report coverage
-        if: always() && !env.ACT
-        uses: davelosert/vitest-coverage-report-action@v2
-
-  container:
-    name: Container, E2E, and memory
-    needs: fast-gate
-    if: |
-      github.event_name == 'merge_group' ||
-      (github.event_name == 'pull_request' && github.event.pull_request.draft == false) ||
-      (github.event_name == 'workflow_dispatch' && (inputs.operation == 'validate' || inputs.operation == 'publish'))
-    runs-on: ubuntu-latest
-    timeout-minutes: 30
-    permissions:
-      contents: read
-      packages: write
-    steps:
-      - uses: actions/checkout@v7
-        if: '!env.ACT'
-        with:
-          persist-credentials: false
-          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || '' }}
-
-      - name: Setup
-        uses: ./tooling/github/setup
-
-      - name: Set up Docker Buildx
-        if: '!env.ACT'
-        uses: docker/setup-buildx-action@v4
-
-      - name: Build container once
-        if: '!env.ACT'
-        uses: docker/build-push-action@v7
-        with:
-          context: .
-          network: host
-          platforms: linux/amd64
-          load: true
-          push: false
-          tags: |
-            homarr-ci
-            homarr-e2e
-          labels: |
-            org.opencontainers.image.source=${{ github.server_url }}/${{ github.repository }}
-            org.opencontainers.image.revision=${{ github.sha }}
-            org.opencontainers.image.ref.name=pr-${{ github.event.pull_request.number || inputs.pr_number || 'none' }}
-          cache-from: type=gha,scope=homarr-linux-amd64
-          cache-to: type=gha,scope=homarr-linux-amd64,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 }}
-
-      - name: Build container once with Act
-        if: env.ACT
-        env:
-          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 }}
-        run: |
-          secret_args=()
-          for secret in TURBO_API TURBO_TEAM TURBO_TOKEN TURBO_REMOTE_CACHE_SIGNATURE_KEY; do
-            if [ -n "${!secret:-}" ]; then
-              secret_args+=(--secret "id=${secret},env=${secret}")
-            fi
-          done
-          DOCKER_BUILDKIT=1 docker build --platform linux/amd64 \
-            --tag homarr-ci --tag homarr-e2e "${secret_args[@]}" .
-
-      - name: Cache Playwright browsers
-        if: '!env.ACT'
-        id: playwright-cache
-        uses: actions/cache@v6
-        with:
-          path: ~/.cache/ms-playwright
-          key: playwright-${{ runner.os }}-${{ hashFiles('pnpm-lock.yaml') }}
-
-      - name: Install Playwright Chromium
-        if: steps.playwright-cache.outputs.cache-hit != 'true' || env.ACT
-        run: pnpm exec playwright install --with-deps chromium
-
-      - name: Install Playwright system deps
-        if: steps.playwright-cache.outputs.cache-hit == 'true'
-        run: pnpm exec playwright install-deps chromium
-
-      - name: Run E2E tests
-        run: pnpm test:e2e
-
-      - name: Upload E2E artifacts
-        if: failure() && !env.ACT
-        uses: actions/upload-artifact@v7
-        with:
-          name: playwright-report
-          path: e2e/test-results/
-          retention-days: 7
-
-      - name: Run memory regression test
-        env:
-          CONTAINER_NAME: homarr-mem-${{ github.run_id }}-${{ github.run_attempt }}
-          SECRET_ENCRYPTION_KEY: 0000000000000000000000000000000000000000000000000000000000000000
-        run: |
-          docker run -d --name "$CONTAINER_NAME" -p 127.0.0.1::7575 \
-            -e NO_EXTERNAL_CONNECTION=true \
-            -e SECRET_ENCRYPTION_KEY="$SECRET_ENCRYPTION_KEY" \
-            homarr-ci
-          PORT=$(docker port "$CONTAINER_NAME" 7575/tcp | sed 's/.*://')
-          [[ "$PORT" =~ ^[0-9]+$ ]] || { echo "ERROR: invalid port mapping: '$PORT'"; exit 1; }
-          URL="http://127.0.0.1:${PORT}"
-
-          healthy=false
-          for i in $(seq 1 30); do
-            if curl -sf "$URL/api/health/ready" >/dev/null 2>&1; then
-              echo "Container healthy after $((i * 2))s"
-              healthy=true
-              break
-            fi
-            sleep 2
-          done
-
-          if [ "$healthy" != "true" ]; then
-            echo "ERROR: Container never became healthy"
-            docker logs "$CONTAINER_NAME" --tail 100
-            exit 1
-          fi
-
-          warmup_ok=0
-          for _ in $(seq 1 5); do
-            curl -sf "$URL/" >/dev/null 2>&1 && warmup_ok=$((warmup_ok + 1))
-            sleep 2
-          done
-          if [ "$warmup_ok" -eq 0 ]; then
-            echo "ERROR: All warmup requests failed"
-            docker logs "$CONTAINER_NAME" --tail 50
-            exit 1
-          fi
-
-          docker inspect -f '{{.State.Running}}' "$CONTAINER_NAME" | grep -qx true || {
-            echo "ERROR: Container died before memory measurement"
-            docker logs "$CONTAINER_NAME" --tail 100
-            exit 1
-          }
-
-          RAW_MEMORY=$(docker stats --no-stream --format '{{.MemUsage}}' "$CONTAINER_NAME" | sed 's| /.*||')
-          MEMORY_MB=$(echo "$RAW_MEMORY" | awk '
-            /GiB/ { gsub(/GiB/, ""); print $1 * 1024; next }
-            /MiB/ { gsub(/MiB/, ""); print $1; next }
-            /KiB/ { gsub(/KiB/, ""); print $1 / 1024; next }
-            { print $1 / 1048576 }
-          ')
-
-          echo "Memory usage: ${MEMORY_MB} MB (${RAW_MEMORY})"
-          [[ "$MEMORY_MB" =~ ^[0-9]+(\.[0-9]+)?$ ]] || {
-            echo "ERROR: non-numeric memory value: '$MEMORY_MB' (raw: '$RAW_MEMORY')"
-            docker logs "$CONTAINER_NAME" --tail 100
-            exit 1
-          }
-          if awk "BEGIN { exit !($MEMORY_MB < 50) }"; then
-            echo "ERROR: Memory suspiciously low (${MEMORY_MB} MB) — container may have crashed"
-            docker logs "$CONTAINER_NAME" --tail 100
-            exit 1
-          elif awk "BEGIN { exit !($MEMORY_MB > 700) }"; then
-            echo "ERROR: Memory usage ${MEMORY_MB} MB exceeds 700 MB"
-            docker logs "$CONTAINER_NAME" --tail 100
-            exit 1
-          fi
-
-      - name: Clean up memory test container
-        if: always()
-        env:
-          CONTAINER_NAME: homarr-mem-${{ github.run_id }}-${{ github.run_attempt }}
-        run: docker rm -f "$CONTAINER_NAME" >/dev/null 2>&1 || true
-
-      - 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 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."
-
-  cleanup:
-    name: Clean up preview image
-    if: github.event_name == 'pull_request_target' || (github.event_name == 'workflow_dispatch' && inputs.operation == 'cleanup')
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    permissions:
-      packages: write
-    env:
-      IMAGE_TAG: pr-${{ github.event.pull_request.number || inputs.pr_number }}
-    steps:
-      - name: Validate cleanup input
-        if: github.event_name == 'workflow_dispatch'
-        env:
-          PR_NUMBER: ${{ inputs.pr_number }}
-        run: test -n "$PR_NUMBER" || { echo "pr_number is required for cleanup"; exit 1; }
-
-      - name: Delete GHCR package version
-        if: '!env.ACT'
-        uses: actions/github-script@v8
-        with:
-          script: |
-            const packageName = "homarr-test";
-            const org = context.repo.owner;
-            const tag = process.env.IMAGE_TAG;
-            const versions = await github.paginate(
-              github.rest.packages.getAllPackageVersionsForPackageOwnedByOrg,
-              { package_type: "container", package_name: packageName, org, per_page: 100 },
-            );
-            const target = versions.find((version) =>
-              version.metadata?.container?.tags?.includes(tag),
-            );
-            if (!target) {
-              core.info(`No package version found with tag "${tag}"`);
-              return;
-            }
-            await github.rest.packages.deletePackageVersionForOrg({
-              package_type: "container",
-              package_name: packageName,
-              org,
-              package_version_id: target.id,
-            });
-            core.info(`Deleted package version ${target.id} (${tag})`);
-
-      - name: Show Act cleanup result
-        if: env.ACT
-        run: echo "Act validated cleanup for ${IMAGE_TAG}; external GHCR writes are disabled locally."
@@ -0,0 +1,227 @@
+name: "[Quality] Code Analysis"
+permissions:
+  contents: read
+
+on:
+  pull_request:
+    branches: ["*"]
+  push:
+    branches: ["main"]
+  merge_group:
+
+concurrency:
+  group: "${{ github.workflow }}-${{ github.ref }}"
+  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
+
+env:
+  FORCE_COLOR: 3
+  SKIP_ENV_VALIDATION: true
+  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 }}
+  TURBO_SCM_BASE: ${{ github.event.pull_request.base.sha || github.event.before || 'HEAD~1' }}
+  TURBO_SCM_HEAD: ${{ github.sha }}
+
+jobs:
+  lint-format-autofix:
+    if: github.event_name == 'pull_request'
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+          ref: ${{ github.head_ref }}
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Get changed files
+        id: changed
+        run: |
+          git diff --name-only --diff-filter=ACMR origin/${{ github.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"
+
+  lint:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Copy env
+        shell: bash
+        run: cp .env.example .env
+
+      - name: Lint
+        run: pnpm turbo lint --affected && pnpm lint:ws
+
+  format:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Format
+        run: pnpm turbo format --affected --continue
+
+  typecheck:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Typecheck
+        run: pnpm turbo typecheck --affected
+
+  test:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Test
+        run: pnpm test
+
+      - name: "Report Coverage"
+        # Set if: always() to also generate the report if tests are failing
+        # Only works if you set `reportOnFailure: true` in your vite config as specified above
+        if: always()
+        uses: davelosert/vitest-coverage-report-action@v2
+
+  e2e:
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@v6
+      - name: Setup
+        uses: ./tooling/github/setup
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v4
+      - name: Build docker image
+        id: build-docker-image
+        uses: docker/build-push-action@v7
+        with:
+          platforms: linux/amd64
+          context: .
+          push: false
+          load: true
+          tags: homarr-e2e
+          network: host
+          cache-from: type=gha
+          cache-to: type=gha,mode=max
+        env:
+          SKIP_ENV_VALIDATION: true
+      - name: Install playwright browsers
+        run: pnpm exec playwright install chromium
+      - name: Run E2E Tests
+        shell: bash
+        run: pnpm test:e2e
+
+  build:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+      - name: Setup
+        uses: ./tooling/github/setup
+      - name: Copy env
+        shell: bash
+        run: cp .env.example .env
+      - name: Build
+        run: pnpm turbo build --affected
+
+  memory-regression:
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@v6
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v4
+      - name: Build Docker image
+        uses: docker/build-push-action@v7
+        with:
+          platforms: linux/amd64
+          context: .
+          push: false
+          load: true
+          tags: homarr-memory-test
+          network: host
+          cache-from: type=gha
+          cache-to: type=gha,mode=max
+        env:
+          SKIP_ENV_VALIDATION: true
+      - name: Start container and measure memory
+        run: |
+          docker run -d --name homarr-mem-test -p 17575:7575 homarr-memory-test
+          # Wait for container to be healthy (up to 60s)
+          healthy=false
+          for i in $(seq 1 30); do
+            if curl -sf http://localhost:17575/api/health 2>/dev/null; then
+              echo "Container healthy after $((i * 2))s"
+              healthy=true
+              break
+            fi
+            sleep 2
+          done
+          if [ "$healthy" != "true" ]; then
+            echo "ERROR: Container never became healthy"
+            docker logs homarr-mem-test --tail 50
+            exit 1
+          fi
+          # Warm up: hit the dashboard page a few times
+          for i in $(seq 1 5); do
+            curl -sf http://localhost:17575/ > /dev/null 2>&1 || true
+            sleep 2
+          done
+          # Measure RSS after warmup
+          MEM_KB=$(docker stats --no-stream --format '{{.MemUsage}}' homarr-mem-test | sed 's| /.*||')
+          echo "Raw memory: $MEM_KB"
+          # Convert to numeric MB (handles GiB and MiB suffixes)
+          MEM_NUM=$(echo "$MEM_KB" | awk '{
+            if ($0 ~ /GiB/) { gsub(/GiB/,""); print $1 * 1024 }
+            else if ($0 ~ /MiB/) { gsub(/MiB/,""); print $1 }
+            else if ($0 ~ /KiB/) { gsub(/KiB/,""); print $1 / 1024 }
+            else { print $1 / 1048576 }
+          }')
+          echo "Memory usage: ${MEM_NUM} MB"
+          MAX_MB=700
+          if awk "BEGIN {exit !($MEM_NUM > $MAX_MB)}"; then
+            echo "ERROR: Memory usage ${MEM_NUM} MB exceeds ${MAX_MB} MB threshold"
+            docker logs homarr-mem-test --tail 50
+            exit 1
+          fi
+          echo "Memory check passed: ${MEM_NUM} MB <= ${MAX_MB} MB"
@@ -15,7 +15,7 @@ jobs:

    steps:
      - name: Checkout
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6

      - name: Obtain token
        id: obtainToken
@@ -18,7 +18,7 @@ jobs:

    steps:
      - name: Checkout
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6

      - name: Upload Crowdin translations
        uses: crowdin/github-action@v2
@@ -26,7 +26,7 @@ jobs:
        with:
          args: "Beta release has been triggered: [run ${{ github.run_number }}](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})"
      - name: Checkout repository
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
        with:
          fetch-depth: 0
      - name: Get Next Version
@@ -57,7 +57,7 @@ jobs:
          client-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
          permission-contents: write # required to commit package.json & changelog changes, merge them to dev / next and publish the release

-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
        if: env.SKIP_RELEASE == 'false'
        with:
          persist-credentials: false
@@ -119,7 +119,7 @@ jobs:
    outputs:
      digest: ${{ steps.build.outputs.digest }}
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
        with:
          ref: ${{ needs.release.outputs.git_ref }}

@@ -148,11 +148,6 @@ jobs:
          platforms: linux/amd64
          labels: ${{ steps.meta.outputs.labels }}
          outputs: type=image,"name=${{ env.GHCR_REPO }}",push-by-digest=true,name-canonical=true,push=true
-          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 }}
        env:
          SKIP_ENV_VALIDATION: true
  build-arm64:
@@ -163,7 +158,7 @@ jobs:
    outputs:
      digest: ${{ steps.build.outputs.digest }}
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
        with:
          ref: ${{ needs.release.outputs.git_ref }}

@@ -192,11 +187,6 @@ jobs:
          platforms: linux/arm64
          labels: ${{ steps.meta.outputs.labels }}
          outputs: type=image,"name=${{ env.GHCR_REPO }}",push-by-digest=true,name-canonical=true,push=true
-          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 }}
        env:
          SKIP_ENV_VALIDATION: true
  extract-asset-amd64:
@@ -30,7 +30,7 @@ jobs:
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
      - name: Setup
        uses: ./tooling/github/setup
      - name: Build docs
@@ -29,7 +29,7 @@ jobs:
        with:
          args: "Automatic release has been triggered: [run ${{ github.run_number }}](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})"
      - name: Checkout repository
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
        with:
          fetch-depth: 0
      - name: Get Next Version
@@ -20,7 +20,7 @@ jobs:
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6

      - name: Setup
        uses: ./tooling/github/setup
@@ -19,7 +19,7 @@ jobs:
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
        with:
          ref: dev

@@ -16,7 +16,7 @@ jobs:
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
        with:
          ref: dev

@@ -13,7 +13,7 @@ jobs:
    runs-on: ubuntu-latest
    timeout-minutes: 5
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
      - name: Validate prebuilt dependencies for amd64
        id: validate-amd64
        uses: ./.github/actions/prebuilt-debian
@@ -30,7 +30,7 @@ jobs:
    runs-on: ubuntu-24.04-arm
    timeout-minutes: 5
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
      - name: Validate prebuilt dependencies for arm64
        id: validate-arm64
        uses: ./.github/actions/prebuilt-debian
@@ -13,7 +13,7 @@ jobs:
    runs-on: ubuntu-latest
    timeout-minutes: 2
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
      - run: |
          npx --yes --package renovate -- \
              renovate-config-validator --strict .github/renovate.json5
@@ -52,7 +52,7 @@ jobs:
          permission-contents: write # required to commit to branch
          permission-pull-requests: write # required to create pr & enable automerge
      - name: Checkout code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
        with:
          token: ${{ steps.obtainToken.outputs.token }}
          ref: dev
@@ -29,7 +29,7 @@ jobs:
          permission-pull-requests: write # required to create pr & enable automerge

      - name: Checkout repository
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
        env:
          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}

@@ -28,7 +28,7 @@ jobs:
          permission-contents: write # required to commit to branch
          permission-pull-requests: write # required to create pr & enable automerge
      - name: Checkout code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
        env:
          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
      - name: Setup
@@ -2,7 +2,6 @@

 # dependencies
 node_modules
-.pnpm-store/
 .pnp
 .pnp.js
 .idea/
@@ -71,10 +70,7 @@ apps/nextjs/public/images/background.png

 # personal agent config
 .opencode
-.agents/
-skills-lock.json

 # docusaurus
 apps/docs/.docusaurus
 apps/docs/build
-.pnpm-store
@@ -1,535 +0,0 @@
-# Custom Widgets Architecture Audit and North Star
-
-> Status: implemented in the current working tree; baseline retained below for traceability
-> Evidence snapshot: `c5703e7e5` on PR #6304
-> Scope: built-in custom-widget displays, Custom JSX, network execution, authoring, preview, import/export, AI prompts, and MCP tools
-
-## Implementation outcome
-
-The migration described by this audit is implemented. `@homarr/custom-widgets` now owns the domain through explicit `core`, `jsx`, `runtime`, `server`, and `workbench` exports. API, Widgets, and Next.js retain only authorization, persistence, transport, board registration, navigation, and localized adapter concerns.
-
-Key outcomes:
-
- One typed configuration and display-descriptor model drives schemas, defaults, form hydration, serialization, import/export, preview, examples, diagnostics, generated references, and AI prompts.
- Display-data extraction moved out of API and Widgets into the domain package; the former API-to-Widgets re-export chain no longer exists.
- The interpreter, shared security policy, registry, wrappers, named-request runtime, hardened executor, preview sessions, rate limits, and workbench UI have focused package-owned modules and tests.
- Runtime and workbench network behavior is injected through typed ports. The domain package has no dependency on API, Widgets, Next.js routes, notification infrastructure, or modal infrastructure.
- Public tRPC and MCP procedures are characterized, v2 and v3 import envelopes remain accepted, display-only v1 remains covered, and MCP offers iterative schema, validation, template read/write/patch, create/import/update, preview query, simulation, and journal tools.
- The AI prompt uses a multiline two-block authoring bundle, documents the `SubFetch` render-child contract, and is generated from the canonical registry and tested examples.
- Architecture enforcement currently scans 110 production modules for dependency direction, cycles, file budgets, dynamic loading, and untranslated JSX literals. Generated-reference drift and every Mantine export classification are test-enforced.
- The latest production build measured the largest Custom JSX route payload at 99,852 gzip bytes across two chunks, below the 768 KiB budget.
-
-Focused verification is green: 278 package tests, 35 API/MCP tests, 52 Widgets renderer tests, 7 E2E tests, affected typecheck, affected lint, docs build, production Next.js build, architecture checks, generated drift, and the bundle budget. The root `pnpm test` command is presently blocked on this workstation by unrelated Docker-backed integration suites timing out while the shared Docker daemon is under external load; no Custom Widget test failed in those runs.
-
-## Executive summary
-
-The feature has a strong security direction and a capable authoring experience, but its implementation has outgrown its current ownership model. PR #6304 changes 56 files with 13,206 additions. The primary feature directories contain 10,437 lines, spread across `@homarr/widgets`, `@homarr/api`, `@homarr/definitions`, `@homarr/validation`, and the Next.js management route.
-
-The main problem is not the absolute line count. It is that domain policy, transport, persistence, rendering, form state, compatibility, and documentation generation are interleaved across package boundaries. A change to one display type can require synchronized edits in schemas, form defaults, import conversion, preview extraction, runtime rendering, documentation, and AI instructions. Several of those paths use untyped records, duplicated conversion logic, or direct API dependencies.
-
-The north star is a single `@homarr/custom-widgets` domain package with explicit `core`, `jsx`, `runtime`, `server`, and `workbench` entry points. Existing applications and packages become thin adapters. The extraction must preserve public APIs, import formats, permission behavior, and the current UI while improving internal cohesion.
-
-This audit does not authorize a big-bang rewrite. The migration should be a sequence of behavior-preserving PRs, beginning with characterization tests and ending with enforced dependency and complexity budgets.
-
-## Measured baseline
-
-### Change footprint
-
-| Measure                         | Current value |
-| ------------------------------- | ------------: |
-| PR files changed                |            56 |
-| PR additions                    |        13,206 |
-| PR deletions                    |         1,385 |
-| Primary feature-directory lines |        10,437 |
-
-Generated component-reference JSON accounts for 2,491 added lines and is not treated as source complexity.
-
-### Largest production files
-
-| File                                                                            | Lines | Responsibilities currently combined                                                                                                                                                   |
-| ------------------------------------------------------------------------------- | ----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `apps/nextjs/src/app/[locale]/manage/custom-widgets/_custom-widget-form.tsx`    | 1,911 | Schema refinement, defaults, server-error mapping, form conversion, submission, preview state, focus management, display picker, connection fields, and every display-specific editor |
-| `packages/api/src/router/custom-widget/custom-widget-router.ts`                 |   978 | CRUD, import/export, template patching, MCP descriptions, preview sessions, preview execution, journals, and action simulation/execution                                              |
-| `packages/widgets/src/custom-api/safe-jsx-interpreter.tsx`                      |   944 | AST model, parsing, environments, budgets, sanitization, expression evaluation, safe methods, callbacks, and React rendering                                                          |
-| `apps/nextjs/src/app/[locale]/manage/custom-widgets/_custom-widget-preview.tsx` |   834 | Preview orchestration, error boundary, tabs, response tree, diagnostics, request journal, sample data, and renderer selection                                                         |
-| `packages/widgets/src/custom-api/jsx-whitelist.ts`                              |   775 | Mantine imports, wrappers, icon mapping, runtime component map, registry filtering, data sanitization, and safe bindings                                                              |
-| `packages/widgets/src/custom-api/jsx-sub-fetch.tsx`                             |   599 | Query rendering, render props, path display, action execution, buttons, toggles, refresh, notifications, and confirmations                                                            |
-
-These files exceed the proposed 300-line production-module target. The interpreter is a reasonable candidate for a documented 400-line exception after its independent policies, evaluators, and renderer are extracted.
-
-### Current ownership
-
-```mermaid
-flowchart LR
-  D["@homarr/definitions<br/>registry and examples"]
-  V["@homarr/validation<br/>schemas and AST diagnostics"]
-  W["@homarr/widgets<br/>renderers and interpreter"]
-  A["@homarr/api<br/>CRUD, permissions, execution and MCP"]
-  N["Next.js route<br/>workbench, preview and prompt"]
-  X["Docs<br/>generated reference and guides"]
-
-  N --> A
-  N --> V
-  N --> D
-  N --> W
-  W --> A
-  W --> D
-  A --> V
-  X --> D
-```
-
-The `@homarr/widgets → @homarr/api` edge is particularly costly. Runtime request components call the generated tRPC client directly, so moving the domain into a package that is also consumed by the API would create a dependency cycle unless request execution is inverted behind a typed port.
-
-## What is working well
-
- Custom JSX v2 replaces raw runtime URLs and methods with named, typed requests.
- Board permissions, network scope, DNS validation, redirect policy, response limits, caching, concurrency, and action rules are server-enforced.
- The safe interpreter no longer treats an upstream JSX parser as a sandbox.
- Component metadata drives runtime classification, editor completion, docs generation, and part of the AI prompt.
- The workbench supports multiline JSX, diagnostics, real preview sizes, response inspection, request journals, import review, undo/redo, and paste-to-import.
- MCP exposes schema, validation, preview, journal, template read/write/patch, import, and update workflows without exposing stored secrets.
- Shared examples cover simple metrics, nested queries, charts, actions, and richer interactive layouts.
-
-The migration must preserve these capabilities. Package extraction is not a reason to weaken the security boundary or remove authoring features.
-
-## Findings
-
-### P1 — Domain ownership is fragmented
-
-Custom-widget behavior is implemented in five packages/applications. None of them is the clear source of truth for the complete lifecycle. `@homarr/definitions` owns component metadata and examples, `@homarr/validation` owns schemas and template diagnostics, `@homarr/widgets` owns runtime evaluation, `@homarr/api` owns network and persistence flows, and Next.js owns authoring transformations.
-
-Impact:
-
- Maintainers must search unrelated packages to understand one behavior.
- Changes have a large synchronization surface and can drift silently.
- The domain cannot be tested or reused as a coherent unit.
- Package names describe infrastructure location rather than feature ownership.
-
-### P1 — Giant modules mix unrelated reasons to change
-
-The largest files are not merely long; they combine policy, orchestration, state, and presentation. The form contains all display editors. The router contains every management and preview procedure. The interpreter contains parsing through React emission. The request component file contains both query and mutation interaction models.
-
-Impact:
-
- Reviews are broad and regression-prone.
- Unit-test seams are difficult to identify.
- Merge conflicts concentrate in a small number of files.
- Small feature changes require understanding thousands of lines of adjacent behavior.
-
-### P1 — Runtime code depends directly on the API client
-
-`packages/widgets/src/custom-api/component.tsx` and `jsx-sub-fetch.tsx` import `@homarr/api/client`. They also directly invoke notifications and confirmation modals.
-
-Impact:
-
- The renderer cannot be used or tested without application infrastructure.
- A future `@homarr/custom-widgets` package would cycle with `@homarr/api` if both retained these imports.
- Preview and board runtime cannot share the same renderer through different request implementations without branching inside the components.
-
-Required direction: a runtime provider must receive typed query, action, confirmation, notification, and invalidation ports. The board and preview layers supply adapters.
-
-### P1 — Configuration transformations are duplicated
-
-Create defaults and builders live in the form, edit hydration lives in the edit page, and import hydration lives in `_custom-widget-import-utils.ts`. These paths independently translate between stored display configs and form values. They rely on display-type switches, record casts, and JSON text fields such as the request manifest.
-
-Impact:
-
- Create, edit, paste replacement, import, export, and MCP can disagree.
- Adding a field requires updating multiple transforms.
- Round trips are difficult to prove lossless.
-
-Required direction: each display type supplies one typed descriptor containing schema, defaults, `toForm`, `fromForm`, preview projection, and migration behavior.
-
-### P1 — Type safety degrades at domain boundaries
-
-`Record<string, unknown>`, `as never`, and `as unknown as` are frequent in form conversion, display extraction, preview state, imports, registry wrappers, and API parsing. Some casts are necessary at the interpreter/React boundary, but most domain-level casts indicate missing discriminated unions or validated adapters.
-
-Impact:
-
- Invalid combinations survive until runtime.
- Refactors do not receive complete compiler guidance.
- Server and client transformations can diverge while continuing to compile.
-
-Required direction: parse unknown values once at ingress and use typed domain objects afterward. Unsafe casts must be isolated to named boundary modules and justified by tests.
-
-### P1 — Security policy is represented more than once
-
-The template validator and interpreter both parse JSX and maintain concepts such as blocked properties, blocked props, AST depth, and operation limits. Runtime component filtering adds another policy layer.
-
-The analyzer and interpreter have different jobs, so they should not be collapsed into one evaluator. They must, however, consume one immutable policy definition and shared AST normalization utilities.
-
-Impact:
-
- A property can be rejected by one layer and missed by another.
- Security changes require parallel edits and duplicate tests.
- Diagnostics can describe behavior that differs from runtime enforcement.
-
-### P1 — The API router combines transport and application behavior
-
-The router owns tRPC metadata, Zod inputs, database writes, encryption, import/export, template revisions, preview execution, rate-limit acquisition, journal recording, and MCP documentation.
-
-Impact:
-
- Domain logic is only testable through tRPC context setup.
- MCP and browser endpoints can accidentally implement different workflows.
- Framework-specific `TRPCError` values leak into lower-level executor and manifest code.
-
-Required direction: tRPC procedures authorize, load persistence models, call a domain service, and map domain errors. They do not implement request rendering, template patching, preview execution, or import conversion inline.
-
-### P2 — Metadata generation is only partially centralized
-
-The component registry and examples are shared, but runtime maps, wrappers, safe bindings, display-type metadata, AI prompt prose, form choices, and some docs remain separately assembled. The AI prompt is built inside a client button component.
-
-Impact:
-
- Agent instructions can drift from validation and runtime behavior.
- Prompt generation requires UI and network context.
- Display types lack the same single-registry guarantee as JSX components.
-
-Required direction: prompt generation is a pure function in `core`, using the schema, display descriptors, component registry, and tested fixtures. The UI only fetches context and copies the result.
-
-### P2 — Compatibility behavior is mixed into primary flows
-
-V1 detection, migration warnings, legacy network diagnostics, v2 imports, v3 exports, and fallback display parsing are embedded beside current authoring/runtime logic.
-
-Impact:
-
- Happy paths are harder to read.
- Legacy behavior can accidentally influence v2 code.
- Compatibility retirement has no obvious deletion boundary.
-
-Required direction: version detection and migrations live under `core/migrations`. Runtime and workbench receive a normalized current model plus explicit review state.
-
-### P2 — Test topology does not mirror the architecture
-
-Interpreter coverage is substantial, and request-executor/router tests exist, but tests are colocated under their current infrastructure owners instead of a feature package. A focused renderer run passed 52 tests during review, while the selected API suites failed before collecting tests because the root Vitest client environment rejected server-only environment access.
-
-Impact:
-
- The complete feature cannot be verified with one package command.
- Server test failures can be configuration failures rather than behavioral failures.
- Form conversion and workbench orchestration have limited direct characterization coverage relative to their size.
-
-Required direction: the package owns focused test projects or environment-specific configs for core, DOM runtime/workbench, and Node server tests. API adapter tests remain in `@homarr/api`.
-
-### P2 — A small amount of user-facing copy bypasses translation
-
-Examples found during the snapshot include the raw-response tooltip and a default empty template message. Dynamic translation keys also require repeated `as never` casts, reducing translation-key safety.
-
-Impact:
-
- Locale completeness gates are unreliable.
- Refactoring copy is harder than changing typed translation keys.
-
-Required direction: all package UI receives a typed message catalog or uses typed scoped translations. No visible fallback literals are allowed in production components.
-
-## North-star package
-
-```text
-packages/custom-widgets/
-├── src/core/
-│   ├── config/          # discriminated display configurations and form models
-│   ├── displays/        # typed display descriptors and built-in display metadata
-│   ├── import/          # v2/v3 parsing, export, review, and authoring bundles
-│   ├── migrations/      # v1 detection, normalization, and review requirements
-│   ├── prompts/         # pure AI prompt generation
-│   └── examples/        # typed fixtures shared by tests, docs, editor, and prompts
-├── src/jsx/
-│   ├── ast/             # parser adapter, AST types, traversal, and normalization
-│   ├── policy/          # blocked properties, props, URLs, and budgets
-│   ├── analyzer/        # authoring diagnostics
-│   ├── interpreter/     # expression and collection evaluation
-│   ├── registry/        # component descriptors, wrappers, and export classification
-│   └── bindings/        # branded safe helpers and sanitized data
-├── src/runtime/
-│   ├── displays/        # built-in renderers
-│   ├── jsx/             # Custom JSX renderer and error containment
-│   ├── requests/        # SubFetch, actions, toggles, refresh, and state handling
-│   └── provider/        # injected runtime capabilities
-├── src/server/
-│   ├── network/         # hardened executor and destination policy
-│   ├── requests/        # manifest resolution and parameter substitution
-│   ├── limits/          # rate and concurrency limits
-│   └── preview/         # sessions, simulation, and journals
-└── src/workbench/
-    ├── form/            # shared state and connection/display sections
-    ├── editor/          # CodeMirror and registry-driven diagnostics
-    ├── preview/         # widget, response, journal, and diagnostic views
-    └── import/          # clipboard parsing and review UI
-```
-
-Public exports are explicit:
-
-```json
-{
-  "exports": {
-    "./core": "./src/core/index.ts",
-    "./jsx": "./src/jsx/index.ts",
-    "./runtime": "./src/runtime/index.ts",
-    "./server": "./src/server/index.ts",
-    "./workbench": "./src/workbench/index.ts"
-  }
-}
-```
-
-There is no broad root barrel. Internal folders cannot be imported by consumers.
-
-### Dependency rules
-
-```mermaid
-flowchart LR
-  C["custom-widgets/core"]
-  J["custom-widgets/jsx"]
-  R["custom-widgets/runtime"]
-  S["custom-widgets/server"]
-  B["custom-widgets/workbench"]
-  API["@homarr/api adapter"]
-  W["@homarr/widgets adapter"]
-  N["Next.js route adapter"]
-  DOC["Docs generator"]
-
-  J --> C
-  R --> C
-  R --> J
-  S --> C
-  B --> C
-  B --> R
-  API --> C
-  API --> S
-  W --> C
-  W --> R
-  N --> C
-  N --> B
-  DOC --> C
-  DOC --> J
-```
-
-Hard rules:
-
-1. `@homarr/custom-widgets` never imports `@homarr/api`, `@homarr/widgets`, or Next.js route modules.
-2. `core` has no React, Mantine, tRPC, database, Redis, or browser dependency.
-3. `jsx` has no API, persistence, Redis, notification, or modal dependency.
-4. `runtime` performs no direct tRPC calls. It consumes `CustomWidgetRuntimePort`.
-5. `workbench` performs no direct tRPC calls. It consumes `CustomWidgetWorkbenchPort` callbacks.
-6. `server` has no tRPC or database-query dependency. API adapters load authorized records and map errors.
-7. Cross-entry imports follow the arrows above; reverse imports fail CI.
-
-### Runtime ports
-
-The exact transport remains owned by adapters. The domain contract should cover behavior rather than tRPC details:
-
-```ts
-interface CustomWidgetRuntimePort {
-  getData(input: { itemId: string; signal?: AbortSignal }): Promise<CustomWidgetRequestResult>;
-  query(input: NamedRequestInvocation & { signal?: AbortSignal }): Promise<CustomWidgetRequestResult>;
-  action(input: NamedRequestInvocation & { confirmed?: boolean }): Promise<CustomWidgetRequestResult>;
-  confirm(input: ActionConfirmation): Promise<boolean>;
-  notify(input: RuntimeNotification): void;
-  invalidate(input: RuntimeInvalidation): Promise<void>;
-}
-```
-
-Board runtime and preview runtime implement the same port. Preview simulation is an adapter capability, not a conditional tRPC import inside `ActionButton`.
-
-### Display descriptors
-
-Every display type is represented once:
-
-```ts
-interface CustomWidgetDisplayDescriptor<TConfig, TForm> {
-  type: CustomWidgetDisplayType;
-  configSchema: ZodType<TConfig>;
-  formSchema: ZodType<TForm>;
-  createDefault(): TConfig;
-  toForm(config: TConfig): TForm;
-  fromForm(form: TForm): TConfig;
-  migrate(input: unknown): DisplayMigrationResult<TConfig>;
-  extract(response: unknown, config: TConfig): DisplayModel;
-  capabilities(config: TConfig): CustomWidgetCapability[];
-}
-```
-
-UI fields and renderer components may be registered in runtime/workbench companion maps keyed by the same typed display identifier. Domain descriptors remain serializable and framework-independent.
-
-## Developer-experience north star
-
-### Maintainers
-
- Start at `packages/custom-widgets` for every feature behavior.
- Find one module per concept and one descriptor per display type.
- Add a display type without editing central switches in multiple packages.
- Run one package command for core, DOM, and server tests.
- Receive compile-time failures when a configuration field is not handled by forms, preview, migration, or export.
- Review PRs that move one domain boundary at a time.
-
-### Administrators and template authors
-
- Preserve the current continuous form and live workbench.
- Keep preview usable before a live response exists through schema-valid defaults and editable sample data.
- Keep diagnostics actionable, localized, clickable, and consistent with runtime policy.
- Keep imports reviewable and secrets excluded.
- Keep query and action capabilities visible without noisy permanent warnings.
-
-### AI agents
-
- Obtain schema, registry, limits, examples, and prompt rules from the same typed sources.
- Use readable multiline templates through authoring bundles and line-based template tools.
- Validate, preview, inspect journals, patch, and revalidate without rewriting unrelated configuration.
- Receive stable machine-actionable issue codes in addition to localized or human-readable messages.
- Never need to infer runtime behavior from UI-only prompt strings.
-
-## Fragmentation rules
-
- Production modules target at most 300 lines, excluding generated files, fixtures, and type-only declarations.
- Algorithmic modules can reach 400 lines only with a file-level rationale and focused tests.
- A module has one primary reason to change; moving lines without separating policy from orchestration does not satisfy the target.
- React components do not contain schema definitions or persistence transforms.
- Routers do not contain reusable domain algorithms.
- Domain functions do not throw framework-specific errors.
- Unknown input is validated once. Parsed values are not carried as `Record<string, unknown>` through internal layers.
- Compatibility code lives in versioned migration modules and has explicit removal criteria.
- Generated artifacts are reproducible and checked for drift, but excluded from line budgets.
-
-## Migration roadmap
-
-### PR 1 — Characterize contracts
-
- Add round-trip tests for every display descriptor: default → form → config, stored config → form → config, and import → export.
- Add fixtures for v1 display-only, v1 network-review-required, v2 import, and v3 export.
- Add prompt snapshots sourced from the component registry and examples.
- Split Node and DOM Vitest projects so server suites collect and run reliably.
- Record bundle and render baselines before moving modules.
-
-Gate: all existing behavior is represented by tests, with no production moves yet.
-
-### PR 2 — Establish `core`
-
- Create `@homarr/custom-widgets` and explicit exports.
- Move custom-widget schemas, typed configs, display descriptors, examples, import/export, migration, capability analysis, and prompt generation into `core`.
- Replace form/edit/import conversion duplication with descriptor calls.
- Temporarily re-export legacy imports from definitions and validation to keep consumers stable.
-
-Gate: create, edit, import, export, MCP validation, and AI prompt generation use the same domain contracts.
-
-### PR 3 — Extract JSX policy and interpreter
-
- Move AST types, parser adapter, shared security policy, analyzer, evaluator, budgets, bindings, and registry into `jsx`.
- Separate evaluator modules by expression family and React emission.
- Generate diagnostics and runtime enforcement from the same policy constants.
- Keep the Mantine export-classification CI check.
-
-Gate: the security suite passes unchanged, analyzer/runtime policy drift tests pass, and no consumer imports JSX internals.
-
-### PR 4 — Extract runtime
-
- Move built-in renderers, Custom JSX display, SubFetch, actions, toggles, refresh, and error containment into `runtime`.
- Introduce the runtime port and adapters for board and preview contexts.
- Remove direct imports of the API client, modals, and notifications from domain components.
- Split request components into query, action, toggle, refresh, feedback, and shared-state modules.
-
-Gate: board rendering and workbench preview use the same runtime components through different adapters; actions retain confirmation, rollback, invalidation, and permission behavior.
-
-### PR 5 — Extract server services
-
- Move executor, manifests, network policy, limits, caching/single-flight, and preview-session logic into `server`.
- Replace `TRPCError` below the adapter with typed domain errors.
- Split API procedures into management, templates, preview, and runtime routers that delegate to package services.
- Keep authorization, database lookup, encryption, and tRPC/MCP metadata in `@homarr/api`.
-
-Gate: browser and MCP flows call the same services; request security tests run as Node package tests; public procedure names and inputs remain compatible.
-
-### PR 6 — Extract and fragment workbench
-
- Move reusable editor, preview, response tree, import review, connection section, display picker, and display-specific fields into `workbench`.
- Introduce a workbench port for validate, preview, query, simulate action, journal, and save callbacks.
- Keep Next.js pages responsible only for routing, loading initial data, and constructing adapters.
- Replace the monolithic form with small sections and descriptor-driven display fields while preserving the continuous form, two-pane scrolling, autofocus, and mobile modes.
-
-Gate: no workbench source file exceeds the agreed budget, and create/edit/paste replacement share one state model.
-
-### PR 7 — Remove scaffolding and enforce boundaries
-
- Remove compatibility re-exports and old implementations after all consumers move.
- Add CI checks for forbidden imports, dependency cycles, source-size budgets, untranslated literals, generated-artifact drift, component classification, and custom-JSX chunk size.
- Update contributor and architecture documentation with package entry points and extension recipes.
-
-Gate: old ownership paths contain only thin adapters or are deleted.
-
-## Verification strategy
-
-### Core
-
- Every display descriptor accepts valid data and rejects mismatched configuration.
- All create/edit/import/export transformations are lossless where expected.
- V1/v2/v3 compatibility and review states are deterministic.
- Prompt output, authoring bundles, fixtures, docs data, and completion data are generated from shared sources.
-
-### JSX
-
- Computed and Unicode-obfuscated reflective access remains blocked.
- Analyzer and interpreter share property, prop, URL, and budget policy.
- Own-property resolution, branded calls, callback accounting, and node/operation limits remain enforced.
- Every upstream Mantine export is classified and every enabled runtime component resolves.
-
-### Runtime and workbench
-
- Query cancellation, stale results, retries, render children, action locks, DELETE confirmation, toggle rollback, and invalidation behave identically in preview and boards.
- Error boundaries isolate template and display failures.
- Empty, sample, stale, loading, failure, and success states are localized and accessible.
- Keyboard, focus, responsive, reduced-motion, and narrow-widget behavior remain covered.
-
-### Server and adapters
-
- Board IDOR, permission levels, anonymous actions, named-request kinds, substitutions, DNS classes, redirects, headers, response limits, caching, and rate limits remain covered.
- Server tests run under an explicit Node environment rather than failing during client-environment initialization.
- MCP schemas and descriptions remain discoverable, stable, and absent from unsafe runtime procedures.
-
-### Required commands
-
-At the end of the migration, the package and repository must pass:
-
-```sh
-pnpm --filter @homarr/custom-widgets test
-pnpm test
-pnpm test:e2e
-pnpm turbo typecheck --affected
-pnpm turbo lint --affected
-pnpm turbo build --filter=@homarr/docs
-pnpm check:custom-widget-bundle # after the Next.js production build
-```
-
-CI additionally checks dependency direction, cycles, file budgets, generated references, translations, and client bundle size.
-
-## Completion criteria
-
- `@homarr/custom-widgets` owns every reusable custom-widget domain behavior.
- No circular dependencies exist.
- The package does not import `@homarr/api`, `@homarr/widgets`, or Next.js route modules.
- Runtime and workbench networking uses injected typed ports.
- One typed descriptor is the source of truth for each display type.
- One shared JSX policy drives authoring diagnostics and runtime enforcement.
- Create, edit, import, export, preview, MCP, and board runtime use the same typed transformations.
- Public tRPC/MCP names, import formats, stored configuration, and permission behavior remain compatible.
- V1 display-only migration and network-review states remain tested.
- Production modules satisfy the 300/400-line budgets.
- No untranslated user-facing strings remain.
- Core, JSX, runtime, server, workbench, integration, E2E, accessibility, docs, and bundle checks pass.
- A maintainer can locate a custom-widget behavior from the package structure without searching unrelated packages.
-
-## Explicit non-goals
-
- Replacing Mantine or Homarr's visual language.
- Allowing arbitrary cross-origin requests.
- Replacing named requests with general JavaScript execution.
- Changing stored secrets or exposing them through export or MCP.
- Redesigning the current management UX during the package extraction.
- Removing compatibility formats before migration and review flows are proven.
-
-## Decision record
-
- The package owns all Custom Widget behavior, not only Custom JSX.
- Security and correctness are hard constraints.
- Maintainer simplicity is the primary tie-breaker after those constraints.
- Current user and agent workflows are preserved during extraction.
- Generated artifacts do not count toward source-size budgets.
- Migration occurs through reviewable, behavior-preserving PRs rather than a single rewrite.
@@ -1,50 +1,3 @@
-## [1.70.0](https://github.com/homarr-labs/homarr/compare/v1.69.2...v1.70.0) (2026-07-10)
-
-## [1.69.2](https://github.com/homarr-labs/homarr/compare/v1.69.1...v1.69.2) (2026-07-06)
-
-### Bug Fixes
-
-* **layout:** raise AppShellHeader z-index above Indicator dots ([687edb9](https://github.com/homarr-labs/homarr/commit/687edb9226307cb83986097abb24fe7f672e1778)), closes [#6194](https://github.com/homarr-labs/homarr/issues/6194)
-
-## [1.69.1](https://github.com/homarr-labs/homarr/compare/v1.69.0...v1.69.1) (2026-07-04)
-
-### Bug Fixes
-
-* unblock query cache mutations in demo mode and add cache buster ([#6176](https://github.com/homarr-labs/homarr/issues/6176)) ([a382c75](https://github.com/homarr-labs/homarr/commit/a382c75968e73bafff55b5890b1e95f0779b50d3))
-
-## [1.69.0](https://github.com/homarr-labs/homarr/compare/v1.68.1...v1.69.0) (2026-07-03)
-
-### Features
-
-* add per-widget secret storage for release provider authentication ([77884a3](https://github.com/homarr-labs/homarr/commit/77884a31794e12a6f7bc59d96c8f61aa429ca68d))
-* **config:** enable pnpm global virtual store for worktree support ([#6098](https://github.com/homarr-labs/homarr/issues/6098)) ([3864727](https://github.com/homarr-labs/homarr/commit/3864727502a64052c4e3838468094b30bf04a133))
-* **docker-widget:** add per-column visibility toggle ([#6093](https://github.com/homarr-labs/homarr/issues/6093)) ([0765262](https://github.com/homarr-labs/homarr/commit/076526293d13379004461633d7ba4c2e83bd5ffe))
-* **docs:** addd in documentation for archiveteam warrior ([f66469d](https://github.com/homarr-labs/homarr/commit/f66469d79797a2da214588f4e8253b03633c59a5))
-* simplify caching — TanStack Query as single source of truth ([#6075](https://github.com/homarr-labs/homarr/issues/6075)) ([f19033e](https://github.com/homarr-labs/homarr/commit/f19033e0d53d248aed678737f3d04d5d8c7815b5))
-* **widgets:** right-click context menu with auto-generated toggle actions ([#6126](https://github.com/homarr-labs/homarr/issues/6126)) ([7e58858](https://github.com/homarr-labs/homarr/commit/7e58858353ae866efd657270d4bb16d2c7d3e551))
-* **widgets:** show calendar events on hover with pin on click ([#2637](https://github.com/homarr-labs/homarr/issues/2637)) ([#6081](https://github.com/homarr-labs/homarr/issues/6081)) ([db3d588](https://github.com/homarr-labs/homarr/commit/db3d58821e4de8d46b110125d0fa36919765248f))
-
-### Bug Fixes
-
-* add id to repository schema and handle missing ids gracefully ([8747d5f](https://github.com/homarr-labs/homarr/commit/8747d5f93ee9a295aad3c7035e8c6c7080bf5ee6))
-* address PR review - atomic upsert, MCP metadata, stale tokens, save UX ([757d598](https://github.com/homarr-labs/homarr/commit/757d59854e5ec82d91c053b8bc3d7eaf2e70efc4))
-* address PR review findings for widget-only integration refactor ([c892731](https://github.com/homarr-labs/homarr/commit/c892731479b47fab6218bd1f52fa6eccbdaa371e))
-* address review - paginate GH releases, GitLab tag_name, docs, test ([e687bc8](https://github.com/homarr-labs/homarr/commit/e687bc8c9277797acaa164a09c74b3808a2cb346))
-* apply version filter to LinuxServer.io provider ([34d976e](https://github.com/homarr-labs/homarr/commit/34d976eeea09e396334ce8fce5c492c07e7dd32b))
-* catch individual repo fetch failures to prevent batch crashes ([d893515](https://github.com/homarr-labs/homarr/commit/d893515b932608ea08c9c6e90b83f340e40f6f8e))
-* compile versionRegex once and add fetch timeouts ([64c7512](https://github.com/homarr-labs/homarr/commit/64c75122833981a49e9c8bf1789d501faff6d62d))
-* **deps:** update dependency postcss to ^8.5.16 ([#6169](https://github.com/homarr-labs/homarr/issues/6169)) ([9252fdc](https://github.com/homarr-labs/homarr/commit/9252fdc13971bd982224a31d7be577112f99ec45))
-* dns-hole widgets showing stale disconnected state ([#6096](https://github.com/homarr-labs/homarr/issues/6096)) ([2443f1c](https://github.com/homarr-labs/homarr/commit/2443f1cd3ff6765a91783d60d42aa03d9ba63fcd))
-* gracefully degrade when widget_secret table is missing or access denied ([30107e4](https://github.com/homarr-labs/homarr/commit/30107e4e76a454ff7402de9a8bc2e0dd6f422aa8))
-* handle missing widgetSecrets table and add default releases repo ([af35a50](https://github.com/homarr-labs/homarr/commit/af35a50fa05fee2f0118e98727eb108b0200f762))
-* **immich:** v3 API compatibility — use searchAssets for album assets, drop deviceAssetId ([#5977](https://github.com/homarr-labs/homarr/issues/5977)) ([a5ec880](https://github.com/homarr-labs/homarr/commit/a5ec880eec276e0814d2ab3ed7f9bc0b804d0465))
-* quick wins — calendar, about, glances, admin UX, releases, iframe, notes ([#6116](https://github.com/homarr-labs/homarr/issues/6116)) ([f9da71a](https://github.com/homarr-labs/homarr/commit/f9da71a19bdfa589aafe26b164d0e0782208ac0a))
-* restore ArchiveTeam Warrior as a proper integration ([8a5ad58](https://github.com/homarr-labs/homarr/commit/8a5ad5861ba4c2d0978f1fa3f6115a1c5974f8a2))
-* **timetable:** restore station search by removing disabled query guard ([d670b69](https://github.com/homarr-labs/homarr/commit/d670b6939672932c1a3d17ab9913901491cb46e3))
-* update CHANGES.md for ArchiveTeam Warrior restoration, remove typo translation key ([62baaf7](https://github.com/homarr-labs/homarr/commit/62baaf78130c4b74e899a948cee17097d8c02593))
-* verbose error messages in all release providers ([2155f13](https://github.com/homarr-labs/homarr/commit/2155f13f245f601b99458e227b6e058fbfa44cd9))
-* **widgets:** make downloads widget table background transparent ([#6025](https://github.com/homarr-labs/homarr/issues/6025)) ([73bed51](https://github.com/homarr-labs/homarr/commit/73bed51df895250f415efd7a87e721e403b3fd99))
-
 ## [1.68.1](https://github.com/homarr-labs/homarr/compare/v1.68.0...v1.68.1) (2026-06-30)

 ### Bug Fixes
@@ -1,96 +0,0 @@
-# Changes
-
-## Goal
-
-Remove widget-only services from Homarr's global Integration system.
-
-The affected services are release providers and Search.ch. They are only used by specific widgets, so keeping them as global integrations added unnecessary setup, UI, database rows, docs pages, and integration package code.
-
-ArchiveTeam Warrior remains a proper integration but is no longer auto-seeded on first install.
-
-## Why
-
-These services do not need shared integration state.
-
- Release providers are selected per Releases widget repository.
- Search.ch is only used by the Timetable widget.
-
-Moving them into widget options makes configuration simpler and removes dead-weight integration code from `packages/integrations`.
-
-## What Changed
-
-### Release Providers
-
- Added release provider definitions in `packages/definitions/src/release-provider.ts`.
- Removed release providers from `IntegrationKind`.
- Moved release-fetching code out of `packages/integrations` and into `packages/request-handler/src/release-providers.ts`.
- Updated the Releases widget to store provider configuration directly in widget options:
-  - `provider`
-  - `identifier`
-  - `versionFilter`
-  - `providerUrl`
- Updated the Releases widget editor to use a provider select instead of an integration select.
- Updated Docker import mapping so `ghcr.io` maps to `gitHubContainerRegistry`.
- GitHub Container Registry now uses the public OCI registry API and accepts full image references such as `ghcr.io/homarr-labs/homarr:latest`.
-
-### Timetable / Search.ch
-
- Removed Search.ch as an integration.
- Added a Timetable widget `baseUrl` option, defaulting to `https://search.ch`.
- Moved Search.ch request/parsing logic into `packages/request-handler/src/timetable.ts`.
- Updated the Timetable API to receive `baseUrl` directly from widget options.
-
-### ArchiveTeam Warrior
-
- Kept as a proper integration (not removed).
- Removed `defaultUrl` from the integration definition to prevent auto-seeding on first install.
-
-### Integration Cleanup
-
- Removed creators, exports, docs references, and implementation files for the deleted integrations.
- Removed unused dependencies from `packages/integrations/package.json`.
-
-### Database Migration
-
- Added `packages/db/migrations/custom/0003_remove_widget_only_integrations.ts`.
- The migration moves old integration-linked widget config into widget options, then deletes the old widget-only integration rows.
- Updated the earlier release widget migration to use the new `provider` field instead of `providerIntegrationId`.
-
-### Docs
-
- Updated Releases widget docs to describe providers instead of integrations.
- Updated Timetable docs to remove Search.ch integration setup.
- Removed obsolete integration docs pages for the deleted integration kinds.
- Updated docs sitemap and integration docs mappings.
-
-### Translations
-
- Added English labels for the new widget options:
-  - `widget.timetable.option.baseUrl.label`
-  - `widget.releases.option.repositories.providerUrl.label`
-
-## How It Works Now
-
-Release provider configuration lives on each Releases widget repository entry. The request handler resolves provider metadata and fetches releases directly from the provider-specific endpoint. GHCR uses anonymous OCI registry access for public packages.
-
-Timetable passes its widget URL option directly to its API router and request handler. No global integration lookup is needed.
-
-ArchiveTeam Warrior continues to use the standard integration system, but users must manually add the integration (it is not auto-created on install).
-
-## Deliberate Non-Goals
-
- No provider secret/token support was added.
- No new secret storage model was introduced.
- No compatibility layer was kept in `packages/integrations`.
-
-Widget options are client-visible, so storing provider credentials there would be wrong. If authenticated provider requests are needed later, they need a separate secret-storage design.
-
-## Verification So Far
-
- Focused typechecks passed for affected packages.
- Full `pnpm turbo typecheck` passed.
- Full `pnpm lint` passed with existing warnings.
- Focused release provider normalization tests passed.
- Widget translation test passed.
- Live GHCR smoke checks passed for `ghcr.io/muchobien/pocketbase:latest` and `ghcr.io/homarr-labs/homarr:latest`.
- `pnpm test packages/integrations/test/pi-hole.spec.ts` passed earlier, but failed on rebased reruns because Pi-hole reported `domainsBeingBlocked` as `-2`/`0` instead of `> 1`.
@@ -19,14 +19,6 @@ packages/integrations/src/anchor @ohmzi
 apps/docs/docs/integrations/archive-team-warrior @darbyjack
 packages/integrations/src/archive-team-warrior @darbyjack

-# Bazarr - introduced in https://github.com/homarr-labs/homarr/pull/6156 by @Ayush7614
-apps/docs/docs/integrations/bazarr @Ayush7614
-apps/docs/docs/widgets/bazarr @Ayush7614
-packages/api/src/router/widgets/bazarr.ts @Ayush7614
-packages/integrations/src/bazarr @Ayush7614
-packages/request-handler/src/bazarr.ts @Ayush7614
-packages/widgets/src/bazarr @Ayush7614
-
 # Audiobookshelf - introduced in https://github.com/homarr-labs/homarr/pull/5910 by @ajnart
 apps/docs/docs/integrations/audiobookshelf @ajnart
 packages/integrations/src/audiobookshelf @ajnart
@@ -135,13 +127,6 @@ packages/integrations/src/overseerr @manuel-rw
 apps/docs/docs/integrations/paperless-ngx @ajnart
 packages/integrations/src/paperless-ngx @ajnart

-# PatchMon - introduced in https://github.com/homarr-labs/homarr/pull/6119 by @mrjoshuap
-apps/docs/docs/integrations/patchmon @mrjoshuap
-packages/integrations/src/patchmon @mrjoshuap
-packages/widgets/src/patchmon @mrjoshuap
-packages/api/src/router/widgets/patchmon.ts @mrjoshuap
-packages/request-handler/src/patchmon.ts @mrjoshuap
-
 # PeaNUT - introduced in https://github.com/homarr-labs/homarr/pull/5862 by @afonsojramos
 apps/docs/docs/integrations/peanut @afonsojramos
 packages/integrations/src/peanut @afonsojramos
@@ -174,10 +159,6 @@ packages/integrations/src/search-ch @Meierschlumpf
 apps/docs/docs/integrations/speedtest-tracker @kylegrieder
 packages/integrations/src/speedtest-tracker @kylegrieder

-# Synology - introduced in https://github.com/homarr-labs/homarr/pull/6121 by @mrjoshuap
-apps/docs/docs/integrations/synology @mrjoshuap
-packages/integrations/src/synology @mrjoshuap
-
 # Technitium DNS - introduced in https://github.com/homarr-labs/homarr/pull/5832 by @lopsch
 apps/docs/docs/integrations/technitium-dns @lopsch
 packages/integrations/src/technitium @lopsch
@@ -206,14 +187,6 @@ packages/integrations/src/unraid @manuel-rw
 apps/docs/docs/integrations/uptime-kuma @ajnart
 packages/integrations/src/uptime-kuma @ajnart

-# Traefik - by @Nerdy-Technician
-apps/docs/docs/integrations/traefik @Nerdy-Technician
-apps/docs/docs/widgets/traefik @Nerdy-Technician
-packages/api/src/router/widgets/traefik.ts @Nerdy-Technician
-packages/integrations/src/traefik @Nerdy-Technician
-packages/request-handler/src/traefik.ts @Nerdy-Technician
-packages/widgets/src/traefik @Nerdy-Technician
-
 # Exempt Renovate-managed files (no owners)
 package.json
 **/package.json
@@ -1,43 +1,24 @@
-# syntax=docker/dockerfile:1.25
-
 FROM node:24.18.0-alpine AS base

 FROM base AS builder
+RUN apk add --no-cache libc6-compat
+RUN apk update
+
+# Set working directory
 WORKDIR /app
-RUN apk add --no-cache libc6-compat curl bash && apk update
-
-RUN corepack enable pnpm
-COPY pnpm-lock.yaml pnpm-workspace.yaml package.json ./
-COPY patches ./patches
-# Workaround for pnpm/pnpm#5268: pnpm fetch crashes when patchedDependencies
-# are configured with nodeLinker: hoisted. The applyPatchToDir function tries
-# to chdir into node_modules/<pkg> which doesn't exist during fetch (only the
-# content-addressable store is populated). By temporarily switching to the
-# 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 \
-    pnpm config set store-dir /pnpm/store && \
-    sed -i 's/nodeLinker: hoisted/nodeLinker: isolated/' pnpm-workspace.yaml && \
-    pnpm fetch && \
-    sed -i 's/nodeLinker: isolated/nodeLinker: hoisted/' pnpm-workspace.yaml
-
+RUN apk add --no-cache libc6-compat curl bash
+RUN apk update
 COPY . .
-# Follow the pnpm fetch pattern from https://pnpm.io/cli/fetch
-# --frozen-lockfile is omitted as recommended by the pnpm fetch docs
-RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
-    pnpm install --recursive

+RUN corepack enable pnpm && pnpm install --recursive --frozen-lockfile
+
+# Copy static data as it is not part of the build
+COPY static-data ./static-data
 ARG SKIP_ENV_VALIDATION='true'
 ARG CI='true'
 ARG DISABLE_REDIS_LOGS='true'
-ARG TARGETPLATFORM

-RUN --mount=type=secret,id=TURBO_API,env=TURBO_API \
-    --mount=type=secret,id=TURBO_TEAM,env=TURBO_TEAM \
-    --mount=type=secret,id=TURBO_TOKEN,env=TURBO_TOKEN \
-    --mount=type=secret,id=TURBO_REMOTE_CACHE_SIGNATURE_KEY,env=TURBO_REMOTE_CACHE_SIGNATURE_KEY \
-    TURBO_PLATFORM="${TARGETPLATFORM:-linux/amd64}" pnpm build
+RUN corepack enable pnpm && pnpm build

 FROM base AS runner
 WORKDIR /app
@@ -5,47 +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. Administrators can create [Custom Widgets](/docs/management/custom-widgets) that read an HTTP API and render the response with a built-in display type. These display types require no programming.
+- 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.

-Custom JSX is available when you need a more specific layout or an interactive control. It uses a restricted declarative JSX interpreter with a classified Mantine component set. Network operations are declared as named, same-origin requests and are checked against board permissions on the server. It does not execute arbitrary JavaScript or expose browser `fetch`.
-
-You should be comfortable reading JSON and JSX to author complex templates. The management workbench includes examples, diagnostics, a component reference, API response inspection, and a prompt you can copy into an AI assistant. Always review imported templates and request capabilities before saving them.
+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>
@@ -53,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

@@ -28,7 +28,6 @@ Read our [glossary](/docs/getting-started/glossary) if you are new to Homarr.
 Congratulations on installing Homarr. Now it's time to get yourself familiar with the concepts of Homarr and how to use it.

 ## Onboarding
-
 The onboard will show the first time you start Homarr.
 This process will help you with your first steps and adding some initial data, such as the administrator account.

@@ -46,68 +45,50 @@ You can either import a previous dashboard using the ZIP archive or start from s
 You may refresh anytime and continue from a different device - the onboarding is saved immediately on the server for your convenience.

 ### Starting from scratch
-
 Depending on your auth provider configuration you will either first see the admin user creation form or the external group creation form.
-If the credentials provider was selected, you'll be prompted to create an admin user for Homarr.
-This user cannot be deleted and has full control over Homarr and all of its boards.
-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.
+If credentials provider was selected, you'll be prompted to create an admin user for Homarr.
+This user cannot be deleted and has full control over Homarr and all of it's boards.
+You must choose an username and password (both can later be changed).
+We enforce strict password requirements, when you enter your password, to protect your instance if you accidentially
+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.
-When a user logs in through the provider, any of their groups that match groups in Homarr will be assigned to the user.
-The name of the group must match exactly the name of the group in the provider.
+This group will be used to synchronize users from your provider to Homarr. 
+When a user is logged in through the provider the groups of him that match groups with any in Homarr will be added to the user.
+The name of the group has to match exactly the name of the group in the provider.

-<img
-  src={imageStartFromScratchStepExternalAdminGroup}
-  alt={"Screenshot form to create external admin group"}
-  width={300}
-/>
+<img src={imageStartFromScratchStepExternalAdminGroup} alt={"Screenshot form to create external admin group"} width={300} />

 Next, you can configure some basic settings for Homarr. We recommend to leave all settings at default for most users.
 Here you can also disable analytics. Please note that our analytics are completly anonymous and is fully compliant with GDPR and PECR.

-<img
-  src={imageStartFromScratchStepServerSettings}
-  alt={"Screenshot of analytics and indexing settings in the onboarding"}
-  width={300}
-/>
+<img src={imageStartFromScratchStepServerSettings} alt={"Screenshot of analytics and indexing settings in the onboarding"} width={300} />

 ### Setting up integrations

 After configuring server settings, the onboarding guides you through setting up your integrations.

 #### Docker service discovery
-
 If Docker is available (socket mounted), Homarr automatically detects running containers and matches them to known integration types.
 Matching integrations are pre-selected in the integration list, saving you from manually picking each one.

 #### URL templating
-
 You can define a base URL template to auto-fill integration URLs in bulk.
 Two modes are supported:
-
 - **Subdomain mode** - e.g. `{app}.example.com` where `{app}` is replaced with the integration name
 - **Port mode** - e.g. `192.168.1.1:{port}` where `{port}` is replaced with the integration's default port

 #### API key helper links
-
 For integrations that require API keys (such as Sonarr, Radarr, SABnzbd, or Seerr), a helper link opens the relevant settings page in the target application so you can quickly copy your key.

 #### Creating apps from Docker containers
-
 You can optionally auto-create bookmark apps for all discovered Docker containers, making them immediately available on your board.

 :::note

-Release providers and Search.ch are configured directly in their widgets instead of the integrations page.
+Some niche and registry integrations (GitHub, npm, Docker Hub, GitLab, Codeberg, LinuxServer.io, GHCR, Quay, Search.ch) are hidden from the onboarding selection grid but remain available on the manage integrations page.

 :::

@@ -116,41 +97,30 @@ 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**
-
-1. Navigate to your old Homarr, open your management pages, open the tools submenu and open `Migrate to 1.0`.
+1. Navigate to your old Homarr, open your management pages, open the tools submenu and open ``Migrate to 1.0``.
 2. Check the contents that you want to export. We recommend you to export all data.
 3. Click on the export data button
 4. Save the ZIP file, that is being downloaded, on your device. If you selected "integrations" or "users", you also get an encryption / decryption key.
-   Copy it and do not loose it!
-5. Go to your new >1.0.0 Homarr instance and start the onboarding. Choose `Import from Homarr before 1.0`
+Copy it and do not loose it!
+5. Go to your new >1.0.0 Homarr instance and start the onboarding. Choose ``Import from Homarr before 1.0``
 6. Drag and drop your previously downloaded ZIP archive into the file upload: <br/><img src={manageImportOldHomarrDropzone} style={{ maxWidth: 500 }} />
 7. Next, choose the data that you want to import and how to import it. Since screen sizes were removed in 1.0, we create a new board for every screen size by default. We recommend you to only keep the best layout and adjust it later in 1.0.0 - but you can also import all of them and pick later.<br/><img src={manageImportOldHomarrChooseData} style={{ maxWidth: 500 }} />
 8. If you previously exported integrations or users, you will be asked to decrypt the data safely using your obtained encryption token. Paste into the modal and confirm your action.<br/><img src={manageImportDecryptionToken} style={{ maxWidth: 500 }} />
 9. Next, you can [follow the same setup as when starting from scratch](#starting-from-scratch). After you completed the onboarding, all of your data will be migrated and available.

 ## Creating your first board
-
 In Homarr, you organize your apps and widgets on boards.
 Boards can be organized using the interactive drag and drop.
-Let's create your first board by navigating here: `Manage` > `Boards` > `New board`:
+Let's create your first board by navigating here: ``Manage`` > ``Boards`` > ``New board``:
 ![](./img/manage-create-board-button.png)

 A board must always have a name and can either be public or private.
@@ -163,13 +133,12 @@ Congratulations - you've just created your first board. You can see boards, that
 ![](./img/manage-view-board.png)

 ## Add your first app to Homarr
-
 To add links to your dashboard, you must first add them as an "app".
 Navigate to this page to add an app:

 ![](./img/manage-navigate-apps.png)

-Next, click on the `New app` button. You'll need to provide a name and an icon to create an app.
+Next, click on the ``New app`` button. You'll need to provide a name and an icon to create an app.
 The name must be at least one character long but you can provide any image URL for the icon.
 Homarr ships with over 11K icons - so you can just search by entering a search text instead.

@@ -180,9 +149,8 @@ After you created the app, you'll see in on the apps page:
 ![](./img/manage-created-app.png)

 ## Arrange and organize your board
-
 Let's add your freshly created app, from the previous step, to the board.
-To do this, edit your previously created board by clicking on the big `Open board` button:
+To do this, edit your previously created board by clicking on the big ``Open board`` button:

 ![](./img/manage-view-board.png)

@@ -197,38 +165,23 @@ 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.
@@ -275,18 +228,17 @@ Be sure to save your changes by exiting edit mode!
 ![](./img/exit-edit-mode.png)

 ## Adding your first integration
-
 Now it's time to integrate some basic data into your board.
 To do this, we first need to create an integration.
 An integration is a connection between Homarr and a third party application - usually something that you run and deploy yourself.

-Navigate to `Manage` > `Integrations` (for example via your user menu).
+Navigate to ``Manage`` > ``Integrations`` (for example via your user menu).
 As an example, we are going to use the public demo instance of **Dash.** - a popular application to monitor CPU / hardware usage.
 Choose the **Dash.** integration from the list of available integrations:

 ![](./img/choose-integration.gif)

-Next, choose a name (or leave it at default), enter `https://dash.mauz.dev/` as the URL in the form and click on `Test connection and create`.
+Next, choose a name (or leave it at default), enter ``https://dash.mauz.dev/`` as the URL in the form and click on ``Test connection and create``.
 Pressing the save button will perform a test request to the integration, to confirm that the networking setup is working as expected.
 Sometimes invalid configurations, firewalls and other mistakes can lead to connectivity problems - [follow this guide here](/docs/management/integrations/#troubleshooting-connection) if you experience issues.

@@ -302,14 +254,13 @@ the target application or your router.
 :::

 ## Embed integration data using widgets
-
 Let's add your integration, that you have configured in the section above, as a widget to your board.
 First, navigate back to your board that you want to add it to.
 Next, enter edit mode again and add another item to your board:

 ![](./img/manage-board-header-add-item-menu.png)

-Instead of choosing an app, let's choose `System Health Monitoring` this time.
+Instead of choosing an app, let's choose ``System Health Monitoring`` this time.
 Click on "Add to board":

 ![](./img/manage-board-header-choose-system-health.png)
@@ -339,12 +290,10 @@ As with every change, don't forget to save your changes using the exit edit mode
 ![](./img/exit-edit-mode.png)

 ## Grouping your items
-
 As the last step, let's organize your freshly created items using two different options.
 You can choose either or both of them on your boards.

 ### Using dynamic sections
-
 Dynamic sections are a simple, resizable visual group to group items.

 ![](./img/create-dynamic-section.png)
@@ -354,7 +303,6 @@ After adding a dynamic section, you can simply drag and drop items into the sect
 ![](./img/dynamic-section.gif)

 ### Using categories
-
 Categories are more advanced and complicated than dynamic sections.
 To create a category, open the add item modal and choose "new category":

@@ -381,27 +329,22 @@ You cannot reduce their horizontal width.
 After completing the onboarding, Homarr provides interactive guided tours to help you discover key features.

 ### Management tour
-
 When you first visit the management area (`/manage`), Homarr walks you through the main pages: boards, apps, integrations, and users (admin only).
 Each page highlights the list view and the create action so you know where to find and add things.

 ### Board tour
-
 When you first open a board, a tour highlights the board header elements: search, edit mode, settings, board switcher, and user menu.

 ### Tour controls
-
 - Press **Enter** (or click **Next**) to advance through tour steps
 - Tours auto-start on first visit and do not repeat once completed
 - Tours are skipped on mobile screens (below `sm` breakpoint)
 - You can **reset tours** from the user settings page under **Manage > Users > [Your user] > General**

 ## Next steps
-
 You're done with the basic setup 🔥. Now it's time to organize and customize even more.
 We highly recommend you to experiment with different options, styles and configurations.
 See these curated pages for your next steps:
-
 - Create new apps using the [apps management](/docs/management/apps/)
 - Customize your board or add more boards using the [boards management](/docs/management/boards/)
 - Integrate software that you use using the [integrations management](/docs/management/integrations/)
@@ -2,9 +2,9 @@

 <img src="https://raw.githubusercontent.com/homarr-labs/charts/refs/heads/main/charts/homarr/icon.svg" align="right" width="92" alt="homarr logo">

-![Version: 8.22.0](https://img.shields.io/badge/Version-8.22.0-informational?style=flat)
+![Version: 8.20.0](https://img.shields.io/badge/Version-8.20.0-informational?style=flat)
 ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat)
-![AppVersion: v1.70.0](https://img.shields.io/badge/AppVersion-v1.70.0-informational?style=flat)
+![AppVersion: v1.68.0](https://img.shields.io/badge/AppVersion-v1.68.0-informational?style=flat)

 A Helm chart to deploy homarr for Kubernetes

@@ -429,7 +429,7 @@ All available values are listed on the [artifacthub](https://artifacthub.io/pack
 | 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.70.0"` | Overrides the image tag whose default is the chart appVersion |
+| image.tag | string | `"v1.60.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 |
@@ -4,6 +4,7 @@ description: "AdGuard Home is a network-wide software for blocking ads and track
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -18,6 +19,10 @@ import { dnsHoleControlsWidget } from '@site/docs/widgets/dns-hole-controls';
    categories={['DNS Hole']}
 />

+### Data
+
+<IntegrationData integration={adguardHomeIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[{
@@ -6,4 +6,5 @@ export const adguardHomeIntegration: IntegrationDefinition = {
    "AdGuard Home is a network-wide software for blocking ads and trackers, providing a safer and faster internet experience.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/adguard-home.svg",
  path: "../../integrations/adguard-home",
+  data: "Fetches DNS query statistics, blocking status, and filtering rules from AdGuard Home.",
 };
@@ -4,6 +4,7 @@ description: "Anchor is a self-hosted note-taking application."
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -19,6 +20,10 @@ import { anchorNoteWidget } from '@site/docs/widgets/anchor-note';

 The Anchor integration lets Homarr connect to your Anchor instance so you can display and edit selected notes directly from your dashboard.

+### Data
+
+<IntegrationData integration={anchorIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
  items={[{
@@ -6,4 +6,5 @@ export const anchorIntegration: IntegrationDefinition = {
    "Anchor is a self-hosted note-taking application. The Anchor integration lets Homarr display and edit selected notes directly from the dashboard.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/anchor.svg",
  path: "../../integrations/anchor",
+  data: "Fetches and updates notes from an Anchor note-taking server.",
 };
@@ -4,6 +4,7 @@ description: "ArchiveTeam Warrior is an easy-to-run virtual machine that helps p
 hide_title: true
 ---

+import { IntegrationData } from "@site/src/components/integrations/data";
 import { IntegrationHeader } from "@site/src/components/integrations/header";
 import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
@@ -13,6 +14,10 @@ import { archiveTeamWarriorIntegration } from ".";

 The ArchiveTeam Warrior integration lets Homarr connect to your ArchiveTeam Warrior instance so you can manage and monitor your archiving tasks directly from your dashboard.

+### Data
+
+<IntegrationData integration={archiveTeamWarriorIntegration} />
+
 ### Adding the integration

 <AddingIntegration />
@@ -6,4 +6,5 @@ export const archiveTeamWarriorIntegration: IntegrationDefinition = {
    "ArchiveTeam Warrior is an easy-to-run virtual machine that helps preserve websites by using some of your bandwidth and disk space to download and upload content to ArchiveTeam’s archive.",
  iconUrl: "https://cdn.jsdelivr.net/gh/selfhst/icons/png/archiveteam-warrior.png",
  path: "../../integrations/archiveteam-warrior",
+  data: "Fetches Archive Team Warrior status including project, bandwidth stats, and item progress via WebSocket.",
 };
@@ -4,6 +4,7 @@ description: "Lightweight multiprotocol & multi-source command-line download uti
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -16,6 +17,10 @@ import { downloadsWidget } from '@site/docs/widgets/downloads';
  categories={['Download', 'Multiprotocol', 'Multi-source']}
 />

+### Data
+
+<IntegrationData integration={aria2Integration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
  items={[{
@@ -6,4 +6,5 @@ export const aria2Integration: IntegrationDefinition = {
    "Lightweight multi-protocol & multi-source command-line download utility. It supports HTTP/HTTPS, FTP, SFTP, BitTorrent and Metalink",
  iconUrl: "https://cdn.jsdelivr.net/gh/PapirusDevelopmentTeam/papirus_icons@latest/src/system_downloads_3.svg",
  path: "../../integrations/aria2",
+  data: "Manages and monitors Aria2 downloads including active, waiting, and stopped transfers.",
 };
@@ -4,6 +4,7 @@ description: "Audiobookshelf is a self-hosted audiobook and podcast server that
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -19,6 +20,10 @@ import { audioStatsWidget } from '@site/docs/widgets/audio-stats';

 Audiobookshelf provides library statistics including audiobook and podcast counts, listening time, and active sessions.

+### Data
+
+<IntegrationData integration={audiobookshelfIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[
@@ -6,4 +6,5 @@ export const audiobookshelfIntegration: IntegrationDefinition = {
    "Audiobookshelf is a self-hosted audiobook and podcast server that lets you manage and stream your audio library.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/audiobookshelf.svg",
  path: "../../integrations/audiobookshelf",
+  data: "Fetches library statistics, listening time, and active sessions from Audiobookshelf.",
 };
@@ -1,54 +0,0 @@
---
-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';
-
-<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';
-
-<div className="flex flex-col gap-4">
-  <div>
-    <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>
-    <p>Bazarr widget on a Homarr board:</p>
-    <img src={widgetOverview} alt="bazarr-widget-on-board" width={128 * 4} />
-  </div>
-</div>
-
-### Widgets & Capabilities
-<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.",
-    ],
-}]} />
@@ -1,9 +0,0 @@
-import { IntegrationDefinition } from "@site/src/types";
-
-export const bazarrIntegration: IntegrationDefinition = {
-  name: "Bazarr",
-  description:
-    "Bazarr is a companion application to Sonarr and Radarr that manages and downloads subtitles for your media library.",
-  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/bazarr.svg",
-  path: "../../integrations/bazarr",
-};
@@ -4,6 +4,7 @@ description: "Beszel is a lightweight server monitoring platform with Docker sta
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -27,6 +28,10 @@ Beszel monitors your servers in real time via lightweight agents, collecting CPU

 <img src={beszelDashboard} alt="Beszel dashboard overview showing all four widgets" />

+### Data
+
+<IntegrationData integration={beszelIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[
@@ -6,4 +6,5 @@ export const beszelIntegration: IntegrationDefinition = {
    "Beszel is a lightweight server monitoring platform with Docker stats, historical data, and alert functions.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons@master/svg/beszel.svg",
  path: "../../integrations/beszel",
+  data: "Fetches server monitoring data including system stats, containers, SMART devices, alerts, and real-time metrics.",
 };
@@ -0,0 +1,42 @@
+---
+title: 'Codeberg'
+description: "Codeberg is a non-profit, community-driven platform for hosting and collaborating on software projects."
+hide_title: true
+---
+
+import { IntegrationData } from '@site/src/components/integrations/data';
+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 { codebergIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={codebergIntegration}
+    categories={['Version Control', 'Software']}
+/>
+
+### Data
+
+<IntegrationData integration={codebergIntegration} />
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}, {
+    credentials: ['personalAccessToken'],
+    steps: []
+}]} />
@@ -0,0 +1,10 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const codebergIntegration: IntegrationDefinition = {
+  name: "Codeberg",
+  description:
+    "Codeberg is a non-profit, community-driven platform for hosting and collaborating on software projects.",
+  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/codeberg.svg",
+  path: "../../integrations/codeberg",
+  data: "Fetches latest releases and repository metadata from a Codeberg instance.",
+};
@@ -4,6 +4,7 @@ description: 'Self-hosted PaaS and deployment platform'
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -16,6 +17,10 @@ import { coolifyWidget } from '../../widgets/coolify';
  categories={['System monitoring', 'Deployment']}
 />

+### Data
+
+<IntegrationData integration={coolifyIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
  items={[
@@ -5,4 +5,5 @@ export const coolifyIntegration: IntegrationDefinition = {
  description: "Self-hosted PaaS and deployment platform",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons@master/svg/coolify.svg",
  path: "../../integrations/coolify",
+  data: "Fetches Coolify instance information including applications, services, servers, projects, and health status.",
 };
@@ -4,6 +4,7 @@ description: "Dash. is a system performance and resource monitoring tool"
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -19,6 +20,10 @@ import { systemResourcesWidget } from '@site/docs/widgets/system-resources';
  categories={['System monitoring']}
 />

+### Data
+
+<IntegrationData integration={dashDotIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[{
@@ -5,4 +5,5 @@ export const dashDotIntegration: IntegrationDefinition = {
  description: "Dash. is a system performance and resource monitoring tool",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/png/dashdot.png",
  path: "../../integrations/dash-dot",
+  data: "Fetches system health monitoring data including CPU, RAM, storage, network, and GPU information.",
 };
@@ -4,6 +4,7 @@ description: "Deluge is a lightweight, Free Software, cross-platform BitTorrent
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -19,6 +20,10 @@ import { downloadsWidget } from '@site/docs/widgets/downloads';
    categories={['Torrent client']}
 />

+### Data
+
+<IntegrationData integration={delugeIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[{
@@ -5,4 +5,5 @@ export const delugeIntegration: IntegrationDefinition = {
  description: "Deluge is a lightweight, Free Software, cross-platform BitTorrent client.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/deluge.svg",
  path: "../../integrations/deluge",
+  data: "Manages and monitors Deluge torrents including progress, speeds, and pause/resume/delete actions.",
 };
@@ -0,0 +1,42 @@
+---
+title: 'Docker Hub'
+description: "Docker Hub is a cloud-based registry service for sharing and managing Docker images."
+hide_title: true
+---
+
+import { IntegrationData } from '@site/src/components/integrations/data';
+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 { dockerHubIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={dockerHubIntegration}
+    categories={['Container Management', 'Software']}
+/>
+
+### Data
+
+<IntegrationData integration={dockerHubIntegration} />
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}, {
+    credentials: ['username', 'personalAccessToken'],
+    steps: []
+}]} />
@@ -0,0 +1,9 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const dockerHubIntegration: IntegrationDefinition = {
+  name: "Docker Hub",
+  description: "Docker Hub is a cloud-based registry service for sharing and managing Docker images.",
+  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/docker.svg",
+  path: "../../integrations/docker-hub",
+  data: "Fetches container image tags and repository metadata from Docker Hub.",
+};
@@ -4,6 +4,7 @@ description: "Docker is a platform where you can run your applications in contai
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
@@ -17,6 +18,10 @@ import { dockerContainersWidget } from '@site/docs/widgets/docker-containers';
  categories={['Containers']}
 />

+### Data
+
+<IntegrationData integration={dockerIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[{
@@ -6,4 +6,5 @@ export const dockerIntegration: IntegrationDefinition = {
    "Docker is a platform where you can run your applications in containers, allowing for easy deployment and management of applications.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/docker.svg",
  path: "../../integrations/docker",
+  data: "Fetches Docker container information including status, CPU, and memory usage via the Docker socket.",
 };
@@ -4,6 +4,7 @@ description: "Emby is a media server platform that allows you to organize, manag
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -19,6 +20,10 @@ import { mediaReleasesWidget } from '@site/docs/widgets/media-releases';
    categories={['Media server']}
 />

+### Data
+
+<IntegrationData integration={embyIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[
@@ -6,4 +6,5 @@ export const embyIntegration: IntegrationDefinition = {
    "Emby is a media server platform that allows you to organize, manage, and stream your personal media collection.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/emby.svg",
  path: "../../integrations/emby",
+  data: "Fetches active streams and recently added media from an Emby media server.",
 };
@@ -0,0 +1,47 @@
+---
+title: 'GitHub Container Registry'
+description: "GitHub Container Registry is a platform for hosting and managing packages."
+hide_title: true
+---
+
+import { IntegrationData } from '@site/src/components/integrations/data';
+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 { gitHubContainerRegistryIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={gitHubContainerRegistryIntegration}
+    categories={['Package Management', 'Software']}
+/>
+
+
+### Data
+
+<IntegrationData integration={gitHubContainerRegistryIntegration} />
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}, {
+    credentials: ["personalAccessToken"],
+    steps: []
+}, {
+    tabLabel: "GitHub App",
+    credentials: ['githubAppId', 'githubInstallationId', 'privateKey'],
+    steps: ['Create GitHub App', 'Create a private key for it', 'Install it to your organization / user']
+}]} />
@@ -0,0 +1,12 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const gitHubContainerRegistryIntegration: IntegrationDefinition = {
+  name: "GitHub Container Registry",
+  description: "GitHub Container Registry is a platform for hosting and managing packages.",
+  iconUrl: {
+    light: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/github.svg",
+    dark: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/github-light.svg",
+  },
+  path: "../../integrations/github-packages",
+  data: "Fetches container image tags and package metadata from GitHub Container Registry.",
+};
@@ -0,0 +1,46 @@
+---
+title: 'GitHub'
+description: "GitHub is a web-based platform for version control and collaboration."
+hide_title: true
+---
+
+import { IntegrationData } from '@site/src/components/integrations/data';
+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 { githubIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={githubIntegration}
+    categories={['Version Control', 'Software']}
+/>
+
+### Data
+
+<IntegrationData integration={githubIntegration} />
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}, {
+    credentials: ['personalAccessToken'],
+    steps: []
+}, {
+    tabLabel: "GitHub App",
+    credentials: ['githubAppId', 'githubInstallationId', 'privateKey'],
+    steps: ['Create GitHub App', 'Create a private key for it', 'Install it to your organization / user']
+}]} />
@@ -0,0 +1,12 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const githubIntegration: IntegrationDefinition = {
+  name: "GitHub",
+  description: "GitHub is a web-based platform for version control and collaboration.",
+  iconUrl: {
+    light: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/github.svg",
+    dark: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/github-light.svg",
+  },
+  path: "../../integrations/github",
+  data: "Fetches releases and repository metadata from GitHub using the Octokit API.",
+};
@@ -0,0 +1,42 @@
+---
+title: 'GitLab'
+description: "GitLab is a web-based DevOps lifecycle tool that provides a Git repository manager."
+hide_title: true
+---
+
+import { IntegrationData } from '@site/src/components/integrations/data';
+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 { gitlabIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={gitlabIntegration}
+    categories={['Version Control', 'Software']}
+/>
+
+### Data
+
+<IntegrationData integration={gitlabIntegration} />
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}, {
+    credentials: ['personalAccessToken'],
+    steps: []
+}]} />
@@ -0,0 +1,9 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const gitlabIntegration: IntegrationDefinition = {
+  name: "GitLab",
+  description: "GitLab is a web-based DevOps lifecycle tool that provides a Git repository manager.",
+  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/gitlab.svg",
+  path: "../../integrations/gitlab",
+  data: "Fetches releases and project metadata from a GitLab instance.",
+};
@@ -4,6 +4,7 @@ description: "Glances is a cross-platform system monitoring tool."
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -18,6 +19,10 @@ import { healthMonitoringWidget } from '@site/docs/widgets/health-monitoring';
    categories={['System Monitoring']}
 />

+### Data
+
+<IntegrationData integration={glancesIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[{
@@ -8,4 +8,5 @@ export const glancesIntegration: IntegrationDefinition = {
    dark: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/glances-light.svg",
  },
  path: "../../integrations/glances",
+  data: "Fetches system health data including CPU, RAM, disk, network, GPU, and sensors from Glances.",
 };
@@ -4,6 +4,7 @@ description: 'Connect Gluetun to Homarr as a VPN integration.'
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -19,6 +20,10 @@ import { vpnWidget } from '@site/docs/widgets/vpn';
 [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.

+### Data
+
+<IntegrationData integration={gluetunIntegration} />
+
 ### Widgets & Capabilities

 <IntegrationCapabilites
@@ -5,4 +5,5 @@ export const gluetunIntegration: IntegrationDefinition = {
  description: "VPN control server integration for Homarr's VPN widget.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/gluetun.svg",
  path: "../../integrations/gluetun",
+  data: "Fetches VPN status, public IP, and DNS information from a Gluetun VPN container.",
 };
@@ -6,6 +6,7 @@ hide_title: true

 import { notificationsWidget } from '@site/docs/widgets/notifications';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
@@ -16,6 +17,10 @@ import { gotifyIntegration } from '.';
    categories={['Notifications', 'Messaging']}
 />

+### Data
+
+<IntegrationData integration={gotifyIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[{
@@ -5,4 +5,5 @@ export const gotifyIntegration: IntegrationDefinition = {
  description: "Gotify is a simple, self-hosted server for sending and receiving messages in real time.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/gotify.svg",
  path: "../../integrations/gotify",
+  data: "Fetches recent push notification messages from a Gotify server.",
 };
@@ -4,6 +4,7 @@ description: "Home Assistant is an open-source home automation platform that foc
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -19,6 +20,10 @@ import { smartHomeExecuteAutomationWidget } from '@site/docs/widgets/smart-home-
    categories={['Smart Home', 'Automation']}
 />

+### Data
+
+<IntegrationData integration={homeAssistantIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[{
@@ -6,4 +6,5 @@ export const homeAssistantIntegration: IntegrationDefinition = {
    "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.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/home-assistant.svg",
  path: "../../integrations/home-assistant",
+  data: "Fetches entity states, triggers automations, toggles entities, and retrieves calendar events from Home Assistant.",
 };
@@ -4,6 +4,7 @@ description: "iCal is a standard for calendar data exchange, allowing users to s
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -17,6 +18,10 @@ import { calendarWidget } from '@site/docs/widgets/calendar';
  categories={['Calendar']}
 />

+### Data
+
+<IntegrationData integration={icalIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[{
@@ -6,4 +6,5 @@ export const icalIntegration: IntegrationDefinition = {
    "iCal is a standard for calendar data exchange, allowing users to share and manage calendar events across different platforms.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/ical.svg",
  path: "../../integrations/ical",
+  data: "Fetches and parses an iCal/ICS calendar feed to retrieve calendar events.",
 };
@@ -9,6 +9,7 @@ import { immichAlbumCarouselWidget } from '../../widgets/immich-album-carousel';
 } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
 import { immichIntegration } from '.';
 import { immichServerStatsWidget } from '../../widgets/immich-server-stats';
@@ -19,6 +20,10 @@ import { immichServerStatsWidget } from '../../widgets/immich-server-stats';
  categories={['Photo server']}
 />

+### Data
+
+<IntegrationData integration={immichIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
  items={[
@@ -39,26 +44,13 @@ import { immichServerStatsWidget } from '../../widgets/immich-server-stats';
    'Scroll down to "API Keys"', 
    'Click "New API Key"', 
    'Enter a name, e.g. "Homarr"', 
-(
-
-  <span>
-
-    Select the following permissions:{" "}
-    <code>album.statistics</code>,{" "}
-    <code>album.read</code>,{" "}
-    <code>album.create</code>,{" "}
-    <code>user.read</code>,{" "}
-    <code>user.update</code>,{" "}
-    <code>asset.read</code>,{" "}
-    <code>asset.download</code>,{" "}
-    <code>asset.statistics</code>,{" "}
-    <code>server.statistics</code>,{" "}
-    <code>server.about</code>.
-    <br />
-    Additional permissions may be required depending on your Immich version. If you encounter authorization errors, grant any missing permissions requested by the server.
-  </span>
-
-),
+    (<span>
+      Select the following permissions:{" "}
+      <code>album.read</code>,{" "}
+      <code>user.read</code>,{" "}
+      <code>server.statistics</code>,{" "}
+      <code>asset.download</code>
+    </span>), 
    'Create the integration in Homarr and copy the API key to there'
    ]
-}]} />
+}]} />
@@ -5,4 +5,5 @@ export const immichIntegration: IntegrationDefinition = {
  description: "Self-hosted photo and video management solution",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/immich.svg",
  path: "../../integrations/immich",
+  data: "Fetches server statistics, albums, and users from an Immich photo management server.",
 };
@@ -4,6 +4,7 @@ description: "Jellyfin is a free and open-source media server software that allo
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -19,6 +20,10 @@ import { mediaReleasesWidget } from '@site/docs/widgets/media-releases';
    categories={['Media server']}
 />

+### Data
+
+<IntegrationData integration={jellyfinIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[
@@ -6,4 +6,5 @@ export const jellyfinIntegration: IntegrationDefinition = {
    "Jellyfin is a free and open-source media server software that allows you to organize, manage, and share your media files.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/jellyfin.svg",
  path: "../../integrations/jellyfin",
+  data: "Fetches active streams and recently added media from a Jellyfin media server.",
 };
@@ -4,6 +4,7 @@ description: "Jellyseerr is a self-hosted media request management system that i
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -19,6 +20,10 @@ import { mediaRequestStatsWidget } from '@site/docs/widgets/media-request-stats'
  categories={['Media requests']}
 />

+### Data
+
+<IntegrationData integration={jellyseerrIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[{
@@ -6,4 +6,5 @@ export const jellyseerrIntegration: IntegrationDefinition = {
    "Jellyseerr is a self-hosted media request management system that integrates with Jellyfin and other media servers.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/jellyseerr.svg",
  path: "../../integrations/jellyseerr",
+  data: "Fetches media requests, search results, and user information from Jellyseerr.",
 };
@@ -4,6 +4,7 @@ description: "Kubernetes is a powerful container orchestration platform that aut
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
@@ -24,6 +25,10 @@ This integration is read-only, meaning Homarr does not modify or manage cluster

 ![Dashboard](img/dashboard.jpeg)

+### Data
+
+<IntegrationData integration={kubernetesIntegration} />
+
 ### Prerequisites

 Before deploying Homarr in Kubernetes, ensure the following prerequisites are met:
@@ -6,4 +6,5 @@ export const kubernetesIntegration: IntegrationDefinition = {
    "Kubernetes is a powerful container orchestration platform that automates the deployment, scaling, and management of containerized applications.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/kubernetes.svg",
  path: "../../integrations/kubernetes",
+  data: "Fetches Kubernetes cluster information including pods, deployments, and services.",
 };
@@ -4,6 +4,7 @@ description: "Lidarr is a music management tool that automates the process of do
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -18,6 +19,10 @@ import { calendarWidget } from '@site/docs/widgets/calendar';
    categories={['Media manager', "Servarr"]}
 />

+### Data
+
+<IntegrationData integration={lidarrIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[{
@@ -6,4 +6,5 @@ export const lidarrIntegration: IntegrationDefinition = {
    "Lidarr is a music management tool that automates the process of downloading, sorting, and renaming music.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/lidarr.svg",
  path: "../../integrations/lidarr",
+  data: "Fetches music album release calendar events from Lidarr.",
 };
@@ -0,0 +1,39 @@
+---
+title: 'LinuxServer.io'
+description: "LinuxServer.io is a platform for managing and deploying containerized applications."
+hide_title: true
+---
+
+import { IntegrationData } from '@site/src/components/integrations/data';
+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 { linuxServerIoIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={linuxServerIoIntegration}
+    categories={['Container Management', 'Software']}
+/>
+
+### Data
+
+<IntegrationData integration={linuxServerIoIntegration} />
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}]} />
@@ -0,0 +1,9 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const linuxServerIoIntegration: IntegrationDefinition = {
+  name: "LinuxServer.io",
+  description: "LinuxServer.io is a platform for managing and deploying containerized applications.",
+  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons@master/svg/linuxserver-io.svg",
+  path: "../../integrations/linux-server-io",
+  data: "Fetches Docker image versions and changelogs from LinuxServer.io.",
+};
@@ -4,6 +4,7 @@ description: "Navidrome is a self-hosted music server and streamer compatible wi
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -19,6 +20,10 @@ import { audioStatsWidget } from '@site/docs/widgets/audio-stats';

 Navidrome provides music library statistics including artist, album, and song counts, as well as now playing information via the Subsonic API.

+### Data
+
+<IntegrationData integration={navidromeIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[
@@ -5,4 +5,5 @@ export const navidromeIntegration: IntegrationDefinition = {
  description: "Navidrome is a self-hosted music server and streamer compatible with the Subsonic API.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/navidrome.svg",
  path: "../../integrations/navidrome",
+  data: "Fetches library statistics and currently playing tracks from a Navidrome music server.",
 };
@@ -4,6 +4,7 @@ description: "Nextcloud is a self-hosted productivity platform that provides fil
 hide_title: true
 ---

+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
@@ -19,6 +20,10 @@ import { notificationsWidget } from '@site/docs/widgets/notifications';
  categories={['Calendar', 'Notifications']}
 />

+### Data
+
+<IntegrationData integration={nextcloudIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[
@@ -6,4 +6,5 @@ export const nextcloudIntegration: IntegrationDefinition = {
    "Nextcloud is a self-hosted productivity platform that provides file storage, collaboration tools, and more.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/nextcloud.svg",
  path: "../../integrations/nextcloud",
+  data: "Fetches calendar events and notifications from a Nextcloud instance.",
 };
@@ -0,0 +1,39 @@
+---
+title: 'NPM'
+description: "NPM is a package manager for the JavaScript programming language, primarily used for managing Node.js packages."
+hide_title: true
+---
+
+import { IntegrationData } from '@site/src/components/integrations/data';
+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 { npmIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={npmIntegration}
+    categories={['Package Management', 'Software']}
+/>
+
+### Data
+
+<IntegrationData integration={npmIntegration} />
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}]} />
@@ -0,0 +1,10 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const npmIntegration: IntegrationDefinition = {
+  name: "NPM",
+  description:
+    "NPM is a package manager for the JavaScript programming language, primarily used for managing Node.js packages.",
+  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/npm.svg",
+  path: "../../integrations/npm",
+  data: "Fetches the latest npm package version and metadata from the npm registry.",
+};
@@ -6,6 +6,7 @@ hide_title: true

 import { notificationsWidget } from '@site/docs/widgets/notifications';
 import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationData } from '@site/src/components/integrations/data';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
 import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
@@ -17,6 +18,10 @@ import { ntfyIntegration } from '.';
    categories={['Notifications', 'Messaging']}
 />

+### Data
+
+<IntegrationData integration={ntfyIntegration} />
+
 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[{
@@ -6,4 +6,5 @@ export const ntfyIntegration: IntegrationDefinition = {
    "Ntfy is a simple, open-source notification service that allows you to send and receive notifications across devices.",
  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/ntfy.svg",
  path: "../../integrations/ntfy",
+  data: "Fetches recent push notifications from an ntfy.sh topic.",
 };