docs: record that the registry is Gitea's built-in container registry #32

Merged
Noel merged 4 commits from feat/docs_registrys into main 2026-10-31 19:03:08 +00:00
2 changed files with 16 additions and 0 deletions
Showing only changes of commit 5f7027bd86 - Show all commits

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:
+4
View File
@@ -1,5 +1,9 @@
# Update Log
## 2026-10-31 (registry confirmed: Gitea's built-in container registry)
* **Confirmation**: Logged in to `registry.noelsabia.dev` and pushed by hand - push access works. The registry is **Gitea's built-in container registry** ([docs.gitea.com/usage/packages/container](https://docs.gitea.com/usage/packages/container/)), not a separately deployed component: `registry.noelsabia.dev` is the same server as Gitea, and the `/cv_website/` path segment is the organisation namespace. This is the default - no Registry/Harbor to stand up, nothing to reinvent. Noted as such at the top of [Publishing images to the own registry](decisions/registry-publishing.md).
## 2026-10-27 (release-please still never tagged: the deleted head branch)
* **Fix**: [release-please-config.json](../release-please-config.json) gained `"changelog-host": "https://git.noelsabia.dev"` - the changelog compare links were generated against `github.com/CV_Website/CV_Site_Nuxt`, a host this repository does not live on. Root cause of the missing tags: **Gitea rewrites `head.ref` to `refs/pull/<n>/head` when the merged PR's branch is deleted**, and release-please parses that field as the release branch, so `BranchName.parse` fails and the release is dropped - silently, exit code 0. Evidence: run 143 (task 475) logs `✖ Bad branch name: refs/pull/22/head` right after `Found pull request #22`, then `Expected 1 releases, only found 0`; #22 did carry `autorelease: pending`. The repository deleted every merged branch (`default_delete_branch_after_merge: true`); it is `false` now. Four versions (1.1.0-1.4.0) were consumed by the manifest with no tag ever created, so the release baseline has to be restored by hand. See [Release engineering](decisions/release-engineering.md).