docker-compose-delivery

What problem does it solve?

It solves the problem of inconsistent local setup for AgentHub demos and acceptance testing by standardizing Docker Compose topology, healthchecks, secrets handling, and smoke-test expectations.

Core Features & Use Cases

• Compose delivery contract: Defines how to organize compose.yaml/docker-compose.yml and any optional overrides so docker compose config works and environments don’t drift.
• Service topology & Child Agent pattern: Establishes required characteristics for every Child Agent service (stable service name, internal port, /health, safe logging, and smoke-test visibility) without hard-coding agent names.
• Readiness, healthcheck, and smoke-test layers: Requires healthcheck coverage (mysql/gateway/frontend/agents), forbids readiness hacks like sleep, and specifies multi-level smoke tests from config validation to minimal run.
• Safety rules for secrets and logs: Prevents committing real .env/tokens, avoids secret leakage into images, smoke-test output, and container logs.

Quick Start

Ask for the compose delivery checklist by targeting the docker-compose-delivery skill to confirm your local AgentHub demo can start, pass healthchecks, and succeed on smoke test without leaking secrets.