vnclagoon/vnctalk-hybridauth
14
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

chore: retag product images to vnclagoon/* (#2)
Build + push image / build-and-push (push) Successful in 4m48s
Details

Browse Source
This commit was merged in pull request #2.
This commit is contained in:
Bernd-Rodler
2026-08-20 09:19:20 +00:00
parent 97e6fb83b5
commit b01ba5397e
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/deploy.yml
+1 -1
View File
@@ -6,7 +6,7 @@ on:
env: env:
REGISTRY: gitea.saas.vnc.biz REGISTRY: gitea.saas.vnc.biz
IMAGE: gitea.saas.vnc.biz/vnciac/vnc-hybridauth-api IMAGE: gitea.saas.vnc.biz/vnclagoon/vnc-hybridauth-api
jobs: jobs:
build-and-push: build-and-push:
README.md
+2 -2
View File
@@ -13,8 +13,8 @@ endpoint (default port `9544`).
Built by Gitea Actions (`.gitea/workflows/deploy.yml`) on every push to `master`, using Built by Gitea Actions (`.gitea/workflows/deploy.yml`) on every push to `master`, using
kaniko (no Docker daemon on the runner). The image is pushed to the Gitea registry: kaniko (no Docker daemon on the runner). The image is pushed to the Gitea registry:
- `gitea.saas.vnc.biz/vnciac/vnc-hybridauth-api:latest` - `gitea.saas.vnc.biz/vnclagoon/vnc-hybridauth-api:latest`
- `gitea.saas.vnc.biz/vnciac/vnc-hybridauth-api:sha-<short-sha>` - `gitea.saas.vnc.biz/vnclagoon/vnc-hybridauth-api:sha-<short-sha>`
Registry auth uses the `REGISTRY_USER` / `REGISTRY_TOKEN` Actions secrets. The image runs Registry auth uses the `REGISTRY_USER` / `REGISTRY_TOKEN` Actions secrets. The image runs
as the non-root `vncuser` (uid 1001) and starts `node /usr/share/vnctalk-hybrid-authenticator2/app/app.js`. as the non-root `vncuser` (uid 1001) and starts `node /usr/share/vnctalk-hybrid-authenticator2/app/app.js`.