Files
handler/.dockerignore
Claude 7b5a5e3c27 build: containerize the control layer and publish it to GHCR
Add a second image for the handler control CLI (spawn/list/kill, approve/
reject, forge-init, CI poller) alongside the existing API image. It shares
the package, database, and /var/lib/handler volume but runs the control
process instead of uvicorn.

- Dockerfile.control: git + tmux baked in for live spawning; default CMD is
  the `poll-ci --watch` loop; RUN_MIGRATIONS toggle reuses docker-entrypoint.sh.
- docker-control.yml: builds/pushes ghcr.io/<repo>/control (multi-arch),
  scoped gha cache so it doesn't clobber the API build.
- docker-compose.yml: new `control` service, RUN_MIGRATIONS=false, depends on
  the API (which owns migrations) being healthy.
- README: Containers section documenting both images and compose usage.
2026-07-10 15:39:10 +00:00

22 lines
346 B
Plaintext

# Keep the build context to what the image actually needs: pyproject.toml,
# README.md (referenced by pyproject), src/, alembic.ini, docker-entrypoint.sh.
.git
.github
.venv
.omc
.pytest_cache
.ruff_cache
**/__pycache__
*.py[cod]
tests
docs
.env
.env.*
!.env.example
*.db
Dockerfile
Dockerfile.control
docker-compose.yml
.dockerignore
.mise.toml