fluxerapp/fluxer
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

fix: use registry_token secret for Gitea authentication
Some checks failed
release server / resolve build metadata (push) Successful in 12s
Details
release server / build fluxer server (push) Failing after 3m40s
Details
release server / create release (push) Has been skipped
Details
release server / release summary (push) Failing after 5s
Details
test cassandra-backup / Test latest Cassandra backup (push) Has been cancelled
Details

Browse Source 
Gitea doesn't allow secrets with GITEA_ or GITHUB_ prefixes.
Using registry_token secret instead.
This commit is contained in:
Kitty Cat
2026-03-01 10:51:58 -05:00
parent 3577f5fb95
commit d977b35636
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.github/workflows/release-server.yaml vendored
View File

@@ -123,7 +123,7 @@ jobs:
with: with:
registry: ${{ env.REGISTRY }} registry: ${{ env.REGISTRY }}
username: ${{ github.actor }} username: ${{ github.actor }}
password: ${{ secrets.GITEA_TOKEN || github.token }} password: ${{ secrets.registry_token }}
- name: docker metadata - name: docker metadata
id: docker_meta id: docker_meta

8
NOTES.md
View File

@@ -58,11 +58,11 @@ The old `main`/`canary` branches have the legacy stack that's harder to self-hos
The workflow tries to use `secrets.GITEA_TOKEN` or `github.token` for registry auth. The workflow tries to use `secrets.GITEA_TOKEN` or `github.token` for registry auth.
**If automatic token fails**, create a Gitea Personal Access Token: **Required**: Create a Gitea Personal Access Token:
1. Go to Gitea Settings → Applications → Generate New Token 1. Go to Gitea Settings → Applications → Generate New Token
2. Name: `CI_REGISTRY_TOKEN` 2. Name: `CI_Container_Registry`
3. Permissions: Select `package:write` 3. Permissions: Select `package` (write access)
4. Add to repository secrets as `GITEA_TOKEN` 4. Add to repository secrets as `registry_token` (Note: Can't use GITEA_ or GITHUB_ prefix)
**Alternative**: Update the workflow to use username/password: **Alternative**: Update the workflow to use username/password:
- Create a secret `REGISTRY_USERNAME` with your Gitea username - Create a secret `REGISTRY_USERNAME` with your Gitea username