Gitea's built-in registry is served on the Gitea host itself; there is no separate registry.noelsabia.dev host.
1.7 KiB
1.7 KiB
type, title, description, tags, status, generated
| type | title | description | tags | status | generated | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Pipeline | Delivery | Gitea Actions on the home server scan, build, push to the Gitea registry, deploy with kubectl, and version with release-please. |
|
stable |
|
Pipeline
push to main ─► Gitea Actions (runner on the home server)
├─ go test ./...
├─ snyk test
├─ build images: gateway (with Nuxt), chapter
├─ push to the Gitea container registry (git.noelsabia.dev)
└─ kubectl apply -k deploy/
─► release-please (Gitea variant) opens a release PR; merging it tags the version
Details
- Commits: Conventional Commits.
feat:bumps minor,fix:bumps patch,docs:andchore:do not release. - Image tags: the git SHA, so every deploy is traceable.
- Registry pull: the cluster needs an
imagePullSecretfor the Gitea registry (git.noelsabia.dev), or/etc/containerd/certs.d/<registry>/hosts.tomlif the registry is plain HTTP. - Runner permissions: a kubeconfig for a ServiceAccount that can only
manage resources in
cv. - Jobs are immutable: changing a completed chapter's Job spec needs a delete before apply. Rare, since finished chapters do not change.
- Snyk: needs a
SNYK_TOKENsecret in Gitea. - Memory: builds run on the same 4 GB server. Runner capacity 1, Node capped at 512 MB, swap as a safety net. See server budget.
Later
- k6 as a release gate needs a staging target. See open questions.