Merge branch 'dev'

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>

.codecov.yml

@@ -0,0 +1,21 @@
+codecov:
+  require_ci_to_pass: true
+
+coverage:
+  precision: 2
+  round: down
+  range: "0...100"
+  status:
+    project:
+      default:
+        target: 100%
+        threshold: 15%
+    patch:
+      default:
+        target: 100%
+        threshold: 10%
+
+comment:
+  layout: "reach,diff,flags,files"
+  behavior: default
+  require_changes: false

.dockerignore

@@ -16,11 +16,11 @@
 **/compose*
 **/Dockerfile*
 **/node_modules
+!.next/standalone/node_modules
 **/npm-debug.log
 **/obj
 **/secrets.dev.yaml
 **/values.dev.yaml
-**/.next
 README.md
 config/
 k3d/

.eslintrc.json

@@ -1,42 +0,0 @@
-{
-  "extends": [
-    "next/core-web-vitals",
-    "prettier",
-    "plugin:react-hooks/recommended"
-  ],
-  "plugins": ["prettier"],
-  "rules": {
-    "import/no-cycle": [
-      "error",
-      {
-        "maxDepth": 1
-      }
-    ],
-    "import/order": [
-      "error",
-      {
-        "newlines-between": "always"
-      }
-    ],
-    "no-else-return": [
-      "error",
-      {
-        "allowElseIf": true
-      }
-    ]
-  },
-  "settings": {
-    "import/resolver": {
-      "node": {
-        "paths": ["src"]
-      }
-    }
-  },
-  "parserOptions": {
-    "ecmaVersion": 6,
-    "sourceType": "module",
-    "ecmaFeatures": {
-      "modules": true
-    }
-  }
-}

.github/DISCUSSION_TEMPLATE/feature-requests.yml

@@ -1,6 +1,10 @@
 title: "[Feature Request] "
 labels: ["enhancement"]
 body:
+  - type: markdown
+    attributes:
+      value: |
+        #### ⚠️ Don't forget to search [existing issues](https://github.com/gethomepage/homepage/search?q=&type=issues) and [discussions](https://github.com/gethomepage/homepage/search?q=&type=discussions) (including closed ones!).
   - type: textarea
     id: description
     attributes:

.github/DISCUSSION_TEMPLATE/support.yml

@@ -4,7 +4,7 @@ body:
       value: |
         ### ⚠️ Before opening a discussion:
 
-        - [Check the troubleshooting guide](https://gethomepage.dev/troubleshooting/).
+        - [Check the troubleshooting guide](https://gethomepage.dev/troubleshooting/) and include the output of all steps below.
         - [Search existing issues](https://github.com/gethomepage/homepage/search?q=&type=issues) [and discussions](https://github.com/gethomepage/homepage/search?q=&type=discussions) (including closed ones!).
   - type: textarea
     id: description
@@ -51,7 +51,7 @@ body:
     id: troubleshooting
     attributes:
       label: Troubleshooting
-      description: Please include output from your [troubleshooting steps](https://gethomepage.dev/more/troubleshooting/#service-widget-errors), if relevant.
+      description: Please include output from your [troubleshooting steps](https://gethomepage.dev/troubleshooting/#service-widget-errors), if relevant.
     validations:
       required: true
   - type: markdown
@@ -59,6 +59,6 @@ body:
       value: |
         ## ⚠️ STOP ⚠️
 
-        Before you submit this support request, please ensure you have entered your configuration files and actually followed the steps from the troubleshooting guide linked above, if relevant. The troubleshooting steps often help to solve the problem.
+        Before you submit this support request, please ensure you have entered your configuration files and actually followed the steps from the troubleshooting guide linked above *and posted the output*, if relevant. The troubleshooting steps often help to solve the problem or at least can help figure it out.
 
         *Please remember that this project is maintained by regular people **just like you**, so if you don't take the time to fill out the requested information, don't expect a reply back.*

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -15,7 +15,7 @@ body:
       options:
         - label: I confirm this was discussed, and the maintainers asked that I open an issue.
           required: true
-        - label: I am aware that if I create this issue without a discussion, it will be removed without a response.
+        - label: I am aware that if I create this issue without a discussion, it will be closed without a response.
           required: true
   - type: input
     id: discussion

.github/PULL_REQUEST_TEMPLATE.md

@@ -35,6 +35,8 @@ What type of change does your PR introduce to Homepage?
 ## Checklist:
 
 - [ ] If applicable, I have added corresponding documentation changes.
-- [ ] If applicable, I have reviewed the [feature / enhancement](https://gethomepage.dev/more/development/#new-feature-guidelines) and / or [service widget guidelines](https://gethomepage.dev/more/development/#service-widget-guidelines).
-- [ ] I have checked that all code style checks pass using [pre-commit hooks](https://gethomepage.dev/more/development/#code-formatting-with-pre-commit-hooks) and [linting checks](https://gethomepage.dev/more/development/#code-linting).
+- [ ] If applicable, I have added or updated tests for new features and bug fixes (see [testing](https://gethomepage.dev/widgets/authoring/getting-started/#testing)).
+- [ ] If applicable, I have reviewed the [feature / enhancement](https://gethomepage.dev/widgets/authoring/getting-started/#new-feature-guidelines) and / or [service widget guidelines](https://gethomepage.dev/widgets/authoring/getting-started/#service-widget-guidelines).
+- [ ] I have checked that all code style checks pass using [pre-commit hooks](https://gethomepage.dev/widgets/authoring/getting-started/#code-formatting-with-pre-commit-hooks) and [linting checks](https://gethomepage.dev/widgets/authoring/getting-started/#code-linting).
 - [ ] If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
+- [ ] In the description above I have disclosed the use of AI tools in the coding of this PR.

.github/dependabot.yml

@@ -8,8 +8,12 @@ updates:
   - package-ecosystem: "github-actions"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
+    cooldown:
+      default-days: 7
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
       interval: "monthly"
+    cooldown:
+      default-days: 7

.github/release-drafter.yml

@@ -0,0 +1,87 @@
+name-template: 'v$RESOLVED_VERSION'
+tag-template: 'v$RESOLVED_VERSION'
+change-template: '- $TITLE (#$NUMBER) @$AUTHOR'
+change-title-escapes: '\\<*_&'
+
+version-resolver:
+  major:
+    labels:
+      - 'major'
+      - 'breaking-change'
+  minor:
+    labels:
+      - 'enhancement'
+      - 'feature'
+  patch:
+    labels:
+      - 'bug'
+      - 'fix'
+      - 'dependencies'
+      - 'translation'
+      - 'documentation'
+  default: patch
+
+categories:
+  - title: '⚠️ Breaking Changes'
+    labels:
+      - 'major'
+      - 'breaking-change'
+  - title: '🚀 Features'
+    labels:
+      - 'enhancement'
+      - 'feature'
+  - title: '🐛 Fixes'
+    labels:
+      - 'bug'
+      - 'fix'
+  - title: '🧰 Maintenance'
+    labels:
+      - 'dependencies'
+      - 'ci'
+      - 'chore'
+  - title: '🌐 Translations'
+    labels:
+      - 'translation'
+  - title: '📚 Documentation'
+    labels:
+      - 'documentation'
+
+autolabeler:
+  - label: 'documentation'
+    files:
+      - 'docs/**'
+      - '*.md'
+      - '.github/**/*.md'
+
+  - label: 'ci'
+    files:
+      - '.github/workflows/**'
+
+  - label: 'dependencies'
+    files:
+      - 'package.json'
+      - 'pnpm-lock.yaml'
+      - 'pyproject.toml'
+      - 'uv.lock'
+
+  - label: 'feature'
+    files:
+      - 'src/components/**'
+      - 'src/widgets/**'
+      - 'src/pages/**'
+      - 'src/utils/**'
+
+  - label: 'chore'
+    files:
+      - 'Dockerfile*'
+      - 'docker-entrypoint.sh'
+      - 'k3d/**'
+
+  - label: 'translation'
+    files:
+      - 'public/locales/**'
+
+template: |
+  ## What's Changed
+
+  $CHANGES

.github/workflows/crowdin.yml

@@ -17,14 +17,15 @@ jobs:
 
     steps:
     - name: Checkout
-      uses: actions/checkout@v4
+      uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
     - name: crowdin action
-      uses: crowdin/github-action@v2
+      uses: crowdin/github-action@8868a33591d21088edfc398968173a3b98d51706 # v2
       with:
         upload_translations: false
         download_translations: true
         crowdin_branch_name: dev
         localization_branch_name: l10n_dev
+        pull_request_labels: translation
       env:
         GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID }}

.github/workflows/docker-publish.yml

@@ -1,9 +1,4 @@
-name: Docker
-
-# This workflow uses actions that are not certified by GitHub.
-# They are provided by a third-party and are governed by
-# separate terms of service, privacy policy, and support
-# documentation.
+name: Docker CI
 
 on:
   schedule:
@@ -12,136 +7,121 @@ on:
     branches:
       - main
       - feature/**
+      - fix/**
       - dev
-    # Publish semver tags as releases.
     tags: [ 'v*.*.*' ]
-    paths-ignore:
-      - 'docs/**'
-      - 'mkdocs.yml'
   pull_request:
     branches: [ "dev" ]
-    paths-ignore:
-      - 'docs/**'
-      - 'mkdocs.yml'
   merge_group:
 
 env:
-  # github.repository as <account>/<repo>
   IMAGE_NAME: ${{ github.repository }}
 
-
 jobs:
-  pre-commit:
-    name: Linting Checks
-    runs-on: ubuntu-22.04
-    steps:
-      -
-        name: Checkout repository
-        uses: actions/checkout@v4
-      -
-        name: Install python
-        uses: actions/setup-python@v5
-        with:
-          python-version: 3.x
-      -
-        name: Check files
-        uses: pre-commit/action@v3.0.1
-      -
-        name: Install pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 10
-          run_install: false
-      -
-        name: Install Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: 'pnpm'
-      -
-        name: Install dependencies
-        run: pnpm install
-      -
-        name: Lint frontend
-        run: pnpm run lint
+
 
   build:
     name: Docker Build & Push
-    if:  github.repository == 'gethomepage/homepage'
-    runs-on: self-hosted
-    needs:
-      - pre-commit
+    if: github.repository == 'gethomepage/homepage'
+    runs-on: ubuntu-22.04
     permissions:
       contents: read
       packages: write
-      # This is used to complete the identity challenge
-      # with sigstore/fulcio when running outside of PRs.
       id-token: write
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
 
-      # Login to Docker Registry
-      # https://github.com/docker/login-action
-      - name: Log into registry ${{ env.REGISTRY }}
-        if: github.event_name != 'pull_request'
-        uses: docker/login-action@v3
-        with:
-          registry: ghcr.io
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-      - name: Login to Docker Hub
-        if: github.event_name != 'pull_request'
-        uses: docker/login-action@v3
-        with:
-          username: ${{ secrets.DOCKERHUB_USERNAME }}
-          password: ${{ secrets.DOCKERHUB_TOKEN }}
-
-      # Setup QEMU
-      # https://github.com/marketplace/actions/docker-setup-buildx#with-qemu
-      - name: Setup QEMU
-        uses: docker/setup-qemu-action@v3.6.0
-
-      # Workaround: https://github.com/docker/build-push-action/issues/461
-      - name: Setup Docker buildx
-        uses: docker/setup-buildx-action@v3
-
-      # Extract metadata (tags, labels) for Docker
-      # https://github.com/docker/metadata-action
       - name: Extract Docker metadata
         id: meta
-        uses: docker/metadata-action@v5
+        uses: docker/metadata-action@030e881283bb7a6894de51c315a6bfe6a94e05cf # v6
         with:
           images: |
             ${{ env.IMAGE_NAME }}
             ghcr.io/${{ env.IMAGE_NAME }}
+          tags: |
+            # Default tags
+            type=schedule,pattern=nightly
+            type=ref,event=branch
+            type=ref,event=tag
+            # Versioning tags
+            type=semver,pattern=v{{version}}
+            type=semver,pattern=v{{major}}.{{minor}}
+            type=semver,pattern=v{{major}}
           flavor: |
             latest=auto
 
-      # Build and push Docker image with Buildx (don't push on PR)
-      # https://github.com/docker/build-push-action
+      - name: Next.js build cache
+        uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5
+        with:
+          path: .next/cache
+          key: nextjs-${{ runner.os }}-${{ hashFiles('pnpm-lock.yaml') }}-${{ hashFiles('**/*.js', '**/*.jsx') }}
+          restore-keys: |
+            nextjs-${{ runner.os }}-${{ hashFiles('pnpm-lock.yaml') }}
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@26f6d4f2c533a43e6b5da0b4a5dd983f98f7b49a # v6.0.4
+        with:
+          version: 10
+          run_install: false
+
+      - name: Setup Node.js
+        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6
+        with:
+          node-version: 24
+          cache: 'pnpm'
+
+      - name: Install dependencies
+        run: pnpm install
+
+      - name: Build app
+        run: |
+          NEXT_PUBLIC_BUILDTIME="${{ fromJSON(steps.meta.outputs.json).labels['org.opencontainers.image.created'] }}" \
+          NEXT_PUBLIC_VERSION="${{ fromJSON(steps.meta.outputs.json).labels['org.opencontainers.image.version'] }}" \
+          NEXT_PUBLIC_REVISION="${{ fromJSON(steps.meta.outputs.json).labels['org.opencontainers.image.revision'] }}" \
+          pnpm run build
+
+      - name: Log into registry ${{ env.REGISTRY }}
+        if: github.event_name != 'pull_request'
+        uses: docker/login-action@4907a6ddec9925e35a0a9e82d7399ccc52663121 # v4
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Login to Docker Hub
+        if: github.event_name != 'pull_request'
+        uses: docker/login-action@4907a6ddec9925e35a0a9e82d7399ccc52663121 # v4
+        with:
+          username: ${{ secrets.DOCKERHUB_USERNAME }}
+          password: ${{ secrets.DOCKERHUB_TOKEN }}
+
+      - name: Setup QEMU
+        uses: docker/setup-qemu-action@ce360397dd3f832beb865e1373c09c0e9f86d70a # v4.0.0
+
+      - name: Setup Docker buildx
+        uses: docker/setup-buildx-action@4d04d5d9486b7bd6fa91e7baf45bbb4f8b9deedd # v4
+
       - name: Build and push Docker image
         id: build-and-push
-        uses: docker/build-push-action@v6
+        uses: docker/build-push-action@bcafcacb16a39f128d818304e6c9c0c18556b85f # v7
         with:
           context: .
           push: ${{ github.event_name != 'pull_request' }}
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}
           build-args: |
+            CI=true
             BUILDTIME=${{ fromJSON(steps.meta.outputs.json).labels['org.opencontainers.image.created'] }}
             VERSION=${{ fromJSON(steps.meta.outputs.json).labels['org.opencontainers.image.version'] }}
             REVISION=${{ fromJSON(steps.meta.outputs.json).labels['org.opencontainers.image.revision'] }}
-          # https://github.com/docker/setup-qemu-action#about
-          # platforms: linux/amd64,linux/arm64,linux/riscv64,linux/ppc64le,linux/s390x,linux/386,linux/mips64le,linux/mips64,linux/arm/v7,linux/arm/v6
           platforms: linux/amd64,linux/arm64
+          provenance: false
           cache-from: type=local,src=/tmp/.buildx-cache
           cache-to: type=local,dest=/tmp/.buildx-cache-new,mode=max
 
-      # Temp fix
-      # https://github.com/docker/build-push-action/issues/252
-      # https://github.com/moby/buildkit/issues/1896
+      # https://github.com/docker/build-push-action/issues/252 / https://github.com/moby/buildkit/issues/1896
       - name: Move cache
         run: |
           rm -rf /tmp/.buildx-cache

.github/workflows/docs-publish.yml

@@ -4,81 +4,51 @@ on:
   push:
     tags: ["v*.*.*"]
     branches: ["main"]
-    paths:
-      - "docs/**"
-      - "mkdocs.yml"
   pull_request:
-    paths:
-      - "docs/**"
-      - "mkdocs.yml"
   merge_group:
   workflow_dispatch:
 
 permissions:
-  contents: write
+  contents: read
+  pages: write
+  id-token: write
 
 jobs:
-  pre-commit:
-    name: Linting Checks
-    runs-on: ubuntu-22.04
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-      - name: Install python
-        uses: actions/setup-python@v5
-        with:
-          python-version: 3.x
-      - name: Check files
-        uses: pre-commit/action@v3.0.1
 
   test:
-    name: Test Build
+    name: Test Build Docs
     if: github.repository == 'gethomepage/homepage' && github.event_name == 'pull_request'
     runs-on: ubuntu-latest
-    needs:
-      - pre-commit
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-python@v5
+      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+      - uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6
         with:
-          python-version: 3.x
-      - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV
-      - uses: actions/cache@v4
-        with:
-          key: mkdocs-material-${{ env.cache_id }}
-          path: .cache
-          restore-keys: |
-            mkdocs-material-
+          python-version-file: ".python-version"
+      - name: Install uv
+        uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
       - run: sudo apt-get install pngquant
-      - run: pip install mkdocs-material mkdocs-redirects "mkdocs-material[imaging]"
       - name: Test Docs Build
-        run: MKINSIDERS=false mkdocs build
+        run: uv run --frozen zensical build --clean
   deploy:
-    name: Build & Deploy
-    if: github.repository == 'gethomepage/homepage' && github.event_name != 'pull_request'
+    name: Build & Deploy Docs
+    if: github.repository == 'gethomepage/homepage' && github.event_name != 'pull_request' && github.ref == 'refs/heads/main'
     runs-on: ubuntu-latest
-    needs:
-      - pre-commit
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
     steps:
-      - uses: actions/checkout@v4
-      - name: Configure Git Credentials
-        run: |
-          git config user.name github-actions[bot]
-          git config user.email 41898282+github-actions[bot]@users.noreply.github.com
-      - uses: actions/setup-python@v5
+      - uses: actions/configure-pages@45bfe0192ca1faeb007ade9deae92b16b8254a0d # v6.0.0
+      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+      - uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6
         with:
-          python-version: 3.x
-      - run: echo "cache_id=${{github.sha}}" >> $GITHUB_ENV
-      - uses: actions/cache@v4
-        with:
-          key: mkdocs-material-${{ env.cache_id }}
-          path: .cache
-          restore-keys: |
-            mkdocs-material-
+          python-version-file: ".python-version"
+      - name: Install uv
+        uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
       - run: sudo apt-get install pngquant
-      - run: pip install git+https://${GH_TOKEN}@github.com/benphelps/mkdocs-material-insiders.git
-      - run: pip install mkdocs-redirects "mkdocs-material[imaging]"
-      - name: Docs Deploy
-        run: MKINSIDERS=true mkdocs gh-deploy --force
-env:
-  GH_TOKEN: ${{ secrets.GH_TOKEN }}
+      - name: Build Docs
+        run: uv run --frozen zensical build --clean
+      - uses: actions/upload-pages-artifact@fc324d3547104276b827a68afc52ff2a11cc49c9 # v5.0.0
+        with:
+          path: site
+      - uses: actions/deploy-pages@cd2ce8fcbc39b97be8ca5fce6e763baed58fa128 # v5.0.0
+        id: deployment

.github/workflows/lint.yml

@@ -0,0 +1,41 @@
+name: Lint
+
+on:
+  pull_request:
+  push:
+  workflow_dispatch:
+  merge_group:
+
+jobs:
+  lint:
+    name: Linting Checks
+    runs-on: ubuntu-22.04
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+
+      - name: Install python
+        uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6
+        with:
+          python-version: 3.x
+
+      - name: Check files
+        uses: pre-commit/action@2c7b3805fd2a0fd8c1884dcaebf91fc102a13ecd # v3.0.1
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@26f6d4f2c533a43e6b5da0b4a5dd983f98f7b49a # v6.0.4
+        with:
+          version: 10
+          run_install: false
+
+      - name: Setup Node.js
+        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6
+        with:
+          node-version: 24
+          cache: 'pnpm'
+
+      - name: Install dependencies
+        run: pnpm install
+
+      - name: Lint frontend
+        run: pnpm run lint

.github/workflows/pr-quality.yml

@@ -0,0 +1,18 @@
+name: PR Quality
+
+permissions:
+  contents: read
+  issues: read
+  pull-requests: write
+
+on:
+  pull_request_target:
+    types: [opened, reopened]
+
+jobs:
+  anti-slop:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: peakoss/anti-slop@57858eead489d08b255fab2af45a506c2ca6eab2 # v0
+        with:
+          max-failures: 4

.github/workflows/reaction-comments.yml

@@ -15,4 +15,4 @@ jobs:
   action:
     runs-on: ubuntu-latest
     steps:
-      - uses: dessant/reaction-comments@v4
+      - uses: dessant/reaction-comments@e86d247c12bd5c043eec379a1a4453f20cadf913 # v4

.github/workflows/release-drafter.yml

@@ -0,0 +1,54 @@
+name: Release Drafter
+
+on:
+  push:
+    branches:
+      - dev
+  pull_request_target:
+    types: [opened, reopened, synchronize]
+  workflow_dispatch:
+    inputs:
+      version:
+        description: "Optional explicit version override (for example: 2.0.0)"
+        required: false
+        type: string
+
+permissions:
+  contents: read
+
+jobs:
+  update_release_draft:
+    name: Update Release Draft
+    if: github.event_name == 'push' || github.event_name == 'workflow_dispatch'
+    permissions:
+      contents: write
+      pull-requests: read
+    runs-on: ubuntu-latest
+    steps:
+      - if: github.event_name == 'workflow_dispatch' && github.event.inputs.version != ''
+        uses: release-drafter/release-drafter@563bf132657a13ded0b01fcb723c5a58cdd824e2 # v7
+        with:
+          config-name: release-drafter.yml
+          version: ${{ github.event.inputs.version }}
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - if: github.event_name != 'workflow_dispatch' || github.event.inputs.version == ''
+        uses: release-drafter/release-drafter@563bf132657a13ded0b01fcb723c5a58cdd824e2 # v7
+        with:
+          config-name: release-drafter.yml
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+  auto_label:
+    name: Auto Label PR
+    if: github.event_name == 'pull_request_target'
+    permissions:
+      contents: read
+      pull-requests: write
+    runs-on: ubuntu-latest
+    steps:
+      - uses: release-drafter/release-drafter/autolabeler@563bf132657a13ded0b01fcb723c5a58cdd824e2
+        with:
+          config-name: release-drafter.yml
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/repo-maintenance.yml

@@ -18,7 +18,7 @@ jobs:
     name: 'Stale'
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/stale@v9
+      - uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f # v10
         with:
           days-before-stale: 7
           days-before-close: 14
@@ -32,7 +32,7 @@ jobs:
     name: 'Lock Old Threads'
     runs-on: ubuntu-latest
     steps:
-      - uses: dessant/lock-threads@v5
+      - uses: dessant/lock-threads@7266a7ce5c1df01b1c6db85bf8cd86c737dadbe7 # v6
         with:
           issue-inactive-days: '30'
           pr-inactive-days: '30'
@@ -57,7 +57,7 @@ jobs:
     name: 'Close Answered Discussions'
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v7
+      - uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
         with:
           script: |
             function sleep(ms) {
@@ -113,7 +113,7 @@ jobs:
     name: 'Close Outdated Discussions'
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v7
+      - uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
         with:
           script: |
             function sleep(ms) {
@@ -204,7 +204,7 @@ jobs:
     name: 'Close Unsupported Feature Requests'
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v7
+      - uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
         with:
           script: |
             function sleep(ms) {
@@ -212,9 +212,9 @@ jobs:
             }
 
             const CUTOFF_1_DAYS = 180;
-            const CUTOFF_1_COUNT = 10;
+            const CUTOFF_1_COUNT = 20;
             const CUTOFF_2_DAYS = 365;
-            const CUTOFF_2_COUNT = 20;
+            const CUTOFF_2_COUNT = 40;
 
             const cutoff1Date = new Date();
             cutoff1Date.setDate(cutoff1Date.getDate() - CUTOFF_1_DAYS);

.github/workflows/test.yml

@@ -0,0 +1,37 @@
+name: Tests
+
+on:
+  pull_request:
+  push:
+  workflow_dispatch:
+
+jobs:
+  vitest:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        shard: [1, 2, 3, 4]
+    steps:
+      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+
+      - uses: pnpm/action-setup@26f6d4f2c533a43e6b5da0b4a5dd983f98f7b49a # v6.0.4
+        with:
+          version: 9
+
+      - uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6
+        with:
+          node-version: 20
+          cache: pnpm
+
+      - run: pnpm install --frozen-lockfile
+      # Run Vitest directly so `--shard` is parsed as an option
+      - run: pnpm -s exec vitest run --coverage --shard ${{ matrix.shard }}/4 --pool forks
+      - name: Upload coverage reports to Codecov
+        uses: codecov/codecov-action@57e3a136b779b570ffcdbf80b3bdc90e7fab3de2 # v6.0.0
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}
+          files: ./coverage/lcov.info
+          flags: vitest,shard-${{ matrix.shard }}
+          name: vitest-shard-${{ matrix.shard }}
+          fail_ci_if_error: true

.gitignore

@@ -46,7 +46,7 @@ next-env.d.ts
 # IDEs
 /.idea/
 
-# MkDocs documentation
+# Zensical documentation
 site*/
 .cache/
 

.pre-commit-config.yaml

@@ -9,11 +9,14 @@ repos:
     -   id: check-yaml
         exclude: "(^mkdocs\\.yml$)"
     -   id: check-added-large-files
--   repo: https://github.com/pre-commit/mirrors-prettier
-    rev: 'v3.0.3'
+-   repo: https://github.com/rbubley/mirrors-prettier
+    rev: 'v3.3.3'
     hooks:
     -   id: prettier
         types_or:
           - javascript
           - markdown
           - jsx
+        additional_dependencies:
+          - prettier@3.3.3
+          - 'prettier-plugin-organize-imports@4.1.0'

.prettierrc

@@ -1 +0,0 @@
-{}

.prettierrc.js

@@ -0,0 +1,5 @@
+const config = {
+  plugins: [require("prettier-plugin-organize-imports")],
+};
+
+module.exports = config;

.python-version

@@ -0,0 +1 @@
+3.13

.vscode/launch.json

@@ -1,19 +1,32 @@
 {
-  // Use IntelliSense to learn about possible attributes.
-  // Hover to view descriptions of existing attributes.
-  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
-  "version": "0.2.0",
   "configurations": [
     {
-      "name": "Next.js: debug full stack",
+      "name": "Debug homepage",
       "type": "node",
+      "preLaunchTask": "pnpm install",
       "request": "launch",
-      "runtimeExecutable": "${workspaceFolder}/node_modules/.bin/next",
-      "serverReadyAction": {
-        "pattern": "started server on .+, url: (https?://.+)",
-        "uriFormat": "%s",
-        "action": "debugWithChrome"
+      "runtimeExecutable": "pnpm",
+      "runtimeArgs": ["run", "dev"],
+      "env": {
+        "LOG_LEVEL": "debug"
+      },
+      "skipFiles": ["<node_internals>/**"],
+      "console": "integratedTerminal",
+      "serverReadyAction":{
+        "pattern": ".*http://localhost:3000.*",
+        "action": "startDebugging",
+        "name": "Launch Chromium",
+        "killOnServerStop": true,
       }
+    },
+    {
+      "name": "Launch Chromium",
+      "type": "chrome",
+      "request": "launch",
+      "url": "http://localhost:3000",
+      "urlFilter": "http://localhost:3000",
+      "webRoot": "${workspaceFolder}",
+      "trace": true
     }
   ]
 }

.vscode/tasks.json

@@ -0,0 +1,21 @@
+{
+	"version": "2.0.0",
+	"tasks": [
+		{
+			"type": "shell",
+			"label": "pnpm install",
+            "command": "pnpm install",
+            "group": {
+                "kind": "build",
+                "isDefault": true
+            },
+            "presentation": {
+                "clear": true,
+                "panel": "shared",
+                "showReuseMessage": false
+            },
+            "problemMatcher": []
+
+		}
+	]
+}

CONTRIBUTING.md

@@ -38,11 +38,11 @@ People _love_ thorough bug reports. I'm not even kidding.
 
 ## Development Guidelines
 
-Please see the [documentation regarding development](https://gethomepage.dev/more/development/) and specifically the [guidelines for new service widgets](https://gethomepage.dev/more/development/#service-widget-guidelines) if you are considering making one.
+Please see the [documentation regarding development](https://gethomepage.dev/widgets/authoring/getting-started/#development) and specifically the [guidelines for new service widgets](https://gethomepage.dev/widgets/authoring/getting-started/#service-widget-guidelines) if you are considering making one.
 
 ## Use a Consistent Coding Style
 
-Please see information in the docs regarding [code formatting with pre-commit hooks](https://gethomepage.dev/more/development/#code-formatting-with-pre-commit-hooks).
+Please see information in the docs regarding [code formatting with pre-commit hooks](https://gethomepage.dev/widgets/authoring/getting-started/#code-formatting-with-pre-commit-hooks).
 
 ## License
 
@@ -63,7 +63,7 @@ The homepage team appreciates all effort and interest from the community in fili
 - Issues, pull requests and discussions that are closed will be locked after 30 days of inactivity.
 - Discussions with a marked answer will be automatically closed.
 - Discussions in the 'General' or 'Support' categories will be closed after 180 days of inactivity.
-- Feature requests that do not meet the following thresholds will be closed: 10 "up-votes" after 180 days of inactivity or 20 "up-votes" after 365 days.
+- Feature requests that do not meet the following thresholds will be closed: 20 "up-votes" after 180 days of inactivity or 40 "up-votes" after 365 days.
 
 In all cases, threads can be re-opened by project maintainers and, of course, users can always create a new discussion for related concerns.
 Finally, remember that all information remains searchable and 'closed' feature requests can still serve as inspiration for new features.

Dockerfile

@@ -1,67 +1,65 @@
-# Install dependencies only when needed
-FROM docker.io/node:22-alpine AS deps
-
-WORKDIR /app
-
-COPY --link package.json pnpm-lock.yaml* ./
-
-SHELL ["/bin/ash", "-xeo", "pipefail", "-c"]
-RUN apk add --no-cache libc6-compat \
- && apk add --no-cache --virtual .gyp python3 make g++ \
- && npm install -g pnpm
-
-RUN --mount=type=cache,id=pnpm-store,target=/root/.local/share/pnpm/store pnpm fetch | grep -v "cross-device link not permitted\|Falling back to copying packages from store"
-
-RUN --mount=type=cache,id=pnpm-store,target=/root/.local/share/pnpm/store pnpm install -r --offline
-
-# Rebuild the source code only when needed
-FROM docker.io/node:22-alpine AS builder
+# =========================
+# Builder Stage
+# =========================
+FROM node:22-slim AS builder
 WORKDIR /app
 
+# Setup
 RUN mkdir config
+COPY . .
 
+ARG CI
 ARG BUILDTIME
 ARG VERSION
 ARG REVISION
+ENV CI=$CI
 
-COPY --link --from=deps /app/node_modules ./node_modules/
-COPY . .
+# Install and build only outside CI
+RUN if [ "$CI" != "true" ]; then \
+      corepack enable && corepack prepare pnpm@latest --activate && \
+      pnpm install --frozen-lockfile --prefer-offline && \
+      NEXT_TELEMETRY_DISABLED=1 \
+      NEXT_PUBLIC_BUILDTIME=$BUILDTIME \
+      NEXT_PUBLIC_VERSION=$VERSION \
+      NEXT_PUBLIC_REVISION=$REVISION \
+      pnpm run build; \
+    else \
+      echo "✅ Using prebuilt app from CI context"; \
+    fi
 
-SHELL ["/bin/ash", "-xeo", "pipefail", "-c"]
-RUN npm install -g pnpm \
- && pnpm run telemetry \
- && NEXT_PUBLIC_BUILDTIME=$BUILDTIME NEXT_PUBLIC_VERSION=$VERSION NEXT_PUBLIC_REVISION=$REVISION pnpm run build
-
-# Production image, copy all the files and run next
-FROM docker.io/node:22-alpine AS runner
-LABEL org.opencontainers.image.title "Homepage"
-LABEL org.opencontainers.image.description "A self-hosted services landing page, with docker and service integrations."
+# =========================
+# Runtime Stage
+# =========================
+FROM node:22-alpine AS runner
+LABEL org.opencontainers.image.title="Homepage"
+LABEL org.opencontainers.image.description="A self-hosted services landing page, with docker and service integrations."
 LABEL org.opencontainers.image.url="https://github.com/gethomepage/homepage"
 LABEL org.opencontainers.image.documentation='https://github.com/gethomepage/homepage/wiki'
 LABEL org.opencontainers.image.source='https://github.com/gethomepage/homepage'
 LABEL org.opencontainers.image.licenses='Apache-2.0'
 
-ENV NODE_ENV=production
-
+# Setup
 WORKDIR /app
 
-# Copy files from context (this allows the files to copy before the builder stage is done).
-COPY --link --chown=1000:1000 package.json next.config.js ./
+# Copy some files from context
 COPY --link --chown=1000:1000 /public ./public/
-
-# Copy files from builder
-COPY --link --from=builder --chown=1000:1000 /app/.next/standalone ./
-COPY --link --from=builder --chown=1000:1000 /app/.next/static/ ./.next/static/
 COPY --link --chmod=755 docker-entrypoint.sh /usr/local/bin/
 
-RUN apk add --no-cache su-exec
+# Copy only necessary files from the build stage
+COPY --link --from=builder --chown=1000:1000 /app/.next/standalone/ ./
+COPY --link --from=builder --chown=1000:1000 /app/.next/static/ ./.next/static
 
-ENV HOSTNAME=0.0.0.0
+RUN apk add --no-cache su-exec iputils-ping shadow
+
+USER root
+
+ENV NODE_ENV=production
+ENV HOSTNAME=::
 ENV PORT=3000
 EXPOSE $PORT
 
 HEALTHCHECK --interval=10s --timeout=3s --start-period=20s \
-  CMD wget --no-verbose --tries=1 --spider --no-check-certificate http://127.0.0.1:$PORT/api/healthcheck || exit 1
+  CMD wget --no-verbose --tries=1 --spider http://127.0.0.1:$PORT/api/healthcheck || exit 1
 
 ENTRYPOINT ["docker-entrypoint.sh"]
 CMD ["node", "server.js"]

README.md

@@ -16,6 +16,8 @@
 <p align="center">
   <a href="https://github.com/gethomepage/homepage/actions/workflows/docker-publish.yml"><img alt="GitHub Workflow Status (with event)" src="https://img.shields.io/github/actions/workflow/status/gethomepage/homepage/docker-publish.yml"></a>
   &nbsp;
+  <a href="https://codecov.io/gh/gethomepage/homepage"><img src="https://codecov.io/gh/gethomepage/homepage/graph/badge.svg?token=7SKFL4D9K7"/></a>
+  &nbsp;
   <a href="https://crowdin.com/project/gethomepage" target="_blank"><img src="https://badges.crowdin.net/gethomepage/localized.svg"></a>
   &nbsp;
   <a href="https://discord.gg/k4ruYNrudu"><img alt="Discord" src="https://img.shields.io/discord/1019316731635834932"></a>
@@ -25,13 +27,6 @@
   <a href="https://paypal.me/phelpsben" title="Donate"><img alt="GitHub Sponsors" src="https://img.shields.io/github/sponsors/benphelps"></a>
 </p>
 
-<p align="center">
-  <a href="https://www.digitalocean.com/?refcode=df14bcb7c016&utm_campaign=Referral_Invite&utm_medium=Referral_Program&utm_source=badge"><img src="https://web-platforms.sfo2.cdn.digitaloceanspaces.com/WWW/Badge%201.svg" alt="DigitalOcean Referral Badge" /></a>
-</p>
-<p align="center">
-<em>Homepage builds are kindly powered by DigitalOcean.</em>
-</p>
-
 # Features
 
 With features like quick search, bookmarks, weather support, a wide range of integrations and widgets, an elegant and modern design, and a focus on performance, Homepage is your ideal start to the day and a handy companion throughout it.
@@ -68,7 +63,7 @@ For configuration options, examples and more, [please check out the homepage doc
 
 ## Security Notice 🔒
 
-Please note that when using features such as widgets, Homepage can access personal information (for example from your home automation system) and Homepage currently does not (and is not planned to) include any authentication layer itself. Thus, we recommend homepage be deployed behind a reverse proxy including authentication, SSL etc, and / or behind a VPN.
+Please note that when using features such as widgets, Homepage can access personal information (for example from your home automation system) and Homepage currently does not (and is not planned to) include any authentication layer itself. If Homepage is reachable from any untrusted network, it **must** sit behind a reverse proxy (and/or VPN) that enforces authentication, TLS, and strictly validates Host headers. The built-in host check in Homepage is a best-effort guard and should not be treated as security when exposed publicly.
 
 ## With Docker
 
@@ -154,16 +149,16 @@ This is a [Next.js](https://nextjs.org/) application, see their documentation fo
 
 The homepage documentation is available at [https://gethomepage.dev/](https://gethomepage.dev/).
 
-Homepage uses Material for MkDocs for documentation. To run the documentation locally, first install the dependencies:
+Homepage uses Zensical for documentation. To run the documentation locally, first install the dependencies:
 
 ```bash
-pip install -r requirements.txt
+uv sync
 ```
 
 Then run the development server:
 
 ```bash
-mkdocs serve # or build, to build the static site
+uv run zensical serve # or build, to build the static site
 ```
 
 # Support & Suggestions

docker-entrypoint.sh

@@ -12,14 +12,66 @@ export PGID=${PGID:-0}
 
 export HOMEPAGE_BUILDTIME=$(date +%s)
 
-# Set privileges for /app but only if pid 1 user is root and we are dropping privileges.
-# If container is run as an unprivileged user, it means owner already handled ownership setup on their own.
-# Running chown in that case (as non-root) will cause error
-[ "$(id -u)" == "0" ] && [ "${PUID}" != "0" ] && chown -R ${PUID}:${PGID} /app/config /app/public
+# Try IPv6 first (dual stack when available), but fall back to IPv4 if the bind fails
+export HOSTNAME=${HOSTNAME:-::}
+if [ "$HOSTNAME" = "::" ]; then
+  if ! node -e "const server = require('http').createServer(() => {}); const host = '::'; const port = process.env.PORT || 3000; server.once('error', (err) => { console.error('IPv6 bind failed:', err.message); process.exit(1); }); server.listen(port, host, () => server.close(() => process.exit(0)));"; then
+    echo "Falling back to IPv4 bind at 0.0.0.0"
+    export HOSTNAME=0.0.0.0
+  fi
+fi
+
+# Check ownership before chown
+if [ "$PUID" = "0" ]; then
+  echo "Skipping ownership changes for /app/config"
+elif [ -e /app/config ]; then
+  CURRENT_UID=$(stat -c %u /app/config)
+  CURRENT_GID=$(stat -c %g /app/config)
+
+  if [ "$CURRENT_UID" -ne "$PUID" ] || [ "$CURRENT_GID" -ne "$PGID" ]; then
+    echo "Fixing ownership of /app/config"
+    if ! chown -R "$PUID:$PGID" /app/config 2>/dev/null; then
+      echo "Warning: Could not chown /app/config; continuing anyway"
+    fi
+  else
+    echo "/app/config already owned by correct UID/GID, skipping chown"
+  fi
+else
+  echo "/app/config does not exist; skipping ownership check"
+fi
+
+# Ensure /app/config/logs exists and is owned
+if [ "$PUID" = "0" ]; then
+  echo "Skipping ownership changes for /app/config/logs"
+elif [ -n "$PUID" ] && [ -n "$PGID" ]; then
+  mkdir -p /app/config/logs 2>/dev/null || true
+  if [ -d /app/config/logs ]; then
+    LOG_UID=$(stat -c %u /app/config/logs)
+    LOG_GID=$(stat -c %g /app/config/logs)
+    if [ "$LOG_UID" -ne "$PUID" ] || [ "$LOG_GID" -ne "$PGID" ]; then
+      echo "Fixing ownership of /app/config/logs"
+      chown -R "$PUID:$PGID" /app/config/logs 2>/dev/null || echo "Warning: Could not chown /app/config/logs"
+    fi
+  fi
+fi
+
+if [ -d /app/.next ]; then
+  CURRENT_UID=$(stat -c %u /app/.next)
+  CURRENT_GID=$(stat -c %g /app/.next)
+
+  if [ "$PUID" -ne 0 ] && ([ "$CURRENT_UID" -ne "$PUID" ] || [ "$CURRENT_GID" -ne "$PGID" ]); then
+    echo "Fixing ownership of /app/.next"
+    if ! chown -R "$PUID:$PGID" /app/.next 2>/dev/null; then
+      echo "Warning: Could not chown /app/.next; continuing anyway"
+    fi
+  else
+    echo "/app/.next already owned by correct UID/GID or running as root, skipping chown"
+  fi
+fi
 
 # Drop privileges (when asked to) if root, otherwise run as current user
-if [ "$(id -u)" == "0" ] && [ "${PUID}" != "0" ]; then
-  su-exec ${PUID}:${PGID} "$@"
+if [ "$(id -u)" = "0" ] && [ "${PUID}" != "0" ]; then
+  exec su-exec ${PUID}:${PGID} "$@"
 else
   exec "$@"
 fi

docs/configs/docker.md

@@ -20,7 +20,7 @@ Since Docker supports connecting with TLS and client certificate authentication,
 ```yaml
 my-remote-docker:
   host: 192.168.0.101
-  port: 275
+  port: 2375
   tls:
     keyFile: tls/key.pem
     caFile: tls/ca.pem
@@ -66,6 +66,30 @@ my-docker:
   port: 2375
 ```
 
+Use `protocol: https` if you’re connecting through a reverse proxy (e.g., Traefik) that serves the Docker API over HTTPS:
+
+```yaml
+my-docker:
+  host: dockerproxy
+  port: 443
+  protocol: https
+```
+
+!!! note
+
+    Note: This does not require TLS certificates if the proxy handles encryption. Do not use `protocol: https` unless you’re sure the target host supports HTTPS.
+
+You can also include `headers` for the connection, for example, if you are using a reverse proxy that requires authentication:
+
+```yaml
+my-docker:
+  host: dockerproxy
+  port: 443
+  protocol: https
+  headers:
+    Authorization: Basic <base64-encoded-credentials>
+```
+
 ## Using Socket Directly
 
 If you'd rather use the socket directly, first make sure that you're passing the local socket into the Docker container.
@@ -153,6 +177,16 @@ labels:
   - homepage.widget.fields=["field1","field2"] # optional
 ```
 
+!!! note
+
+    If you use mapping syntax (`:`) for labels instead of list syntax (`-`), array values like `fields` must be wrapped in single quotes so they are passed as a string:
+
+    ```yaml
+    labels:
+      ...
+      homepage.widget.fields: '["field1","field2"]'
+    ```
+
 Multiple widgets can be specified by incrementing the index, e.g.
 
 ```yaml
@@ -165,6 +199,8 @@ labels: ...
   - homepage.widgets[1].slug=youreventslughere
 ```
 
+To pass custom HTTP headers with a widget request when using labels, use the same dot-notation: `homepage.widget.headers.X-Auth-Key=secret` (or `homepage.widgets[0].headers.X-Auth-Key=secret` when multiple widgets are present).
+
 You can add specify fields for e.g. the [CustomAPI](../widgets/services/customapi.md) widget by using array-style dot notation:
 
 ```yaml
@@ -247,4 +283,4 @@ You can show the docker stats by clicking the status indicator but this can also
   showStats: true
 ```
 
-Also see the settings for [show docker stats](settings.md#show-docker-stats).
+Also see the settings for [show docker stats](settings.md#show-container-stats).

docs/configs/kubernetes.md

@@ -94,6 +94,7 @@ metadata:
     gethomepage.dev/name: Emby
     gethomepage.dev/widget.type: "emby"
     gethomepage.dev/widget.url: "https://emby.example.com"
+    gethomepage.dev/widget.headers.X-Auth-Key: "your-secret-here"
     gethomepage.dev/pod-selector: ""
     gethomepage.dev/weight: 10 # optional
     gethomepage.dev/instance: "public" # optional
@@ -121,7 +122,7 @@ Use the `gethomepage.dev/pod-selector` selector to specify the pod used for the
 
 ### Traefik IngressRoute support
 
-Homepage can also read ingresses defined using the Traefik IngressRoute custom resource definition. Due to the complex nature of Traefik routing rules, it is required for the `gethomepage.dev/href` annotation to be set:
+If enabled (with `traefik: true` in kubernetes.yaml), homepage can also read ingresses defined using the Traefik IngressRoute custom resource definition. Due to the complex nature of Traefik routing rules, it is required for the `gethomepage.dev/href` annotation to be set:
 
 ```yaml
 apiVersion: traefik.io/v1alpha1
@@ -163,6 +164,47 @@ If the `href` attribute is not present, Homepage will ignore the specific Ingres
 
 Homepage also features automatic service discovery for Gateway API. Service definitions are read by annotating the HttpRoute custom resource definition and are indentical to the Ingress example as defined in [Automatic Service Discovery](#automatic-service-discovery).
 
+To enable Gateway API HttpRoute update `kubernetes.yaml` to include:
+
+```
+gateway: true # enable gateway-api
+```
+
+#### Using the unoffocial helm chart?
+
+If you are using the unofficial helm chart ensure that the `ClusterRole` has required permissions for `gateway.networking.k8s.io`.
+
+See [ClusterRole and ClusterRoleBinding](../installation/k8s.md#clusterrole-and-clusterrolebinding)
+
 ## Caveats
 
 Similarly to Docker service discovery, there currently is no rigid ordering to discovered services and discovered services will be displayed above those specified in the `services.yaml`.
+
+## Adding extra configuration files
+
+Some Homepage features (for example, [Proxmox](../configs/proxmox.md)) require additional configuration files such as `proxmox.yaml`.
+When running Homepage on Kubernetes, these files must be provided via a `ConfigMap` and mounted into the container at `/app/config`.
+
+### ConfigMap example
+
+```yaml
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: homepage
+data:
+  proxmox.yaml: |
+    pve:
+      url: https://proxmox.host.or.ip:8006
+      token: username@pam!Token ID
+      secret: secret
+```
+
+Mount the file into `/app/config` by updating the `Deployment`:
+
+```yaml
+volumeMounts:
+  - mountPath: /app/config/proxmox.yaml
+    name: homepage-config
+    subPath: proxmox.yaml
+```

docs/configs/proxmox.md

@@ -0,0 +1,81 @@
+---
+title: Proxmox
+description: Proxmox Configuration
+---
+
+The Proxmox connection is configured in the `proxmox.yaml` file. See [Create token](#create-token) section below for details on how to generate the required API token.
+To configure multiple nodes, ensure the key name in the `proxmox.yaml` matches the `proxmoxNode` field used in your service configuration.
+
+```yaml
+pve: # must match your actual Proxmox node name
+  url: https://proxmox.host.or.ip:8006
+  token: username@pam!Token ID
+  secret: secret
+```
+
+## Services
+
+Once the Proxmox connection is configured, individual services can be configured to pull statistics of VMs or LXCs. Only CPU and Memory are currently supported.
+
+### Configuration Options
+
+- `proxmoxNode`: The name of the Proxmox node where your VM/LXC is running, must match with a node configured in the `proxmox.yaml`
+- `proxmoxVMID`: The ID of the Proxmox VM or LXC container
+- `proxmoxType`: (Optional) The type of Proxmox virtual machine. Defaults to `qemu` for VMs, but can be set to `lxc` for LXC containers
+
+#### Examples
+
+For a QEMU VM (default):
+
+```yaml
+- HomeAssistant:
+  icon: home-assistant.png
+  href: http://homeassistant.local/
+  description: Home automation
+  proxmoxNode: pve
+  proxmoxVMID: 101
+  # proxmoxType: qemu # This is the default, so it can be omitted
+```
+
+For an LXC container:
+
+```yaml
+- Nginx:
+  icon: nginx.png
+  href: http://nginx.local/
+  description: Web server
+  proxmoxNode: pve
+  proxmoxVMID: 200
+  proxmoxType: lxc
+```
+
+## Create token
+
+You will need to generate an API Token for new or an existing user. Here is an example of how to do this for a new user.
+
+1.  Navigate to the Proxmox portal, click on Datacenter
+2.  Expand Permissions, click on Groups
+3.  Click the Create button
+4.  Name the group something informative, like api-ro-users
+5.  Click on the Permissions "folder"
+6.  Click Add -> Group Permission
+    - Path: /
+    - Group: group from bullet 4 above
+    - Role: PVEAuditor
+    - Propagate: Checked
+7.  Expand Permissions, click on Users
+8.  Click the Add button
+    - User name: something informative like `api`
+    - Realm: Linux PAM standard authentication
+    - Group: group from bullet 4 above
+9.  Expand Permissions, click on API Tokens
+10. Click the Add button
+    - User: user from bullet 8 above
+    - Token ID: something informative like the application or purpose like `homepage`
+    - Privilege Separation: Checked
+11. Go back to the "Permissions" menu
+12. Click Add -> API Token Permission
+    - Path: /
+    - API Token: select the Token ID created in Step 10
+    - Role: PVE Auditor
+    - Propagate: Checked

docs/configs/services.md

@@ -101,6 +101,25 @@ Each service can have multiple widgets attached to it, for example:
 
       Multiple widgets per service are not yet supported with Kubernetes ingress annotations.
 
+#### Custom HTTP headers
+
+Widgets that make HTTP calls support extra request headers via `headers`. This is useful when a reverse proxy expects a secret header.
+
+```yaml
+- UptimeRobot:
+    icon: uptimekuma.png
+    href: https://uptimerobot.com/
+    widget:
+      type: uptimerobot
+      url: https://api.uptimerobot.com
+      key: ${UPTIMEROBOT_API_KEY}
+      headers:
+        User-Agent: homepage
+        X-Auth-Key: your-secret-here
+```
+
+If you define services via Docker labels or Kubernetes annotations, use the same key with dot-notation (for example `homepage.widget.headers.X-Auth-Key=secret` or `gethomepage.dev/widget.headers.X-Auth-Key: "secret"`).
+
 #### Field Visibility
 
 Each widget can optionally provide a list of which fields should be visible via the `fields` widget property. If no fields are specified, then all fields will be displayed. The `fields` property must be a valid YAML array of strings. As an example, here is the entry for Sonarr showing only a couple of fields.
@@ -118,6 +137,60 @@ Each widget can optionally provide a list of which fields should be visible via
       key: apikeyapikeyapikeyapikeyapikey
 ```
 
+### Block Highlighting
+
+Widgets can tint their metric block text automatically based on rules defined alongside the service. Attach a `highlight` section to the widget configuration and map each block to one or more numeric or string rules using the field key (for example, `queued`, `lan_users`).
+
+```yaml
+- Sonarr:
+    icon: sonarr.png
+    href: http://sonarr.host.or.ip
+    widget:
+      type: sonarr
+      url: http://sonarr.host.or.ip
+      key: ${SONARR_API_KEY}
+      highlight:
+        queued:
+          numeric:
+            - level: danger
+              when: gte
+              value: 20
+            - level: warn
+              when: gte
+              value: 5
+            - level: good
+              when: eq
+              value: 0
+        status:
+          string:
+            - level: danger
+              when: regex
+              value: "(failed|import) pending"
+            - level: good
+              when: equals
+              value: "All good"
+        status_code:
+          string:
+            - level: warn
+              when: regex
+              value: "^5\\d{2}$"
+```
+
+Supported numeric operators for the `when` property are `gt`, `gte`, `lt`, `lte`, `eq`, `ne`, `between`, and `outside`. String rules support `equals`, `includes`, `startsWith`, `endsWith`, and `regex`. Each rule can be inverted with `negate: true`, and string rules may pass `caseSensitive: true` or custom regex `flags`. The highlight engine does its best to coerce formatted values, but you will get the most reliable results when you pass plain numbers or strings into `<Block>`.
+
+#### Value Only Highlighting
+
+You can optionally apply highlighting only to the value portion of a block (not the label) by setting `valueOnly: true` on the field configuration. This keeps the label visible while highlighting only the metric value itself.
+
+```yaml
+- Sonarr:
+    ...
+      highlight:
+        queued:
+          valueOnly: true
+          ...
+```
+
 ## Descriptions
 
 Services may have descriptions,

docs/configs/settings.md

@@ -101,7 +101,7 @@ theme: dark # or light
 
 ## Color Palette
 
-You can configured a fixed color palette (and disable the palette switcher) by passing the `color` option, like so:
+You can configure a fixed color palette (and disable the palette switcher) by passing the `color` option, like so:
 
 ```yaml
 color: slate
@@ -109,6 +109,72 @@ color: slate
 
 Supported colors are: `slate`, `gray`, `zinc`, `neutral`, `stone`, `amber`, `yellow`, `lime`, `green`, `emerald`, `teal`, `cyan`, `sky`, `blue`, `indigo`, `violet`, `purple`, `fuchsia`, `pink`, `rose`, `red`, `white`
 
+## Block Highlight Levels
+
+You can override the default Tailwind classes applied when a widget highlight rule resolves to the `good`, `warn`, or `danger` level.
+
+```yaml
+blockHighlights:
+  levels:
+    good: "bg-emerald-500/40 text-emerald-950 dark:bg-emerald-900/60 dark:text-emerald-400"
+    warn: "bg-amber-300/30 text-amber-900 dark:bg-amber-900/30 dark:text-amber-200"
+    danger: "bg-rose-700/45 text-rose-200 dark:bg-rose-950/70 dark:text-rose-400"
+```
+
+Any unspecified level falls back to the built-in defaults.
+
+## Progressive Web App (PWA)
+
+A progressive web app is an app that can be installed on a device and provide user experience like a native app. Homepage comes with built-in support for PWA with some default configurations, but you can customize them.
+
+More information on PWAs can be found in [MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps).
+
+### App icons
+
+You can set custom icons for installable apps. More information about how you can set them can be found in the [MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Manifest/Reference/icons).
+
+The default value is the Homepage icon in sizes 192x192 and 512x512.
+
+```yaml
+pwa:
+  icons:
+    - src: https://developer.mozilla.org/favicon-192x192.png
+      type: image/png
+      sizes: 192x192
+    - src: https://developer.mozilla.org/favicon-512x512.png
+      type: image/png
+      sizes: 512x512
+```
+
+For icon `src` you can pass either full URL or a local path relative to the `/app/public` directory. See [Background Image](#background-image) for more detailed information on how to provide your own files.
+
+### Shortcuts
+
+Shortcuts can be used to specify links to tabs, to be preselected when the homepage is opened as an app.
+More information about how you can set them can be found in the [MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Manifest/Reference/shortcuts).
+
+```yaml
+pwa:
+  shortcuts:
+    - name: First
+      url: "/#first" # opens the first tab
+    - name: Second
+      url: "/#second" # opens the second tab
+    - name: Third
+      url: "/#third" # opens the third tab
+```
+
+### Other PWA configurations
+
+Homepage sets few other PWA configurations, that are based on global settings in `settings.yaml`:
+
+- `name`, `short_name` - Both equal to the [`title`](#title) setting.
+- `theme_color`, `background_color` - Both based on the [`color`](#color-palette) and [`theme`](#theme) settings.
+- `display` - It is always set to "standalone".
+- `start_url` - Equal to the [`startUrl`](#start-url) setting.
+
+More information for wach of the PWA configurations can be found in the [MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Manifest/Reference).
+
 ## Layout
 
 You can configure service and bookmarks sections to be either "column" or "row" based layouts, like so:
@@ -264,7 +330,7 @@ fullWidth: true
 
 ### Maximum Group Columns
 
-You can set the maximum number of columns of groups on larger screen sizes (note this is only for groups with the default `style: columns`, not groups with `stle: row`) by adding:
+You can set the maximum number of columns of groups on larger screen sizes (note this is only for groups with the default `style: columns`, not groups with `style: row`) by adding:
 
 ```yaml
 maxGroupColumns: 8 # default is 4 for services, 6 for bookmarks, max 8
@@ -382,7 +448,9 @@ Set your desired language using:
 language: fr
 ```
 
-Currently supported languages: ca, de, en, es, fr, he, hr, hu, it, nb-NO, nl, pt, ru, sv, vi, zh-CN, zh-Hant
+Currently supported languages: ca, de, en, es, fr, he, hr, hu, it, nb-NO, nl, pt, ru, sv, vi, zh-Hans (Simplified), zh-Hant (Traditional)
+
+`zh-CN` will still work and is automatically mapped to `zh-Hans` for backwards compatibility.
 
 You can also specify locales e.g. for the DateTime widget, e.g. en-AU, en-GB, etc.
 
@@ -441,6 +509,7 @@ There are a few optional settings for the Quick Launch feature:
 - `showSearchSuggestions`: show search suggestions for the internet search. If this is not specified then the setting will be inherited from the search widget. If it is not specified there either, it will default to false. For custom providers the `suggestionUrl` needs to be set in order for this to work.
 - `provider`: search engine provider. If none is specified it will try to use the provider set for the Search Widget, if neither are present then internet search will be disabled.
 - `hideVisitURL`: disable detecting and offering an option to open URLs. This is false by default, enabling the feature.
+- `mobileButtonPosition`: enables and sets the position of the mobile quicklaunch button. Options are `top-left`, `top-right`, `bottom-left`, `bottom-right`. This is empty by default, disabling the feature.
 
 ```yaml
 quicklaunch:
@@ -485,9 +554,9 @@ logpath: /logfile/path
 
 By default, logs are sent both to `stdout` and to a file at the path specified. This can be changed by setting the `LOG_TARGETS` environment variable to one of `both` (default), `stdout` or `file`.
 
-## Show Docker Stats
+## Show Container Stats
 
-You can show all docker stats expanded in `settings.yaml`:
+You can show all docker or proxmox stats expanded in `settings.yaml`:
 
 ```yaml
 showStats: true
@@ -556,3 +625,18 @@ or per service widget (`services.yaml`) with:
 ```
 
 If either value is set to true, the error message will be hidden.
+
+## Disable Search Engine Indexing
+
+You can request that search engines not to index your Homepage instance by enabling the `disableIndexing` setting.
+
+```yaml
+disableIndexing: true
+```
+
+When enabled, this will:
+
+- Disallow all crawlers in `robots.txt`
+- Add `<meta name="robots" content="noindex, nofollow">` tags to prevent indexing
+
+By default this feature is disabled.

docs/installation/docker.md

@@ -14,7 +14,7 @@ services:
       - 3000:3000
     volumes:
       - /path/to/config:/app/config # Make sure your local config directory exists
-      - /var/run/docker.sock:/var/run/docker.sock # (optional) For docker integrations
+      - /var/run/docker.sock:/var/run/docker.sock:ro # (optional) For docker integrations
     environment:
       HOMEPAGE_ALLOWED_HOSTS: gethomepage.dev # required, may need port. See gethomepage.dev/installation/#homepage_allowed_hosts
 ```
@@ -36,7 +36,7 @@ services:
       - 3000:3000
     volumes:
       - /path/to/config:/app/config # Make sure your local config directory exists
-      - /var/run/docker.sock:/var/run/docker.sock # (optional) For docker integrations, see alternative methods
+      - /var/run/docker.sock:/var/run/docker.sock:ro # (optional) For docker integrations, see alternative methods
     environment:
       HOMEPAGE_ALLOWED_HOSTS: gethomepage.dev # required, may need port. See gethomepage.dev/installation/#homepage_allowed_hosts
       PUID: $PUID

docs/installation/index.md

@@ -37,4 +37,4 @@ The value is a comma-separated (no spaces) list of allowed hosts (sometimes with
 
 If you are seeing errors about host validation, check the homepage logs and ensure that the host exactly as output in the logs is in the `HOMEPAGE_ALLOWED_HOSTS` list.
 
-This can be disabled by setting `HOMEPAGE_ALLOWED_HOSTS` to `*` but this is not recommended.
+This can be disabled by setting `HOMEPAGE_ALLOWED_HOSTS` to `*` but this is not recommended. Public deployments must rely on a reverse proxy (and/or VPN) that enforces authentication, TLS, and unexpected Host headers; the built-in host check is a best-effort guard for local setups and is not a substitute for edge protections.

docs/installation/k8s.md

@@ -223,13 +223,33 @@ spec:
         - name: homepage
           image: "ghcr.io/gethomepage/homepage:latest"
           imagePullPolicy: Always
+          securityContext:
+            allowPrivilegeEscalation: false
+            capabilities:
+              drop:
+                - ALL
+            runAsNonRoot: true
+            runAsUser: 1000
+            runAsGroup: 1000
+            seccompProfile:
+              type: RuntimeDefault
           env:
+            - name: MY_POD_IP
+              valueFrom:
+                fieldRef:
+                  fieldPath: status.podIP
             - name: HOMEPAGE_ALLOWED_HOSTS
-              value: gethomepage.dev # required, may need port. See gethomepage.dev/installation/#homepage_allowed_hosts
+              value: "$(MY_POD_IP):3000,gethomepage.dev" # See gethomepage.dev/installation/#homepage_allowed_hosts . Value before the comma is required for the k8s probe
           ports:
             - name: http
               containerPort: 3000
               protocol: TCP
+          livenessProbe:
+            httpGet:
+              path: /api/healthcheck
+              port: http
+            initialDelaySeconds: 5
+            periodSeconds: 15
           volumeMounts:
             - mountPath: /app/config/custom.js
               name: homepage-config

docs/more/sponsors.md

@@ -28,7 +28,7 @@ These companies help the Homepage project by providing services, tools, and reso
   </div>
 
   <div style="margin-bottom: 16px;">
-    <a href="https://crowdin.com/project/homepage"><img src="https://support.crowdin.com/assets/logos/core-logo/png/crowdin-core-logo-cWhite.png" alt="Crowdin" style="max-width: 100%; height: 64px; display: block;" /></a>
+    <a href="https://crowdin.com/project/gethomepage"><img src="https://support.crowdin.com/assets/logos/core-logo/png/crowdin-core-logo-cWhite.png" alt="Crowdin" style="max-width: 100%; height: 64px; display: block;" /></a>
     <p>
       Crowdin provides the translation platform for the project.  Making it easy to translate the project into multiple languages.
     </p>

docs/stylesheets/extra.css

@@ -104,7 +104,7 @@
 
 body {
   background-color: transparent !important;
-  background-image: url("https://raw.githubusercontent.com/gethomepage/homepage/main/docs/assets/blossom_valley.jpg");
+  background-image: url("https://raw.githubusercontent.com/gethomepage/homepage/main/docs/assets/blossom_valley_blur.jpg");
   background-size: cover;
   background-attachment: fixed;
   background-position: center;
@@ -119,20 +119,6 @@ body[data-md-color-scheme="default"] {
   color: rgba(255, 255, 255, 1);
 }
 
-.blur-overlay {
-  z-index: -1;
-  position: fixed;
-  width: 100%;
-  height: 100%;
-  background: hsl(0deg 0% 0% / 10%);
-  backdrop-filter: blur(128px);
-  -webkit-backdrop-filter: blur(128px);
-}
-
-[data-md-color-scheme="default"] .blur-overlay {
-  background: hsla(0, 0%, 0%, 0);
-}
-
 .md-nav--lifted > .md-nav__list > .md-nav__item--active > .md-nav__link,
 .md-nav--secondary .md-nav__title {
   background: none;

docs/troubleshooting/index.md

@@ -12,7 +12,6 @@ hide:
 - Check config/logs/homepage.log, on docker simply e.g. `docker logs homepage`. This may provide some insight into the reason for an error.
 - Check the browser error console, this can also sometimes provide useful information.
 - Consider setting the `ENV` variable `LOG_LEVEL` to `debug`.
-- If certain widgets are failing when connecting to public APIs, consider [disabling IPv6](#disabling-ipv6).
 
 ## Service Widget Errors
 
@@ -20,7 +19,7 @@ All service widgets work essentially the same, that is, homepage makes a proxied
 
 1.  URLs should not end with a / or other API path. Each widget will handle the path on its own.
 
-2.  All services with a widget require a unique name.
+2.  All services with a widget require a unique name as well as a unique group (and all subgroups) name.
 
 3.  Verify the homepage installation can connect to the IP address or host you are using for the widget `url`. This is most simply achieved by pinging the server from the homepage machine, in Docker this means _from inside the container_ itself, e.g.:
 
@@ -67,17 +66,3 @@ All service widgets work essentially the same, that is, homepage makes a proxied
 ## Missing custom icons
 
 If, after correctly adding and mapping your custom icons via the [Icons](../configs/services.md#icons) instructions, you are still unable to see your icons please try recreating your container.
-
-## Disabling IPv6
-
-If you are having issues with certain widgets that are unable to reach public APIs (e.g. weather), in certain setups you may need to disable IPv6. You can set the environment variable `HOMEPAGE_PROXY_DISABLE_IPV6` to `true` to disable IPv6 for the homepage proxy.
-
-Alternatively, you can use the `sysctls` option in your docker-compose file to disable IPv6 for the homepage container completely:
-
-```yaml
-services:
-  homepage:
-    ...
-    sysctls:
-      - net.ipv6.conf.all.disable_ipv6=1
-```

docs/widgets/authoring/getting-started.md

@@ -33,6 +33,32 @@ Once dependencies have been installed you can lint your code with
 pnpm lint
 ```
 
+## Testing
+
+Homepage uses [Vitest](https://vitest.dev/) for unit and component tests.
+
+Run the test suite:
+
+```bash
+pnpm test
+```
+
+Run the test suite with coverage:
+
+```bash
+pnpm test:coverage
+```
+
+### What tests to include
+
+- New or updated widgets should generally include a component test near the widget component (for example `src/widgets/<widget>/component.test.jsx`) that covers realistic behavior: loading/placeholder state, error state, and a representative "happy path" render.
+- If you add or change a widget definition file (`src/widgets/<widget>/widget.js`), add/update its corresponding unit test (`src/widgets/<widget>/widget.test.js`) to cover the config/mapping behavior.
+- If your widget requires a custom proxy (`src/widgets/<widget>/proxy.js`), add a proxy unit test (`src/widgets/<widget>/proxy.test.js`) that validates:
+  - request construction (URL, query params, headers/auth)
+  - response mapping (what the widget consumes)
+  - error pathways (upstream error, unexpected payloads)
+- Avoid placing test files under `src/pages/**` (Next.js treats files there as routes). Page tests should live under `src/__tests__/pages/**`.
+
 ## Code formatting with pre-commit hooks
 
 To ensure a consistent style and formatting across the project source, the project utilizes Git [`pre-commit`](https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks) hooks to perform some formatting and linting before a commit is allowed.
@@ -62,3 +88,4 @@ To ensure cohesiveness of various widgets, the following should be used as a gui
 - Minimize the number of API calls
 - Avoid the use of custom proxy unless absolutely necessary
 - Widgets should be 'read-only', as in they should not make write changes using the relevant tool's API. Homepage widgets are designed to surface information, not to be a (usually worse) replacement for the tool itself.
+- Widgets should not allow manually overriding the "refresh interval" setting, as misconfigured refresh intervals can easily lead to performance issues for users.

docs/widgets/authoring/metadata.md

@@ -225,20 +225,8 @@ const widgetExample = {
 
 #### `method`
 
-The `method` property is a string that represents the HTTP method that should be used to make the API request. The default value is `GET`.
-
-```js
-const widgetExample = {
-  api: "{url}/api/{endpoint}",
-  mappings: {
-    // `/api/stats`
-    stats: {
-      endpoint: "stats",
-      method: "POST",
-    },
-  },
-};
-```
+The `method` represents the HTTP method that should be used to make the API request. The default value is `GET`. Note that `POST` requests are not allowed via the
+widget API and require the use of a custom proxy.
 
 #### `headers`
 
@@ -251,7 +239,6 @@ const widgetExample = {
     // `/api/stats`
     stats: {
       endpoint: "stats",
-      method: "POST",
       headers: {
         "Content-Type": "application/json",
       },
@@ -271,7 +258,6 @@ const widgetExample = {
     // `/api/graphql`
     stats: {
       endpoint: "graphql",
-      method: "POST",
       body: {
         query: `
           query {

docs/widgets/authoring/proxies.md

@@ -201,3 +201,18 @@ export default async function customProxyHandler(req, res, map) {
 ```
 
 Proxy handlers are a complex topic and require a good understanding of JavaScript and the Homepage codebase. If you are new to Homepage, we recommend using the built-in proxy handlers.
+
+## Testing proxy handlers
+
+Proxy handlers are a common source of regressions because they deal with authentication, request formatting, and sometimes odd upstream API behavior.
+
+When you add a new proxy handler or custom widget proxy, include tests that focus on behavior:
+
+- **Request construction:** the correct URL/path, query params, headers, and auth (and that secrets are not accidentally logged).
+- **Response mapping:** the payload shape expected by the widget/component (including optional/missing fields).
+- **Error handling:** upstream non-200s, invalid JSON, timeouts, and unexpected payloads should produce a predictable result.
+
+Test locations:
+
+- Shared handlers live in `src/utils/proxy/handlers/*.js` with tests alongside them (for example `src/utils/proxy/handlers/generic.test.js`).
+- Widget-specific proxies live in `src/widgets/<widget>/proxy.js` with tests in `src/widgets/<widget>/proxy.test.js`.

docs/widgets/authoring/translations.md

@@ -34,7 +34,7 @@ Homepage uses the [next-i18next](https://github.com/i18next/next-i18next) librar
 
 Homepage uses translated and localized strings for **all text and numerical content** in widgets. English is the default language, and other languages can be added via [Crowdin](https://crowdin.com/project/gethomepage). To add the English translations for your widget, follow these steps:
 
-Open the `public/locales/en/common.js` file.
+Open the `public/locales/en/common.json` file.
 
 Add a new object for your widget to the bottom of the list, like this:
 

docs/widgets/authoring/tutorial.md

@@ -150,7 +150,7 @@ This will render the widget with placeholders for the data, i.e., a skeleton vie
 
 !!! tip "Translation Tips"
 
-      The `label` prop in the `Block` component corresponds to the translation key we defined earlier in the `common.js` file.  All text and numerical content should be translated.
+      The `label` prop in the `Block` component corresponds to the translation key we defined earlier in the `common.json` file.  All text and numerical content should be translated.
 
 ---
 

docs/widgets/index.md

@@ -32,7 +32,7 @@ More detail on configuring service widgets can be found in the [Service Widgets
 
 ## Info Widgets
 
-Info widgets are used to display information in the header, often about your system or environment. Info widgets are defined your `widgets.yaml` file. Here's an example:
+Info widgets are used to display information in the header, often about your system or environment. Info widgets are defined in your `widgets.yaml` file. Here's an example:
 
 ```yaml
 - openmeteo:

docs/widgets/info/glances.md

@@ -16,6 +16,8 @@ The Glances widget allows you to monitor the resources (CPU, memory, storage, te
     cpu: true # optional, enabled by default, disable by setting to false
     mem: true # optional, enabled by default, disable by setting to false
     cputemp: true # disabled by default
+    cpuSensorLabel: Package id # optional additional cputemp sensor label prefix
+    unit: imperial # optional for temp, default is metric
     uptime: true # disabled by default
     disk: / # disabled by default, use mount point of disk(s) in glances. Can also be a list (see below)
     diskUnits: bytes # optional, bytes (default) or bbytes. Only applies to disk
@@ -23,6 +25,8 @@ The Glances widget allows you to monitor the resources (CPU, memory, storage, te
     label: MyMachine # optional
 ```
 
+The built-in `cputemp` sensor matching already checks common prefixes such as `cpu_thermal`, `Core`, `Tctl`, and `Temperature`. Use `cpuSensorLabel` to add your own Glances sensor label prefix when your system reports CPU temperatures under a different name.
+
 Multiple disks can be specified as:
 
 ```yaml
@@ -31,5 +35,3 @@ disk:
   - /boot
   ...
 ```
-
-_Added in v0.4.18, updated in v0.6.11, v0.6.21_

docs/widgets/info/resources.md

@@ -7,13 +7,17 @@ You can include all or some of the available resources. If you do not want to se
 
 The disk path is the path reported by `df` (Mounted On), or the mount point of the disk.
 
+!!! note
+
+    Any disk you wish to access must be mounted to your container as a volume.
+
 The cpu and memory resource information are the container's usage while [glances](glances.md) displays statistics for the host machine on which it is installed.
 
 The resources widget primarily relies on a popular tool called [systeminformation](https://systeminformation.io). Thus, any limitiations of that software apply, for example, BRTFS RAID is not supported for the disk usage. In this case users may want to use the [glances widget](glances.md) instead.
 
-_Note: unfortunately, the package used for getting CPU temp ([systeminformation](https://systeminformation.io)) is not compatible with some setups and will not report any value(s) for CPU temp._
+!!! warning
 
-**Any disk you wish to access must be mounted to your container as a volume.**
+    The package used for getting CPU temp ([systeminformation](https://systeminformation.io)) is not compatible with some setups and will not report any value(s) for CPU temp.
 
 ```yaml
 - resources:
@@ -75,3 +79,10 @@ You can additionally supply an optional `expanded` property set to true in order
 ```
 
 ![194136533-c4238c82-4d67-41a4-b3c8-18bf26d33ac2](https://user-images.githubusercontent.com/3441425/194728642-a9885274-922b-4027-acf5-a746f58fdfce.png)
+
+To monitor a named host network interface in Docker (for example `network: eno1`), mount host `/sys` (read-only):
+
+```yaml
+volumes:
+  - /sys:/sys:ro
+```

docs/widgets/info/unifi_controller.md

@@ -13,7 +13,7 @@ You can display general connectivity status from your Unifi (Network) Controller
 
 An optional 'site' parameter can be supplied, if it is not the widget will use the default site for the controller.
 
-!!! hint
+!!! tip
 
     If you enter e.g. incorrect credentials and receive an "API Error", you may need to recreate the container to clear the cache.
 

docs/widgets/services/arcane.md

@@ -0,0 +1,18 @@
+---
+title: Arcane
+description: Arcane Widget Configuration
+---
+
+Learn more about [Arcane](https://github.com/getarcaneapp/arcane).
+
+**Allowed fields** (max 4): `running`, `stopped`, `total`, `images`, `images_used`, `images_unused`, `image_updates`.
+**Default fields**: `running`, `stopped`, `total`, `image_updates`.
+
+```yaml
+widget:
+  type: arcane
+  url: http://localhost:3552
+  env: 0 # required, 0 is Arcane default local environment
+  key: your-api-key
+  fields: ["running", "stopped", "total", "image_updates"] # optional
+```

docs/widgets/services/authentik.md

@@ -17,9 +17,15 @@ The account you made the API token for also needs the following **Assigned globa
 
 Allowed fields: `["users", "loginsLast24H", "failedLoginsLast24H"]`.
 
+| Authentik Version | Homepage Widget Version |
+| ----------------- | ----------------------- |
+| < 2025.8.0        | 1 (default)             |
+| >= 2025.8.0       | 2                       |
+
 ```yaml
 widget:
   type: authentik
   url: http://authentik.host.or.ip:port
   key: api_token
+  version: 2 # optional, default is 1
 ```

docs/widgets/services/backrest.md

@@ -0,0 +1,17 @@
+---
+title: Backrest
+description: Backrest Widget Configuration
+---
+
+[Backrest](https://garethgeorge.github.io/backrest/) is a web-based frontend for
+the [Restic](https://restic.net/) backup tool.
+
+**Allowed fields:** `["num_success_latest","num_failure_latest","num_success_30","num_plans","num_failure_30","bytes_added_30"]`
+
+```yaml
+widget:
+  type: backrest
+  url: http://backrest.host.or.ip
+  username: admin # optional if auth is enabled in Backrest
+  password: admin # optional if auth is enabled in Backrest
+```

docs/widgets/services/beszel.md

@@ -9,7 +9,7 @@ The widget has two modes, a single system with detailed info if `systemId` is pr
 
 The `systemID` is the `id` field on the collections page of Beszel under the PocketBase admin panel. You can also use the 'nice name' from the Beszel UI.
 
-A "superuser" is currently required to access the data from tbe Beszel API.
+A "superuser" is currently required to access the data from the Beszel API.
 
 Allowed fields for 'overview' mode: `["systems", "up"]`
 Allowed fields for a single system: `["name", "status", "updated", "cpu", "memory", "disk", "network"]`

docs/widgets/services/booklore.md

@@ -0,0 +1,16 @@
+---
+title: Booklore
+description: Booklore Widget Configuration
+---
+
+Learn more about [Booklore](https://github.com/booklore-app/booklore).
+
+The widget authenticates with your Booklore credentials to surface total libraries, books, and reading progress counts for your account.
+
+```yaml
+widget:
+  type: booklore
+  url: https://booklore.host.or.ip
+  username: username
+  password: password
+```

docs/widgets/services/calendar.md

@@ -22,6 +22,7 @@ widget:
       service_group: Media # group name where widget exists
       service_name: Sonarr # service name for that widget
       color: teal # optional - defaults to pre-defined color for the service (teal for sonarr)
+      baseUrl: https://sonarr.domain.url # optional - adds links to sonarr/radarr pages
       params: # optional - additional params for the service
         unmonitored: true # optional - defaults to false, used with *arr stack
     - type: ical # Show calendar events from another service

docs/widgets/services/checkmk.md

@@ -0,0 +1,17 @@
+---
+title: Checkmk
+description: Checkmk Widget Configuration
+---
+
+Learn more about [Checkmk](https://github.com/Checkmk/checkmk).
+
+To setup authentication, follow the official [Checkmk API](https://docs.checkmk.com/latest/en/rest_api.html?lquery=api#bearerauth) documentation.
+
+```yaml
+widget:
+  type: checkmk
+  url: http://checkmk.host.or.ip:port
+  site: your-site-name-cla-by-default
+  username: username
+  password: password
+```

docs/widgets/services/crowdsec.md

@@ -8,6 +8,9 @@ Learn more about [Crowdsec](https://crowdsec.net).
 See the [crowdsec docs](https://docs.crowdsec.net/docs/local_api/intro/#machines) for information about registering a machine,
 in most instances you can use the default credentials (`/etc/crowdsec/local_api_credentials.yaml`).
 
+!!! note
+Without the `limit24h` option, the widget will fetch all alerts which is limited to 100 by the API to avoid performance issues.
+
 Allowed fields: `["alerts", "bans"]`.
 
 ```yaml
@@ -16,4 +19,5 @@ widget:
   url: http://crowdsechostorip:port
   username: localhost # machine_id in crowdsec
   password: password
+  limit24h: true # optional, limits alerts to last 24h. Default: false
 ```

docs/widgets/services/customapi.md

@@ -189,6 +189,7 @@ widget:
     name: id # required, field in each item to use as the item name (left side)
     label: ip_address # required, field in each item to use as the item label (right side)
     limit: 5 # optional, limit the number of items to display
+    format: text # optional - format of the label field
     target: https://example.com/server/{id} # optional, makes items clickable with template support
 ```
 

docs/widgets/services/diskstation.md

@@ -18,7 +18,7 @@ To access these system metrics you need to connect to the DiskStation (`DSM`) wi
 3. Under the `User Groups` tab of the user config dialogue check the box for `Administrators`.
 4. On the `Permissions` tab check the top box for `No Access`, effectively prohibiting the user from accessing anything in the shared folders.
 5. Under `Applications` check the box next to `Deny` in the header to explicitly prohibit login to all applications.
-6. Now _only_ allow login to the `DSM` application, either by
+6. Now _only_ allow login to the `DSM` and `Download Station` applications, either by
    - unchecking `Deny` in the respective row, or (if inheriting permission doesn't work because of other group settings)
    - checking `Allow` for this app, or
    - checking `By IP` for this app to limit the source of login attempts to one or more IP addresses/subnets.

docs/widgets/services/dispatcharr.md

@@ -0,0 +1,17 @@
+---
+title: Dispatcharr
+description: Dispatcharr Widget Configuration
+---
+
+Learn more about [Dispatcharr](https://github.com/Dispatcharr/Dispatcharr).
+
+Allowed fields: `["channels", "streams"]`.
+
+```yaml
+widget:
+  type: dispatcharr
+  url: http://dispatcharr.host.or.ip
+  username: username
+  password: password
+  enableActiveStreams: true # optional, defaults to false
+```

docs/widgets/services/dockhand.md

@@ -0,0 +1,20 @@
+---
+title: Dockhand
+description: Dockhand Widget Configuration
+---
+
+Learn more about [Dockhand](https://dockhand.pro/).
+
+Note: The widget currently supports Dockhand's **local** authentication only.
+
+**Allowed fields:** (max 4): `running`, `stopped`, `paused`, `total`, `cpu`, `memory`, `images`, `volumes`, `events_today`, `pending_updates`, `stacks`.
+**Default fields:** `running`, `total`, `cpu`, `memory`.
+
+```yaml
+widget:
+  type: dockhand
+  url: http://localhost:3001
+  environment: local # optional: name or id; aggregates all when omitted
+  username: your-user # required for local auth
+  password: your-pass # required for local auth
+```

docs/widgets/services/emby.md

@@ -17,6 +17,7 @@ widget:
   enableBlocks: true # optional, defaults to false
   enableNowPlaying: true # optional, defaults to true
   enableUser: true # optional, defaults to false
+  enableMediaControl: false # optional, defaults to true
   showEpisodeNumber: true # optional, defaults to false
   expandOneStreamToTwoRows: false # optional, defaults to true
 ```

docs/widgets/services/filebrowser.md

@@ -0,0 +1,19 @@
+---
+title: Filebrowser
+description: Filebrowser Widget Configuration
+---
+
+Learn more about [Filebrowser](https://filebrowser.org).
+
+If you are using [Proxy header authentication](https://filebrowser.org/configuration/authentication-method#proxy-header) you have to set `authHeader` and `username`.
+
+Allowed fields: `["available", "used", "total"]`.
+
+```yaml
+widget:
+  type: filebrowser
+  url: http://filebrowserhostorip:port
+  username: username
+  password: password
+  authHeader: X-My-Header # If using Proxy header authentication
+```

docs/widgets/services/frigate.md

@@ -14,4 +14,6 @@ widget:
   type: frigate
   url: http://frigate.host.or.ip:port
   enableRecentEvents: true # Optional, defaults to false
+  username: username # optional
+  password: password # optional
 ```

docs/widgets/services/gamedig.md

@@ -14,4 +14,5 @@ widget:
   type: gamedig
   serverType: csgo # see https://github.com/gamedig/node-gamedig#games-list
   url: udp://server.host.or.ip:port
+  gameToken: # optional, a token used by gamedig with certain games
 ```

docs/widgets/services/gatus.md

@@ -3,6 +3,8 @@ title: Gatus
 description: Gatus Widget Configuration
 ---
 
+Learn more about [Gatus](https://github.com/TwiN/gatus).
+
 Allowed fields: `["up", "down", "uptime"]`.
 
 ```yaml

docs/widgets/services/ghostfolio.md

@@ -15,7 +15,7 @@ See the [official docs](https://github.com/ghostfolio/ghostfolio#authorization-b
 
 _Note that the Bearer token is valid for 6 months, after which a new one must be generated._
 
-Allowed fields: `["gross_percent_today", "gross_percent_1y", "gross_percent_max"]`
+Allowed fields: `["gross_percent_today", "gross_percent_1y", "gross_percent_max", "net_worth"]`
 
 ```yaml
 widget:

docs/widgets/services/gluetun.md

@@ -9,13 +9,20 @@ Learn more about [Gluetun](https://github.com/qdm12/gluetun).
 
     Requires [HTTP control server options](https://github.com/qdm12/gluetun-wiki/blob/main/setup/advanced/control-server.md) to be enabled. By default this runs on port `8000`.
 
-Allowed fields: `["public_ip", "region", "country"]`.
+Allowed fields: `["public_ip", "region", "country", "port_forwarded"]`.
+Default fields: `["public_ip", "region", "country"]`.
 
-To setup authentication, follow [the official Gluetun documentation](https://github.com/qdm12/gluetun-wiki/blob/main/setup/advanced/control-server.md#authentication). Note that to use the api key method, you must add the route `GET /v1/publicip/ip` to the `routes` array in your Gluetun config.toml.
+To setup authentication, follow [the official Gluetun documentation](https://github.com/qdm12/gluetun-wiki/blob/main/setup/advanced/control-server.md#authentication). Note that to use the api key method, you must add the route `GET /v1/publicip/ip` to the `routes` array in your Gluetun config.toml. Similarly, if you want to include the `port_forwarded` field, you must add the route `GET /v1/openvpn/portforwarded` (or `/v1/portforward`) to your Gluetun config.toml.
+
+| Gluetun Version | Homepage Widget Version |
+| --------------- | ----------------------- |
+| < 3.40.1        | 1 (default)             |
+| >= 3.40.1       | 2                       |
 
 ```yaml
 widget:
   type: gluetun
   url: http://gluetun.host.or.ip:port
   key: gluetunkey # Not required if /v1/publicip/ip endpoint is configured with `auth = none`
+  version: 2 # optional, default is 1
 ```

docs/widgets/services/grafana.md

@@ -5,11 +5,18 @@ description: Grafana Widget Configuration
 
 Learn more about [Grafana](https://github.com/grafana/grafana).
 
+| Grafana Version | Homepage Widget Version |
+| --------------- | ----------------------- |
+| <= v10.4        | 1 (default)             |
+| > v10.4         | 2                       |
+
 Allowed fields: `["dashboards", "datasources", "totalalerts", "alertstriggered"]`.
 
 ```yaml
 widget:
   type: grafana
+  version: 2 # optional, default is 1
+  alerts: alertmanager # optional, default is grafana
   url: http://grafana.host.or.ip:port
   username: username
   password: password

docs/widgets/services/hoarder.md

@@ -1,17 +0,0 @@
----
-title: Hoarder
-description: Hoarder Widget Configuration
----
-
-Learn more about [Hoarder](https://hoarder.app).
-
-Generate an API key for your user at `User Settings > API Keys`.
-
-Allowed fields: `["bookmarks", "favorites", "archived", "highlights", "lists", "tags"]` (maximum of 4).
-
-```yaml
-widget:
-  type: hoarder
-  url: http[s]://hoarder.host.or.ip[:port]
-  key: hoarderapikey
-```

docs/widgets/services/immich.md

@@ -10,12 +10,11 @@ Learn more about [Immich](https://github.com/immich-app/immich).
 | < v1.118       | 1 (default)             |
 | >= v1.118      | 2                       |
 
-Find your API key under `Account Settings > API Keys`.
+Find your API key under `Account Settings > API Keys`. The key should have the
+`server.statistics` permission.
 
 Allowed fields: `["users" ,"photos", "videos", "storage"]`.
 
-Note that API key must be from admin user.
-
 ```yaml
 widget:
   type: immich

docs/widgets/services/index.md

@@ -9,19 +9,23 @@ You can also find a list of all available service widgets in the sidebar navigat
 
 - [Adguard Home](adguard-home.md)
 - [APC UPS](apcups.md)
+- [Arcane](arcane.md)
 - [ArgoCD](argocd.md)
 - [Atsumeru](atsumeru.md)
 - [Audiobookshelf](audiobookshelf.md)
 - [Authentik](authentik.md)
 - [Autobrr](autobrr.md)
 - [Azure DevOps](azuredevops.md)
+- [Backrest](backrest.md)
 - [Bazarr](bazarr.md)
+- [Booklore](booklore.md)
 - [Beszel](beszel.md)
 - [Caddy](caddy.md)
 - [Calendar](calendar.md)
 - [Calibre-Web](calibre-web.md)
 - [ChangeDetection.io](changedetectionio.md)
 - [Channels DVR Server](channelsdvrserver.md)
+- [Checkmk](checkmk.md)
 - [Cloudflared](cloudflared.md)
 - [Coin Market Cap](coin-market-cap.md)
 - [CrowdSec](crowdsec.md)
@@ -29,10 +33,13 @@ You can also find a list of all available service widgets in the sidebar navigat
 - [Deluge](deluge.md)
 - [DeveLanCacheUI](develancacheui.md)
 - [DiskStation](diskstation.md)
+- [Dispatcharr](dispatcharr.md)
+- [Dockhand](dockhand.md)
 - [DownloadStation](downloadstation.md)
 - [Emby](emby.md)
 - [ESPHome](esphome.md)
 - [EVCC](evcc.md)
+- [Filebrowser](filebrowser.md)
 - [Fileflows](fileflows.md)
 - [Firefly III](firefly.md)
 - [Flood](flood.md)
@@ -51,7 +58,7 @@ You can also find a list of all available service widgets in the sidebar navigat
 - [HDHomeRun](hdhomerun.md)
 - [Headscale](headscale.md)
 - [Healthchecks](healthchecks.md)
-- [Hoarder](hoarder.md)
+- [Karakeep](karakeep.md)
 - [Home Assistant](homeassistant.md)
 - [HomeBox](homebox.md)
 - [Homebridge](homebridge.md)
@@ -60,9 +67,11 @@ You can also find a list of all available service widgets in the sidebar navigat
 - [Jackett](jackett.md)
 - [JDownloader](jdownloader.md)
 - [Jellyfin](jellyfin.md)
-- [Jellyseerr](jellyseerr.md)
+- [Seerr](seerr.md)
+- [Jellystat](jellystat.md)
 - [Kavita](kavita.md)
 - [Komga](komga.md)
+- [Komodo](komodo.md)
 - [Kopia](kopia.md)
 - [Lidarr](lidarr.md)
 - [Linkwarden](linkwarden.md)
@@ -92,7 +101,6 @@ You can also find a list of all available service widgets in the sidebar navigat
 - [OpenMediaVault](openmediavault.md)
 - [OpenWRT](openwrt.md)
 - [OPNsense](opnsense.md)
-- [Overseerr](overseerr.md)
 - [PaperlessNGX](paperlessngx.md)
 - [Peanut](peanut.md)
 - [pfSense](pfsense.md)
@@ -130,14 +138,17 @@ You can also find a list of all available service widgets in the sidebar navigat
 - [TDarr](tdarr.md)
 - [Traefik](traefik.md)
 - [Transmission](transmission.md)
+- [Trilium](trilium.md)
 - [TrueNAS](truenas.md)
 - [TubeArchivist](tubearchivist.md)
 - [UniFi Controller](unifi-controller.md)
 - [Unmanic](unmanic.md)
+- [Unraid](unraid.md)
 - [Uptime Kuma](uptime-kuma.md)
 - [UptimeRobot](uptimerobot.md)
 - [UrBackup](urbackup.md)
 - [Vikunja](vikunja.md)
+- [Wallos](wallos.md)
 - [Watchtower](watchtower.md)
 - [WGEasy](wgeasy.md)
 - [WhatsUpDocker](whatsupdocker.md)

docs/widgets/services/jdownloader.md

@@ -1,6 +1,6 @@
 ---
 title: JDownloader
-description: NextPVR Widget Configuration
+description: JDownloader Widget Configuration
 ---
 
 Learn more about [JDownloader](https://jdownloader.org/).

docs/widgets/services/jellyfin.md

@@ -5,18 +5,25 @@ description: Jellyfin Widget Configuration
 
 Learn more about [Jellyfin](https://github.com/jellyfin/jellyfin).
 
-You can create an API key from inside Jellyfin at `Settings > Advanced > Api Keys`.
+You can create an API key from inside the Jellyfin Administration Dashboard under `Advanced > API Keys`.
 
 As of v0.6.11 the widget supports fields `["movies", "series", "episodes", "songs"]`. These blocks are disabled by default but can be enabled with the `enableBlocks` option, and the "Now Playing" feature (enabled by default) can be disabled with the `enableNowPlaying` option.
 
+| Jellyfin Version | Homepage Widget Version |
+| ---------------- | ----------------------- |
+| < 10.12          | 1 (default)             |
+| >= 10.12         | 2                       |
+
 ```yaml
 widget:
   type: jellyfin
-  url: http://jellyfin.host.or.ip
+  url: http://jellyfin.host.or.ip:port
   key: apikeyapikeyapikeyapikeyapikey
+  version: 2 # optional, default is 1
   enableBlocks: true # optional, defaults to false
   enableNowPlaying: true # optional, defaults to true
   enableUser: true # optional, defaults to false
+  enableMediaControl: false # optional, defaults to true
   showEpisodeNumber: true # optional, defaults to false
   expandOneStreamToTwoRows: false # optional, defaults to true
 ```

docs/widgets/services/jellyseerr.md

@@ -1,17 +0,0 @@
----
-title: Jellyseerr
-description: Jellyseerr Widget Configuration
----
-
-Learn more about [Jellyseerr](https://github.com/Fallenbagel/jellyseerr).
-
-Find your API key under `Settings > General > API Key`.
-
-Allowed fields: `["pending", "approved", "available"]`.
-
-```yaml
-widget:
-  type: jellyseerr
-  url: http://jellyseerr.host.or.ip
-  key: apikeyapikeyapikeyapikeyapikey
-```

docs/widgets/services/jellystat.md

@@ -0,0 +1,18 @@
+---
+title: Jellystat
+description: Jellystat Widget Configuration
+---
+
+Learn more about [Jellystat](https://github.com/CyferShepard/Jellystat). The widget supports (at least) Jellystat version 1.1.6
+
+You can create an API key from inside Jellystat at `Settings > API Key`.
+
+Allowed fields: `["songs", "movies", "episodes", "other"]`.
+
+```yaml
+widget:
+  type: jellystat
+  url: http://jellystat.host.or.ip
+  key: apikeyapikeyapikeyapikeyapikey
+  days: 30 # optional, defaults to 30
+```

docs/widgets/services/karakeep.md

@@ -0,0 +1,17 @@
+---
+title: Karakeep
+description: Karakeep Widget Configuration
+---
+
+Learn more about [Karakeep](https://karakeep.app) (formerly known as Hoarder).
+
+Generate an API key for your user at `User Settings > API Keys`.
+
+Allowed fields: `["bookmarks", "favorites", "archived", "highlights", "lists", "tags"]` (maximum of 4).
+
+```yaml
+widget:
+  type: karakeep
+  url: http[s]://karakeep.host.or.ip[:port]
+  key: karakeep_api_key
+```

docs/widgets/services/komodo.md

@@ -0,0 +1,22 @@
+---
+title: Komodo
+description: Komodo Widget Configuration
+---
+
+This widget shows either details about all containers or stacks (if `showStacks` is true) managed by [Komodo](https://komo.do/) or the number of running servers, containers and stacks when `showSummary` is enabled.
+
+The api key and secret can be found in the Komodo settings.
+
+Allowed fields (max 4): `["total", "running", "stopped", "unhealthy", "unknown"]`.
+Allowed fields with `showStacks` (max 4): `["total", "running", "down", "unhealthy", "unknown"]`.
+Allowed fields with `showSummary`: `["servers", "stacks", "containers"]`.
+
+```yaml
+widget:
+  type: komodo
+  url: http://komodo.hostname.or.ip:port
+  key: K-xxxxxx...
+  secret: S-xxxxxx...
+  showSummary: true # optional, default: false. Takes precedence over showStacks
+  showStacks: true # optional, default: false
+```

docs/widgets/services/mylar.md

@@ -3,7 +3,7 @@ title: Mylar3
 description: Mylar3 Widget Configuration
 ---
 
-Learn more about [Mylar3](https://github.com/mylar3/mylar3).
+Learn more about [Mylar3](https://github.com/MylarComics/mylar3).
 
 API must be enabled in Mylar3 settings.
 

docs/widgets/services/netalertx.md

@@ -9,11 +9,17 @@ _Note that the project was renamed from PiAlert to NetAlertX._
 
 Allowed fields: `["total", "connected", "new_devices", "down_alerts"]`.
 
-If you have enabled a password on your NetAlertX instance, you will need to provide the `SYNC_api_token` as the `key` in your config.
+Provide the `API_TOKEN` (f.k.a. `SYNC_api_token`) as the `key` in your config.
+
+| NetAlertX Version | Homepage Widget Version |
+| ----------------- | ----------------------- |
+| < v26.1.17        | 1 (default)             |
+| > v26.1.17        | 2                       |
 
 ```yaml
 widget:
   type: netalertx
-  url: http://ip:port
-  key: netalertxsyncapitoken # optional, only if password is enabled
+  url: http://ip:port # use backend port for widget version 2+
+  key: yournetalertxapitoken
+  version: 2 # optional, default is 1
 ```

docs/widgets/services/ntfy.md

@@ -0,0 +1,36 @@
+---
+title: ntfy
+description: ntfy Widget Configuration
+---
+
+Learn more about [ntfy](https://github.com/binwiederhier/ntfy).
+
+This widget shows the latest notification for a ntfy topic, including the title or body, priority level, and when it was received. Works with both self-hosted ntfy instances and the public [ntfy.sh](https://ntfy.sh) service.
+
+Allowed fields: `["title", "message", "priority", "lastReceived", "tags"]`.
+
+Default fields: `["title", "message", "priority", "lastReceived"]`.
+
+If more than 4 fields are provided, only the first 4 are displayed.
+
+## Authentication
+
+ntfy supports both public and private topics. For private instances or access-controlled topics, you can authenticate using either a **Bearer token** (ntfy access token) or **Basic auth** (username/password).
+
+| Auth Method  | Config Fields                  | Notes                             |
+| ------------ | ------------------------------ | --------------------------------- |
+| None         | _(omit key/username/password)_ | For public topics                 |
+| Bearer token | `key`                          | ntfy access tokens (`tk_` prefix) |
+| Basic auth   | `username` + `password`        | Username/password credentials     |
+
+See the [ntfy documentation](https://docs.ntfy.sh/config/#access-control) for details on access control.
+
+```yaml
+widget:
+  type: ntfy
+  url: http://ntfy.host.or.ip:port # required
+  topic: mytopic # required
+  # key: tk_accesstoken # optional — for token auth
+  # username: user # optional — for basic auth
+  # password: pass # optional — for basic auth
+```

docs/widgets/services/omada.md

@@ -3,7 +3,7 @@ title: Omada
 description: Omada Widget Configuration
 ---
 
-The widget supports controller versions 3, 4 and 5.
+The widget supports controller versions 3, 4, 5 and 6.
 
 Allowed fields: `["connectedAp", "activeUser", "alerts", "connectedGateways", "connectedSwitches"]`.
 

docs/widgets/services/overseerr.md

@@ -1,17 +0,0 @@
----
-title: Overseerr
-description: Overseerr Widget Configuration
----
-
-Learn more about [Overseerr](https://github.com/sct/overseerr).
-
-Find your API key under `Settings > General`.
-
-Allowed fields: `["pending", "approved", "available", "processing"]`.
-
-```yaml
-widget:
-  type: overseerr
-  url: http://overseerr.host.or.ip
-  key: apikeyapikeyapikeyapikeyapikey
-```

docs/widgets/services/pangolin.md

@@ -0,0 +1,29 @@
+---
+title: Pangolin
+description: Pangolin Widget Configuration
+---
+
+Learn more about [Pangolin](https://github.com/fosrl/pangolin).
+
+This widget shows sites (online/total), resources (healthy/total), targets (healthy/total), and traffic statistics for a Pangolin organization. A resource is considered healthy if at least one of its targets is healthy, or if it has no targets.
+
+Allowed fields: `["sites", "resources", "targets", "traffic", "in", "out"]` (maximum of 4).
+
+```yaml
+widget:
+  type: pangolin
+  url: https://api.pangolin.net
+  key: your-api-key
+  org: your-org-id
+```
+
+Find your organization ID in the URL when logged in (e.g., `https://app.pangolin.net/{org-id}/...`).
+
+## API Key Setup
+
+Create an API key with the following permissions:
+
+- **List Sites**
+- **List Resources**
+
+**Self-Hosted:** Enable the [Integration API](https://docs.pangolin.net/self-host/advanced/integration-api) in your Pangolin configuration before creating the key.

docs/widgets/services/plex-tautulli.md

@@ -12,7 +12,7 @@ Allowed fields: no configurable fields for this widget.
 ```yaml
 widget:
   type: tautulli
-  url: http://tautulli.host.or.ip
+  url: http://tautulli.host.or.ip:port
   key: apikeyapikeyapikeyapikeyapikey
   enableUser: true # optional, defaults to false
   showEpisodeNumber: true # optional, defaults to false

docs/widgets/services/portainer.md

@@ -7,12 +7,16 @@ Learn more about [Portainer](https://github.com/portainer/portainer).
 
 You'll need to make sure you have the correct environment set for the integration to work properly. From the Environments section inside of Portainer, click the one you'd like to connect to and observe the ID at the end of the URL (should be), something like `#!/endpoints/1`, here `1` is the value to set as the `env` value. In order to generate an API key, please follow the steps outlined here https://docs.portainer.io/api/access.
 
-Allowed fields: `["running", "stopped", "total"]`.
+Allowed fields:
+
+- For Docker mode (default): `["running", "stopped", "total"]`
+- For Kubernetes mode (`kubernetes: true`): `["applications", "services", "namespaces"]`
 
 ```yaml
 widget:
   type: portainer
   url: https://portainer.host.or.ip:9443
   env: 1
+  kubernetes: true # optional, defaults to false
   key: ptr_accesskeyaccesskeyaccesskeyaccesskey
 ```

docs/widgets/services/proxmox.md

@@ -7,34 +7,7 @@ Learn more about [Proxmox](https://www.proxmox.com/en/).
 
 This widget shows the running and total counts of both QEMU VMs and LX Containers in the Proxmox cluster. It also shows the CPU and memory usage of the first node in the cluster.
 
-You will need to generate an API Token for new or an existing user. Here is an example of how to do this for a new user.
-
-1.  Navigate to the Proxmox portal, click on Datacenter
-2.  Expand Permissions, click on Groups
-3.  Click the Create button
-4.  Name the group something informative, like api-ro-users
-5.  Click on the Permissions "folder"
-6.  Click Add -> Group Permission
-    - Path: /
-    - Group: group from bullet 4 above
-    - Role: PVEAuditor
-    - Propagate: Checked
-7.  Expand Permissions, click on Users
-8.  Click the Add button
-    - User name: something informative like `api`
-    - Realm: Linux PAM standard authentication
-    - Group: group from bullet 4 above
-9.  Expand Permissions, click on API Tokens
-10. Click the Add button
-    - User: user from bullet 8 above
-    - Token ID: something informative like the application or purpose like `homepage`
-    - Privilege Separation: Checked
-11. Go back to the "Permissions" menu
-12. Click Add -> API Token Permission
-    - Path: /
-    - API Token: select the Token ID created in Step 10
-    - Role: PVE Auditor
-    - Propagate: Checked
+See the [Proxmox configuration documentation](../../configs/proxmox.md#create-token) for details on creating API tokens.
 
 Use `username@pam!Token ID` as the `username` (e.g `api@pam!homepage`) setting and `Secret` as the `password` setting.
 

docs/widgets/services/proxmoxbackupserver.md

@@ -5,6 +5,8 @@ description: Proxmox Backup Server Widget Configuration
 
 Learn more about [Proxmox Backup Server](https://www.proxmox.com/en/proxmox-backup-server/overview).
 
+Create a user and an API token similar to the [Proxmox VE description](proxmox.md). The "Audit" role is required for both the user and token (not group).
+
 Allowed fields: `["datastore_usage", "failed_tasks_24h", "cpu_usage", "memory_usage"]`.
 
 ```yaml
@@ -13,4 +15,5 @@ widget:
   url: https://proxmoxbackupserver.host:port
   username: api_token_id
   password: api_token_secret
+  datastore: datastore_name #optional; if ommitted, will display a combination of all datastores used / total
 ```

docs/widgets/services/pyload.md

@@ -13,4 +13,5 @@ widget:
   url: http://pyload.host.or.ip:port
   username: username
   password: password # only needed if set
+  key: pyloadapikey # only needed if set, takes precedence over username/password
 ```

docs/widgets/services/qbittorrent.md

@@ -16,4 +16,5 @@ widget:
   username: username
   password: password
   enableLeechProgress: true # optional, defaults to false
+  enableLeechSize: true # optional, defaults to false
 ```

docs/widgets/services/seerr.md

@@ -0,0 +1,20 @@
+---
+title: Seerr Widget
+description: Seerr Widget Configuration
+---
+
+Learn more about [Seerr](https://github.com/seerr-team/seerr).
+
+Find your API key under `Settings > General > API Key`.
+
+_Jellyseerr and Overseerr merged into Seerr. Use `type: seerr` (legacy `type: jellyseerr` and `type: overseerr` are aliased)._
+
+Allowed fields: `["pending", "approved", "available", "completed", "processing", "issues"]`.
+Default fields: `["pending", "approved", "completed"]`.
+
+```yaml
+widget:
+  type: seerr
+  url: http://seerr.host.or.ip
+  key: apikeyapikeyapikeyapikeyapikey
+```

docs/widgets/services/sparkyfitness.md

@@ -0,0 +1,15 @@
+---
+title: SparkyFitness
+description: SparkyFitness Widget Configuration
+---
+
+Learn more about [SparkyFitness](https://github.com/CodeWithCJ/SparkyFitness).
+
+Allowed fields: `["eaten", "burned", "remaining", "steps"]`.
+
+```yaml
+widget:
+  type: sparkyfitness
+  url: http://sparkyfitness.host.or.ip
+  key: apikeyapikeyapikeyapikeyapikey
+```

docs/widgets/services/tailscale.md

@@ -9,7 +9,7 @@ You will need to generate an API access token from the [keys page](https://login
 
 To find your device ID, go to the [machine overview page](https://login.tailscale.com/admin/machines) and select your machine. In the "Machine Details" section, copy your `ID`. It will end with `CNTRL`.
 
-Allowed fields: `["address", "last_seen", "expires"]`.
+Allowed fields: `[ "address", "last_seen", "expires", "user", "hostname", "name", "client_version", "os", "created", "authorized", "is_external", "update_available", "tags" ]`.
 
 ```yaml
 widget:

docs/widgets/services/technitium.md

@@ -14,6 +14,7 @@ widget:
   type: technitium
   url: <url to dns server>
   key: biglongapitoken
+  node: <node dns name or cluster> # optional, defaults to current node
   range: LastDay # optional, defaults to LastHour
 ```
 
@@ -21,6 +22,10 @@ widget:
 
 This can be generated via the Technitium DNS Dashboard, and should be generated from a special API specific user.
 
+#### Node
+
+`node` value determines which Technitium cluster node the statistics are returned for. Specifying a value of `cluster` returns aggregrate stats for all nodes in the cluster. Specify a node domain name to return specific node stats, no value returns stats for the node against which the API is executed.
+
 #### Range
 
 `range` value determines how far back of statistics to pull data for. The value comes directly from Technitium API documentation found [here](https://github.com/TechnitiumSoftware/DnsServer/blob/master/APIDOCS.md#dashboard-api-calls), defined as `"type"`. The value can be one of: `LastHour`, `LastDay`, `LastWeek`, `LastMonth`, `LastYear`.

docs/widgets/services/tracearr.md

@@ -0,0 +1,21 @@
+---
+title: Tracearr
+description: Tracearr Widget Configuration
+---
+
+Learn more about [Tracearr](https://www.tracearr.com/).
+
+Provides detailed information about currently active streams across multiple servers.
+
+Allowed fields (for summary view): `["streams", "transcodes", "directplay", "bitrate"]`.
+
+```yaml
+widget:
+  type: tracearr
+  url: http://tracearr.host.or.ip:3000
+  key: apikeyapikeyapikeyapikeyapikey
+  view: both # optional, "summary", "details", or "both", defaults to "details"
+  enableUser: true # optional, defaults to false
+  showEpisodeNumber: true # optional, defaults to false
+  expandOneStreamToTwoRows: false # optional, defaults to true
+```

docs/widgets/services/trilium.md

@@ -0,0 +1,19 @@
+---
+title: Trilium
+description: Trilium Widget Configuration
+---
+
+Learn more about [Trilium](https://github.com/TriliumNext/Notes).
+
+This widget is compatible with [TriliumNext](https://github.com/TriliumNext/Notes) versions >= [v0.94.0](https://github.com/TriliumNext/Notes/releases/tag/v0.94.0).
+
+Find (or create) your ETAPI key under `Options > ETAPI > Create new ETAPI token`.
+
+Allowed fields: `["version", "notesCount", "dbSize"]`
+
+```yaml
+widget:
+  type: trilium
+  url: https://trilium.host.or.ip
+  key: etapi_token
+```

docs/widgets/services/truenas.md

@@ -5,6 +5,11 @@ description: TrueNas Scale Widget Configuration
 
 Learn more about [TrueNas](https://www.truenas.com/).
 
+| TrueNAS Version         | Homepage widget version |
+| ----------------------- | ----------------------- |
+| < 26.04 (REST API)      | 1 (default)             |
+| > 25.04 (Websocket API) | 2                       |
+
 Allowed fields: `["load", "uptime", "alerts"]`.
 
 To create an API Key, follow [the official TrueNAS documentation](https://www.truenas.com/docs/scale/scaletutorials/toptoolbar/managingapikeys/).
@@ -17,6 +22,7 @@ To use the `enablePools` option with TrueNAS Core, the `nasType` parameter is re
 widget:
   type: truenas
   url: http://truenas.host.or.ip
+  version: 2 # optional, defaults to 1
   username: user # not required if using api key
   password: pass # not required if using api key
   key: yourtruenasapikey # not required if using username / password

docs/widgets/services/unifi-controller.md

@@ -17,7 +17,7 @@ An optional 'site' parameter can be supplied, if it is not the widget will use t
 
 Allowed fields: `["uptime", "wan", "lan", "lan_users", "lan_devices", "wlan", "wlan_users", "wlan_devices"]` (maximum of four). Fields unsupported by the unifi device will not be shown.
 
-!!! hint
+!!! tip
 
     If you enter e.g. incorrect credentials and receive an "API Error", you may need to recreate the container or restart the service to clear the cache.
 

docs/widgets/services/unifi-drive.md

@@ -0,0 +1,24 @@
+---
+title: UniFi Drive
+description: UniFi Drive Widget Configuration
+---
+
+Learn more about [UniFi Drive](https://ui.com/integrations/network-storage).
+
+## Configuration
+
+Displays storage statistics from your UniFi Network Attached Storage (UNAS) device. Requires a local UniFi account with at least read privileges.
+
+Allowed fields: `["total", "used", "available", "status"]`
+
+```yaml
+widget:
+  type: unifi_drive
+  url: https://unifi.host.or.ip
+  username: your_username
+  password: your_password
+```
+
+!!! tip
+
+    If you enter incorrect credentials and receive an "API Error", you may need to recreate the container or restart the service to clear the cache.

docs/widgets/services/unraid.md

@@ -0,0 +1,28 @@
+---
+title: Unraid
+description: Unraid Widget Configuration
+---
+
+Learn more about [Unraid](https://unraid.net/).
+
+The Unraid widget allows you to monitor the resources of an Unraid server.
+
+**Minimum Requirements:**
+
+- Unraid 7.2 -or- Unraid Connect plugin 2025.08.19.1850
+- API key with the **ADMIN** role: [Managing API Keys](https://docs.unraid.net/go/managing-api-keys)
+
+The widget can display metrics for selected Unraid pools. If using one of the "pool" fields, you must also add the pool name to the settings.
+
+**Allowed fields:** `["cpu","memoryPercent","memoryAvailable","memoryUsed","notifications","arrayFree","arrayUsedSpace","arrayUsedPercent","status","pool1UsedSpace","pool1FreeSpace","pool1UsedPercent","pool2UsedSpace","pool2FreeSpace","pool2UsedPercent","pool3UsedSpace","pool3FreeSpace","pool3UsedPercent","pool4UsedSpace","pool4FreeSpace","pool4UsedPercent"]`
+
+```yaml
+widget:
+  type: unraid
+  url: https://unraid.host.or.ip
+  key: api-key
+  pool1: pool1name # required only if using pool1 fields
+  pool2: pool2name # required only if using pool2 fields
+  pool3: pool3name # required only if using pool3 fields
+  pool4: pool4name # required only if using pool4 fields
+```