Files
computer-playbook/roles/web-app-homeassistant/meta/services.yml
kevinveenbirkenbachandClaude Opus 5 83c1c729de refactor(mcp)!: derive admission from the client
allowed_consumers was twenty hand-kept lists of which fourteen were identical, so every new client meant an edit in every provider. A client now declares services.<own-entity>.mcp_consumer: true once and a provider refuses one with mcp_consumer: false, which is also what tells a deliberate exclusion apart from a forgotten entry.

The group_names-gated consumer entries give the inventory resolver the co-deploy edge meta/mcp.yml never had: one of sixty-nine matrix rounds carried an MCP client before, twenty-three role/round pairs do now. bond 0.5 keeps the clients out of round 0 so the host memory budget still holds.

BREAKING CHANGE: meta/mcp.yml no longer accepts allowed_consumers; declare services.<entity>.mcp_consumer on the client instead.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-31 18:33:22 +02:00

87 lines
2.7 KiB
YAML

---
# nocheck: playwright-service-flag
homeassistant:
modes:
compose:
enabled: true
swarm:
enabled: true
bond: 1
enabled: true
shared: true
backup:
no_stop_required: true
image: ghcr.io/home-assistant/home-assistant
version: "2026.7"
name: homeassistant
min_storage: 823MB
cpus: "2.0"
mem_reservation: 1g
mem_limit: 2g
pids_limit: 2048
# nocheck: single-replica Home Assistant guards its config directory with a PID lock, so a second replica on the shared volume aborts with "Another Home Assistant instance is already running" and crash-loops; upstream supports no multi-instance mode
replicas: 1
ports:
local:
http: 8091
internal:
http: 8123
lifecycle: beta
proxy:
service_key: homeassistant
# nocheck: sso, dynamic-flag, playwright-service-flag
sso:
enabled: false
shared: false
# nocheck: logout, dynamic-flag, playwright-service-flag
logout:
enabled: false
shared: false
# nocheck: playwright-service-flag
dashboard:
bond: 1
enabled: "{{ 'web-app-dashboard' in group_names }}"
shared: "{{ 'web-app-dashboard' in group_names }}"
# nocheck: playwright-service-flag
prometheus:
bond: 1
enabled: "{{ 'web-app-prometheus' in group_names }}"
shared: "{{ 'web-app-prometheus' in group_names }}"
# nocheck: playwright-service-flag
# nocheck: variants-coverage — sso-variant-tor requires the onion on in every variant, so the false polarity has no variant left to live in
tor:
bond: 0.5
enabled: "{{ 'svc-net-tor' in group_names }}"
shared: true # nocheck: dynamic-flag
# nocheck: playwright-service-flag, dynamic-flag
container_backup: # nocheck: bond-baseline
bond: 1
enabled: "{{ 'svc-bkp-volume-2-local' in group_names }}"
shared: true
# nocheck: playwright-service-flag MCP pairing is proven by the role's own MCP spec, not by a per-consumer gate
openwebui:
bond: 0.5
enabled: "{{ 'web-app-openwebui' in group_names }}"
shared: "{{ 'web-app-openwebui' in group_names }}"
# nocheck: playwright-service-flag MCP pairing is proven by the role's own MCP spec, not by a per-consumer gate
hermes:
bond: 0.5
enabled: "{{ 'web-app-hermes' in group_names }}"
shared: "{{ 'web-app-hermes' in group_names }}"
# nocheck: playwright-service-flag MCP pairing is proven by the role's own MCP spec, not by a per-consumer gate
openclaw:
bond: 0.5
enabled: "{{ 'web-app-openclaw' in group_names }}"
shared: "{{ 'web-app-openclaw' in group_names }}"
# nocheck: playwright-service-flag MCP pairing is proven by the role's own MCP spec, not by a per-consumer gate
flowise:
bond: 0.5
enabled: "{{ 'web-app-flowise' in group_names }}"
shared: "{{ 'web-app-flowise' in group_names }}"