Use registry token for image publishing
Some checks failed
Build / test (push) Successful in 11s
Build / container (push) Failing after 23s

This commit is contained in:
MrSphay
2026-05-14 17:48:16 +02:00
parent f3608568a0
commit ae098261ef
3 changed files with 18 additions and 2 deletions

View File

@@ -32,6 +32,8 @@ Container image from `Dockerfile` published by Gitea Actions:
git.wilkensxl.de/mrsphay/dockge-image-update-checker:latest
```
Publishing requires a repository Actions secret named `REGISTRY_TOKEN` with package write access for `MrSphay`.
## Notes
Dockge does not currently expose a stable documented plugin API. This repository is structured as a read-only companion service that can run beside Dockge and inspect the same stack directory plus Docker Engine metadata.

View File

@@ -43,8 +43,8 @@ jobs:
uses: docker/login-action@v3
with:
registry: git.wilkensxl.de
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
username: MrSphay
password: ${{ secrets.REGISTRY_TOKEN }}
- name: Build and push image
uses: docker/build-push-action@v6

View File

@@ -64,6 +64,20 @@ services:
If your Dockge stacks directory is not `/opt/stacks`, change both the host-side volume path and `STACKS_DIR`.
The Gitea workflow publishes this image to the registry:
```text
git.wilkensxl.de/mrsphay/dockge-image-update-checker:latest
```
Repository secret required for publishing:
```text
REGISTRY_TOKEN
```
`REGISTRY_TOKEN` must be a Gitea access token for `MrSphay` with package write access.
For local development you can still build from source:
```yaml