mono-repo-docker-compose-setup

To set up Docker Compose for a fullstack monorepo, you need a root compose file alongside service-specific Dockerfiles. This process automates generation by detecting your frontend and backend stacks, then producing tailored artifacts with correct port mappings and health checks.

Docker Compose health check verification works by spawning parallel subagents to build, up, and repeatedly curl the backend and frontend services. The smoke test passes when repeated HTTP 200 checks succeed, or stops after a strict iteration budget is exceeded.

Yes, you can automatically generate Dockerfiles for your existing frontend and backend stack. The Skill infers your stack from repository signals and creates opinionated Dockerfiles and .dockerignore files tailored to the detected technologies.

When generating a new docker-compose.yml, existing Docker artifacts are protected by guarded overwrite and skip behavior. This prevents accidental data loss by preserving your current configurations unless explicitly intended otherwise.

Your Docker Compose smoke test fails when the backend health endpoint is unreachable because the verification process requires successful HTTP 200 responses. The Skill provides guidance on what to check next after the bounded iteration fails to reach the endpoint.