Use registry token secret for image publishing
Build and publish Docker image / build-and-publish (push) Successful in 11s

This commit is contained in:
wfalkowski committed 2026-10-20 15:51:48 +00:00
1 parent 59d2a5aab3
commit d8862c9611
2 files changed
+2 -2

No files matched your search

+1 -1
View File
@@ -17,6 +17,6 @@ Edit the root `branding.json` to set the product name, domain, logo path, public
## Gitea Actions Docker publishing
`.gitea/workflows/docker.yml` builds the Docker image when `main` is updated and can also be started manually from the Actions page. It publishes `git.anchorhost.eu/anchorhost.eu/anchorhost-frontend:frontend` and a commit-specific `main-<12 character SHA>` tag to the Gitea Container Registry. The workflow logs in with Gitea's per-job `GITEA_TOKEN`, granted `contents: read` and `packages: write`; no registry password secret is needed.
`.gitea/workflows/docker.yml` builds the Docker image when `main` is updated and can also be started manually from the Actions page. It publishes `git.anchorhost.eu/anchorhost.eu/anchorhost-frontend:frontend` and a commit-specific `main-<12 character SHA>` tag to the Gitea Container Registry. Add a repository Actions secret named `REGISTRY_TOKEN` containing a Gitea personal access token with package read/write permission. The workflow uses the triggering Gitea username to authenticate.
Enable Actions for the repository and ensure a runner with the Docker CLI and a working Docker daemon is registered. `.dockerignore` keeps local dependencies, Git history, build output, and recovered production artifacts out of the build context.