[FEAT] [MVP] Run the stack with Compose: API plus database, local env file, Dokploy deployment

[nicky-mezzina-lhc]

Motivation

We assume that the scaffolded backend only has make db-up to start PostgreSQL on its own and the API runs on the host through make dev.

There is no way to bring the whole stack up together, no committed environment mapping for local development, and no compose file.

Proposed Solution

Up to the developer.

Alternatives Considered

None, Compose and Postgres are accepted architectural decisions.

Acceptance Criteria

• docker compose up runs the mock API server and the database service together
• Local development reads environment variables from .env
• A separate Dokploy-specific compose file exists for deployment
• Documentation reflects both paths

Bonus, if possible

• Run an mock operation that produces an artifact that persists in the database.

Additional Context

The same compose config can include other services from the backend stack: eg. Celery, Redis, RabbitMQ, if it's trivial enough to include.

[nicky-mezzina-lhc]

This was started before my PTO, but if anyone wants to continue, structure proposal:

# ./docker-comose.yml
name: nc3-testing-platform

include:
  - infra/compose/postgres.yml
  - infra/compose/redis.yml
  - infra/compose/rabbitmq.yml
  - infra/compose/celery.yml
  - infra/compose/rauthy.yml # or whatever, for local dev

# ./Makefile
.PHONY: dev export-openapi lint test up down logs scan

dev:
	uv run fastapi dev src/nc3_testing_platform/main.py

up:
	docker compose up -d

down:
	docker compose down

logs:
	docker compose logs -f

# make scan DOMAIN=example.com
DOMAIN ?= example.com
scan:
	docker compose exec -T worker-platform \
		celery -A nc3_testing_platform.worker.app call scan.dispatch --args='["$(DOMAIN)"]'

export-openapi:
	uv run export-openapi

lint:
	uv run ruff check .

test:
	uv run pytest

Write a worker task, call it with Redis, dispatch a run_module() that sleeps across multiple steps and return findings.