Compose was interpolating ${DATABASE_URL} from the Act runner, so containerized tests could hit shared Postgres. Use COMPOSE_DATABASE_URL, an ephemeral compose project with down -v, and clear DB env in unit-test workflows.
39 lines
1.2 KiB
YAML
39 lines
1.2 KiB
YAML
services:
|
|
db:
|
|
image: postgres:16-alpine
|
|
environment:
|
|
POSTGRES_DB: scha
|
|
POSTGRES_USER: scha
|
|
POSTGRES_PASSWORD: scha
|
|
volumes:
|
|
- postgres_data:/var/lib/postgresql/data
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "pg_isready -U scha -d scha"]
|
|
interval: 5s
|
|
timeout: 5s
|
|
retries: 10
|
|
start_period: 10s
|
|
|
|
web:
|
|
build: .
|
|
ports:
|
|
- "8000:8000"
|
|
# No required env_file — CI has no .env. Defaults below; for local secrets:
|
|
# docker compose --env-file .env up
|
|
#
|
|
# Do NOT interpolate ${DATABASE_URL} here. On the Act runner / control node that
|
|
# var often points at shared prod/beta Postgres; compose would bake it into
|
|
# containerized tests. Use COMPOSE_DATABASE_URL only if you need to override.
|
|
environment:
|
|
DJANGO_ENV: ${DJANGO_ENV:-dev}
|
|
DJANGO_SECRET_KEY: ${DJANGO_SECRET_KEY:-dev-only-change-me}
|
|
DJANGO_DEBUG: ${DJANGO_DEBUG:-true}
|
|
DJANGO_ALLOWED_HOSTS: ${DJANGO_ALLOWED_HOSTS:-localhost,127.0.0.1,0.0.0.0}
|
|
DATABASE_URL: ${COMPOSE_DATABASE_URL:-postgres://scha:scha@db:5432/scha}
|
|
depends_on:
|
|
db:
|
|
condition: service_healthy
|
|
|
|
volumes:
|
|
postgres_data:
|