Update README.md

.github/PULL_REQUEST_TEMPLATE.md

@@ -25,7 +25,7 @@ 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](https://gethomepage.dev/latest/more/development/#new-feature-guidelines) and / or [service widget guidelines](https://gethomepage.dev/latest/more/development/#service-widget-guidelines).
-- [ ] I have checked that all code style checks pass using [pre-commit hooks](https://gethomepage.dev/latest/more/development/#code-formatting-with-pre-commit-hooks) and [linting checks](https://gethomepage.dev/latest/more/development/#code-linting).
+- [ ] If adding a service widget or a change that requires it, I have added corresponding documentation changes.
+- [ ] If adding a new widget I have reviewed the [guidelines](https://gethomepage.dev/latest/more/development/#service-widget-guidelines).
+- [ ] If applicable, I have checked that all tests pass with e.g. `pnpm lint`.
 - [ ] If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.

.github/workflows/crowdin.yml

@@ -1,31 +0,0 @@
-name: Crowdin Action
-
-on:
-  workflow_dispatch:
-  schedule:
-    - cron: '2 */12 * * *'
-  push:
-    paths: [
-      '/public/locales/en/**',
-    ]
-    branches: [ main ]
-
-jobs:
-  synchronize-with-crowdin:
-    name: Crowdin Sync
-    runs-on: ubuntu-latest
-
-    steps:
-    - name: Checkout
-      uses: actions/checkout@v4
-    - name: crowdin action
-      uses: crowdin/github-action@v1
-      with:
-        upload_translations: false
-        download_translations: true
-        crowdin_branch_name: main
-        localization_branch_name: l10n_main
-      env:
-        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID }}
-        CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}

.github/workflows/docker-publish.yml

@@ -9,9 +9,7 @@ on:
   schedule:
     - cron: '20 0 * * *'
   push:
-    branches:
-      - main
-      - feature/**
+    branches: [ "main" ]
     # Publish semver tags as releases.
     tags: [ 'v*.*.*' ]
     paths-ignore:
@@ -32,28 +30,10 @@ env:
 
 
 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.0
-
   build:
     name: Docker Build & Push
     if:  github.repository == 'gethomepage/homepage'
     runs-on: self-hosted
-    needs:
-      - pre-commit
     permissions:
       contents: read
       packages: write
@@ -68,7 +48,7 @@ jobs:
       # Install the cosign tool except on PR
       # https://github.com/sigstore/cosign-installer
       - name: Install cosign
-        if: github.event_name != 'pull_request'
+        if: github.event_name != 'pull_request' 
         uses: sigstore/cosign-installer@main
         with:
           cosign-release: 'v1.13.1' # optional
@@ -77,11 +57,11 @@ jobs:
       # https://github.com/marketplace/actions/docker-setup-buildx#with-qemu
       - name: Setup QEMU
         uses: docker/setup-qemu-action@v3
-
+      
       # Workaround: https://github.com/docker/build-push-action/issues/461
       - name: Setup Docker buildx
         uses: docker/setup-buildx-action@v3
-
+        
       # This step is being disabled because the runner is on a self-hosted machine
       # where the cache will stick between runs.
       # - name: Cache Docker layers
@@ -119,7 +99,7 @@ jobs:
         uses: docker/build-push-action@v5
         with:
           context: .
-          push: ${{ github.event_name != 'pull_request' && !(github.event_name == 'push' && startsWith(github.ref, 'refs/heads/feature')) }}
+          push: ${{ github.event_name != 'pull_request' }}
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}
           build-args: |

.github/workflows/docs-publish.yml

@@ -18,31 +18,13 @@ permissions:
   contents: 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.0
-
   test:
     name: Test Build
     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/setup-python@v4
         with:
           python-version: 3.x
       - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV
@@ -58,16 +40,14 @@ jobs:
       - name: Test Docs Build
         run: MKINSIDERS=false mkdocs build
   deploy:
-    name: Build & Deploy
+    name: Build & Deploy 
     if: github.repository == 'gethomepage/homepage' && github.event_name != 'pull_request'
     runs-on: ubuntu-latest
-    needs:
-      - pre-commit
     steps:
       - uses: actions/checkout@v4
         with:
           ref: main
-      - uses: actions/setup-python@v5
+      - uses: actions/setup-python@v4
         with:
           python-version: 3.x
       - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV
@@ -78,7 +58,7 @@ jobs:
           restore-keys: |
             mkdocs-material-
       - run: sudo apt-get install pngquant
-      - run: pip install mike==1.1.2
+      - run: pip install mike
       - run: pip install git+https://${GH_TOKEN}@github.com/benphelps/mkdocs-material-insiders.git
       - name: Set Git config
         run: |

.pre-commit-config.yaml

@@ -1,19 +0,0 @@
-# See https://pre-commit.com for more information
-# See https://pre-commit.com/hooks.html for more hooks
-repos:
--   repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v3.2.0
-    hooks:
-    -   id: trailing-whitespace
-    -   id: end-of-file-fixer
-    -   id: check-yaml
-        exclude: "(^mkdocs\\.yml$)"
-    -   id: check-added-large-files
--   repo: https://github.com/pre-commit/mirrors-prettier
-    rev: 'v3.0.3'
-    hooks:
-    -   id: prettier
-        types_or:
-          - javascript
-          - markdown
-          - jsx

.prettierrc

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

CODE_OF_CONDUCT.md

@@ -17,23 +17,23 @@ diverse, inclusive, and healthy community.
 Examples of behavior that contributes to a positive environment for our
 community include:
 
-- Demonstrating empathy and kindness toward other people
-- Being respectful of differing opinions, viewpoints, and experiences
-- Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing to those affected by our mistakes,
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
   and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the
+* Focusing on what is best not just for us as individuals, but for the
   overall community
 
 Examples of unacceptable behavior include:
 
-- The use of sexualized language or imagery, and sexual attention or
+* The use of sexualized language or imagery, and sexual attention or
   advances of any kind
-- Trolling, insulting or derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or email
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
   address, without their explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
+* Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Enforcement Responsibilities
@@ -106,7 +106,7 @@ Violating these terms may lead to a permanent ban.
 ### 4. Permanent Ban
 
 **Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
+standards, including sustained inappropriate behavior,  harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 
 **Consequence**: A permanent ban from any sort of public interaction within

CONTRIBUTING.md

@@ -1,5 +1,4 @@
 # Contributing to Homepage
-
 We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
 
 - Reporting a bug
@@ -9,20 +8,16 @@ We love your input! We want to make contributing to this project as easy and tra
 - Becoming a maintainer
 
 ## We Develop with Github
-
 We use github to host code, to track issues and feature requests, as well as accept pull requests.
 
 ## Any contributions you make will be under the GNU General Public License v3.0
-
 In short, when you submit code changes, your submissions are understood to be under the same [GNU General Public License v3.0](https://choosealicense.com/licenses/gpl-3.0/) that covers the project. Feel free to contact the maintainers if that's a concern.
 
 ## Report bugs using Github's [issues](https://github.com/gethomepage/homepage/issues)
-
 We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/gethomepage/homepage/issues/new); it's that easy!
 
 ## Write bug reports with detail, background, and sample configurations
-
-Homepage includes a lot of configuration options and is often deploying in larger systems. Please include as much information (configurations, deployment method, Docker & API versions, etc) as you can when reporting an issue.
+Homepage includes a lot of configuration options and is often deploying in larger systems.  Please include as much information (configurations, deployment method, Docker & API versions, etc) as you can when reporting an issue.
 
 **Great Bug Reports** tend to have:
 
@@ -34,20 +29,16 @@ Homepage includes a lot of configuration options and is often deploying in large
 - What actually happens
 - Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
 
-People _love_ thorough bug reports. I'm not even kidding.
+People *love* thorough bug reports. I'm not even kidding.
 
 ## Development Guidelines
-
 Please see the [documentation regarding development](https://gethomepage.dev/latest/more/development/) and specifically the [guidelines for new service widgets](https://gethomepage.dev/latest/more/development/#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/latest/more/development/#code-formatting-with-pre-commit-hooks).
+This project follows the [Airbnb JavaScript Style Guide](https://github.com/airbnb/javascript), please follow it when submitting pull requests.
 
 ## License
-
 By contributing, you agree that your contributions will be licensed under its GNU General Public License.
 
 ## References
-
 This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/main/CONTRIBUTING.md)

README.md

@@ -20,8 +20,6 @@
    
   <a href="https://discord.gg/k4ruYNrudu"><img alt="Discord" src="https://img.shields.io/discord/1019316731635834932"></a>
   &nbsp;
-  <a href="http://gethomepage.dev/latest/" title="Docs"><img title="Docs" src="https://github.com/gethomepage/homepage/actions/workflows/docs-publish.yml/badge.svg"/></a>
-  &nbsp;
   <a href="https://paypal.me/phelpsben" title="Donate"><img alt="GitHub Sponsors" src="https://img.shields.io/github/sponsors/benphelps"></a>
 </p>
 
@@ -45,11 +43,11 @@ Homepage has built-in support for Docker, and can automatically discover and add
 
 ## Service Widgets
 
-Homepage also has support for over 100 3rd party services, including all popular starr apps, and most popular self-hosted apps. Some examples include: Radarr, Sonarr, Lidarr, Bazarr, Ombi, Tautulli, Plex, Jellyfin, Emby, Transmission, qBittorrent, Deluge, Jackett, NZBGet, SABnzbd, etc. As well as service integrations, Homepage also has a number of information providers, sourcing information from a variety of external 3rd party APIs. See the [Service](https://gethomepage.dev/latest/widgets/) page for more information.
+Homepage also has support for over 100 3rd party services, including all popular starr apps, and most popular self-hosted apps. Some examples include: Radarr, Sonarr, Lidarr, Bazarr, Ombi, Tautulli, Plex, Jellyfin, Emby, Transmission, qBittorrent, Deluge, Jackett, NZBGet, SABnzbd, etc. As well as service integrations, Homepage also has a number of information providers, sourcing information from a variety of external 3rd party APIs. See the [Service](https://gethomepage.dev/latest/configs/service-widgets/) page for more information.
 
 ## Information Widgets
 
-Homepage has built-in support for a number of information providers, including weather, time, date, search, glances and more. System and status information presented at the top of the page. See the [Information Providers](https://gethomepage.dev/latest/widgets/) page for more information.
+Homepage has built-in support for a number of information providers, including weather, time, date, search, glances and more. System and status information presented at the top of the page. See the [Information Providers](https://gethomepage.dev/latest/configs/widgets/) page for more information.
 
 ## Customization
 
@@ -166,7 +164,7 @@ If you have any questions, suggestions, or general issues, please start a discus
 
 For bug reports, please open an issue on the [Issues](https://github.com/gethomepage/homepage/issues) page.
 
-## Contributing & Contributors
+## Contributing & Contributers
 
 Contributions are welcome! Please see the [CONTRIBUTING.md](CONTRIBUTING.md) file for more information.
 

crowdin.yml

@@ -1,6 +1,3 @@
-project_id_env: CROWDIN_PROJECT_ID
-api_token_env: CROWDIN_PERSONAL_TOKEN
-preserve_hierarchy: true
 files:
   - source: /public/locales/en/*.json
     translation: /public/locales/%osx_locale%/%original_file_name%

docs/configs/bookmarks.md

@@ -13,20 +13,20 @@ By default, the description will use the hostname of the link, but you can overr
 
 ```yaml
 - Developer:
-    - Github:
-        - abbr: GH
-          href: https://github.com/
+      - Github:
+            - abbr: GH
+              href: https://github.com/
 
 - Social:
-    - Reddit:
-        - icon: reddit.png
-          href: https://reddit.com/
-          description: The front page of the internet
+      - Reddit:
+            - icon: reddit.png
+              href: https://reddit.com/
+              description: The front page of the internet
 
 - Entertainment:
-    - YouTube:
-        - abbr: YT
-          href: https://youtube.com/
+      - YouTube:
+            - abbr: YT
+              href: https://youtube.com/
 ```
 
 <img width="1000" alt="Bookmarks" src="https://user-images.githubusercontent.com/19408/269307009-d7e45885-230f-4e07-b421-9822017ae878.png">

docs/configs/docker.md

@@ -9,8 +9,8 @@ For IP:PORT, simply make sure your Docker instance [has been configured](https:/
 
 ```yaml
 my-remote-docker:
-  host: 192.168.0.101
-  port: 2375
+    host: 192.168.0.101
+    port: 2375
 ```
 
 ## Using Docker TLS
@@ -19,12 +19,12 @@ Since Docker supports connecting with TLS and client certificate authentication,
 
 ```yaml
 my-remote-docker:
-  host: 192.168.0.101
-  port: 275
-  tls:
-    keyFile: tls/key.pem
-    caFile: tls/ca.pem
-    certFile: tls/cert.pem
+    host: 192.168.0.101
+    port: 275
+    tls:
+        keyFile: tls/key.pem
+        caFile: tls/ca.pem
+        certFile: tls/cert.pem
 ```
 
 ## Using Docker Socket Proxy
@@ -35,35 +35,35 @@ Here is an example docker-compose file that will expose the docker socket, and t
 
 ```yaml
 dockerproxy:
-  image: ghcr.io/tecnativa/docker-socket-proxy:latest
-  container_name: dockerproxy
-  environment:
-    - CONTAINERS=1 # Allow access to viewing containers
-    - SERVICES=1 # Allow access to viewing services (necessary when using Docker Swarm)
-    - TASKS=1 # Allow access to viewing tasks (necessary when using Docker Swarm)
-    - POST=0 # Disallow any POST operations (effectively read-only)
-  ports:
-    - 127.0.0.1:2375:2375
-  volumes:
-    - /var/run/docker.sock:/var/run/docker.sock:ro # Mounted as read-only
-  restart: unless-stopped
+    image: ghcr.io/tecnativa/docker-socket-proxy:latest
+    container_name: dockerproxy
+    environment:
+        - CONTAINERS=1 # Allow access to viewing containers
+        - SERVICES=1 # Allow access to viewing services (necessary when using Docker Swarm)
+        - TASKS=1 # Allow access to viewing tasks (necessary when using Docker Swarm)
+        - POST=0 # Disallow any POST operations (effectively read-only)
+    ports:
+        - 127.0.0.1:2375:2375
+    volumes:
+        - /var/run/docker.sock:/var/run/docker.sock:ro # Mounted as read-only
+    restart: unless-stopped
 
 homepage:
-  image: ghcr.io/gethomepage/homepage:latest
-  container_name: homepage
-  volumes:
-    - /path/to/config:/app/config
-  ports:
-    - 3000:3000
-  restart: unless-stopped
+    image: ghcr.io/gethomepage/homepage:latest
+    container_name: homepage
+    volumes:
+        - /path/to/config:/app/config
+    ports:
+        - 3000:3000
+    restart: unless-stopped
 ```
 
 Then, inside of your `docker.yaml` settings file, you'd configure the docker instance like so:
 
 ```yaml
 my-docker:
-  host: dockerproxy
-  port: 2375
+    host: dockerproxy
+    port: 2375
 ```
 
 ## Using Socket Directly
@@ -76,14 +76,14 @@ If you'd rather use the socket directly, first make sure that you're passing the
 
 ```yaml
 homepage:
-  image: ghcr.io/gethomepage/homepage:latest
-  container_name: homepage
-  volumes:
-    - /path/to/config:/app/config
-    - /var/run/docker.sock:/var/run/docker.sock # pass local proxy
-  ports:
-    - 3000:3000
-  restart: unless-stopped
+    image: ghcr.io/gethomepage/homepage:latest
+    container_name: homepage
+    volumes:
+        - /path/to/config:/app/config
+        - /var/run/docker.sock:/var/run/docker.sock # pass local proxy
+    ports:
+        - 3000:3000
+    restart: unless-stopped
 ```
 
 If you're using `docker run`, this would be `-v /var/run/docker.sock:/var/run/docker.sock`.
@@ -92,7 +92,7 @@ Then, inside of your `docker.yaml` settings file, you'd configure the docker ins
 
 ```yaml
 my-docker:
-  socket: /var/run/docker.sock
+    socket: /var/run/docker.sock
 ```
 
 ## Services
@@ -118,18 +118,18 @@ Below is an example of the same service entry shown above, as docker labels.
 
 ```yaml
 services:
-  emby:
-    image: lscr.io/linuxserver/emby:latest
-    container_name: emby
-    ports:
-      - 8096:8096
-    restart: unless-stopped
-    labels:
-      - homepage.group=Media
-      - homepage.name=Emby
-      - homepage.icon=emby.png
-      - homepage.href=http://emby.home/
-      - homepage.description=Media server
+    emby:
+        image: lscr.io/linuxserver/emby:latest
+        container_name: emby
+        ports:
+            - 8096:8096
+        restart: unless-stopped
+        labels:
+            - homepage.group=Media
+            - homepage.name=Emby
+            - homepage.icon=emby.png
+            - homepage.href=http://emby.home/
+            - homepage.description=Media server
 ```
 
 When your Docker instance has been properly configured, this service will be automatically discovered and added to your Homepage. **You do not need to specify the `server` or `container` values, as they will be automatically inferred.**
@@ -142,32 +142,15 @@ You may also configure widgets, along with the standard service entry, again, us
 
 ```yaml
 labels:
-  - homepage.group=Media
-  - homepage.name=Emby
-  - homepage.icon=emby.png
-  - homepage.href=http://emby.home/
-  - homepage.description=Media server
-  - homepage.widget.type=emby
-  - homepage.widget.url=http://emby.home
-  - homepage.widget.key=yourembyapikeyhere
-  - homepage.widget.fields=["field1","field2"] # optional
-```
-
-You can add specify fields for e.g. the [CustomAPI](../widgets/services/customapi.md) widget by using array-style dot notation:
-
-```yaml
-labels:
-  - homepage.group=Media
-  - homepage.name=Emby
-  - homepage.icon=emby.png
-  - homepage.href=http://emby.home/
-  - homepage.description=Media server
-  - homepage.widget.type=customapi
-  - homepage.widget.url=http://argus.service/api/v1/service/summary/emby
-  - homepage.widget.field[0].label=Deployed Version
-  - homepage.widget.field[0].field.status=deployed_version
-  - homepage.widget.field[1].label=Latest Version
-  - homepage.widget.field[1].field.status=latest_version
+    - homepage.group=Media
+    - homepage.name=Emby
+    - homepage.icon=emby.png
+    - homepage.href=http://emby.home/
+    - homepage.description=Media server
+    - homepage.widget.type=emby
+    - homepage.widget.url=http://emby.home
+    - homepage.widget.key=yourembyapikeyhere
+    - homepage.widget.fields=["field1","field2"] # optional
 ```
 
 ## Docker Swarm
@@ -176,8 +159,8 @@ Docker swarm is supported and Docker services are specified with the same `serve
 
 ```yaml
 my-docker:
-  socket: /var/run/docker.sock
-  swarm: true
+    socket: /var/run/docker.sock
+    swarm: true
 ```
 
 For the automatic service discovery to discover all services it is important that homepage should be deployed on a manager node. Set deploy requirements to the master node in your stack yaml config, e.g.
@@ -201,29 +184,13 @@ In order to detect every service within the Docker swarm it is necessary that se
 ...
 ```
 
-## Multiple Homepage Instances
-
-The optional field `instanceName` can be configured in [settings.md](settings.md#instance-name) to differentiate between multiple homepage instances.
-
-To limit a label to an instance, insert `.instance.{{instanceName}}` after the `homepage` prefix.
-
-```yaml
-labels:
-  - homepage.group=Media
-  - homepage.name=Emby
-  - homepage.icon=emby.png
-  - homepage.instance.internal.href=http://emby.lan/
-  - homepage.instance.public.href=https://emby.mydomain.com/
-  - homepage.description=Media server
-```
-
 ## Ordering
 
 As of v0.6.4 discovered services can include an optional `weight` field to determine sorting such that:
 
-- Default weight for discovered services is 0
-- Default weight for configured services is their index within their group scaled by 100, i.e. (index + 1) \* 100
-- If two items have the same weight value, then they will be sorted by name
+-   Default weight for discovered services is 0
+-   Default weight for configured services is their index within their group scaled by 100, i.e. (index + 1) \* 100
+-   If two items have the same weight value, then they will be sorted by name
 
 ## Show stats
 

docs/configs/kubernetes.md

@@ -5,15 +5,15 @@ description: Kubernetes Configuration
 
 The Kubernetes connectivity has the following requirements:
 
-- Kubernetes 1.19+
-- Metrics Service
-- An Ingress controller
+-   Kubernetes 1.19+
+-   Metrics Service
+-   An Ingress controller
 
 The Kubernetes connection is configured in the `kubernetes.yaml` file. There are 3 modes to choose from:
 
-- **disabled** - disables kubernetes connectivity
-- **default** - uses the default kubeconfig [resolution](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
-- **cluster** - uses a service account inside the cluster
+-   **disabled** - disables kubernetes connectivity
+-   **default** - uses the default kubeconfig [resolution](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
+-   **cluster** - uses a service account inside the cluster
 
 ```yaml
 mode: default
@@ -36,29 +36,29 @@ Inside of the service you'd like to connect to a pod:
 
 The `app` field is used to create a label selector, in this example case it would match pods with the label: `app.kubernetes.io/name=emby`.
 
-Sometimes this is insufficient for complex or atypical application deployments. In these cases, the `pod-selector` field can be used. Any field selector can be used with it, so it allows for some very powerful selection capabilities.
+Sometimes this is insufficient for complex or atypical application deployments. In these cases, the `podSelector` field can be used. Any field selector can be used with it, so it allows for some very powerful selection capabilities.
 
 For instance, it can be utilized to roll multiple underlying deployments under one application to see a high-level aggregate:
 
 ```yaml
 - Element Chat:
-    icon: matrix-light.png
-    href: https://chat.example.com
-    description: Matrix Synapse Powered Chat
-    app: matrix-element
-    namespace: comms
-    pod-selector: >-
-      app.kubernetes.io/instance in (
-          matrix-element,
-          matrix-media-repo,
-          matrix-media-repo-postgresql,
-          matrix-synapse
-      )
+      icon: matrix-light.png
+      href: https://chat.example.com
+      description: Matrix Synapse Powered Chat
+      app: matrix-element
+      namespace: comms
+      podSelector: >-
+          app.kubernetes.io/instance in (
+              matrix-element,
+              matrix-media-repo,
+              matrix-media-repo-postgresql,
+              matrix-synapse
+          )
 ```
 
 !!! note
 
-    A blank string as a pod-selector does not deactivate it, but will actually select all pods in the namespace. This is a useful way to capture the resource usage of a complex application siloed to a single namespace, like Longhorn.
+    A blank string as a podSelector does not deactivate it, but will actually select all pods in the namespace. This is a useful way to capture the resource usage of a complex application siloed to a single namespace, like Longhorn.
 
 ## Automatic Service Discovery
 
@@ -68,29 +68,29 @@ Homepage features automatic service discovery by Ingress annotations. All config
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
-  name: emby
-  annotations:
-    gethomepage.dev/enabled: "true"
-    gethomepage.dev/description: Media Server
-    gethomepage.dev/group: Media
-    gethomepage.dev/icon: emby.png
-    gethomepage.dev/name: Emby
-    gethomepage.dev/widget.type: "emby"
-    gethomepage.dev/widget.url: "https://emby.example.com"
-    gethomepage.dev/pod-selector: ""
-    gethomepage.dev/weight: 10 # optional
+    name: emby
+    annotations:
+        gethomepage.dev/enabled: "true"
+        gethomepage.dev/description: Media Server
+        gethomepage.dev/group: Media
+        gethomepage.dev/icon: emby.png
+        gethomepage.dev/name: Emby
+        gethomepage.dev/widget.type: "emby"
+        gethomepage.dev/widget.url: "https://emby.example.com"
+        gethomepage.dev/podSelector: ""
+        gethomepage.dev/weight: 10 # optional
 spec:
-  rules:
-    - host: emby.example.com
-      http:
-        paths:
-          - backend:
-              service:
-                name: emby
-                port:
-                  number: 8080
-            path: /
-            pathType: Prefix
+    rules:
+        - host: emby.example.com
+          http:
+              paths:
+                  - backend:
+                        service:
+                            name: emby
+                            port:
+                                number: 8080
+                    path: /
+                    pathType: Prefix
 ```
 
 When the Kubernetes cluster connection has been properly configured, this service will be automatically discovered and added to your Homepage. **You do not need to specify the `namespace` or `app` values, as they will be automatically inferred.**
@@ -103,33 +103,32 @@ Homepage can also read ingresses defined using the Traefik IngressRoute custom r
 apiVersion: traefik.io/v1alpha1
 kind: IngressRoute
 metadata:
-  name: emby
-  annotations:
-    gethomepage.dev/href: "https://emby.example.com"
-    gethomepage.dev/enabled: "true"
-    gethomepage.dev/description: Media Server
-    gethomepage.dev/group: Media
-    gethomepage.dev/icon: emby.png
-    gethomepage.dev/app: emby-app # optional, may be needed if app.kubernetes.io/name != ingress metadata.name
-    gethomepage.dev/name: Emby
-    gethomepage.dev/widget.type: "emby"
-    gethomepage.dev/widget.url: "https://emby.example.com"
-    gethomepage.dev/pod-selector: ""
-    gethomepage.dev/weight: 10 # optional
+    name: emby
+    annotations:
+        gethomepage.dev/href: "https://emby.example.com"
+        gethomepage.dev/enabled: "true"
+        gethomepage.dev/description: Media Server
+        gethomepage.dev/group: Media
+        gethomepage.dev/icon: emby.png
+        gethomepage.dev/name: Emby
+        gethomepage.dev/widget.type: "emby"
+        gethomepage.dev/widget.url: "https://emby.example.com"
+        gethomepage.dev/podSelector: ""
+        gethomepage.dev/weight: 10 # optional
 spec:
-  entryPoints:
-    - websecure
-  routes:
-    - kind: Rule
-      match: Host(`emby.example.com`)
-      services:
-        - kind: Service
-          name: emby
-          namespace: emby
-          port: 8080
-          scheme: http
-          strategy: RoundRobin
-          weight: 10
+    entryPoints:
+        - websecure
+    routes:
+        - kind: Rule
+          match: Host(`emby.example.com`)
+          services:
+              - kind: Service
+                name: emby
+                namespace: emby
+                port: 8080
+                scheme: http
+                strategy: RoundRobin
+                weight: 10
 ```
 
 If the `href` attribute is not present, Homepage will ignore the specific IngressRoute.

docs/configs/service-widgets.md

@@ -5,7 +5,7 @@ description: Service Widget Configuration
 
 Unless otherwise noted, URLs should not end with a `/` or other API path. Each widget will handle the path on its own.
 
-Each service can have one widget attached to it (often matching the service type, but that's not forced).
+Each service can have one widget attached to it (often matching the service type, but thats not forced).
 
 In addition to the href of the service, you can also specify the target location in which to open that link. See [Link Target](settings.md#link-target) for more details.
 
@@ -13,13 +13,13 @@ Using Emby as an example, this is how you would attach the Emby service widget.
 
 ```yaml
 - Emby:
-    icon: emby.png
-    href: http://emby.host.or.ip/
-    description: Movies & TV Shows
-    widget:
-      type: emby
-      url: http://emby.host.or.ip
-      key: apikeyapikeyapikeyapikeyapikey
+      icon: emby.png
+      href: http://emby.host.or.ip/
+      description: Movies & TV Shows
+      widget:
+          type: emby
+          url: http://emby.host.or.ip
+          key: apikeyapikeyapikeyapikeyapikey
 ```
 
 ## Field Visibility
@@ -30,11 +30,11 @@ Each widget can optionally provide a list of which fields should be visible via
 
 ```yaml
 - Sonarr:
-    icon: sonarr.png
-    href: http://sonarr.host.or.ip
-    widget:
-      type: sonarr
-      fields: ["wanted", "queued"]
-      url: http://sonarr.host.or.ip
-      key: apikeyapikeyapikeyapikeyapikey
+      icon: sonarr.png
+      href: http://sonarr.host.or.ip
+      widget:
+          type: sonarr
+          fields: ["wanted", "queued"]
+          url: http://sonarr.host.or.ip
+          key: apikeyapikeyapikeyapikeyapikey
 ```

docs/configs/services.md

@@ -101,50 +101,30 @@ To use a local icon, first create a Docker mount to `/app/public/icons` and then
 
 ## Ping
 
-Services may have an optional `ping` property that allows you to monitor the availability of an external host. As of v0.8.0, the ping feature attempts to use a true (ICMP) ping command on the underlying host.
+Services may have an optional `ping` property that allows you to monitor the availability of an endpoint you chose and have the response time displayed. You do not need to set your ping URL equal to your href URL.
+
+!!! note
+
+    The ping feature works by making an http `HEAD` request to the URL, and falls back to `GET` in case that fails. It will not, for example, login if the URL requires auth or is behind e.g. Authelia. In the case of a reverse proxy and/or auth this usually requires the use of an 'internal' URL to make the ping feature correctly display status.
 
 ```yaml
 - Group A:
     - Sonarr:
         icon: sonarr.png
         href: http://sonarr.host/
-        ping: sonarr.host
+        ping: http://sonarr.host/
 
 - Group B:
     - Radarr:
         icon: radarr.png
         href: http://radarr.host/
-        ping: some.other.host
+        ping: http://some.other.host/
 ```
 
 <img width="1038" alt="Ping" src="https://github.com/gethomepage/homepage/assets/88257202/7bc13bd3-0d0b-44e3-888c-a20e069a3233">
 
 You can also apply different styles to the ping indicator by using the `statusStyle` property, see [settings](settings.md#status-style).
 
-## Site Monitor
-
-Services may have an optional `siteMonitor` property (formerly `ping`) that allows you to monitor the availability of a URL you chose and have the response time displayed. You do not need to set your monitor URL equal to your href or ping URL.
-
-!!! note
-
-    The site monitor feature works by making an http `HEAD` request to the URL, and falls back to `GET` in case that fails. It will not, for example, login if the URL requires auth or is behind e.g. Authelia. In the case of a reverse proxy and/or auth this usually requires the use of an 'internal' URL to make the site monitor feature correctly display status.
-
-```yaml
-- Group A:
-    - Sonarr:
-        icon: sonarr.png
-        href: http://sonarr.host/
-        siteMonitor: http://sonarr.host/
-
-- Group B:
-    - Radarr:
-        icon: radarr.png
-        href: http://radarr.host/
-        siteMonitor: http://some.other.host/
-```
-
-You can also apply different styles to the site monitor indicator by using the `statusStyle` property, see [settings](settings.md#status-style).
-
 ## Docker Integration
 
 Services may be connected to a Docker container, either running on the local machine, or a remote machine.

docs/configs/settings.md

@@ -67,7 +67,7 @@ background:
 
 ### Card Background Blur
 
-You can apply a blur filter to the service & bookmark cards. Note this option is incompatible with the background blur, saturate and brightness filters.
+You can apply a blur filter to the service & bookmark cards. Note this option is incompatible with the backround blur, saturate and brightness filters.
 
 ```yaml
 cardBlur: sm # sm, "", md, etc... see https://tailwindcss.com/docs/backdrop-blur
@@ -229,28 +229,6 @@ disableCollapse: true
 
 By default the feature is enabled.
 
-### Use Equal Height Cards
-
-You can enable equal height cards for groups of services, this will make all cards in a row the same height.
-
-Global setting in `settings.yaml`:
-
-```yaml
-useEqualHeights: true
-```
-
-Per layout group in `settings.yaml`:
-
-```yaml
-useEqualHeights: false
-layout:
-  ...
-  Group Name:
-    useEqualHeights: true # overrides global setting
-```
-
-By default the feature is disabled
-
 ## Header Style
 
 There are currently 4 options for header styles, you can see each one below.
@@ -351,7 +329,7 @@ You can then pass `provider` instead of `apiKey` in your widget configuration.
 
 ## Quick Launch
 
-You can use the 'Quick Launch' feature to search services, perform a web search or open a URL. To use Quick Launch, just start typing while on your homepage (as long as the search widget doesn't have focus).
+You can use the 'Quick Launch' feature to search services, perform a web search or open a URL. To use Quick Launch, just start typing while on your homepage (as long as the search widget doesnt have focus).
 
 <img width="1000" alt="quicklaunch" src="https://user-images.githubusercontent.com/4887959/216880811-90ff72cb-2990-4475-889b-7c3a31e6beef.png">
 
@@ -404,16 +382,16 @@ If you have both set the per-service settings take precedence.
 
 ## Status Style
 
-You can choose from the following styles for docker or k8s status, site monitor and ping: `dot` or `basic`
+You can choose from the following styles for docker or k8s status and ping: `dot` or `basic`
 
-- The default is no value, and displays the monitor and ping response time in ms and the docker / k8s container status
-- `dot` shows a green dot for a successful monitor ping or healthy status.
-- `basic` shows either UP or DOWN for monitor & ping
+- The default is no value, and displays the ping response time in ms and the docker / k8s container status
+- `dot` shows a green dot for a successful ping or healthy status.
+- `basic` shows either UP or DOWN for ping
 
 For example:
 
 ```yaml
-statusStyle: "dot"
+statusStyle: 'dot'
 ```
 
 or per-service (`services.yaml`) with:
@@ -426,16 +404,6 @@ or per-service (`services.yaml`) with:
 
 If you have both set, the per-service settings take precedence.
 
-## Instance Name
-
-Name used by automatic docker service discovery to differentiate between multiple homepage instances.
-
-For example:
-
-```yaml
-instanceName: public
-```
-
 ## Hide Widget Error Messages
 
 Hide the visible API error messages either globally in `settings.yaml`:
@@ -454,4 +422,4 @@ or per service widget (`services.yaml`) with:
         hideErrors: true
 ```
 
-If either value is set to true, the error message will be hidden.
+If either value is set to true, the errror message will be hidden.

docs/installation/docker.md

@@ -8,14 +8,14 @@ Using docker compose:
 ```yaml
 version: "3.3"
 services:
-  homepage:
-    image: ghcr.io/gethomepage/homepage:latest
-    container_name: homepage
-    ports:
-      - 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
+    homepage:
+        image: ghcr.io/gethomepage/homepage:latest
+        container_name: homepage
+        ports:
+            - 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
 ```
 
 ### Running as non-root
@@ -29,17 +29,17 @@ In the docker compose example below, the environment variables `$PUID` and `$PGI
 ```yaml
 version: "3.3"
 services:
-  homepage:
-    image: ghcr.io/gethomepage/homepage:latest
-    container_name: homepage
-    ports:
-      - 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
-    environment:
-      PUID: $PUID
-      PGID: $PGID
+    homepage:
+        image: ghcr.io/gethomepage/homepage:latest
+        container_name: homepage
+        ports:
+            - 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
+        environment:
+            PUID: $PUID
+            PGID: $PGID
 ```
 
 ### With Docker Run
@@ -52,6 +52,6 @@ docker run -p 3000:3000 -v /path/to/config:/app/config -v /var/run/docker.sock:/
 
 You can also include environment variables in your config files to protect sensitive information. Note:
 
-- Environment variables must start with `HOMEPAGE_VAR_` or `HOMEPAGE_FILE_`
-- The value of env var `HOMEPAGE_VAR_XXX` will replace `{{HOMEPAGE_VAR_XXX}}` in any config
-- The value of env var `HOMEPAGE_FILE_XXX` must be a file path, the contents of which will be used to replace `{{HOMEPAGE_FILE_XXX}}` in any config
+-   Environment variables must start with `HOMEPAGE_VAR_` or `HOMEPAGE_FILE_`
+-   The value of env var `HOMEPAGE_VAR_XXX` will replace `{{HOMEPAGE_VAR_XXX}}` in any config
+-   The value of env var `HOMEPAGE_FILE_XXX` must be a file path, the contents of which will be used to replace `{{HOMEPAGE_FILE_XXX}}` in any config

docs/installation/k8s.md

@@ -16,70 +16,70 @@ The helm chart allows for all the configurations to be inlined directly in your
 
 ```yaml
 config:
-  bookmarks:
-    - Developer:
-        - Github:
-            - abbr: GH
-              href: https://github.com/
-  services:
-    - My First Group:
-        - My First Service:
-            href: http://localhost/
-            description: Homepage is awesome
+    bookmarks:
+        - Developer:
+              - Github:
+                    - abbr: GH
+                      href: https://github.com/
+    services:
+        - My First Group:
+              - My First Service:
+                    href: http://localhost/
+                    description: Homepage is awesome
 
-    - My Second Group:
-        - My Second Service:
-            href: http://localhost/
-            description: Homepage is the best
+        - My Second Group:
+              - My Second Service:
+                    href: http://localhost/
+                    description: Homepage is the best
 
-    - My Third Group:
-        - My Third Service:
-            href: http://localhost/
-            description: Homepage is 😎
-  widgets:
-    # show the kubernetes widget, with the cluster summary and individual nodes
-    - kubernetes:
-        cluster:
-          show: true
-          cpu: true
-          memory: true
-          showLabel: true
-          label: "cluster"
-        nodes:
-          show: true
-          cpu: true
-          memory: true
-          showLabel: true
-    - search:
-        provider: duckduckgo
-        target: _blank
-  kubernetes:
-    mode: cluster
-  settings:
+        - My Third Group:
+              - My Third Service:
+                    href: http://localhost/
+                    description: Homepage is 😎
+    widgets:
+        # show the kubernetes widget, with the cluster summary and individual nodes
+        - kubernetes:
+              cluster:
+                  show: true
+                  cpu: true
+                  memory: true
+                  showLabel: true
+                  label: "cluster"
+              nodes:
+                  show: true
+                  cpu: true
+                  memory: true
+                  showLabel: true
+        - search:
+              provider: duckduckgo
+              target: _blank
+    kubernetes:
+        mode: cluster
+    settings:
 
 # The service account is necessary to allow discovery of other services
 serviceAccount:
-  create: true
-  name: homepage
+    create: true
+    name: homepage
 
 # This enables the service account to access the necessary resources
 enableRbac: true
 
 ingress:
-  main:
-    enabled: true
-    annotations:
-      # Example annotations to add Homepage to your Homepage!
-      gethomepage.dev/enabled: "true"
-      gethomepage.dev/name: "Homepage"
-      gethomepage.dev/description: "Dynamically Detected Homepage"
-      gethomepage.dev/group: "Dynamic"
-      gethomepage.dev/icon: "homepage.png"
-    hosts:
-      - host: homepage.example.com
-        paths:
-          - path: /
-            pathType: Prefix
+    main:
+        enabled: true
+        annotations:
+            # Example annotations to add Homepage to your Homepage!
+            gethomepage.dev/enabled: "true"
+            gethomepage.dev/name: "Homepage"
+            gethomepage.dev/description: "Dynamically Detected Homepage"
+            gethomepage.dev/group: "Dynamic"
+            gethomepage.dev/icon: "homepage.png"
+        hosts:
+            - host: homepage.example.com
+              paths:
+                  - path: /
+                    pathType: Prefix
 ```
 
 ## Install with Kubernetes Manifests
@@ -94,12 +94,12 @@ Here's a working example of the resources you need:
 apiVersion: v1
 kind: ServiceAccount
 metadata:
-  name: homepage
-  namespace: default
-  labels:
-    app.kubernetes.io/name: homepage
+    name: homepage
+    namespace: default
+    labels:
+        app.kubernetes.io/name: homepage
 secrets:
-  - name: homepage
+    - name: homepage
 ```
 
 #### Secret
@@ -109,12 +109,12 @@ apiVersion: v1
 kind: Secret
 type: kubernetes.io/service-account-token
 metadata:
-  name: homepage
-  namespace: default
-  labels:
-    app.kubernetes.io/name: homepage
-  annotations:
-    kubernetes.io/service-account.name: homepage
+    name: homepage
+    namespace: default
+    labels:
+        app.kubernetes.io/name: homepage
+    annotations:
+        kubernetes.io/service-account.name: homepage
 ```
 
 #### ConfigMap
@@ -123,62 +123,62 @@ metadata:
 apiVersion: v1
 kind: ConfigMap
 metadata:
-  name: homepage
-  namespace: default
-  labels:
-    app.kubernetes.io/name: homepage
+    name: homepage
+    namespace: default
+    labels:
+        app.kubernetes.io/name: homepage
 data:
-  kubernetes.yaml: |
-    mode: cluster
-  settings.yaml: ""
-  #settings.yaml: |
-  #  providers:
-  #    longhorn:
-  #      url: https://longhorn.my.network
-  custom.css: ""
-  custom.js: ""
-  bookmarks.yaml: |
-    - Developer:
-        - Github:
-            - abbr: GH
-              href: https://github.com/
-  services.yaml: |
-    - My First Group:
-        - My First Service:
-            href: http://localhost/
-            description: Homepage is awesome
+    kubernetes.yaml: |
+        mode: cluster
+    settings.yaml: ""
+    #settings.yaml: |
+    #  providers:
+    #    longhorn:
+    #      url: https://longhorn.my.network
+    custom.css: ""
+    custom.js: ""
+    bookmarks.yaml: |
+        - Developer:
+            - Github:
+                - abbr: GH
+                  href: https://github.com/
+    services.yaml: |
+        - My First Group:
+            - My First Service:
+                href: http://localhost/
+                description: Homepage is awesome
 
-    - My Second Group:
-        - My Second Service:
-            href: http://localhost/
-            description: Homepage is the best
+        - My Second Group:
+            - My Second Service:
+                href: http://localhost/
+                description: Homepage is the best
 
-    - My Third Group:
-        - My Third Service:
-            href: http://localhost/
-            description: Homepage is 😎
-  widgets.yaml: |
-    - kubernetes:
-        cluster:
-          show: true
-          cpu: true
-          memory: true
-          showLabel: true
-          label: "cluster"
-        nodes:
-          show: true
-          cpu: true
-          memory: true
-          showLabel: true
-    - resources:
-        backend: resources
-        expanded: true
-        cpu: true
-        memory: true
-    - search:
-        provider: duckduckgo
-        target: _blank
-  docker.yaml: ""
+        - My Third Group:
+            - My Third Service:
+                href: http://localhost/
+                description: Homepage is 😎
+    widgets.yaml: |
+        - kubernetes:
+            cluster:
+              show: true
+              cpu: true
+              memory: true
+              showLabel: true
+              label: "cluster"
+            nodes:
+              show: true
+              cpu: true
+              memory: true
+              showLabel: true
+        - resources:
+            backend: resources
+            expanded: true
+            cpu: true
+            memory: true
+        - search:
+            provider: duckduckgo
+            target: _blank
+    docker.yaml: ""
 ```
 
 #### ClusterRole and ClusterRoleBinding
@@ -187,57 +187,57 @@ data:
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
 metadata:
-  name: homepage
-  labels:
-    app.kubernetes.io/name: homepage
+    name: homepage
+    labels:
+        app.kubernetes.io/name: homepage
 rules:
-  - apiGroups:
-      - ""
-    resources:
-      - namespaces
-      - pods
-      - nodes
-    verbs:
-      - get
-      - list
-  - apiGroups:
-      - extensions
-      - networking.k8s.io
-    resources:
-      - ingresses
-    verbs:
-      - get
-      - list
-  - apiGroups:
-      - traefik.containo.us
-    resources:
-      - ingressroutes
-    verbs:
-      - get
-      - list
-  - apiGroups:
-      - metrics.k8s.io
-    resources:
-      - nodes
-      - pods
-    verbs:
-      - get
-      - list
+    - apiGroups:
+          - ""
+      resources:
+          - namespaces
+          - pods
+          - nodes
+      verbs:
+          - get
+          - list
+    - apiGroups:
+          - extensions
+          - networking.k8s.io
+      resources:
+          - ingresses
+      verbs:
+          - get
+          - list
+    - apiGroups:
+          - traefik.containo.us
+      resources:
+          - ingressroutes
+      verbs:
+          - get
+          - list
+    - apiGroups:
+          - metrics.k8s.io
+      resources:
+          - nodes
+          - pods
+      verbs:
+          - get
+          - list
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
 metadata:
-  name: homepage
-  labels:
-    app.kubernetes.io/name: homepage
-roleRef:
-  apiGroup: rbac.authorization.k8s.io
-  kind: ClusterRole
-  name: homepage
-subjects:
-  - kind: ServiceAccount
     name: homepage
-    namespace: default
+    labels:
+        app.kubernetes.io/name: homepage
+roleRef:
+    apiGroup: rbac.authorization.k8s.io
+    kind: ClusterRole
+    name: homepage
+subjects:
+    - kind: ServiceAccount
+      name: homepage
+      namespace: default
 ```
 
 #### Service
@@ -246,20 +246,20 @@ subjects:
 apiVersion: v1
 kind: Service
 metadata:
-  name: homepage
-  namespace: default
-  labels:
-    app.kubernetes.io/name: homepage
-  annotations:
+    name: homepage
+    namespace: default
+    labels:
+        app.kubernetes.io/name: homepage
+    annotations:
 spec:
-  type: ClusterIP
-  ports:
-    - port: 3000
-      targetPort: http
-      protocol: TCP
-      name: http
-  selector:
-    app.kubernetes.io/name: homepage
+    type: ClusterIP
+    ports:
+        - port: 3000
+          targetPort: http
+          protocol: TCP
+          name: http
+    selector:
+        app.kubernetes.io/name: homepage
 ```
 
 #### Deployment
@@ -268,68 +268,46 @@ spec:
 apiVersion: apps/v1
 kind: Deployment
 metadata:
-  name: homepage
-  namespace: default
-  labels:
-    app.kubernetes.io/name: homepage
-spec:
-  revisionHistoryLimit: 3
-  replicas: 1
-  strategy:
-    type: RollingUpdate
-  selector:
-    matchLabels:
-      app.kubernetes.io/name: homepage
-  template:
-    metadata:
-      labels:
+    name: homepage
+    namespace: default
+    labels:
         app.kubernetes.io/name: homepage
-    spec:
-      serviceAccountName: homepage
-      automountServiceAccountToken: true
-      dnsPolicy: ClusterFirst
-      enableServiceLinks: true
-      containers:
-        - name: homepage
-          image: "ghcr.io/gethomepage/homepage:latest"
-          imagePullPolicy: Always
-          ports:
-            - name: http
-              containerPort: 3000
-              protocol: TCP
-          volumeMounts:
-            - mountPath: /app/config/custom.js
-              name: homepage-config
-              subPath: custom.js
-            - mountPath: /app/config/custom.css
-              name: homepage-config
-              subPath: custom.css
-            - mountPath: /app/config/bookmarks.yaml
-              name: homepage-config
-              subPath: bookmarks.yaml
-            - mountPath: /app/config/docker.yaml
-              name: homepage-config
-              subPath: docker.yaml
-            - mountPath: /app/config/kubernetes.yaml
-              name: homepage-config
-              subPath: kubernetes.yaml
-            - mountPath: /app/config/services.yaml
-              name: homepage-config
-              subPath: services.yaml
-            - mountPath: /app/config/settings.yaml
-              name: homepage-config
-              subPath: settings.yaml
-            - mountPath: /app/config/widgets.yaml
-              name: homepage-config
-              subPath: widgets.yaml
-            - mountPath: /app/config/logs
-              name: logs
-      volumes:
-        - name: homepage-config
-          configMap:
-            name: homepage
-        - name: logs
-          emptyDir: {}
+spec:
+    revisionHistoryLimit: 3
+    replicas: 1
+    strategy:
+        type: RollingUpdate
+    selector:
+        matchLabels:
+            app.kubernetes.io/name: homepage
+    template:
+        metadata:
+            labels:
+                app.kubernetes.io/name: homepage
+        spec:
+            serviceAccountName: homepage
+            automountServiceAccountToken: true
+            dnsPolicy: ClusterFirst
+            enableServiceLinks: true
+            containers:
+                - name: homepage
+                  image: "ghcr.io/gethomepage/homepage:latest"
+                  imagePullPolicy: Always
+                  ports:
+                      - name: http
+                        containerPort: 3000
+                        protocol: TCP
+                  volumeMounts:
+                      - name: homepage-config
+                        mountPath: /app/config
+                      - name: logs
+                        mountPath: /app/config/logs
+            volumes:
+                - name: homepage-config
+                  configMap:
+                      name: homepage
+                - name: logs
+                  emptyDir: {}
 ```
 
 #### Ingress
@@ -338,26 +316,26 @@ spec:
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
-  name: homepage
-  namespace: default
-  labels:
-    app.kubernetes.io/name: homepage
-  annotations:
-    gethomepage.dev/description: Dynamically Detected Homepage
-    gethomepage.dev/enabled: "true"
-    gethomepage.dev/group: Cluster Management
-    gethomepage.dev/icon: homepage.png
-    gethomepage.dev/name: Homepage
+    name: homepage
+    namespace: default
+    labels:
+        app.kubernetes.io/name: homepage
+    annotations:
+        gethomepage.dev/description: Dynamically Detected Homepage
+        gethomepage.dev/enabled: "true"
+        gethomepage.dev/group: Cluster Management
+        gethomepage.dev/icon: homepage.png
+        gethomepage.dev/name: Homepage
 spec:
-  rules:
-    - host: "homepage.my.network"
-      http:
-        paths:
-          - path: "/"
-            pathType: Prefix
-            backend:
-              service:
-                name: homepage
-                port:
-                  number: 3000
+    rules:
+        - host: "homepage.my.network"
+          http:
+              paths:
+                  - path: "/"
+                    pathType: Prefix
+                    backend:
+                        service:
+                            name: homepage
+                            port:
+                                number: 3000
 ```

docs/installation/unraid.md

@@ -7,39 +7,39 @@ Homepage has an UNRAID community package that you may use to install homepage. T
 
 ## Install the Plugin
 
-- In the UNRAID webGUI, go to the **Apps** tab.
-- In the search bar, search for `homepage`.
-- Click on **Install**.
-- Change the parameters to your liking.
-  - Click on **APPLY**.
+-   In the UNRAID webGUI, go to the **Apps** tab.
+-   In the search bar, search for `homepage`.
+-   Click on **Install**.
+-   Change the parameters to your liking.
+    -   Click on **APPLY**.
 
 ## Run the Container
 
-- While the container is running, open the WebUI.
-  - Opening the page will generate the configuration files.
+-   While the container is running, open the WebUI.
+    -   Opening the page will generate the configuration files.
 
 You may need to set the permissions of the folders to be able to edit the files.
 
-- Click on the Homepage icon.
-- Click on **Console**.
-  - Enter `chmod -R u-x,go-rwx,go+u,ugo+X /app/config` and press **Enter**.
-  - Enter `chmod -R u-x,go-rwx,go+u,ugo+X /app/public/icons` and press **Enter**.
-  - Enter `chown -R nobody:users /app/config` and press **Enter**.
-  - Enter `chown -R nobody:users /app/public/icons` and press **Enter**.
+-   Click on the Homepage icon.
+-   Click on **Console**.
+    -   Enter `chmod -R u-x,go-rwx,go+u,ugo+X /app/config` and press **Enter**.
+    -   Enter `chmod -R u-x,go-rwx,go+u,ugo+X /app/public/icons` and press **Enter**.
+    -   Enter `chown -R nobody:users /app/config` and press **Enter**.
+    -   Enter `chown -R nobody:users /app/public/icons` and press **Enter**.
 
 ## Some Other Notes
 
-- To use the [Docker integration](../configs/docker.md), you only need to use the `container:` parameter. There is no need to set the server.
+-    To use the [Docker integration](../configs/docker.md), you only need to use the `container:` parameter. There is no need to set the server.
 
-  !!! note
+    !!! note
 
         To view detailed container statistics (CPU, RAM, etc.), or if you use a remote docker socket, `container:` will still need to be set. For example:
 
-  ```
-      - Plex:
-          icon: /icons/plex.png
-          href: https://app.plex.com
-          container: plex
-  ```
+    ```
+        - Plex:
+            icon: /icons/plex.png
+            href: https://app.plex.com
+            container: plex
+    ```
 
-- When you upload a new image into the **/images** folder, you will need to restart the container for it to show up in the WebUI. Please see the [service icons](../configs/services.md#icons) for more information.
+-   When you upload a new image into the **/images** folder, you will need to restart the container for it to show up in the WebUI. Please see the [service icons](../configs/services.md#icons) for more information.

docs/more/development.md

@@ -31,25 +31,12 @@ Once dependencies have been installed you can lint your code with
 pnpm lint
 ```
 
-## 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.
-
-Once installed, hooks will run when you commit. If the formatting isn't quite right, the commit will be rejected and you'll need to look at the output and fix the issue. Most hooks will automatically format failing files, so all you need to do is `git add` those files again and retry your commit.
-
-See the [pre-commit documentation](https://pre-commit.com/#install) to get started.
-
-## New Feature Guidelines
-
-- New features should be linked to an existing feature request with at least 5 'up-votes'. The purpose of this requirement is to avoid the addition (and maintenance) of features that might only benefit a small number of users.
-- If you have ideas for a larger feature, please open a discussion first.
-
 ## Service Widget Guidelines
 
 To ensure cohesiveness of various widgets, the following should be used as a guide for developing new widgets:
 
-- Please only submit widgets that have been requested and have at least 5 'up-votes'. The purpose of this requirement is to avoid the addition (and maintenance) of service widgets that might only benefit a small number of users.
-- Widgets should be only one row of blocks
-- Widgets should be no more than 4 blocks wide
-- Minimize the number of API calls
-- Avoid the use of custom proxy unless absolutely necessary
+-   Please only submit widgets that have been requested and have at least 5 'up-votes'
+-   Widgets should be only one row of blocks
+-   Widgets should be no more than 4 blocks wide
+-   Minimize the number of API calls
+-   Avoid the use of custom proxy unless absolutely necessary

docs/more/homepage-move.md

@@ -5,4 +5,4 @@ description: Homepage Container Deprecation
 
 As of v0.7.2 homepage migrated from benphelps/homepage to an "organization" repository located at [gethomepage/homepage](https://github.com/gethomepage/homepage/). The reason for this was to setup the project for longevity and allow for community maintenance.
 
-Migrating your installation should be as simple as changing `image: ghcr.io/benphelps/homepage:latest` to `image: ghcr.io/gethomepage/homepage:latest`.
+Migrating your installation should be as simple as changing `image: ghcr.io/benphelps/homepage:latest` to `image: ghcr.io/gethomepage/homepage:latest`.

docs/more/translations.md

@@ -3,7 +3,7 @@ title: Translations
 description: Contributing Translations
 ---
 
-Homepage is developed in English, component contributions must be in English. All translations are community provided, so a huge thanks go out to all those who have helped out so far!
+Homepage is developed in English, component contributions must be in English.  All translations are community provided, so a huge thanks go out to all those who have helped out so far!
 
 ## Support Translations
 

docs/more/troubleshooting.md

@@ -6,10 +6,6 @@ hide:
   - navigation
 ---
 
-## Introducing the Homepage AI Bot
-
-Thanks to the generous folks at [Glime](https://glimelab.ai), Homepage is now equipped with a pretty helpful AI-powered bot. The bot has full knowledge of our docs, GitHub issues and discussions and great at answering specific questions about setting up your Homepage. To use the bot, just hit the 'Ask AI' button on any page in our docs or check out the [#ai-support channel on Discord](https://discord.com/channels/1019316731635834932/1177885603552038993)!
-
 ## General Troubleshooting Tips
 
 - For API errors, clicking the "API Error Information" button in the widget will usually show some helpful information as to whether the issue is reaching the service host, an authentication issue, etc.
@@ -21,49 +17,47 @@ Thanks to the generous folks at [Glime](https://glimelab.ai), Homepage is now eq
 
 All service widgets work essentially the same, that is, homepage makes a proxied call to an API made available by that service. The majority of the time widgets don't work it is a configuration issue. Of course, sometimes things do break. Some basic steps to try:
 
-1.  Ensure that you follow the rule mentioned on https://gethomepage.dev/latest/configs/service-widgets/. **Unless otherwise noted, URLs should not end with a / or other API path. Each widget will handle the path on its own.**. This is very important as including a trailing slash can result in an error.
+1. Ensure that you follow the rule mentioned on https://gethomepage.dev/latest/configs/service-widgets/. **Unless otherwise noted, URLs should not end with a / or other API path. Each widget will handle the path on its own.**. This is very important as including a trailing slash can result in an error.
 
-2.  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.:
+2. 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.:
 
-    ```
-    docker exec homepage ping SERVICEIPORDOMAIN
-    ```
+   ```
+   docker exec homepage ping SERVICEIPORDOMAIN
+   ```
 
-    If your homepage install (container) cannot reach the service then you need to figure out why, for example in Docker this can mean putting the two containers on the same network, checking firewall issues, etc.
+   If your homepage install (container) cannot reach the service then you need to figure out why, for example in Docker this can mean putting the two containers on the same network, checking firewall issues, etc.
 
-3.  If you have verified that homepage can in fact reach the service then you can also check the API output using e.g. `curl`, which is often helpful if you do need to file a bug report. Again, depending on your networking setup this may need to be run from _inside the container_ as IP / hostname resolution can differ inside vs outside.
+3. If you have verified that homepage can in fact reach the service then you can also check the API output using e.g. `curl`, which is often helpful if you do need to file a bug report. Again, depending on your networking setup this may need to be run from _inside the container_ as IP / hostname resolution can differ inside vs outside.
 
-    !!! note
+   _Note: `curl` is not installed in the base image by default but can be added inside the container with `apk add curl`._
 
-        `curl` is not installed in the base image by default but can be added inside the container with `apk add curl`.
+   The exact API endpoints and authentication vary of course, but in many cases instructions can be found by searching the web or if you feel comfortable looking at the homepage source code (e.g. `src/widgets/{widget}/widget.js`).
 
-    The exact API endpoints and authentication vary of course, but in many cases instructions can be found by searching the web or if you feel comfortable looking at the homepage source code (e.g. `src/widgets/{widget}/widget.js`).
+   It is out of the scope of this to go into full detail about how to , but an example for PiHole would be:
 
-    It is out of the scope of this to go into full detail about how to , but an example for PiHole would be:
+   ```
+   curl -L -k http://PIHOLEIPORHOST/admin/api.php
+   ```
 
-    ```
-    curl -L -k http://PIHOLEIPORHOST/admin/api.php
-    ```
+   Or for AdGuard:
 
-    Or for AdGuard:
+   ```
+   curl -L -k -u 'username:password' http://ADGUARDIPORHOST/control/stats
+   ```
 
-    ```
-    curl -L -k -u 'username:password' http://ADGUARDIPORHOST/control/stats
-    ```
+   Or for Portainer:
 
-    Or for Portainer:
+   ```
+   curl -L -k -H 'X-Api-Key:YOURKEY' 'https://PORTAINERIPORHOST:PORT/api/endpoints/2/docker/containers/json'
+   ```
 
-    ```
-    curl -L -k -H 'X-Api-Key:YOURKEY' 'https://PORTAINERIPORHOST:PORT/api/endpoints/2/docker/containers/json'
-    ```
+   Sonarr:
 
-    Sonarr:
+   ```
+   curl -L -k 'http://SONARRIPORHOST:PORT/api/v3/queue?apikey=YOURAPIKEY'
+   ```
 
-    ```
-    curl -L -k 'http://SONARRIPORHOST:PORT/api/v3/queue?apikey=YOURAPIKEY'
-    ```
-
-    This will return some data which may reveal an issue causing a true bug in the service widget.
+   This will return some data which may reveal an issue causing a true bug in the service widget.
 
 ## Missing custom icons
 

docs/scripts/extra.js

@@ -1,35 +0,0 @@
-var glimeScript;
-var glimeStyles = [];
-document$.subscribe(function () {
-  if (!glimeScript) {
-    glimeScript = document.createElement("script");
-    glimeScript.setAttribute("src", "https://cdn.glimelab.ai/widget/1.0.0/widget.js");
-    glimeScript.setAttribute("onload", "onGlimeLoad()");
-    document.head.appendChild(glimeScript);
-  } else {
-    var newGlimeStyle = document.createElement("style");
-    document.head.appendChild(newGlimeStyle);
-    var i = 0;
-    glimeStyles.forEach((rule) => {
-      newGlimeStyle.sheet.insertRule(rule.cssText, i);
-      i++;
-    });
-  }
-});
-
-onGlimeLoad = () => {
-  window.glime.init("Bl3mlvfCnTnRm5");
-  setTimeout(() => {
-    const sheets = document.styleSheets;
-    [...sheets].forEach((sheet) => {
-      if (!sheet.href) {
-        [...sheet.cssRules].forEach((rule) => {
-          if (!rule || rule.href || !rule.selectorText) return;
-          if (rule.selectorText.indexOf(".css-") === 0 || rule.selectorText.indexOf("glime") > -1) {
-            glimeStyles.push(rule);
-          }
-        });
-      }
-    });
-  }, 1000);
-};

docs/stylesheets/extra.css

@@ -17,8 +17,4 @@
         color: var(--md-default-bg-color--lighter);
         border-color: var(--md-default-bg-color--lighter);
     }
-}
-
-#glimeRoot * {
-    font-family: var(--md-text-font) !important;
-}
+}

docs/widgets/index.md

@@ -7,7 +7,7 @@ Homepage has two types of widgets: info and service. Below we'll cover each type
 
 ## Service Widgets
 
-Service widgets are used to display the status of a service, often a web service or API. Services (and their widgets) are defined in your `services.yaml` file. Here's an example:
+Service widgets are used to display the status of a service, often a web service or API. Services (and their widgets) are defined in your `services.yml` file. Here's an example:
 
 ```yaml
 - Plex:
@@ -24,7 +24,7 @@ Service widgets are used to display the status of a service, often a web service
 
 ## 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 your `widgets.yml` file. Here's an example:
 
 ```yaml
 - openmeteo:

docs/widgets/info/datetime.md

@@ -9,9 +9,9 @@ Formatting is locale aware and will present your date in the regional format you
 
 ```yaml
 - datetime:
-    text_size: xl
-    format:
-      timeStyle: short
+      text_size: xl
+      format:
+          timeStyle: short
 ```
 
 Any options passed to `format` are passed directly to [Intl.DateTimeFormat](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat/DateTimeFormat), please reference the MDN documentation for all available options.
@@ -23,29 +23,29 @@ A few examples,
 ```yaml
 # 13:37
 format:
-  timeStyle: short
-  hourCycle: h23
+    timeStyle: short
+    hourCycle: h23
 ```
 
 ```yaml
 # 1:37 PM
 format:
-  timeStyle: short
-  hour12: true
+    timeStyle: short
+    hour12: true
 ```
 
 ```yaml
 # 1/23/22, 1:37 PM
 format:
-  dateStyle: short
-  timeStyle: short
-  hour12: true
+    dateStyle: short
+    timeStyle: short
+    hour12: true
 ```
 
 ```yaml
 # 4 januari 2023 om 13:51:25 PST
 locale: nl
 format:
-  dateStyle: long
-  timeStyle: long
+    dateStyle: long
+    timeStyle: long
 ```

docs/widgets/info/glances.md

@@ -9,16 +9,16 @@ The Glances widget allows you to monitor the resources (CPU, memory, storage, te
 
 ```yaml
 - glances:
-    url: http://host.or.ip:port
-    username: user # optional if auth enabled in Glances
-    password: pass # optional if auth enabled in Glances
-    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
-    uptime: true # disabled by default
-    disk: / # disabled by default, use mount point of disk(s) in glances. Can also be a list (see below)
-    expanded: true # show the expanded view
-    label: MyMachine # optional
+      url: http://host.or.ip:port
+      username: user # optional if auth enabled in Glances
+      password: pass # optional if auth enabled in Glances
+      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
+      uptime: true # disabled by default
+      disk: / # disabled by default, use mount point of disk(s) in glances. Can also be a list (see below)
+      expanded: true # show the expanded view
+      label: MyMachine # optional
 ```
 
 Multiple disks can be specified as:

docs/widgets/info/greeting.md

@@ -7,8 +7,8 @@ This allows you to display simple text, can be configured like so:
 
 ```yaml
 - greeting:
-    text_size: xl
-    text: Greeting Text
+      text_size: xl
+      text: Greeting Text
 ```
 
 Valid text sizes are `4xl`, `3xl`, `2xl`, `xl`, `md`, `sm`, `xs`.

docs/widgets/info/kubernetes.md

@@ -9,23 +9,23 @@ It provides CPU and Memory usage, by node and/or at the cluster level.
 
 ```yaml
 - kubernetes:
-    cluster:
-      # Shows cluster-wide statistics
-      show: true
-      # Shows the aggregate CPU stats
-      cpu: true
-      # Shows the aggregate memory stats
-      memory: true
-      # Shows a custom label
-      showLabel: true
-      label: "cluster"
-    nodes:
-      # Shows node-specific statistics
-      show: true
-      # Shows the CPU for each node
-      cpu: true
-      # Shows the memory for each node
-      memory: true
-      # Shows the label, which is always the node name
-      showLabel: true
+      cluster:
+          # Shows cluster-wide statistics
+          show: true
+          # Shows the aggregate CPU stats
+          cpu: true
+          # Shows the aggregate memory stats
+          memory: true
+          # Shows a custom label
+          showLabel: true
+          label: "cluster"
+      nodes:
+          # Shows node-specific statistics
+          show: true
+          # Shows the CPU for each node
+          cpu: true
+          # Shows the memory for each node
+          memory: true
+          # Shows the label, which is always the node name
+          showLabel: true
 ```

docs/widgets/info/longhorn.md

@@ -12,26 +12,18 @@ It can show the aggregate metrics and/or the individual node metrics.
 
 ```yaml
 - longhorn:
-    # Show the expanded view
-    expanded: true
-    # Shows a node representing the aggregate values
-    total: true
-    # Shows the node names as labels
-    labels: true
-    # Show the nodes
-    nodes: true
-    # An explicit list of nodes to show. All are shown by default if "nodes" is true
-    include:
-      - node1
-      - node2
+      # Show the expanded view
+      expanded: true
+      # Shows a node representing the aggregate values
+      total: true
+      # Shows the node names as labels
+      labels: true
+      # Show the nodes
+      nodes: true
+      # An explicit list of nodes to show. All are shown by default if "nodes" is true
+      include:
+          - node1
+          - node2
 ```
 
-The Longhorn URL and credentials are stored in the `providers` section of the `settings.yaml`. e.g.:
-
-```yaml
-providers:
-  longhorn:
-    username: "longhorn-username" # optional
-    password: "very-secret-longhorn-password" # optional
-    url: https://longhorn.aesop.network
-```
+The Longhorn URL and credentials are stored in the `providers` section of the `settings.yaml`.

docs/widgets/info/openmeteo.md

@@ -7,12 +7,12 @@ No registration is required at all! See [https://open-meteo.com/en/docs](https:/
 
 ```yaml
 - openmeteo:
-    label: Kyiv # optional
-    latitude: 50.449684
-    longitude: 30.525026
-    timezone: Europe/Kiev # optional
-    units: metric # or imperial
-    cache: 5 # Time in minutes to cache API responses, to stay within limits
+      label: Kyiv # optional
+      latitude: 50.449684
+      longitude: 30.525026
+      timezone: Europe/Kiev # optional
+      units: metric # or imperial
+      cache: 5 # Time in minutes to cache API responses, to stay within limits
 ```
 
 You can optionally not pass a `latitude` and `longitude` and the widget will use your current location (requires a secure context, eg. HTTPS).

docs/widgets/info/openweathermap.md

@@ -3,17 +3,17 @@ title: OpenWeatherMap
 description: OpenWeatherMap Information Widget Configuration
 ---
 
-The free tier "One Call API" is all that's required, you will need to [subscribe](https://home.openweathermap.org/subscriptions/unauth_subscribe/onecall_30/base) and grab your API key.
+The free tier "One Call API" is all thats required, you will need to [subscribe](https://home.openweathermap.org/subscriptions/unauth_subscribe/onecall_30/base) and grab your API key.
 
 ```yaml
 - openweathermap:
-    label: Kyiv #optional
-    latitude: 50.449684
-    longitude: 30.525026
-    units: metric # or imperial
-    provider: openweathermap
-    apiKey: youropenweathermapkey # required only if not using provider, this reveals api key in requests
-    cache: 5 # Time in minutes to cache API responses, to stay within limits
+      label: Kyiv #optional
+      latitude: 50.449684
+      longitude: 30.525026
+      units: metric # or imperial
+      provider: openweathermap
+      apiKey: youropenweathermapkey # required only if not using provider, this reveals api key in requests
+      cache: 5 # Time in minutes to cache API responses, to stay within limits
 ```
 
 You can optionally not pass a `latitude` and `longitude` and the widget will use your current location (requires a secure context, eg. HTTPS).

docs/widgets/info/resources.md

@@ -9,32 +9,32 @@ The disk path is the path reported by `df` (Mounted On), or the mount point of t
 
 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.
 
-_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._
+_Note: unfortunately, the package used for getting CPU temp ([systeminformation](https://systeminformation.io)) is not compatibile with some setups and will not report any value(s) for CPU temp._
 
 **Any disk you wish to access must be mounted to your container as a volume.**
 
 ```yaml
 - resources:
-    cpu: true
-    memory: true
-    disk: /disk/mount/path
-    cputemp: true
-    uptime: true
-    units: imperial # only used by cpu temp
-    refresh: 3000 # optional, in ms
+      cpu: true
+      memory: true
+      disk: /disk/mount/path
+      cputemp: true
+      uptime: true
+      units: imperial # only used by cpu temp
+      refresh: 3000 # optional, in ms
 ```
 
 You can also pass a `label` option, which allows you to group resources under named sections,
 
 ```yaml
 - resources:
-    label: System
-    cpu: true
-    memory: true
+      label: System
+      cpu: true
+      memory: true
 
 - resources:
-    label: Storage
-    disk: /mnt/storage
+      label: Storage
+      disk: /mnt/storage
 ```
 
 Which produces something like this,
@@ -45,11 +45,11 @@ If you have more than a single disk and would like to group them together under
 
 ```yaml
 - resources:
-    label: Storage
-    disk:
-      - /mnt/storage
-      - /mnt/backup
-      - /mnt/media
+      label: Storage
+      disk:
+          - /mnt/storage
+          - /mnt/backup
+          - /mnt/media
 ```
 
 To produce something like this,
@@ -60,12 +60,12 @@ You can additionally supply an optional `expanded` property set to true in order
 
 ```yaml
 - resources:
-    label: Array Disks
-    expanded: true
-    disk:
-      - /disk1
-      - /disk2
-      - /disk3
+      label: Array Disks
+      expanded: true
+      disk:
+          - /disk1
+          - /disk2
+          - /disk3
 ```
 
 ![194136533-c4238c82-4d67-41a4-b3c8-18bf26d33ac2](https://user-images.githubusercontent.com/3441425/194728642-a9885274-922b-4027-acf5-a746f58fdfce.png)

docs/widgets/info/search.md

@@ -7,25 +7,25 @@ You can add a search bar to your top widget area that can search using Google, D
 
 ```yaml
 - search:
-    provider: google # google, duckduckgo, bing, baidu, brave or custom
-    focus: true # Optional, will set focus to the search bar on page load
-    target: _blank # One of _self, _blank, _parent or _top
+      provider: google # google, duckduckgo, bing, baidu, brave or custom
+      focus: true # Optional, will set focus to the search bar on page load
+      target: _blank # One of _self, _blank, _parent or _top
 ```
 
 or for a custom search:
 
 ```yaml
 - search:
-    provider: custom
-    url: https://lougle.com/?q=
-    target: _blank
+      provider: custom
+      url: https://lougle.com/?q=
+      target: _blank
 ```
 
 multiple providers is also supported via a dropdown (excluding custom):
 
 ```yaml
 - search:
-    provider: [brave, google, duckduckgo]
+      provider: [brave, google, duckduckgo]
 ```
 
 _Added in v0.1.6, updated in 0.6.0_

docs/widgets/info/weather.md

@@ -5,16 +5,16 @@ description: Weather API Information Widget Configuration
 
 **Note: this widget is considered 'deprecated' since there is no longer a free Weather API tier for new members. See the openmeteo or openweathermap widgets for alternatives.**
 
-The free tier is all that's required, you will need to [register](https://www.weatherapi.com/signup.aspx) and grab your API key.
+The free tier is all thats required, you will need to [register](https://www.weatherapi.com/signup.aspx) and grab your API key.
 
 ```yaml
 - weatherapi:
-    label: Kyiv # optional
-    latitude: 50.449684
-    longitude: 30.525026
-    units: metric # or imperial
-    apiKey: yourweatherapikey
-    cache: 5 # Time in minutes to cache API responses, to stay within limits
+      label: Kyiv # optional
+      latitude: 50.449684
+      longitude: 30.525026
+      units: metric # or imperial
+      apiKey: yourweatherapikey
+      cache: 5 # Time in minutes to cache API responses, to stay within limits
 ```
 
 You can optionally not pass a `latitude` and `longitude` and the widget will use your current location (requires a secure context, eg. HTTPS).

docs/widgets/services/adguard-home.md

@@ -9,8 +9,8 @@ Allowed fields: `["queries", "blocked", "filtered", "latency"]`.
 
 ```yaml
 widget:
-  type: adguard
-  url: http://adguard.host.or.ip
-  username: admin
-  password: password
+    type: adguard
+    url: http://adguard.host.or.ip
+    username: admin
+    password: password
 ```

docs/widgets/services/atsumeru.md

@@ -9,8 +9,8 @@ Allowed fields: `["series", "archives", "chapters", "categories"]`.
 
 ```yaml
 widget:
-  type: atsumeru
-  url: http://atsumeru.host.or.ip:port
-  username: username
-  password: password
+    type: atsumeru
+    url: http://atsumeru.host.or.ip:port
+    username: username
+    password: password
 ```

docs/widgets/services/audiobookshelf.md

@@ -9,7 +9,7 @@ Allowed fields: `["podcasts", "podcastsDuration", "books", "booksDuration"]`
 
 ```yaml
 widget:
-  type: audiobookshelf
-  url: http://audiobookshelf.host.or.ip:port
-  key: audiobookshelflapikey
+    type: audiobookshelf
+    url: http://audiobookshelf.host.or.ip:port
+    key: audiobookshelflapikey
 ```

docs/widgets/services/authentik.md

@@ -18,7 +18,7 @@ Allowed fields: `["users", "loginsLast24H", "failedLoginsLast24H"]`.
 
 ```yaml
 widget:
-  type: authentik
-  url: http://authentik.host.or.ip:22070
-  key: api_token
+    type: authentik
+    url: http://authentik.host.or.ip:22070
+    key: api_token
 ```

docs/widgets/services/autobrr.md

@@ -9,7 +9,7 @@ Allowed fields: `["approvedPushes", "rejectedPushes", "filters", "indexers"]`.
 
 ```yaml
 widget:
-  type: autobrr
-  url: http://autobrr.host.or.ip
-  key: apikeyapikeyapikeyapikeyapikey
+    type: autobrr
+    url: http://autobrr.host.or.ip
+    key: apikeyapikeyapikeyapikeyapikey
 ```

docs/widgets/services/azuredevops.md

@@ -8,19 +8,19 @@ This widget has 2 functions:
 1. Pipelines: checks if the relevant pipeline is running or not, and if not, reports the last status.\
    Allowed fields: `["result", "status"]`.
 
-2. Pull Requests: returns the amount of open PRs, the amount of the PRs you have open, and how many PRs that you open are marked as 'Approved' by at least 1 person and not yet completed.\
+2. Pull Requests: returns the amount of open PRs, the amount of the PRs you have open, and how many PRs that you open are marked as 'Approved' by atleast 1 person and not yet completed.\
    Allowed fields: `["totalPrs", "myPrs", "approved"]`.
 
 You will need to generate a personal access token for an existing user, see the [azure documentation](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows#create-a-pat)
 
 ```yaml
 widget:
-  type: azuredevops
-  organization: myOrganization
-  project: myProject
-  definitionId: pipelineDefinitionId # required for pipelines
-  branchName: branchName # optional for pipelines, leave empty for all
-  userEmail: email # required for pull requests
-  repositoryId: prRepositoryId # required for pull requests
-  key: personalaccesstoken
+    type: azuredevops
+    organization: myOrganization
+    project: myProject
+    definitionId: pipelineDefinitionId # required for pipelines
+    branchName: branchName # optional for pipelines, leave empty for all
+    userEmail: email # required for pull requests
+    repositoryId: prRepositoryId # required for pull requests
+    key: personalaccesstoken
 ```

docs/widgets/services/bazarr.md

@@ -9,7 +9,7 @@ Allowed fields: `["missingEpisodes", "missingMovies"]`.
 
 ```yaml
 widget:
-  type: bazarr
-  url: http://bazarr.host.or.ip
-  key: apikeyapikeyapikeyapikeyapikey
+    type: bazarr
+    url: http://bazarr.host.or.ip
+    key: apikeyapikeyapikeyapikeyapikey
 ```

docs/widgets/services/caddy.md

@@ -7,6 +7,6 @@ Allowed fields: `["upstreams", "requests", "requests_failed"]`.
 
 ```yaml
 widget:
-  type: caddy
-  url: http://caddy.host.or.ip:adminport # default admin port is 2019
+    type: caddy
+    url: http://caddy.host.or.ip:adminport # default admin port is 2019
 ```

docs/widgets/services/calendar.md

@@ -3,8 +3,6 @@ title: Calendar
 description: Calendar widget
 ---
 
-## Monthly view
-
 <img alt="calendar" src="https://user-images.githubusercontent.com/5442891/271131282-6767a3ea-573e-4005-aeb9-6e14ee01e845.png">
 
 This widget shows monthly calendar, with optional integrations to show events from supported widgets.
@@ -13,44 +11,15 @@ This widget shows monthly calendar, with optional integrations to show events fr
 widget:
   type: calendar
   firstDayInWeek: sunday # optional - defaults to monday
-  view: monthly # optional - possible values monthly, agenda
-  maxEvents: 10 # optional - defaults to 10
-  showTime: true # optional - show time for event happening today - defaults to false
   integrations: # optional
-    - type: sonarr # active widget type that is currently enabled on homepage - possible values: radarr, sonarr, lidarr, readarr, ical
+    - type: sonarr # active widget type that is currently enabled on homepage - possible values: radarr, sonarr, lidarr, readarr
       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)
       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
-      url: https://domain.url/with/link/to.ics # URL with calendar events
-      name: My Events # required - name for these calendar events
-      color: zinc # optional - defaults to pre-defined color for the service (zinc for ical)
-      params: # optional - additional params for the service
-        showName: true # optional - show name before event title in event line - defaults to false
 ```
 
-## Agenda
-
-This view shows only list of events from configured integrations
-
-```yaml
-widget:
-  type: calendar
-  view: agenda
-  maxEvents: 10 # optional - defaults to 10
-  showTime: true # optional - show time for event happening today - defaults to false
-  previousDays: 3 # optional - shows events since three days ago - defaults to 0
-  integrations: # same as in Monthly view example
-```
-
-## Integrations
-
 Currently integrated widgets are [sonarr](sonarr.md), [radarr](radarr.md), [lidarr](lidarr.md) and [readarr](readarr.md).
 
 Supported colors can be found on [color palette](../../configs/settings.md#color-palette).
-
-### iCal
-
-This custom integration allows you to show events from any calendar that supports iCal format, for example, Google Calendar (go to `Settings`, select specific calendar, go to `Integrate calendar`, copy URL from `Public Address in iCal format`).

docs/widgets/services/calibre-web.md

@@ -3,14 +3,14 @@ title: Calibre-web
 description: Calibre-web Widget Configuration
 ---
 
-**Note: widget requires calibre-web ≥ v0.6.21.**
+**Note: this widget requires a feature of calibre-web that has not yet been distributed in versioned release. The code is contained in ["nightly" lsio builds after 25/8/23](https://hub.docker.com/layers/linuxserver/calibre-web/nightly/images/sha256-b27cbe5d17503de38135d925e226eb3e5ba04c558dbc865dc85d77824d35d7e2) or running the calibre-web source code including commit [0499e57](https://github.com/janeczku/calibre-web/commit/0499e578cdd45db656da34cd2d7152c8d88ceb23).**
 
 Allowed fields: `["books", "authors", "categories", "series"]`.
 
 ```yaml
 widget:
-  type: calibreweb
-  url: http://your.calibreweb.host:port
-  username: username
-  password: password
+    type: calibreweb
+    url: http://your.calibreweb.host:port
+    username: username
+    password: password
 ```

docs/widgets/services/changedetectionio.md

@@ -7,7 +7,7 @@ Find your API key under `Settings > API`.
 
 ```yaml
 widget:
-  type: changedetectionio
-  url: http://changedetection.host.or.ip:port
-  key: apikeyapikeyapikeyapikeyapikey
+    type: changedetectionio
+    url: http://changedetection.host.or.ip:port
+    key: apikeyapikeyapikeyapikeyapikey
 ```

docs/widgets/services/channelsdvrserver.md

@@ -5,6 +5,6 @@ description: Channels DVR Server Widget Configuration
 
 ```yaml
 widget:
-  type: channelsdvrserver
-  url: http://192.168.1.55:8089
+    type: channelsdvrserver
+    url: http://192.168.1.55:8089
 ```

docs/widgets/services/cloudflared.md

@@ -9,8 +9,8 @@ Allowed fields: `["status", "origin_ip"]`.
 
 ```yaml
 widget:
-  type: cloudflared
-  accountid: accountid # from zero trust dashboard url e.g. https://one.dash.cloudflare.com/<accountid>/home/quick-start
-  tunnelid: tunnelid # found in tunnels dashboard under the tunnel name
-  key: cloudflareapitoken # api token with `Account.Cloudflare Tunnel:Read` https://dash.cloudflare.com/profile/api-tokens
+    type: cloudflared
+    accountid: accountid # from zero trust dashboard url e.g. https://one.dash.cloudflare.com/<accountid>/home/quick-start
+    tunnelid: tunnelid # found in tunnels dashboard under the tunnel name
+    key: cloudflareapitoken # api token with `Account.Cloudflare Tunnel:Read` https://dash.cloudflare.com/profile/api-tokens
 ```

docs/widgets/services/coin-market-cap.md

@@ -9,18 +9,17 @@ Allowed fields: no configurable fields for this widget.
 
 ```yaml
 widget:
-  type: coinmarketcap
-  currency: GBP # Optional
-  symbols: [BTC, LTC, ETH]
-  key: apikeyapikeyapikeyapikeyapikey
-  defaultinterval: 7d # Optional
+    type: coinmarketcap
+    currency: GBP # Optional
+    symbols: [BTC, LTC, ETH]
+    key: apikeyapikeyapikeyapikeyapikey
 ```
 
 You can also specify slugs instead of symbols (since symbols aren't garaunteed to be unique). If you supply both, slugs will be used. For example:
 
 ```yaml
 widget:
-  type: coinmarketcap
-  slugs: [chia-network, uniswap]
-  key: apikeyapikeyapikeyapikeyapikey
+    type: coinmarketcap
+    slugs: [chia-network, uniswap]
+    key: apikeyapikeyapikeyapikeyapikey
 ```

docs/widgets/services/customapi.md

@@ -9,36 +9,31 @@ Fields need to be defined in the `mappings` section YAML object to correlate wit
 
 ```yaml
 widget:
-  type: customapi
-  url: http://custom.api.host.or.ip:port/path/to/exact/api/endpoint
-  refreshInterval: 10000 # optional - in milliseconds, defaults to 10s
-  username: username # auth - optional
-  password: password # auth - optional
-  method: GET # optional, e.g. POST
-  headers: # optional, must be object, see below
-  mappings:
-    - field: key # needs to be YAML string or object
-      label: Field 1
-      format: text # optional - defaults to text
-    - field: # needs to be YAML string or object
-        path:
-          to: key2
-      format: number # optional - defaults to text
-      label: Field 2
-    - field: # needs to be YAML string or object
-        path:
-          to:
-            another: key3
-      label: Field 3
-      format: percent # optional - defaults to text
-    - field: key # needs to be YAML string or object
-      label: Field 4
-      format: date # optional - defaults to text
-      dateStyle: long # optional - defaults to "long". Allowed values: `["full", "long", "medium", "short"]`.
-      timeStyle: medium # optional - Allowed values: `["full", "long", "medium", "short"]`.
+    type: customapi
+    url: http://custom.api.host.or.ip:port/path/to/exact/api/endpoint
+    refreshInterval: 10000 # optional - in milliseconds, defaults to 10s
+    username: username # auth - optional
+    password: password # auth - optional
+    method: GET # optional, e.g. POST
+    headers: # optional, must be object, see below
+    mappings:
+        - field: key # needs to be YAML string or object
+          label: Field 1
+          format: text # optional - defaults to text
+        - field: # needs to be YAML string or object
+              path:
+                  to: key2
+          format: number # optional - defaults to text
+          label: Field 2
+        - field: # needs to be YAML string or object
+              path:
+                  to:
+                      another: key3
+          label: Field 3
+          format: percent # optional - defaults to text
 ```
 
-Supported formats for the values are `text`, `number`, `float`, `percent`, `bytes`, `bitrate` and `date`.
+Supported formats for the values are `text`, `number`, `float`, `percent`, `bytes` and `bitrate`.
 
 ## Example
 
@@ -46,40 +41,40 @@ For the following JSON object from the API:
 
 ```json
 {
-  "id": 1,
-  "name": "Rick Sanchez",
-  "status": "Alive",
-  "species": "Human",
-  "gender": "Male",
-  "origin": {
-    "name": "Earth (C-137)"
-  },
-  "locations": [
-    {
-      "name": "Earth (C-137)"
+    "id": 1,
+    "name": "Rick Sanchez",
+    "status": "Alive",
+    "species": "Human",
+    "gender": "Male",
+    "origin": {
+        "name": "Earth (C-137)"
     },
-    {
-      "name": "Citadel of Ricks"
-    }
-  ]
+    "locations": [
+        {
+            "name": "Earth (C-137)"
+        },
+        {
+            "name": "Citadel of Ricks"
+        }
+    ]
 }
 ```
 
-Define the `mappings` section as an array, for example:
+Define the `mappings` section as an aray, for example:
 
 ```yaml
 mappings:
-  - field: name # Rick Sanchez
-    label: Name
-  - field: status # Alive
-    label: Status
-  - field:
-      origin: name # Earth (C-137)
-    label: Origin
-  - field:
-      locations:
-        1: name # Citadel of Ricks
-    label: Location
+    - field: name # Rick Sanchez
+      label: Name
+    - field: status # Alive
+      label: Status
+    - field:
+          origin: name # Earth (C-137)
+      label: Origin
+    - field:
+          locations:
+              1: name # Citadel of Ricks
+      label: Location
 ```
 
 ## Data Transformation
@@ -91,12 +86,12 @@ You can manipulate data with the following tools `remap`, `scale` and `suffix`,
   label: Field 4
   format: text
   remap:
-    - value: 0
-      to: None
-    - value: 1
-      to: Connected
-    - any: true # will map all other values
-      to: Unknown
+      - value: 0
+        to: None
+      - value: 1
+        to: Connected
+      - any: true # will map all other values
+        to: Unknown
 - field: key5
   label: Power
   format: float
@@ -110,5 +105,5 @@ Pass custom headers using the `headers` option, for example:
 
 ```yaml
 headers:
-  X-API-Token: token
+    X-API-Token: token
 ```

docs/widgets/services/deluge.md

@@ -9,7 +9,7 @@ Allowed fields: `["leech", "download", "seed", "upload"]`.
 
 ```yaml
 widget:
-  type: deluge
-  url: http://deluge.host.or.ip
-  password: password # webui password
+    type: deluge
+    url: http://deluge.host.or.ip
+    password: password # webui password
 ```

docs/widgets/services/diskstation.md

@@ -17,9 +17,9 @@ To access these system metrics you need to connect to the DiskStation with an ac
 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 `Download Station` application, 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.
+    - 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.
 7. When the `Preview` column shows `Allow` in the `Download Station` row, click `Save`.
 
 Now configure the widget with the correct login information and test it.
@@ -28,9 +28,9 @@ If you encounter issues during testing, make sure to uncheck the option for auto
 
 ```yaml
 widget:
-  type: diskstation
-  url: http://diskstation.host.or.ip:port
-  username: username
-  password: password
-  volume: volume_N # optional
+    type: diskstation
+    url: http://diskstation.host.or.ip:port
+    username: username
+    password: password
+    volume: volume_N # optional
 ```

docs/widgets/services/downloadstation.md

@@ -9,8 +9,8 @@ Allowed fields: `["leech", "download", "seed", "upload"]`.
 
 ```yaml
 widget:
-  type: downloadstation
-  url: http://downloadstation.host.or.ip:port
-  username: username
-  password: password
+    type: downloadstation
+    url: http://downloadstation.host.or.ip:port
+    username: username
+    password: password
 ```

docs/widgets/services/emby.md

@@ -9,9 +9,9 @@ As of v0.6.11 the widget supports fields `["movies", "series", "episodes", "song
 
 ```yaml
 widget:
-  type: emby
-  url: http://emby.host.or.ip
-  key: apikeyapikeyapikeyapikeyapikey
-  enableBlocks: true # optional, defaults to false
-  enableNowPlaying: true # optional, defaults to true
+    type: emby
+    url: http://emby.host.or.ip
+    key: apikeyapikeyapikeyapikeyapikey
+    enableBlocks: true # optional, defaults to false
+    enableNowPlaying: true # optional, defaults to true
 ```

docs/widgets/services/evcc.md

@@ -7,6 +7,6 @@ Allowed fields: `["pv_power", "grid_power", "home_power", "charge_power]`.
 
 ```yaml
 widget:
-  type: evcc
-  url: http://evcc.host.or.ip:port
+    type: evcc
+    url: http://evcc.host.or.ip:port
 ```

docs/widgets/services/fileflows.md

@@ -7,6 +7,6 @@ Allowed fields: `["queue", "processing", "processed", "time"]`.
 
 ```yaml
 widget:
-  type: fileflows
-  url: http://your.fileflows.host:port
+    type: fileflows
+    url: http://your.fileflows.host:port
 ```

docs/widgets/services/flood.md

@@ -7,8 +7,8 @@ Allowed fields: `["leech", "download", "seed", "upload"]`.
 
 ```yaml
 widget:
-  type: flood
-  url: http://flood.host.or.ip
-  username: username # if set
-  password: password # if set
+    type: flood
+    url: http://flood.host.or.ip
+    username: username # if set
+    password: password # if set
 ```

docs/widgets/services/freshrss.md

@@ -9,8 +9,8 @@ Allowed fields: `["subscriptions", "unread"]`.
 
 ```yaml
 widget:
-  type: freshrss
-  url: http://freshrss.host.or.ip:port
-  username: username
-  password: password
+    type: freshrss
+    url: http://freshrss.host.or.ip:port
+    username: username
+    password: password
 ```

docs/widgets/services/fritzbox.md

@@ -1,22 +0,0 @@
----
-title: FRITZ!Box
-description: FRITZ!Box Widget Configuration
----
-
-Application access & UPnP must be activated on your device:
-
-```
-Home Network > Network > Network Settings > Access Settings in the Home Network
-[x] Allow access for applications
-[x] Transmit status information over UPnP
-```
-
-Credentials are not needed and, as such, you may want to consider using `http` instead of `https` as those requests are significantly faster.
-
-Allowed fields (limited to a max of 4): `["connectionStatus", "upTime", "maxDown", "maxUp", "down", "up", "received", "sent", "externalIPAddress"]`.
-
-```yaml
-widget:
-  type: fritzbox
-  url: http://192.168.178.1
-```

docs/widgets/services/gamedig.md

@@ -9,7 +9,7 @@ Allowed fields (limited to a max of 4): `["status", "name", "map", "currentPlaye
 
 ```yaml
 widget:
-  type: gamedig
-  serverType: csgo # see https://github.com/gamedig/node-gamedig#games-list
-  url: udp://server.host.or.ip:port
+    type: gamedig
+    serverType: csgo # see https://github.com/gamedig/node-gamedig#games-list
+    url: udp://server.host.or.ip:port
 ```

docs/widgets/services/ghostfolio.md

@@ -17,7 +17,7 @@ Allowed fields: `["gross_percent_today", "gross_percent_1y", "gross_percent_max"
 
 ```yaml
 widget:
-  type: ghostfolio
-  url: http://ghostfoliohost:port
-  key: ghostfoliobearertoken
+    type: ghostfolio
+    url: http://ghostfoliohost:port
+    key: ghostfoliobearertoken
 ```

docs/widgets/services/glances.md

@@ -3,7 +3,7 @@ title: Glances
 description: Glances Widget Configuration
 ---
 
-<img width="1614" alt="glances" src="https://github-production-user-asset-6210df.s3.amazonaws.com/82196/257382012-25648c97-2c1b-4db0-b5a5-f1509806079c.png">
+<img width="1614" alt="glances" src="https://github.com/gethomepage/homepage-docs/assets/82196/25648c97-2c1b-4db0-b5a5-f1509806079c">
 
 _(Find the Glances information widget [here](../info/glances.md))_
 
@@ -18,7 +18,7 @@ widget:
   metric: cpu
 ```
 
-_Please note, this widget does not need an `href`, `icon` or `description` on its parent service. To achieve the same effect as the examples above, see as an example:_
+_Please note, this widget does not need an `href`, `icon` or `description` on its parent service. To achive the same effect as the examples above, see as an example:_
 
 ```yaml
 - CPU Usage:
@@ -45,23 +45,23 @@ The metric field in the configuration determines the type of system monitoring d
 
 `process`: Top 5 processes based on CPU usage. Gives an overview of which processes are consuming the most resources.
 
-`network:<interface_name>`: Network data usage for the specified interface. Replace `<interface_name>` with the name of your network interface, e.g., `network:enp0s25`, as specified in glances.
+`network:<interface_name>`: Network data usage for the specified interface. Replace `<interface_name>` with the name of your network interface, e.g., `network:enp0s25`, as specificed in glances.
 
-`sensor:<sensor_id>`: Temperature of the specified sensor, typically used to monitor CPU temperature. Replace `<sensor_id>` with the name of your sensor, e.g., `sensor:Package id 0` as specified in glances.
+`sensor:<sensor_id>`: Temperature of the specified sensor, typically used to monitor CPU temperature. Replace `<sensor_id>` with the name of your sensor, e.g., `sensor:Package id 0` as specificed in glances.
 
-`disk:<disk_id>`: Disk I/O data for the specified disk. Replace `<disk_id>` with the id of your disk, e.g., `disk:sdb`, as specified in glances.
+`disk:<disk_id>`: Disk I/O data for the specified disk. Replace `<disk_id>` with the id of your disk, e.g., `disk:sdb`, as specificed in glances.
 
-`gpu:<gpu_id>`: GPU usage for the specified GPU. Replace `<gpu_id>` with the id of your GPU, e.g., `gpu:0`, as specified in glances.
+`gpu:<gpu_id>`: GPU usage for the specified GPU. Replace `<gpu_id>` with the id of your GPU, e.g., `gpu:0`, as specificed in glances.
 
-`fs:<mnt_point>`: Disk usage for the specified mount point. Replace `<mnt_point>` with the path of your disk, e.g., `/mnt/storage`, as specified in glances.
+`fs:<mnt_point>`: Disk usage for the specified mount point. Replace `<mnt_point>` with the path of your disk, e.g., `/mnt/storage`, as specificed in glances.
 
 ## Views
 
 All widgets offer an alternative to the full or "graph" view, which is the compact, or "graphless" view.
 
-<img width="970" alt="Screenshot 2023-09-06 at 1 51 48 PM" src="https://github-production-user-asset-6210df.s3.amazonaws.com/82196/265985295-cc6b9adc-4218-4274-96ca-36c3e64de5d0.png">
+<img width="970" alt="Screenshot 2023-09-06 at 1 51 48 PM" src="https://github.com/gethomepage/homepage-docs/assets/82196/cc6b9adc-4218-4274-96ca-36c3e64de5d0">
 
-To switch to the alternative "graphless" view, simply pass `chart: false` as an option to the widget, like so:
+To switch to the alternative "graphless" view, simply passs `chart: false` as an option to the widget, like so:
 
 ```yaml
 - Network Usage:

docs/widgets/services/gluetun.md

@@ -3,14 +3,12 @@ title: Gluetun
 description: Gluetun Widget Configuration
 ---
 
-!!! note
-
-    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`.
+Requires [HTTP control server options](https://github.com/qdm12/gluetun-wiki/blob/main/setup/advanced/control-server.md) to be enabled.
 
 Allowed fields: `["public_ip", "region", "country"]`.
 
 ```yaml
 widget:
-  type: gluetun
-  url: http://gluetun.host.or.ip:port
+    type: gluetun
+    url: http://gluetun.host.or.ip
 ```

docs/widgets/services/gotify.md

@@ -9,7 +9,7 @@ Allowed fields: `["apps", "clients", "messages"]`.
 
 ```yaml
 widget:
-  type: gotify
-  url: http://gotify.host.or.ip
-  key: clientoken
+    type: gotify
+    url: http://gotify.host.or.ip
+    key: clientoken
 ```

docs/widgets/services/grafana.md

@@ -7,8 +7,8 @@ Allowed fields: `["dashboards", "datasources", "totalalerts", "alertstriggered"]
 
 ```yaml
 widget:
-  type: grafana
-  url: http://grafana.host.or.ip:port
-  username: username
-  password: password
+    type: grafana
+    url: http://grafana.host.or.ip:port
+    username: username
+    password: password
 ```

docs/widgets/services/hdhomerun.md

@@ -7,6 +7,6 @@ Allowed fields: `["channels", "hd"]`.
 
 ```yaml
 widget:
-  type: hdhomerun
-  url: http://hdhomerun.host.or.ip
+    type: hdhomerun
+    url: http://hdhomerun.host.or.ip
 ```

docs/widgets/services/healthchecks.md

@@ -13,8 +13,8 @@ Allowed fields: `["status", "last_ping"]`.
 
 ```yaml
 widget:
-  type: healthchecks
-  url: http://healthchecks.host.or.ip:port
-  key: <YOUR_API_KEY>
-  uuid: <YOUR_CHECK_UUID>
+    type: healthchecks
+    url: http://healthchecks.host.or.ip:port
+    key: <YOUR_API_KEY>
+    uuid: <YOUR_CHECK_UUID>
 ```

docs/widgets/services/homeassistant.md

@@ -12,25 +12,25 @@ Allowed fields: `["people_home", "lights_on", "switches_on"]`.
 Up to a maximum of four custom states and/or templates can be queried via the `custom` property like in the example below.
 The `custom` property will have no effect as long as the `fields` property is defined.
 
-- `state` will query the state of the specified `entity_id`
-  - state labels and values can be user defined and may reference entity attributes in curly brackets
-  - if no state label is defined it will default to `"{attributes.friendly_name}"`
-  - if no state value is defined it will default to `"{state} {attributes.unit_of_measurement}"`
-- `template` will query the specified template, see (Home Assistant Templating)[https://www.home-assistant.io/docs/configuration/templating]
-  - if no template label is defined it will be empty
+-   `state` will query the state of the specified `entity_id`
+    -   state labels and values can be user defined and may reference entity attributes in curly brackets
+    -   if no state label is defined it will default to `"{attributes.friendly_name}"`
+    -   if no state value is defined it will default to `"{state} {attributes.unit_of_measurement}"`
+-   `template` will query the specified template, see (Home Assistant Templating)[https://www.home-assistant.io/docs/configuration/templating]
+    -   if no template label is defined it will be empty
 
 ```yaml
 widget:
-  type: homeassistant
-  url: http://homeassistant.host.or.ip:port
-  key: access_token
-  custom:
-    - state: sensor.total_power
-    - state: sensor.total_energy_today
-      label: energy today
-    - template: "{{ states.switch|selectattr('state','equalto','on')|list|length }}"
-      label: switches on
-    - state: weather.forecast_home
-      label: wind speed
-      value: "{attributes.wind_speed} {attributes.wind_speed_unit}"
+    type: homeassistant
+    url: http://homeassistant.host.or.ip:port
+    key: access_token
+    custom:
+        - state: sensor.total_power
+        - state: sensor.total_energy_today
+          label: energy today
+        - template: "{{ states.switch|selectattr('state','equalto','on')|list|length }}"
+          label: switches on
+        - state: weather.forecast_home
+          label: wind speed
+          value: "{attributes.wind_speed} {attributes.wind_speed_unit}"
 ```

docs/widgets/services/homebridge.md

@@ -9,8 +9,8 @@ Allowed fields: `["updates", "child_bridges"]`.
 
 ```yaml
 widget:
-  type: homebridge
-  url: http://homebridge.host.or.ip:port
-  username: username
-  password: password
+    type: homebridge
+    url: http://homebridge.host.or.ip:port
+    username: username
+    password: password
 ```

docs/widgets/services/iframe.md

@@ -1,35 +0,0 @@
----
-title: iFrame
-Description: Add a custom iFrame Widget
----
-
-A basic iFrame widget to show external content, see the [MDN docs](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe) for more details about some of the options.
-
-!!! warning
-
-    Requests made via the iFrame widget are inherently **not proxied** as they are made from the browser itself.
-
-## Basic Example
-
-```yaml
-widget:
-  type: iframe
-  name: myIframe
-  src: http://example.com
-```
-
-## Full Example
-
-```yaml
-widget:
-  type: iframe
-  name: myIframe
-  src: http://example.com
-  classes: h-60 sm:h-60 md:h-60 lg:h-60 xl:h-60 2xl:h-72 # optional, use tailwind height classes, see https://tailwindcss.com/docs/height
-  referrerPolicy: same-origin # optional, no default
-  allowPolicy: autoplay; fullscreen; gamepad # optional, no default
-  allowFullscreen: false # optional, default: true
-  loadingStrategy: eager # optional, default: eager
-  allowScrolling: no # optional, default: yes
-  refreshInterval: 2000 # optional, no default
-```

docs/widgets/services/immich.md

@@ -9,7 +9,7 @@ Note that API key must be from admin user.
 
 ```yaml
 widget:
-  type: immich
-  url: http://immich.host.or.ip
-  key: adminapikeyadminapikeyadminapikey
+    type: immich
+    url: http://immich.host.or.ip
+    key: adminapikeyadminapikeyadminapikey
 ```

docs/widgets/services/jackett.md

@@ -9,6 +9,6 @@ Allowed fields: `["configured", "errored"]`.
 
 ```yaml
 widget:
-  type: jackett
-  url: http://jackett.host.or.ip
+    type: jackett
+    url: http://jackett.host.or.ip
 ```

docs/widgets/services/jdownloader.md

@@ -9,8 +9,8 @@ Allowed fields: `["downloadCount", "downloadTotalBytes","downloadBytesRemaining"
 
 ```yaml
 widget:
-  type: jdownloader
-  username: JDownloader Username
-  password: JDownloader Password
-  client: Name of JDownloader Instance
+    type: jdownloader
+    username: JDownloader Username
+    password: JDownloader Password
+    client: Name of JDownloader Instance
 ```

docs/widgets/services/jellyfin.md

@@ -9,9 +9,9 @@ As of v0.6.11 the widget supports fields `["movies", "series", "episodes", "song
 
 ```yaml
 widget:
-  type: jellyfin
-  url: http://jellyfin.host.or.ip
-  key: apikeyapikeyapikeyapikeyapikey
-  enableBlocks: true # optional, defaults to false
-  enableNowPlaying: true # optional, defaults to true
+    type: jellyfin
+    url: http://jellyfin.host.or.ip
+    key: apikeyapikeyapikeyapikeyapikey
+    enableBlocks: true # optional, defaults to false
+    enableNowPlaying: true # optional, defaults to true
 ```

docs/widgets/services/jellyseerr.md

@@ -9,7 +9,7 @@ Allowed fields: `["pending", "approved", "available"]`.
 
 ```yaml
 widget:
-  type: jellyseerr
-  url: http://jellyseerr.host.or.ip
-  key: apikeyapikeyapikeyapikeyapikey
+    type: jellyseerr
+    url: http://jellyseerr.host.or.ip
+    key: apikeyapikeyapikeyapikeyapikey
 ```

docs/widgets/services/kavita.md

@@ -9,8 +9,8 @@ Allowed fields: `["seriesCount", "totalFiles"]`.
 
 ```yaml
 widget:
-  type: kavita
-  url: http://kavita.host.or.ip:port
-  username: username
-  password: password
+    type: kavita
+    url: http://kavita.host.or.ip:port
+    username: username
+    password: password
 ```

docs/widgets/services/komga.md

@@ -9,8 +9,8 @@ Allowed fields: `["libraries", "series", "books"]`.
 
 ```yaml
 widget:
-  type: komga
-  url: http://komga.host.or.ip:port
-  username: username
-  password: password
+    type: komga
+    url: http://komga.host.or.ip:port
+    username: username
+    password: password
 ```

docs/widgets/services/kopia.md

@@ -9,10 +9,10 @@ You may optionally pass values for `snapshotHost` and / or `snapshotPath` to sel
 
 ```yaml
 widget:
-  type: kopia
-  url: http://kopia.host.or.ip:port
-  username: username
-  password: password
-  snapshotHost: hostname # optional
-  snapshotPath: path # optional
+    type: kopia
+    url: http://kopia.host.or.ip:port
+    username: username
+    password: password
+    snapshotHost: hostname # optional
+    snapshotPath: path # optional
 ```

docs/widgets/services/lidarr.md

@@ -9,7 +9,7 @@ Allowed fields: `["wanted", "queued", "artists"]`.
 
 ```yaml
 widget:
-  type: lidarr
-  url: http://lidarr.host.or.ip
-  key: apikeyapikeyapikeyapikeyapikey
+    type: lidarr
+    url: http://lidarr.host.or.ip
+    key: apikeyapikeyapikeyapikeyapikey
 ```

docs/widgets/services/mastodon.md

@@ -9,6 +9,6 @@ Allowed fields: `["user_count", "status_count", "domain_count"]`.
 
 ```yaml
 widget:
-  type: mastodon
-  url: https://mastodon.host.name
+    type: mastodon
+    url: https://mastodon.host.name
 ```

docs/widgets/services/mealie.md

@@ -9,7 +9,7 @@ Allowed fields: `["recipes", "users", "categories", "tags"]`.
 
 ```yaml
 widget:
-  type: mealie
-  url: http://mealie-frontend.host.or.ip
-  key: mealieapitoken
+    type: mealie
+    url: http://mealie-frontend.host.or.ip
+    key: mealieapitoken
 ```

docs/widgets/services/medusa.md

@@ -7,7 +7,7 @@ Allowed fields: `["wanted", "queued", "series"]`.
 
 ```yaml
 widget:
-  type: medusa
-  url: http://medusa.host.or.ip:port
-  key: medusaapikeyapikeyapikeyapikeyapikey
+    type: medusa
+    url: http://medusa.host.or.ip:port
+    key: medusaapikeyapikeyapikeyapikeyapikey
 ```

docs/widgets/services/mikrotik.md

@@ -9,8 +9,8 @@ Allowed fields: `["uptime", "cpuLoad", "memoryUsed", "numberOfLeases"]`.
 
 ```yaml
 widget:
-  type: mikrotik
-  url: https://mikrotik.host.or.ip
-  username: username
-  password: password
+    type: mikrotik
+    url: https://mikrotik.host.or.ip
+    username: username
+    password: password
 ```

docs/widgets/services/minecraft.md

@@ -7,6 +7,6 @@ Allowed fields: `["players", "version", "status"]`.
 
 ```yaml
 widget:
-  type: minecraft
-  url: udp://minecraftserveripordomain:port
+    type: minecraft
+    url: udp://minecraftserveripordomain:port
 ```

docs/widgets/services/miniflux.md

@@ -9,7 +9,7 @@ Allowed fields: `["unread", "read"]`.
 
 ```yaml
 widget:
-  type: miniflux
-  url: http://miniflux.host.or.ip:port
-  key: minifluxapikey
+    type: miniflux
+    url: http://miniflux.host.or.ip:port
+    key: minifluxapikey
 ```

docs/widgets/services/mjpeg.md

@@ -9,6 +9,6 @@ Pass the stream URL from a service like [µStreamer](https://github.com/pikvm/us
 
 ```yaml
 widget:
-  type: mjpeg
-  stream: http://mjpeg.host.or.ip/webcam/stream
+    type: mjpeg
+    stream: http://mjpeg.host.or.ip/webcam/stream
 ```

docs/widgets/services/moonraker.md

@@ -7,6 +7,6 @@ Allowed fields: `["printer_state", "print_status", "print_progress", "layers"]`.
 
 ```yaml
 widget:
-  type: moonraker
-  url: http://moonraker.host.or.ip:port
+    type: moonraker
+    url: http://moonraker.host.or.ip:port
 ```

docs/widgets/services/mylar.md

@@ -9,7 +9,7 @@ Allowed fields: `["series", "issues", "wanted"]`.
 
 ```yaml
 widget:
-  type: mylar
-  url: http://mylar3.host.or.ip:port
-  key: yourmylar3apikey
+    type: mylar
+    url: http://mylar3.host.or.ip:port
+    key: yourmylar3apikey
 ```

docs/widgets/services/navidrome.md

@@ -9,9 +9,9 @@ Allowed fields: no configurable fields for this widget.
 
 ```yaml
 widget:
-  type: navidrome
-  url: http://navidrome.host.or.ip:port
-  user: username
-  token: token #md5(password + salt)
-  salt: randomsalt
+    type: navidrome
+    url: http://navidrome.host.or.ip:port
+    user: username
+    token: token #md5(password + salt)
+    salt: randomsalt
 ```

docs/widgets/services/nextcloud.md

@@ -11,15 +11,15 @@ Note "cpuload" and "memoryusage" were deprecated in v0.6.18 and a maximum of 4 f
 
 ```yaml
 widget:
-  type: nextcloud
-  url: https://nextcloud.host.or.ip:port
-  key: token
+    type: nextcloud
+    url: https://nextcloud.host.or.ip:port
+    key: token
 ```
 
 ```yaml
 widget:
-  type: nextcloud
-  url: https://nextcloud.host.or.ip:port
-  username: username
-  password: password
+    type: nextcloud
+    url: https://nextcloud.host.or.ip:port
+    username: username
+    password: password
 ```

docs/widgets/services/nextdns.md

@@ -7,7 +7,7 @@ Api key is found under Account > API, profile ID is found under Setup > Endpoint
 
 ```yaml
 widget:
-  type: nextdns
-  profile: profileid
-  key: yourapikeyhere
+    type: nextdns
+    profile: profileid
+    key: yourapikeyhere
 ```

docs/widgets/services/nginx-proxy-manager.md

@@ -9,8 +9,8 @@ Allowed fields: `["enabled", "disabled", "total"]`.
 
 ```yaml
 widget:
-  type: npm
-  url: http://npm.host.or.ip
-  username: admin_username
-  password: admin_password
+    type: npm
+    url: http://npm.host.or.ip
+    username: admin_username
+    password: admin_password
 ```

docs/widgets/services/nzbget.md

@@ -9,8 +9,8 @@ Allowed fields: `["rate", "remaining", "downloaded"]`.
 
 ```yaml
 widget:
-  type: nzbget
-  url: http://nzbget.host.or.ip
-  username: controlusername
-  password: controlpassword
+    type: nzbget
+    url: http://nzbget.host.or.ip
+    username: controlusername
+    password: controlpassword
 ```

docs/widgets/services/octoprint.md

@@ -7,7 +7,7 @@ Allowed fields: `["printer_state", "temp_tool", "temp_bed", "job_completion"]`.
 
 ```yaml
 widget:
-  type: octoprint
-  url: http://octoprint.host.or.ip:port
-  key: youroctoprintapikey
+    type: octoprint
+    url: http://octoprint.host.or.ip:port
+    key: youroctoprintapikey
 ```

docs/widgets/services/omada.md

@@ -9,9 +9,9 @@ Allowed fields: `["connectedAp", "activeUser", "alerts", "connectedGateways", "c
 
 ```yaml
 widget:
-  type: omada
-  url: http://omada.host.or.ip:port
-  username: username
-  password: password
-  site: sitename
+    type: omada
+    url: http://omada.host.or.ip:port
+    username: username
+    password: password
+    site: sitename
 ```

docs/widgets/services/ombi.md

@@ -9,7 +9,7 @@ Allowed fields: `["pending", "approved", "available"]`.
 
 ```yaml
 widget:
-  type: ombi
-  url: http://ombi.host.or.ip
-  key: apikeyapikeyapikeyapikeyapikey
+    type: ombi
+    url: http://ombi.host.or.ip
+    key: apikeyapikeyapikeyapikeyapikey
 ```

docs/widgets/services/opendtu.md

@@ -7,6 +7,6 @@ Allowed fields: `["yieldDay", "relativePower", "absolutePower", "limit"]`.
 
 ```yaml
 widget:
-  type: opendtu
-  url: http://opendtu.host.or.ip
+    type: opendtu
+    url: http://opendtu.host.or.ip
 ```

docs/widgets/services/openmediavault.md

@@ -7,11 +7,11 @@ Provides useful information from your OpenMediaVault
 
 ```yaml
 widget:
-  type: openmediavault
-  url: http://omv.host.or.ip
-  username: admin
-  password: pass
-  method: services.getStatus # required
+    type: openmediavault
+    url: http://omv.host.or.ip
+    username: admin
+    password: pass
+    method: services.getStatus # required
 ```
 
 ## Methods

docs/widgets/services/opnsense.md

@@ -5,8 +5,8 @@ description: OPNSense Widget Configuration
 
 The API key & secret can be generated via the webui by creating a new user at _System/Access/Users_. Ensure "Generate a scrambled password to prevent local database logins for this user" is checked and then edit the effective privileges selecting **only**:
 
-- Diagnostics: System Activity
-- Status: Traffic Graph
+-   Diagnostics: System Activity
+-   Status: Traffic Graph
 
 Finally, create a new API key which will download an `apikey.txt` file with your key and secret in it. Use the values as the username and password fields, respectively, in your homepage config.
 
@@ -14,8 +14,8 @@ Allowed fields: `["cpu", "memory", "wanUpload", "wanDownload"]`.
 
 ```yaml
 widget:
-  type: opnsense
-  url: http://opnsense.host.or.ip
-  username: key
-  password: secret
+    type: opnsense
+    url: http://opnsense.host.or.ip
+    username: key
+    password: secret
 ```