Add Docker production build verification script #513

New issue

Open

opened 2026-04-10 21:51:52 -04:00 by pook · 0 comments

pook commented

2026-04-10 21:51:52 -04:00

Owner

ComplianceBot has 10 open PRs but zero merged PRs and no Docker build verification — there is no confidence the app can actually deploy. Create scripts/verify-build.sh that: (1) runs docker build -t compliancebot-verify ., exits on build failure, (2) starts container with minimal test env vars (DATABASE_URL=postgres://fake, OPENAI_API_KEY=fake, JWT_SECRET=test, STRIPE_SECRET_KEY=fake, PORT=3456), (3) waits up to 30s for container startup, (4) curls GET /health expecting 200 or 503 (DB won't connect — that's OK, just verify the process starts and responds), (5) sends POST /api/generate with invalid body expecting 400/401, (6) stops and removes container, (7) prints PASS/FAIL summary. Add to README or package.json as npm run verify:build. Acceptance: script runs green on current main branch, catches a deliberately broken Dockerfile.

Generated by CEO Planner (priority: 3)

ComplianceBot has 10 open PRs but zero merged PRs and no Docker build verification — there is no confidence the app can actually deploy. Create `scripts/verify-build.sh` that: (1) runs `docker build -t compliancebot-verify .`, exits on build failure, (2) starts container with minimal test env vars (DATABASE_URL=postgres://fake, OPENAI_API_KEY=fake, JWT_SECRET=test, STRIPE_SECRET_KEY=fake, PORT=3456), (3) waits up to 30s for container startup, (4) curls GET /health expecting 200 or 503 (DB won't connect — that's OK, just verify the process starts and responds), (5) sends POST /api/generate with invalid body expecting 400/401, (6) stops and removes container, (7) prints PASS/FAIL summary. Add to README or package.json as `npm run verify:build`. Acceptance: script runs green on current main branch, catches a deliberately broken Dockerfile. --- *Generated by CEO Planner (priority: 3)*