The brief is fully captured in the bundle; it stays in git history. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
766 B
766 B
type, title, description, tags, status, generated, verified
| type | title | description | tags | status | generated | verified | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Decision | CI/CD on Gitea Actions | The existing Gitea instance and runner on the home server build, scan, deploy and version the project. |
|
stable |
|
|
Decision
Use Gitea Actions with the runner already on the home server, the Gitea container registry, and the Gitea variant of the release-please action.
Why
- GitHub Actions cannot reach the k3s API behind the tunnel. The local runner can.
- No new tooling: Gitea, its runner and its registry already exist.
- No GitOps agent (Flux, Argo) needed.
Details
See delivery.