ayurishchevandClaude Sonnet 5
cf5c7fa0e8
control-api was the only component deployable via a bare Dockerfile alone (no entrypoint/template, no default mountable config), and there was no compose file wiring the four services' network, healthcheck ordering, or DB volume together. Adds a base docker-compose.yml plus dev (override, auto-loaded) and prod overlays, split by Compose profiles matching the real deployment topology (control-plane/dashboard/prober/validator), a ready-to-copy mock config for control-api so `docker compose up` works out of the box, and the repo's first .gitignore for the local env/config copies developers create from the committed examples. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NeVbMVEiE7XQAkBd7HQgj6
27 lines
610 B
YAML
27 lines
610 B
YAML
# Dev overlay — auto-loaded by `docker compose up` alongside docker-compose.yml.
|
|
# Not used in prod (docker-compose.prod.yml is loaded explicitly instead).
|
|
|
|
services:
|
|
control-api:
|
|
ports:
|
|
- "8080:8080"
|
|
volumes:
|
|
- ./control-api/control-api.docker.yaml:/etc/cloud-ip-validator/control-api.yaml:ro
|
|
|
|
admin-dashboard:
|
|
ports:
|
|
- "8090:8090"
|
|
depends_on:
|
|
control-api:
|
|
condition: service_healthy
|
|
|
|
prober:
|
|
depends_on:
|
|
control-api:
|
|
condition: service_healthy
|
|
|
|
validator-agent:
|
|
depends_on:
|
|
control-api:
|
|
condition: service_healthy
|