updates2mqtt 1.4.0__tar.gz → 1.4.2__tar.gz

updates2mqtt-1.4.2/.github/workflows/auto_assign_issue.yml

@@ -0,0 +1,18 @@
+name: Issue assignment
+
+on:
+    issues:
+        types: [opened]
+
+jobs:
+    auto-assign:
+        runs-on: ubuntu-latest
+        permissions:
+            issues: write
+        steps:
+            - name: 'Auto-assign issue'
+              uses: pozil/auto-assign-issue@39c06395cbac76e79afc4ad4e5c5c6db6ecfdd2e
+              with:
+                  assignees: jeyrb
+                  numOfAssignee: 1
+                  allowSelfAssign: true

updates2mqtt-1.4.2/.github/workflows/auto_assign_pr.yml

@@ -0,0 +1,18 @@
+name: PR assignment
+
+on:
+    pull_request:
+        types: [opened, edited, synchronize, reopened]
+
+jobs:
+    auto-assign:
+        runs-on: ubuntu-latest
+        permissions:
+            pull-requests: write
+        steps:
+            - name: 'Auto-assign PR'
+              uses: pozil/auto-assign-issue@39c06395cbac76e79afc4ad4e5c5c6db6ecfdd2e
+              with:
+                  repo-token: ${{ secrets.MY_PERSONAL_ACCESS_TOKEN }}
+                  assignees: jeyrb
+                  numOfAssignee: 1

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/.github/workflows/docker-publish.yml

@@ -25,7 +25,7 @@ jobs:
       #
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
       # Uses the `docker/login-action` action to log in to the Container registry registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
       - name: Log in to the Container registry
         uses: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef
@@ -42,7 +42,7 @@ jobs:
         uses: docker/setup-buildx-action@v3
       - name: Extract metadata (tags, labels) for Docker
         id: meta
-        uses: docker/metadata-action@8d8c7c12f7b958582a5cb82ba16d5903cb27976a
+        uses: docker/metadata-action@c299e40c65443455700f0fdfc63efafe5b349051
         with:
           images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
           tags: |

updates2mqtt-1.4.2/.github/workflows/main.yml

@@ -0,0 +1,18 @@
+name: Issue assignment
+
+on:
+    issues:
+        types: [opened]
+
+jobs:
+    auto-assign:
+        runs-on: ubuntu-latest
+        permissions:
+            issues: write
+        steps:
+            - name: 'Auto-assign issue'
+              uses: pozil/auto-assign-issue@v2
+              with:
+                  assignees: jeyrb
+                  numOfAssignee: 1
+                  allowSelfAssign: true

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/.github/workflows/pypi-publish.yml

@@ -2,13 +2,16 @@ name: Publish Python 🐍 distribution 📦 to PyPI and TestPyPI
 
 on: push
 
+permissions:
+  contents: read
+
 jobs:
   build:
     name: Build distribution 📦
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v5
+    - uses: actions/checkout@v6
       with:
         persist-credentials: false
     - name: uv-setup

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/.github/workflows/python-package.yml

@@ -15,7 +15,7 @@ jobs:
     permissions:
       contents: write
     steps:
-    - uses: actions/checkout@v5
+    - uses: actions/checkout@v6
     - name: uv-setup
       # Install a specific uv version using the installer
       run: curl -LsSf https://astral.sh/uv/install.sh | sh
@@ -27,11 +27,32 @@ jobs:
       run: uv sync --all-extras --dev
        
     - name: Ruff
-      uses: chartboost/ruff-action@v1
+      uses:  astral-sh/ruff-action@v3
     - name: Test with pytest
       run: uv run pytest tests
     - name: Build a binary wheel and a source tarball
       run: uv build
+    - name: Generate badges
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      run: |
+        uv run genbadge coverage -i cov.xml -o badges/coverage.svg
+        uv run genbadge tests -i junit/test-results.xml -o badges/tests.svg
+
+        git config --global user.name "github-actions[bot]"
+        git config --global user.email "github-actions[bot]@users.noreply.github.com"
+        TEMP_DIR=$(mktemp -d)
+        cd $TEMP_DIR
+        git clone --single-branch --branch badges https://x-access-token:${{ secrets.GITHUB_TOKEN }}@github.com/${{ github.repository }}.git . 2>/dev/null
+        cp -r ${{ github.workspace }}/badges .
+        git add badges
+        if git commit -m "Update badges [skip ci]"; then
+          git push origin badges --force
+          echo "Badges updated successfully"
+        else
+          echo "No changes to badges"
+        fi
+
     - name: Prep for mkdocs
       run:  uv pip compile pyproject.toml -o requirements_docs.txt --group mkdocs
     - name: Deploy docs

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/.gitignore

@@ -11,6 +11,7 @@ htmlcov/
 lcov.info
 .vscode/
 .DS_Store
+junit/
 
 # C extensions
 *.so

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/.pre-commit-config.yaml

@@ -17,11 +17,11 @@ repos:
       - id: check-shebang-scripts-are-executable
         name: Check shell scripts are executable
   - repo: https://github.com/astral-sh/uv-pre-commit
-    rev: 0.9.13
+    rev: 0.9.16
     hooks:
       - id: uv-lock
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.14.7
+    rev: v0.14.8
     hooks:
      # Run the linter.
       - id: ruff-check

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/CHANGELOG.md

@@ -1,5 +1,14 @@
 # CHANGELOG
 
+## 1.4.2
+- Replace `origin` in config MQTT message with `device` for better HomeAssistant compatibility
+- An `area` can be defined in the Home Assistant section of config and this will then be used as `suggested_area` for device
+- Icon and release note info added for Owntone and Homarr
+## 1.4.1
+- More logging for Docker discovery on why Home Assistant doesn't show an update button
+- More test cases
+- `MqttClient` is now `MqttPublisher` to avoid confusion with actual MQTT client
+- Task cleanup now only interrupts explicit list of tasks - healthcheck and discovery tasks
 ## 1.4.0
 - MQTT protocol can now be set, to one of `3.1`,`3.11` or `5`
 - Debug messages now provided for `on_subscribe` and `on_unsubscribe` callbacks

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: updates2mqtt
-Version: 1.4.0
+Version: 1.4.2
 Summary: System update and docker image notification and execution over MQTT
 Project-URL: Homepage, https://updates2mqtt.rhizomatics.org.uk
 Project-URL: Repository, https://github.com/rhizomatics/updates2mqtt
@@ -35,18 +35,27 @@ Requires-Dist: structlog>=25.4.0
 Requires-Dist: usingversion>=0.1.2
 Description-Content-Type: text/markdown
 
-[![Rhizomatics Open Source](https://avatars.githubusercontent.com/u/162821163?s=96&v=4)](https://github.com/rhizomatics)
+![updates2mqtt](/images/updates2mqtt-dark-256x256.png){ align=left }
 
 # updates2mqtt
 
+[![Rhizomatics Open Source](https://img.shields.io/badge/rhizomatics%20open%20source-lightseagreen)](https://github.com/rhizomatics)
+
 [![PyPI - Version](https://img.shields.io/pypi/v/updates2mqtt)](https://pypi.org/project/updates2mqtt/)
 [![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/rhizomatics/supernotify)
+[![Coverage](https://raw.githubusercontent.com/rhizomatics/updates2mqtt/refs/heads/badges/badges/coverage.svg)](https://updates2mqtt.rhizomatics.org.uk/developer/coverage/)
+![Tests](https://raw.githubusercontent.com/rhizomatics/updates2mqtt/refs/heads/badges/badges/tests.svg)
 [![pre-commit.ci status](https://results.pre-commit.ci/badge/github/rhizomatics/updates2mqtt/main.svg)](https://results.pre-commit.ci/latest/github/rhizomatics/updates2mqtt/main)
 [![Publish Python 🐍 distribution 📦 to PyPI and TestPyPI](https://github.com/rhizomatics/updates2mqtt/actions/workflows/pypi-publish.yml/badge.svg)](https://github.com/rhizomatics/updates2mqtt/actions/workflows/pypi-publish.yml)
 [![Github Deploy](https://github.com/rhizomatics/updates2mqtt/actions/workflows/python-package.yml/badge.svg?branch=main)](https://github.com/rhizomatics/updates2mqtt/actions/workflows/python-package.yml)
 [![CodeQL](https://github.com/rhizomatics/updates2mqtt/actions/workflows/github-code-scanning/codeql/badge.svg)](https://github.com/rhizomatics/updates2mqtt/actions/workflows/github-code-scanning/codeql)
 [![Dependabot Updates](https://github.com/rhizomatics/updates2mqtt/actions/workflows/dependabot/dependabot-updates/badge.svg)](https://github.com/rhizomatics/updates2mqtt/actions/workflows/dependabot/dependabot-updates)
 
+
+<br/>
+<br/>
+
+
 ## Summary
 
 Let Home Assistant tell you about new updates to Docker images for your containers.

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/README.md

@@ -1,15 +1,24 @@
-[![Rhizomatics Open Source](https://avatars.githubusercontent.com/u/162821163?s=96&v=4)](https://github.com/rhizomatics)
+![updates2mqtt](/images/updates2mqtt-dark-256x256.png){ align=left }
 
 # updates2mqtt
 
+[![Rhizomatics Open Source](https://img.shields.io/badge/rhizomatics%20open%20source-lightseagreen)](https://github.com/rhizomatics)
+
 [![PyPI - Version](https://img.shields.io/pypi/v/updates2mqtt)](https://pypi.org/project/updates2mqtt/)
 [![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/rhizomatics/supernotify)
+[![Coverage](https://raw.githubusercontent.com/rhizomatics/updates2mqtt/refs/heads/badges/badges/coverage.svg)](https://updates2mqtt.rhizomatics.org.uk/developer/coverage/)
+![Tests](https://raw.githubusercontent.com/rhizomatics/updates2mqtt/refs/heads/badges/badges/tests.svg)
 [![pre-commit.ci status](https://results.pre-commit.ci/badge/github/rhizomatics/updates2mqtt/main.svg)](https://results.pre-commit.ci/latest/github/rhizomatics/updates2mqtt/main)
 [![Publish Python 🐍 distribution 📦 to PyPI and TestPyPI](https://github.com/rhizomatics/updates2mqtt/actions/workflows/pypi-publish.yml/badge.svg)](https://github.com/rhizomatics/updates2mqtt/actions/workflows/pypi-publish.yml)
 [![Github Deploy](https://github.com/rhizomatics/updates2mqtt/actions/workflows/python-package.yml/badge.svg?branch=main)](https://github.com/rhizomatics/updates2mqtt/actions/workflows/python-package.yml)
 [![CodeQL](https://github.com/rhizomatics/updates2mqtt/actions/workflows/github-code-scanning/codeql/badge.svg)](https://github.com/rhizomatics/updates2mqtt/actions/workflows/github-code-scanning/codeql)
 [![Dependabot Updates](https://github.com/rhizomatics/updates2mqtt/actions/workflows/dependabot/dependabot-updates/badge.svg)](https://github.com/rhizomatics/updates2mqtt/actions/workflows/dependabot/dependabot-updates)
 
+
+<br/>
+<br/>
+
+
 ## Summary
 
 Let Home Assistant tell you about new updates to Docker images for your containers.

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/common_packages.yaml

@@ -26,7 +26,7 @@ common_packages:
   caddy:
     docker:
       image_name: caddy
-    logo_url: https://d1q6f0aelx0por.cloudfront.net/product-logos/library-caddy-logo.png
+    logo_url: https://avatars.githubusercontent.com/u/12955528?s=48&v=4
     release_notes_url: https://github.com/caddyserver/caddy/releases
 
   uptime-kuma:
@@ -81,4 +81,28 @@ common_packages:
     docker:
       image_name: jellyfin/jellyfin
     logo_url: https://avatars.githubusercontent.com/u/45698031?s=48&v=4
-    release_notes_url: https://github.com/jellyfin/jellyfin/releases
+    release_notes_url: https://github.com/jellyfin/jellyfin/releases
+
+  owntone:
+    docker:
+      image_name: owntone/owntone
+    logo_url: https://raw.githubusercontent.com/owntone/owntone-server/443fb684871e005a7e442a08cc4d610208abbe6c/docs/assets/logo.svg
+    release_notes_url: https://github.com/owntone/owntone-server/releases
+
+  homarr:
+    docker:
+      image_name: ghcr.io/homarr-labs/homarr
+    logo_url: https://github.com/homarr-labs/homarr/blob/dev/docs/img/logo/2340450-2-title.png?raw=true
+    release_notes_url: https://github.com/homarr-labs/homarr/releases
+
+  nextcloud:
+    docker:
+      image_name: nextcloud
+    logo_url: https://avatars.githubusercontent.com/u/19211038?s=48&v=4
+    release_notes_url: https://github.com/nextcloud/docker/releases
+
+  n8n:
+    docker:
+      image_name: docker.n8n.io/n8nio/n8n
+    logo_url: https://avatars.githubusercontent.com/u/45487711?s=48&v=4
+    release_notes_url: https://github.com/n8n-io/n8n/releases

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/conftest.py

@@ -1,26 +1,89 @@
-from unittest.mock import MagicMock, Mock, patch
+# python
+from collections.abc import AsyncGenerator, Callable
+from typing import Any
+from unittest.mock import AsyncMock, MagicMock, Mock, patch
 
 import paho.mqtt.client
 import pytest
 from docker import DockerClient
 from docker.models.containers import Container, ContainerCollection
 from docker.models.images import Image, RegistryData
+from omegaconf import DictConfig, OmegaConf
 
+import updates2mqtt.app
+from updates2mqtt.app import (
+    App,  # relative import as required
+    MqttPublisher,
+)
+from updates2mqtt.config import Config
 from updates2mqtt.model import Discovery, ReleaseProvider
 
 
+@pytest.fixture
+def app_with_mocked_external_dependencies(
+    monkeypatch,  # noqa: ANN001
+    mock_provider_class: type,
+    mock_publisher_class: type,
+) -> App:
+    cfg: DictConfig = OmegaConf.structured(Config)
+    monkeypatch.setattr(updates2mqtt.app, "load_app_config", lambda *_args, **__kwargs: cfg)
+    monkeypatch.setattr(updates2mqtt.app, "DockerProvider", mock_provider_class)
+    monkeypatch.setattr(updates2mqtt.app, "MqttPublisher", mock_publisher_class)
+    app: App = App()
+    return app
+
+
+@pytest.fixture
+def mock_discoveries(mock_provider: ReleaseProvider) -> list[Discovery]:
+    return [Discovery(mock_provider, "thing-1", "test001")]
+
+
+@pytest.fixture
+def mock_discovery_generator(mock_discoveries: list[Discovery]) -> Callable[..., AsyncGenerator[Discovery, Any]]:
+    async def g(*args: Any) -> AsyncGenerator[Discovery]:  # noqa: ARG001
+        for d in mock_discoveries:
+            yield d
+
+    return g
+
+
+@pytest.fixture
+def mock_provider_class(mock_provider: ReleaseProvider) -> type:
+    class MockReleaseProvider(ReleaseProvider):
+        def __new__(cls, *args: Any, **kwargs: Any) -> ReleaseProvider:  # type: ignore[misc] # noqa: ARG004
+            return mock_provider
+
+    return MockReleaseProvider
+
+
+@pytest.fixture
+def mock_publisher_class(mock_publisher: MqttPublisher) -> type:
+    class MockPublisher(MqttPublisher):
+        def __new__(cls, *args: Any, **kwargs: Any) -> MqttPublisher:  # type: ignore[misc] # noqa: ARG004
+            return mock_publisher
+
+    return MockPublisher
+
+
 @pytest.fixture
 def mock_provider() -> ReleaseProvider:
-    provider = Mock(spec=ReleaseProvider)
+    provider: ReleaseProvider = AsyncMock(spec=ReleaseProvider)
     provider.source_type = "unit_test"
-    provider.command.return_value = True
-    provider.resolve.return_value = Discovery(
+    provider.command.return_value = True  # type: ignore[attr-defined]
+    provider.resolve.return_value = Discovery(  # type: ignore[attr-defined]
         provider, "fooey", session="test-mqtt-123", current_version="v2", latest_version="v2"
     )
-    provider.hass_state_format.return_value = {"fixture": "test_exec"}
+    provider.hass_state_format.return_value = {"fixture": "test_exec"}  # type: ignore[attr-defined]
     return provider
 
 
+@pytest.fixture
+def mock_publisher(mock_mqtt_client: paho.mqtt.client.Client) -> MqttPublisher:
+    publisher: MqttPublisher = AsyncMock(MqttPublisher)
+    publisher.client = mock_mqtt_client
+    return publisher
+
+
 @pytest.fixture
 def mock_mqtt_client() -> paho.mqtt.client.Client:
     return MagicMock(spec=paho.mqtt.client.Client, name="MQTT Client Fixture")

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/docs/home_assistant.md

@@ -16,6 +16,13 @@ The `homeassistant` default topic prefix matches the default updates2mqtt config
 
 ![Home Assistant updates in Settings](images/ha_update_page.png "Home Assistant Updates")
 
+## Device Creation
+
+A Home Assistant device will be created for each Updates2MQTT agent on each server, and Home Assistant
+will then group all the relevant entities together on this device page. Use `device_creation: false` in the 
+`homeassistant` config block if you want to switch off this behaviour, and `area` if you want to provide
+a `suggested_area` for the device.
+
 ## MQTT Topics
 
 There are 3 separate types of MQTT topic used for HomeAssisstant integration:

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/docs/installation.md

@@ -12,8 +12,22 @@ See `examples` directory for a working `docker-compose.yaml`.
 
 If you want to update and restart containers, then the file system paths to the location of the directory where the docker compose file lives must be available in the updates2mqtt container. 
 
-The example `docker-compose.yaml` mounts `/home/containers` for this purpose, so if your containers are in
-`/home/containers/app1`, `/home/containers/app2` etc, then updates2mqtt will be able to find them. Map as many root paths as needed.
+```yaml
+volumes:
+      # Must have config directory mapped
+      - ./conf:/app/conf
+      # Must have the Docker daemon socket mapped
+      - /var/run/docker.sock:/var/run/docker.sock
+      # This list of paths is only needed when containers are to be updated
+      # The paths here are completely dependent on where your docker-compose files live
+      # and the internal/external paths must be exactly the same
+      - /my/container/home:/my/container/home
+      - /more/containers:/more/containers
+```
+
+The example `docker-compose.yaml` mounts `/my/container/home` for this purpose, so if your containers are in
+`/my/container/home/app1`, `/my/container/home/app2` etc, then updates2mqtt will be able to find them in
+order to restart them. Map as many root paths as needed.
 
 ### Without Docker
 

updates2mqtt-1.4.2/docs/robots.txt

@@ -0,0 +1,4 @@
+User-agent: *
+Allow: /
+
+Sitemap: https://updates2mqtt.rhizomatics.org.uk/sitemap.xml

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/docs/troubleshooting.md

@@ -1,14 +1,60 @@
+---
+tags:
+  - docker
+  - docker-compose
+  - homeassistant
+  - mqtt
+  - paho
+---
 # Troubleshooting
 
-## Log Level
+## General
 
-Update the `config.yaml` and change the log level to DEBUG
+Things that need to work:
+
+- Docker API access to list and inspect containers
+- MQTT Publication of results
+- Home Assistant discovering the Update entities on MQTT
+- Home Assistant generating update notices in UI when there's a new version
+- Command Topic message sent by Home Assistant when Update button clicked
+- Docker Compose available from shell to make updates and restart
+- Git command available in shell to check for local repo updates and pull
+
+## Updates2MQTT Logs
+
+If running under docker, and following the container naming guidance, then see the
+logs using:
+
+`docker logs updates2mqtt`
+
+or change to the directory where the `docker-compose.yaml` is installed and do `docker compose logs`
+
+### Changing Log Level
+
+Update the `config.yaml` and change the log level to DEBUG, which will show much
+more diagnostic information.
 
 ```yaml
 log:
   level: DEBUG
 ```
 
+When you have everything working, its best to change the log level back, so
+your container isn't generating big logs.
+
+### Going Inside Container
+
+From the `docker-compose.yaml` directory, execute 
+
+`docker compose exec -it updates2mqtt bash`
+
+(if you have an old Docker install, you may need to use `docker-compose` instead of `docker compose`)
+
+This will give you shell access inside the container, which is a good way of checking
+for path issues, permissio issues etc. For example, if you have compose directories in the
+`/containers` directory, you could `cd /containers` and validate that Updates2MQTT can see the
+other compose directories, `ls` the contents, and run `docker compose` or `git` actions there.
+
 ## MQTT
 
 If the host, port, user and password for MQTT are incorrect then usually this
@@ -58,6 +104,38 @@ Oddly, the Paho MQTT client used by Updates2MQTT is known to [report success eve
 
 There's also an alternative to MQTT Discovery in HA, using plain yaml, the [MQTT Update Integration](https://www.home-assistant.io/integrations/update.mqtt/#configuration). The [BBQKees Boiler Gateway](https://bbqkees-electronics.nl/wiki/home-automations/home-assistant-configuration.html) has some detailed steps and examples for MQTT Discovery too.
 
+#### No Update Button
+
+If there's an update showing, but no *Update* button present, then there's a few reasons, which
+can be checked directly from the config and log:
+
+- Config has the `allow_pull`,`allow_restart` and `allow_build` all overridden to `False`
+- A new version reference can't be found 
+- The compose working directory can't be found
+  - This is sourced from the `com.docker.compose.project.working_dir` label, which can be seen in `docker inspect`
+  - This only stops restart, not pull, so if `allow_pull` is on, the Update button will still show
+- The git repo path can't be found for a local build
+
+The current state of this can be seen in MQTT, the config message will have two extra
+values as below:
+
+```yaml
+  "command_topic": "updates2mqtt/dockernuc/docker",
+  "payload_install": "docker|homarr|install"
+```
+
+#### Home Assistant Logs
+
+Use the [System Log](https://www.home-assistant.io/integrations/system_log/) to check
+for MQTT errors, or for positive confirmation that Update entities have been discovered. The
+*raw* log will show more, and allow you to scroll back for hours.
+
+The [Logger Integration](https://www.home-assistant.io/integrations/logger/#viewing-logs)
+lets you tweak the levels of specific integrations. This is less useful for Updates2MQTT,
+since all the work is happening outside of Home Assistant, however it can be useful
+for general MQTT issues, and the examples in the Home Assistant documentation shows how
+to tune the MQTT integration.
+
 ## Docker
 
 More detailed information on the Docker API and compatibility with Docker engine versions can be found at Docker's own [Docker Engine API](https://docs.docker.com/reference/api/engine/) reference.

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/examples/config.yaml.maximal

@@ -19,6 +19,8 @@ homeassistant:
     prefix: homeassistant
     enabled: true
   state_topic_suffix: state
+  area: Server Room
+  device_creation: true
 docker:
   enabled: true
   allow_pull: true

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/examples/docker-compose.yaml

@@ -5,7 +5,7 @@ services:
     volumes:
       - ./conf:/app/conf  # Config file lives at /app/conf/config.yaml inside the container
       - /var/run/docker.sock:/var/run/docker.sock # Access to Docker daemon for container updates
-      - /home/containers:/home/containers # Optional, map all root paths for docker compose directories
+      - /my/container/home:/my/container/home # Optional, map all root paths for docker compose directories
     restart: always
     env_file: ./.env  # Environment variables file
     healthcheck:

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/mkdocs.yml

@@ -4,13 +4,18 @@ site_description: Notify and take action on server updates via MQTT, with HomeAs
 
 repo_name: rhizomatics/updates2mqtt
 repo_url: https://github.com/rhizomatics/updates2mqtt
+edit_uri: edit/main/docs/
 
 theme:
   name: material
   highlightjs: true
-  logo: images/logo-blank-256x256.png
+  logo: images/updates2mqtt-dark-256x256.png
   language: en
+  icon:
+    repo: fontawesome/brands/github
   features:
+    - content.action.edit
+    - content.action.view
     - content.code.copy
     - content.code.select
     - content.code.annotate 
@@ -24,14 +29,24 @@ theme:
     - navigation.top
     - toc.follow
     - toc.integrate
+    - search.suggest
+    - search
+    - search.share
 plugins:
   - search
   - autorefs
   - pagetree
   - optimize
-  - tags
+  - tags:
+      tags: false
+  - git-revision-date-localized:
+      enable_creation_date: true
+  - meta-descriptions
   - minify:
       minify_html: true
+  - coverage:
+      page_path: developer/coverage
+      html_report_dir: htmlcov
   - mkdocstrings:
       handlers:
         # See: https://mkdocstrings.github.io/python/usage/
@@ -40,6 +55,10 @@ plugins:
             show_source: false
             show_root_heading: true
             summary: true
+            show_inheritance_diagram: false
+            overloads_only: true
+            show_if_no_docstring: false
+
 markdown_extensions:
   - admonition
   - pymdownx.details
@@ -52,7 +71,6 @@ markdown_extensions:
       pygments_lang_class: true
   - pymdownx.inlinehilite
   - pymdownx.superfences
-  - admonition
   - smarty
   - toc:
       permalink: true

{updates2mqtt-1.4.0 → updates2mqtt-1.4.2}/pyproject.toml

@@ -7,7 +7,7 @@ authors = [
 ]
 
 requires-python = ">=3.13"
-version = "1.4.0"
+version = "1.4.2"
 license="Apache-2.0"
 keywords=["mqtt", "docker", "updates", "automation","home-assistant","homeassistant","selfhosting"]
 
@@ -56,16 +56,20 @@ dev = [
     "pytest-mqtt>=0.6.0",
     "pytest-subprocess>=1.5.3",
     "coverage",
+    "icdiff",
+    "genbadge[all]"
 ]
 mkdocs=[
+    "mkdocs",
     "mkdocs-material",
-    "mkdocstrings",
     "mkdocs-minify-plugin",
     "mkdocs-autorefs",
     "mkdocs-pagetree-plugin",
     "mkdocs-coverage",
     "mkdocstrings[python]",
     "pymdown-extensions",
+    "mkdocs-git-revision-date-localized-plugin",
+    "mkdocs-meta-descriptions-plugin",
     "pngquant"
 ]
 
@@ -154,10 +158,11 @@ norecursedirs = [
     ".git",
     "templates",
 ]
+
 pythonpath = [
   "."
 ]
-addopts = "--cov --cov-report=lcov:lcov.info --cov-report=term --import-mode=importlib"
+addopts = "--junitxml=junit/test-results.xml --cov --cov-report=lcov:lcov.info --cov-report=xml --cov-report=html --cov-report=term --import-mode=importlib"
 
 [tool.coverage.run]
 branch = true