# Live-host compatibility overlay. # # This host predates the isolated 172.30.0.0/24 default network and shares the # existing 172.30.0.0/24 meshcore-analytics_default bridge with independently # managed beacon and Discord services. Treat that bridge as external so Compose # never tries to remove it, and reserve a high, collision-free range for the # analytics proxies. The long-lived data-plane services are provided by the # meshcore-infra project on this external network and must be healthy before the # application project is reconciled. services: db-migrate: # Upstream's CI-oriented compose makes db-migrate depend on timescaledb # (service_healthy), which only exists in docker-compose.ci.yml. On this # host timescaledb is an EXTERNAL service of the meshcore-infra project # (data-plane split 2026-08-09), so the dependency cannot resolve and would # invalidate the whole project. The infra project already guarantees the DB # is healthy before the app project is reconciled. depends_on: !reset {} backend: environment: TRUSTED_PROXY_PEERS: ${TRUSTED_PROXY_PEERS:-172.30.0.10,172.30.0.11,172.30.0.12} prometheus: # The live host's independent isolated-network Prometheus owns 9090. ports: !override - "127.0.0.1:9092:9090" app-ukmesh: networks: default: ipv4_address: 172.30.0.10 website-ukmesh: networks: default: ipv4_address: 172.30.0.11 website-dev: networks: default: ipv4_address: 172.30.0.12 anubis-website-ukmesh: networks: default: ipv4_address: 172.30.0.20 anubis-app-ukmesh: networks: default: ipv4_address: 172.30.0.21 anubis-health-check: networks: default: ipv4_address: 172.30.0.22 aliases: - anubis-mesh-health-check cloudflared: networks: default: ipv4_address: 172.30.0.30 meshcore-beacon-ukmesh: {} networks: default: name: meshcore-analytics_default external: true ipam: !reset null