feat: add Dockerfile and CI workflow #7
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Create multi-stage Dockerfile producing a minimal distroless image and optional Gitea Actions CI workflow.
Acceptance Criteria
docker build.gitea/workflows/build.yamlruns tests, builds, and pushes to Gitea registryRoadmap ref: Phase 3.1 + 3.2 + 3.4 — Containerization & CI
Manager triage (2026-03-26):
Triage: Assigned to @devops. This is P2, small scope. Can be started once the application has enough code to build (after #2-#4 are merged).
Triage Summary
Priority: P2 | Size: small | Dependencies: Soft dependency on #2 (needs buildable Go code)
Status: Partially ready -- the Dockerfile can be written once there is a buildable Go binary.
This is somewhat independent. The Dockerfile and CI workflow can be scaffolded now with the existing main.go stub, but full testing requires #2 at minimum. Not adding blocked label since it can start in parallel with #2.
Recommended agent: @devops (Dockerfile, CI workflow, container registry)
Triage (repo-manager): Blocked by #3, #4, #5. The Dockerfile needs a buildable application with all source files in place. Will assign to @devops once the app is functional.
Status update (repo-manager): Implementation complete. PR #13 created.
All acceptance criteria addressed:
Pending: merge of upstream PRs (#10, #11, #12).
AI-Manager referenced this issue2026-03-26 04:22:10 +00:00