docs: record that the registry is Gitea's built-in container registry
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / Lint + typecheck (pull_request) Failing after 22s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Failing after 9s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 5s
PR Check / AI code review (opencode) (pull_request) Failing after 13s

Verified by logging in to registry.noelsabia.dev and pushing by hand.
The registry is Gitea's own, not a separately deployed component, so
there is nothing to stand up or reinvent.
This commit is contained in:
Noel Sabia committed 2026-10-31 18:56:56 +01:00
1 parent efb73378e9
commit 5f7027bd86
2 files changed
+16

No files matched your search

+12
View File
@@ -20,6 +20,18 @@ sources:
# Decision
**The registry is Gitea's own, and that is the default.** Gitea ships a
built-in container registry per owner/organisation
([docs.gitea.com - container](https://docs.gitea.com/usage/packages/container/)).
`registry.noelsabia.dev` is that registry: the `/cv_website/` path segment
is the Gitea organisation, images live under the package of the
repository that pushed them. Verified 2026-10-31 - Noel logged in with
`docker login registry.noelsabia.dev` and can push. There is nothing to
stand up and nothing to reinvent: no separate Registry/Harbor
deployment, no extra hosting, TLS is already handled by the same server
that serves Gitea. The publishing workflow exists only to automate
pushes to this built-in registry.
`.gitea/workflows/publish-image.yml` builds `Dockerfile` and pushes the
result to the own registry: