chore: retag product images to vnclagoon/* (#2)
Build + push image / build-and-push (push) Successful in 4m48s
Build + push image / build-and-push (push) Successful in 4m48s
This commit was merged in pull request #2.
This commit is contained in:
@@ -6,7 +6,7 @@ on:
|
||||
|
||||
env:
|
||||
REGISTRY: gitea.saas.vnc.biz
|
||||
IMAGE: gitea.saas.vnc.biz/vnciac/vnc-hybridauth-api
|
||||
IMAGE: gitea.saas.vnc.biz/vnclagoon/vnc-hybridauth-api
|
||||
|
||||
jobs:
|
||||
build-and-push:
|
||||
|
||||
@@ -13,8 +13,8 @@ endpoint (default port `9544`).
|
||||
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:
|
||||
|
||||
- `gitea.saas.vnc.biz/vnciac/vnc-hybridauth-api:latest`
|
||||
- `gitea.saas.vnc.biz/vnciac/vnc-hybridauth-api:sha-<short-sha>`
|
||||
- `gitea.saas.vnc.biz/vnclagoon/vnc-hybridauth-api:latest`
|
||||
- `gitea.saas.vnc.biz/vnclagoon/vnc-hybridauth-api:sha-<short-sha>`
|
||||
|
||||
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`.
|
||||
|
||||
Reference in New Issue
Block a user