# Furtka Home Assistant — smart-home hub.
#
# Bridge networking + explicit `8123:8123` port mapping. Upstream's own
# docs lean toward `network_mode: host` because that's what mDNS-based
# discovery, Bluetooth, HomeKit, and Zigbee/Z-Wave dongles need. We're
# deliberately starting in bridge mode for v1: it keeps the catalog's
# network model consistent (every other app is bridged), and Cloud-only
# integrations (Hue Cloud, Tado, Sonos via account, etc.) work fine.
# Host networking + USB passthrough is a follow-up once the manifest
# schema grows a `network_mode` knob.
#
# Image pin: `homeassistant/home-assistant:stable` is upstream's
# recommended tag for production — release-train, not bleeding edge.
# Same image as the Docker Hub link Robert pointed at in the new-app
# request (#1).
#
# No HEALTHCHECK override needed: the upstream image's healthcheck is
# tame, and a temporarily-yellow status during the first-boot DB
# migrations is expected behaviour.
#
# No manifest.settings — Home Assistant's onboarding (admin user, home
# location, units) happens entirely in the browser on first visit, just
# like Jellyfin and Uptime Kuma. Nothing for the install form to ask.

services:
  homeassistant:
    image: homeassistant/home-assistant:stable
    restart: unless-stopped
    ports:
      - "8123:8123"
    environment:
      - TZ=Europe/Berlin
    volumes:
      - furtka_home-assistant_config:/config

volumes:
  furtka_home-assistant_config:
    external: true