remco/EpicNext-Cms
1
1 Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

fix(ci): publish container under token account namespace
CI / check (push) Successful in 56s
Details
CI / deploy (push) Successful in 1m9s
Details
CI / publish-container (push) Failing after 30s
Details

Browse Source
This commit is contained in:
Simo committed 2026-09-09 19:53:16 +02:00
1 parent c389c3893d
commit 867113d5d4
5 files changed
+35 -6
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

README.md
+13 -3
View File
@@ -219,9 +219,19 @@ After changing `.env`, recreate the container; an image rebuild is not required.
To publish from Gitea:
Gitea packages belong to an account or organization, independently of repository
permissions. Publication defaults to the lowercase `CONTAINER_REGISTRY_USER`
namespace, so a Simo token publishes `simo/epicnext-cms` even though the Git
repository belongs to remco. Set the Actions variable
`CONTAINER_REGISTRY_NAMESPACE` only to override this (for example, an organization
where the token account has package write access). Keep the login username and
token from the same account. Changing namespace also changes the image URL used
by installations; existing remco image tags are not moved automatically.
1. In the repository's Actions secrets, configure `CONTAINER_REGISTRY_USER` and
`CONTAINER_REGISTRY_TOKEN`. Use a Gitea access token with package read/write
permission belonging to an account allowed to publish under the repository owner.
permission belonging to the login account. For the Simo token, set
`CONTAINER_REGISTRY_USER=Simo`; the default package namespace will be `simo`.
2. Every push to `main` or `master` automatically builds and publishes the images
after the CI checks and production deployment succeed. Pull requests do not
publish images. The publication job builds from committed source only and checks
@@ -235,12 +245,12 @@ To publish from Gitea:
migrations image is used temporarily for the matching database migrations.
For this repository the image base is
`gitlab.epicnabbo.nl/remco/epicnext-cms`. Package access is controlled by Gitea.
`gitlab.epicnabbo.nl/simo/epicnext-cms`. Package access is controlled by Gitea.
For private packages, run `docker login gitlab.epicnabbo.nl` on the installation
with a token that can read packages. Then update with:
```bash
CMS_IMAGE_REPOSITORY=gitlab.epicnabbo.nl/remco/epicnext-cms \
CMS_IMAGE_REPOSITORY=gitlab.epicnabbo.nl/simo/epicnext-cms \
CMS_PUBLIC_URL=https://your-hotel.example \
bash scripts/docker-update.sh
```