Ping already reused Musify's Zitadel and SeaweedFS, but did so through a hardcoded relative path into Musify's own deploy folder (../../../Musify/MusifyM/deploy/zitadel/.output), which only worked because Musify happened to be the one running them. Those services now live in a separate Infrastructure repository instead, so this points there. Also drops Ping's own Postgres container in favor of Infrastructure's shared instance (its own ping_db database), with a wait-for-postgres one-shot replacing the in-file health check.
42 lines
911 B
YAML
42 lines
911 B
YAML
name: ping-dev
|
|
|
|
# Development overlay: publishes the ports to the host so the .NET apps and
|
|
# the web frontend can run from the IDE.
|
|
#
|
|
# docker compose -f deploy/compose.yml -f deploy/compose.dev.yml up -d
|
|
# docker compose -f deploy/compose.yml -f deploy/compose.dev.yml --profile apps up -d --build
|
|
|
|
x-host-alias: &host-alias
|
|
- "host.docker.internal:host-gateway"
|
|
|
|
services:
|
|
livekit:
|
|
ports:
|
|
- "7880:7880" # HTTP / WebSocket signaling
|
|
- "7881:7881" # RTC TCP fallback
|
|
- "50000-50100:50000-50100/udp" # WebRTC media
|
|
|
|
wait-for-postgres:
|
|
extra_hosts: *host-alias
|
|
|
|
zitadel-init:
|
|
extra_hosts: *host-alias
|
|
volumes:
|
|
- ./.env:/workspace/.env
|
|
|
|
seaweedfs-init:
|
|
extra_hosts: *host-alias
|
|
|
|
migrate:
|
|
extra_hosts: *host-alias
|
|
|
|
api:
|
|
ports:
|
|
- "5211:5211"
|
|
extra_hosts: *host-alias
|
|
|
|
web:
|
|
ports:
|
|
- "3100:3100"
|
|
extra_hosts: *host-alias
|