Files
ukmesh/docker-compose.live.yml
T
gadgethd 9f6065a93c fix(deploy): align live overlay static IPs with the VPS 172.30.0.0/24 external network
The overlay still carried pre-migration 172.18.30.x addresses; the VPS
meshcore-analytics_default bridge is 172.30.0.0/24 (containers already run
on 172.30.0.x). Stale IPs made compose unable to (re)create app-ukmesh
(no subnet contains 172.18.30.10).
2026-08-07 11:16:13 +00:00

62 lines
1.5 KiB
YAML

# 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. Fresh/CI deployments must continue to use only
# docker-compose.yml and its isolated network.
services:
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