graphql-engine/dc-agents/docker-compose.yaml
Samir Talwar 9fe793e828 Split the Docker Compose files into pieces.
With the vague idea that we can eventually avoid publishing ports at all, at least in CI, while still having the flexibility to publish ports locally.

If we can get there, it should help with the issues we're seeing on CI, where ports are already allocated from previous runs and containers aren't properly cleaned up.

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/6836
GitOrigin-RevId: 1d636c73ae889e45e80ad52042c56daa1b9d5838
2022-11-14 12:39:37 +00:00

44 lines
830 B
YAML

version: "3.6"
services:
dc-reference-agent:
build:
context: .
dockerfile: Dockerfile-reference
ports:
- "65005:8100"
healthcheck:
test:
- CMD
- curl
- -f
- localhost:8100/health
start_period: 5s
interval: 5s
timeout: 10s
retries: 20
dc-sqlite-agent:
build:
context: .
dockerfile: Dockerfile-sqlite
ports:
- "65007:8100"
volumes:
- "./sqlite/test/db.chinook.sqlite:/db.chinook.sqlite"
- "./sqlite/test/db.sqlite:/db.sqlite"
environment:
METRICS: y
PRETTY_PRINT_LOGS: y
LOG_LEVEL: debug
healthcheck:
test:
- CMD
- curl
- -f
- localhost:8100/health
start_period: 5s
interval: 5s
timeout: 10s
retries: 20