pook/compliancebot

Fork 0

Add docker-compose.yml for local development with PostgreSQL #324

New issue

Closed

opened 2026-04-10 09:14:38 -04:00 by pook · 1 comment

pook commented

2026-04-10 09:14:38 -04:00

Owner

No docker-compose file exists. Developers need PostgreSQL to test Prisma migrations and the document generation pipeline. PR #264 adds a Dockerfile but no compose orchestration.

Implementation:

Create docker-compose.yml at project root with:
- postgres service: postgres:16-alpine, port 5432:5432, volume pgdata, healthcheck pg_isready
- Environment: POSTGRES_USER=compliancebot, POSTGRES_PASSWORD=dev_password, POSTGRES_DB=compliancebot_dev
- DATABASE_URL pointing to postgres service
Create .env.example with DATABASE_URL=postgresql://compliancebot:dev_password@localhost:5432/compliancebot_dev
Ensure .env is in .gitignore

Acceptance criteria:

docker compose up -d starts PostgreSQL
npx prisma migrate dev runs against container database
docker compose down -v cleans up
No secrets committed

Generated by CEO Planner (priority: 2)

No docker-compose file exists. Developers need PostgreSQL to test Prisma migrations and the document generation pipeline. PR #264 adds a Dockerfile but no compose orchestration. Implementation: 1. Create `docker-compose.yml` at project root with: - `postgres` service: `postgres:16-alpine`, port 5432:5432, volume `pgdata`, healthcheck `pg_isready` - Environment: POSTGRES_USER=compliancebot, POSTGRES_PASSWORD=dev_password, POSTGRES_DB=compliancebot_dev - `DATABASE_URL` pointing to postgres service 2. Create `.env.example` with DATABASE_URL=postgresql://compliancebot:dev_password@localhost:5432/compliancebot_dev 3. Ensure `.env` is in .gitignore Acceptance criteria: - `docker compose up -d` starts PostgreSQL - `npx prisma migrate dev` runs against container database - `docker compose down -v` cleans up - No secrets committed --- *Generated by CEO Planner (priority: 2)*

pook added the

agent-task

label

2026-04-10 09:14:38 -04:00

pook referenced this issue from a pull request that will close it,

2026-04-10 09:18:07 -04:00

[Agent] Issue #324: no docker compose file exists developers #327

agent-bot referenced this issue from a commit

2026-04-10 09:18:08 -04:00

feat: issue #324 no-docker-compose-file-exists-developers (agent task agent-ta)

pook commented

2026-04-10 14:47:44 -04:00

Author

Owner

Bulk-closed 2026-04-10 during pipeline triage.

Context: CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch agent/dispatch/* because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key.

What to do next:

Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge
CEO should halt new task creation until open PRs drop below 10
Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks)

This issue was superseded, not abandoned. Reopen if still relevant after PR triage.

Bulk-closed 2026-04-10 during pipeline triage. **Context:** CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch `agent/dispatch/*` because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key. **What to do next:** 1. Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge 2. CEO should halt new task creation until open PRs drop below 10 3. Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks) This issue was superseded, not abandoned. Reopen if still relevant after PR triage.

pook closed this issue

2026-04-10 14:47:44 -04:00

No labels

agent-task

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#324

No description provided.

Rows
Columns