diff --git a/.gitea/workflows/publish-image.yml b/.gitea/workflows/publish-image.yml index d1562ec..4ab6b9e 100644 --- a/.gitea/workflows/publish-image.yml +++ b/.gitea/workflows/publish-image.yml @@ -18,8 +18,8 @@ concurrency: env: # Registry host + repository path. The path segment is the Gitea - # organisation, so k3s pulls registry.noelsabia.dev/cv_website/nuxt:. - IMAGE: registry.noelsabia.dev/cv_website/nuxt + # organisation, so k3s pulls git.noelsabia.dev/cv_website/nuxt:. + IMAGE: git.noelsabia.dev/cv_website/nuxt APP_DIR: . jobs: @@ -125,7 +125,7 @@ jobs: [ -n "$REGISTRY_USERNAME" ] || { echo "::error::secret REGISTRY_USERNAME is empty"; exit 1; } [ -n "$REGISTRY_PASSWORD" ] || { echo "::error::secret REGISTRY_PASSWORD is empty"; exit 1; } printf '%s' "$REGISTRY_PASSWORD" \ - | docker login registry.noelsabia.dev -u "$REGISTRY_USERNAME" --password-stdin + | docker login git.noelsabia.dev -u "$REGISTRY_USERNAME" --password-stdin - name: Refuse to overwrite a published version env: @@ -143,7 +143,7 @@ jobs: # Debian 20.10 client fails that command on OCI indexes with # "unsupported manifest media type and no default available", # for existing and missing tags alike. - url="https://registry.noelsabia.dev/v2/cv_website/nuxt/manifests/${VERSION}" + url="https://git.noelsabia.dev/v2/cv_website/nuxt/manifests/${VERSION}" code=$(curl -s -o /dev/null -w '%{http_code}' \ -u "${REGISTRY_USERNAME}:${REGISTRY_PASSWORD}" \ -H 'Accept: application/vnd.docker.distribution.manifest.v2+json' \ diff --git a/OKF_Nuxt/decisions/index.md b/OKF_Nuxt/decisions/index.md index 283681c..54b53f7 100644 --- a/OKF_Nuxt/decisions/index.md +++ b/OKF_Nuxt/decisions/index.md @@ -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. diff --git a/OKF_Nuxt/decisions/registry-publishing.md b/OKF_Nuxt/decisions/registry-publishing.md index 38116ac..4d01f45 100644 --- a/OKF_Nuxt/decisions/registry-publishing.md +++ b/OKF_Nuxt/decisions/registry-publishing.md @@ -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: +``` + +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. diff --git a/OKF_Nuxt/index.md b/OKF_Nuxt/index.md index 41f2d09..d315890 100644 --- a/OKF_Nuxt/index.md +++ b/OKF_Nuxt/index.md @@ -23,7 +23,7 @@ config files — the configs say what, these documents say why. * [Vulnerability audit policy](decisions/vulnerability-audit-policy.md) - Blocking audit; reviewed ignore-list for unfixable advisories in pnpm-workspace.yaml. * [Release engineering](decisions/release-engineering.md) - release-please in manifest mode; conventional commits enforced at commit time. * [Snyk paused and secrets policy](decisions/snyk-paused-and-secrets-policy.md) - Quota-paused job kept in place; `write:issue` scope required on every workflow token. -* [Publishing images to the own registry](decisions/registry-publishing.md) - A release tag builds the image and pushes it to registry.noelsabia.dev; the runner socket it needs is root-equivalent and belongs on a separate label. +* [Publishing images to the own registry](decisions/registry-publishing.md) - A release tag builds the image and pushes it to git.noelsabia.dev; the runner socket it needs is root-equivalent and belongs on a separate label. ## Docker and development environment diff --git a/OKF_Nuxt/log.md b/OKF_Nuxt/log.md index debce3c..56f419c 100644 --- a/OKF_Nuxt/log.md +++ b/OKF_Nuxt/log.md @@ -1,8 +1,13 @@ # Update Log +## 2026-10-31 (registry host corrected: Gitea's built-in registry on git.noelsabia.dev) + +* **Correction**: `registry.noelsabia.dev` is gone from the documentation and the workflow. Gitea's built-in container registry is served on the Gitea hostname itself, so the image is **`git.noelsabia.dev/cv_website/nuxt:`** ([docs.gitea.com/usage/packages/container](https://docs.gitea.com/usage/packages/container/)). `registry.noelsabia.dev` was a separate hostname set up before that was known; the server-side setup is being reverted. No separate registry, no extra hostname, no extra certificate - Gitea already provides this by default. +* **Update**: [publish-image.yml](../.gitea/workflows/publish-image.yml) - `IMAGE`, `docker login` and the v2 `manifests/` immutability check all point at `git.noelsabia.dev`. [Publishing images to the own registry](decisions/registry-publishing.md) records the corrected host and the reason. + ## 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). +* **Confirmation**: Logged in 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: it is served on the Gitea host, and the `/cv_website/` path segment is the organisation namespace. This is the default - no Registry/Harbor to stand up, nothing to reinvent. Host corrected in the entry above; see [Publishing images to the own registry](decisions/registry-publishing.md). ## 2026-10-27 (release-please still never tagged: the deleted head branch) @@ -14,7 +19,7 @@ ## 2026-10-24 (release publishes an image) -* **Creation**: [publish-image.yml](../.gitea/workflows/publish-image.yml) - a `vX.Y.Z` tag push builds `Dockerfile` on the arm64 runner and pushes `registry.noelsabia.dev/cv_website/nuxt` as the version and `sha-<12>`, plus `latest` when that tag is the newest release. Main pushes deliberately do not build: the registry holds releases, not commits. The job uses the runner's own Docker daemon (client only in the `node:22-bookworm` container), so the act_runner needs `container.docker_host: automount`; the first step fails with that cause if it is missing. That socket is root-equivalent, so it may only sit on a label PR jobs cannot use - recorded under the trust boundary in [Publishing images to the own registry](decisions/registry-publishing.md). Repo secrets: `REGISTRY_USERNAME`, `REGISTRY_PASSWORD`. +* **Creation**: [publish-image.yml](../.gitea/workflows/publish-image.yml) - a `vX.Y.Z` tag push builds `Dockerfile` on the arm64 runner and pushes `git.noelsabia.dev/cv_website/nuxt` as the version and `sha-<12>`, plus `latest` when that tag is the newest release. Main pushes deliberately do not build: the registry holds releases, not commits. The job uses the runner's own Docker daemon (client only in the `node:22-bookworm` container), so the act_runner needs `container.docker_host: automount`; the first step fails with that cause if it is missing. That socket is root-equivalent, so it may only sit on a label PR jobs cannot use - recorded under the trust boundary in [Publishing images to the own registry](decisions/registry-publishing.md). Repo secrets: `REGISTRY_USERNAME`, `REGISTRY_PASSWORD`. * **Review follow-up** (PR #19, 1 BLOCKER + 4 WARN + 2 NIT): applied the strict `vMAJOR.MINOR.PATCH` check, the newest-release rule for `latest`, a smoke test that starts the image and requires 2xx on `/`, and `timeout-minutes: 20`. Rejected with evidence: the `.dockerignore` leak (`.env*`, `*.pem`, `.git` are excluded) and the Docker-client/daemon API mismatch (20.10.24 client against a 29.9.2 daemon built successfully over the socket). * **Second review follow-up** (PR #19): the job now runs on the dedicated `publish` label instead of `ubuntu-latest`, so the host socket it needs can never be shared with PR jobs - the earlier version required a runner configuration its own trust boundary forbade. Added the immutability guard (registry v2 `manifests/`: `200` aborts, `404` continues) after measuring that `docker manifest inspect` fails on OCI indexes with the pinned 20.10 client; the smoke test now also requires a rendered body (10 kB floor) rather than a bare 2xx. `.github/actionlint.yaml` declares the custom label, and the hook passes it with `-config-file` because this repo keeps workflows in `.gitea/`.