stroblmeandClaude Fable 5 b4d5aa6186 Let two backend CI runs share a runner host ...

The job kept the fixed container names and the fixed 5432 that compose.ci.yml
resets for every other job, so a second run could not start. Layering that
file leaves the db on a port Docker assigns, which the suite is told about,
and the project name is now per run so one teardown cannot take another run's
database with it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01H7LwYgJfpkbLCTeiAf8U4A

2026-08-16 16:46:25 +02:00

..

compose.ci.yml

Let two backend CI runs share a runner host

2026-08-16 16:46:25 +02:00

compose.dev.yml

Supervise the engine's host: deep health, loop watchdog, one worker

2026-08-16 07:14:28 +02:00

compose.local.yml

Green the lint gate and drop the local-stack host ports

2026-08-09 15:52:57 +02:00

compose.traefik.yml

Restructure docker into layered compose files, add a Makefile

2026-08-09 15:21:34 +02:00

compose.yml

Supervise the engine's host: deep health, loop watchdog, one worker

2026-08-16 07:14:28 +02:00