[Agent] Issue #180: issue 176 adds a multi stage dockerfile #182

Closed
pook wants to merge 1 commit from agent-task/180 into main
Owner

Closes #180

Changes

feat: issue #180 issue-176-adds-a-multi-stage-dockerfile (agent task agent-ta)

Acceptance Criteria

Issue #176 adds a multi-stage Dockerfile but Prisma requires prisma generate to create the client during build. Without this, the production image will fail on any DB query.

Ensure the Dockerfile:

  1. Copies prisma/schema.prisma before npm ci --production
  2. Runs npx prisma generate in the build stage to create the Prisma client
  3. Only copies the generated client (node_modules/.prisma) to the production stage — not the full node_modules from build
  4. Sets DATABASE_URL as a required runtime env var (not baked into image)

Acceptance criteria:

  • docker build . succeeds and produces image with working Prisma client
  • Image size is under 200MB (multi-stage strips dev dependencies)
  • Container fails fast with clear error if DATABASE_URL is not set at runtime

Generated by CEO Planner (priority: 2)

Tokens: 108 in / 5112 out

Closes #180 ## Changes feat: issue #180 issue-176-adds-a-multi-stage-dockerfile (agent task agent-ta) ## Acceptance Criteria Issue #176 adds a multi-stage Dockerfile but Prisma requires `prisma generate` to create the client during build. Without this, the production image will fail on any DB query. Ensure the Dockerfile: 1. Copies `prisma/schema.prisma` before `npm ci --production` 2. Runs `npx prisma generate` in the build stage to create the Prisma client 3. Only copies the generated client (`node_modules/.prisma`) to the production stage — not the full node_modules from build 4. Sets `DATABASE_URL` as a required runtime env var (not baked into image) Acceptance criteria: - `docker build .` succeeds and produces image with working Prisma client - Image size is under 200MB (multi-stage strips dev dependencies) - Container fails fast with clear error if DATABASE_URL is not set at runtime --- *Generated by CEO Planner (priority: 2)* Tokens: 108 in / 5112 out
Author
Owner

Closed 2026-04-10 during pipeline triage.

Why: This PR has merge conflicts with current main and is blocking the CEO agent's view of the backlog. The compliancebot repo had 50 open PRs (most conflicting) and 141 open agent-task issues — CEO couldn't see progress and kept duplicating work.

What was fixed upstream:

  • Git-push race in agent-worker executor (dispatch jobs collided on agent/dispatch/* branch name). RunId now threaded through shim → dispatch → executor for unique branches.
  • Shim /shim/ceo route now injects current open issues/PRs into the CEO prompt + refuses dispatch if backlog exceeds 20.

Reopen / resubmit this PR against current main if the work is still relevant — CEO will now see it and avoid duplicating.

Closed 2026-04-10 during pipeline triage. **Why:** This PR has merge conflicts with current `main` and is blocking the CEO agent's view of the backlog. The compliancebot repo had 50 open PRs (most conflicting) and 141 open agent-task issues — CEO couldn't see progress and kept duplicating work. **What was fixed upstream:** - Git-push race in agent-worker executor (dispatch jobs collided on `agent/dispatch/*` branch name). RunId now threaded through shim → dispatch → executor for unique branches. - Shim `/shim/ceo` route now injects current open issues/PRs into the CEO prompt + refuses dispatch if backlog exceeds 20. **Reopen / resubmit** this PR against current main if the work is still relevant — CEO will now see it and avoid duplicating.
pook closed this pull request 2026-04-10 15:05:11 -04:00

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pook/compliancebot!182
No description provided.