Files
home-automation/apps/homekit/docker-compose.yaml
Wolfgang Hottgenroth 5a13183123
All checks were successful
ci/woodpecker/push/build/1 Pipeline was successful
ci/woodpecker/push/predeploy Pipeline was successful
ci/woodpecker/push/build/2 Pipeline was successful
ci/woodpecker/push/build/4 Pipeline was successful
ci/woodpecker/push/deploy/2 Pipeline was successful
ci/woodpecker/push/deploy/4 Pipeline was successful
ci/woodpecker/push/deploy/3 Pipeline was successful
ci/woodpecker/push/deploy/1 Pipeline was successful
ci/woodpecker/push/build/3 Pipeline was successful
homekit
2025-11-30 21:56:52 +01:00

42 lines
1.2 KiB
YAML

version: "3.9"
services:
homekit-bridge:
build:
context: ../..
dockerfile: apps/homekit/Dockerfile
container_name: homekit-bridge
# Host-Netzwerk, damit mDNS/Bonjour im LAN sichtbar ist
network_mode: host
# Environment-Variablen für die Bridge-Konfiguration
environment:
# Anzeigename der Bridge in HomeKit
- HOMEKIT_NAME=Home Automation Bridge
# HomeKit-Setup-PIN (Format XXX-YY-ZZZ)
- HOMEKIT_PIN=031-45-154
# TCP-Port, auf dem HAP-Python lauscht (muss zum EXPOSE passen)
- HOMEKIT_PORT=51826
# Basis-URL deiner bestehenden API (anpassen!)
# Beispiel: UI/API im gleichen Docker-Netzwerk → http://api:8001
# Oder IP/Host im LAN → z.B. http://192.168.1.10:8001
- API_BASE=http://homea2-api-internal.hottis.de
# Optionales API-Token, falls deine API Auth nutzt
- HOMEKIT_API_TOKEN=
# Pfad für Persistenz der HomeKit-Daten im Container
- HOMEKIT_PERSIST_FILE=/data/homekit.state
# Persistentes Volume für Pairing-Infos (homekit.state)
volumes:
- homekit_data:/data
# Neustart-Policy
restart: unless-stopped
volumes:
homekit_data:
driver: local