docs: use Gitea's own registry on git.noelsabia.dev
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / Lint + typecheck (pull_request) Failing after 1m17s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 7s
PR Check / Dependency audit (pull_request) Failing after 10s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 5s
PR Check / AI code review (opencode) (pull_request) Failing after 14s
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / Lint + typecheck (pull_request) Failing after 1m17s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 7s
PR Check / Dependency audit (pull_request) Failing after 10s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 5s
PR Check / AI code review (opencode) (pull_request) Failing after 14s
The registry endpoint is the Gitea hostname itself, not a separate registry.noelsabia.dev host. Point IMAGE, docker login and the v2 manifests check at git.noelsabia.dev and record the correction.
This commit is contained in:
1 parent
5f7027bd86
commit
700b1030fc
5 files changed
+40
-24
No files matched your search
@@ -5,7 +5,7 @@
|
||||
* [Vulnerability audit policy](vulnerability-audit-policy.md) - Blocking audit, reviewed ignore-list for unfixable advisories, and the pnpm-11 settings home.
|
||||
* [Release engineering](release-engineering.md) - release-please in manifest mode, conventional commits as input, message format enforced at commit time.
|
||||
* [Snyk paused and secrets policy](snyk-paused-and-secrets-policy.md) - Why the job is skipped rather than deleted, and the token scopes every workflow secret needs.
|
||||
* [Publishing images to the own registry](registry-publishing.md) - A release tag builds and pushes to registry.noelsabia.dev; main pushes do not build.
|
||||
* [Publishing images to the own registry](registry-publishing.md) - A release tag builds and pushes to git.noelsabia.dev; main pushes do not build.
|
||||
* [Dev container shape](dev-container-shape.md) - The source is bind-mounted into a container that already holds the dependencies, and the dev server runs as the image's `node` user.
|
||||
* [Build layer order](build-layer-order.md) - Why the manifests are copied before the source, and what invalidates what.
|
||||
* [Build context filter](build-context-filter.md) - What `.dockerignore` may exclude, and the one thing it must never exclude.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
type: Decision
|
||||
title: Publishing images to the own registry
|
||||
description: A release tag builds the production image and pushes it to registry.noelsabia.dev, because that is the only way Kubernetes can pull it.
|
||||
description: A release tag builds the production image and pushes it to git.noelsabia.dev, because that is the only way Kubernetes can pull it.
|
||||
tags: [decision, ci, docker, registry, gitea-actions]
|
||||
status: draft
|
||||
generated: { by: opencode-go/deepseek-v4.1-flash, at: 2026-10-24T00:00:00Z }
|
||||
@@ -20,25 +20,36 @@ sources:
|
||||
|
||||
# Decision
|
||||
|
||||
**The registry is Gitea's own, and that is the default.** Gitea ships a
|
||||
**The registry is Gitea's own, served on the Gitea host.** 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.
|
||||
The endpoint is the Gitea hostname itself - `git.noelsabia.dev` - and the
|
||||
`/cv_website/` path segment is the Gitea organisation; images live under
|
||||
the package of the repository that pushed them:
|
||||
|
||||
```
|
||||
docker login git.noelsabia.dev
|
||||
git.noelsabia.dev/cv_website/nuxt:<tag>
|
||||
```
|
||||
|
||||
There is nothing to stand up and nothing to reinvent: no separate
|
||||
Registry/Harbor deployment, no extra hostname, no extra certificate.
|
||||
TLS and auth are the ones Gitea already serves. The publishing workflow
|
||||
exists only to automate pushes to this built-in registry.
|
||||
|
||||
**Corrected 2026-10-31:** `registry.noelsabia.dev` was a separate
|
||||
hostname set up before this was known. It is not needed and is being
|
||||
removed on the server side; this repository now uses
|
||||
`git.noelsabia.dev` everywhere. Any leftover `registry.noelsabia.dev`
|
||||
reference is a bug.
|
||||
|
||||
`.gitea/workflows/publish-image.yml` builds `Dockerfile` and pushes the
|
||||
result to the own registry:
|
||||
|
||||
```
|
||||
registry.noelsabia.dev/cv_website/nuxt:v1.2.3
|
||||
registry.noelsabia.dev/cv_website/nuxt:sha-<12-char-sha>
|
||||
registry.noelsabia.dev/cv_website/nuxt:latest # newest release only
|
||||
git.noelsabia.dev/cv_website/nuxt:v1.2.3
|
||||
git.noelsabia.dev/cv_website/nuxt:sha-<12-char-sha>
|
||||
git.noelsabia.dev/cv_website/nuxt:latest # newest release only
|
||||
```
|
||||
|
||||
**Trigger is the release tag, not the main push.** release-please creates
|
||||
@@ -115,7 +126,7 @@ run.
|
||||
|
||||
| Gitea secret | Use |
|
||||
|---|---|
|
||||
| `REGISTRY_USERNAME` | basic-auth user for `docker login registry.noelsabia.dev` |
|
||||
| `REGISTRY_USERNAME` | basic-auth user for `docker login git.noelsabia.dev` |
|
||||
| `REGISTRY_PASSWORD` | basic-auth password (or token) for the same login |
|
||||
|
||||
Both are repo secrets. The login uses `--password-stdin` so the value never
|
||||
@@ -129,7 +140,7 @@ appears in the process list or the log.
|
||||
forever; without the socket it fails at `Check daemon access`.
|
||||
3. `pr-checker.yml` still runs on a label whose runner has no socket.
|
||||
4. Namespace `cv` has an `imagePullSecret` for the same credentials.
|
||||
5. `registry.noelsabia.dev` answers over HTTPS.
|
||||
5. `git.noelsabia.dev` answers over HTTPS.
|
||||
|
||||
# Guards in the workflow
|
||||
|
||||
@@ -165,7 +176,7 @@ appears in the process list or the log.
|
||||
* That the smoke test passes on arm64. The same script was run against an
|
||||
x86_64 build of the merged tree and answered 2xx; the arm64 run is the
|
||||
first release.
|
||||
* That `registry.noelsabia.dev` is reachable over HTTPS from the runner.
|
||||
* That `git.noelsabia.dev` is reachable over HTTPS from the runner.
|
||||
A plain-HTTP endpoint fails `docker login` with `server gave HTTP
|
||||
response to HTTPS client` and needs `insecure-registries` on the daemon
|
||||
plus `registries.yaml` on k3s.
|
||||
|
||||
Reference in new issue
Block a user