Files
duocthu/infra/docker/docker-compose.yml
T

129 lines
3.5 KiB
YAML

# Local development topology. App services are commented out until their
# Dockerfiles exist (Phase 5) — infra services can be started standalone
# today for Phase 1 (ingestion) development, e.g.:
# docker compose up postgres qdrant redis
services:
postgres:
image: postgres:16-alpine
environment:
POSTGRES_USER: duoc_thu
POSTGRES_PASSWORD: duoc_thu
POSTGRES_DB: duoc_thu
ports:
- "5432:5432"
volumes:
- postgres-data:/var/lib/postgresql/data
qdrant:
image: qdrant/qdrant:latest
ports:
- "6333:6333"
- "6334:6334"
volumes:
- qdrant-data:/qdrant/storage
redis:
image: redis:7-alpine
ports:
- "6379:6379"
volumes:
- redis-data:/data
# Observability. `ai-service` runs on the host during development, so
# Prometheus reaches it via host.docker.internal rather than a service name;
# when ai-service moves into this compose file, change the target to
# `ai-service:8000` and drop the extra_hosts entry.
prometheus:
image: prom/prometheus:v3.3.0
command:
- --config.file=/etc/prometheus/prometheus.yml
- --storage.tsdb.path=/prometheus
- --enable-feature=exemplar-storage
ports:
- "9090:9090"
volumes:
- ./prometheus/prometheus.yml:/etc/prometheus/prometheus.yml:ro
- prometheus-data:/prometheus
extra_hosts:
- "host.docker.internal:host-gateway"
grafana:
image: grafana/grafana:11.5.2
ports:
- "3002:3000"
environment:
# Local development only. The dashboard is the demo surface, and a login
# wall in front of it during a review is friction with no security value
# on a laptop-local stack. Do not carry this into the k3s deployment.
GF_AUTH_ANONYMOUS_ENABLED: "true"
GF_AUTH_ANONYMOUS_ORG_ROLE: Admin
GF_AUTH_DISABLE_LOGIN_FORM: "true"
volumes:
- ./grafana/provisioning:/etc/grafana/provisioning:ro
- ./grafana/dashboards:/var/lib/grafana/dashboards:ro
- grafana-data:/var/lib/grafana
depends_on:
- prometheus
- tempo
tempo:
image: grafana/tempo:2.7.2
command: ["-config.file=/etc/tempo/tempo.yml"]
ports:
- "3200:3200"
volumes:
- ./tempo/tempo.yml:/etc/tempo/tempo.yml:ro
- tempo-data:/var/tempo
otel-collector:
image: otel/opentelemetry-collector-contrib:0.123.0
command: ["--config=/etc/otelcol/config.yml"]
ports:
- "4317:4317"
- "4318:4318"
- "13133:13133"
volumes:
- ./otel/collector.yml:/etc/otelcol/config.yml:ro
depends_on:
- tempo
# ai-service:
# build: ../../apps/ai-service
# env_file: ../../apps/ai-service/.env
# ports: ["8000:8000"]
# depends_on: [qdrant]
#
# web:
# build: ../../apps/web
# ports: ["3001:3000"]
# depends_on: [api-gateway]
# auth-service and api-gateway are real (see the plan this was built
# from) — user-service/chat-service stay commented above pending their own
# scope, and ai-service/web stay commented per the pre-existing
# host-during-dev convention noted at the top of this file.
auth-service:
build: ../../apps/auth-service
env_file: ../../apps/auth-service/.env
ports:
- "3010:3010"
depends_on:
- postgres
api-gateway:
build: ../../apps/api-gateway
env_file: ../../apps/api-gateway/.env
ports:
- "3000:3000"
depends_on:
- auth-service
volumes:
postgres-data:
qdrant-data:
redis-data:
prometheus-data:
grafana-data:
tempo-data: