Use authenticated registry secrets for image publishing
Test, build, and deploy ComfyUI Jobs / test-build (push) Successful in 11m7s
Test, build, and deploy ComfyUI Jobs / deploy (push) Successful in 3m22s

This commit is contained in:
2026-10-02 21:58:54 +00:00
parent b00985aac2
commit d81089edf2
2 changed files with 4 additions and 4 deletions
+3 -3
View File
@@ -41,8 +41,8 @@ jobs:
env:
DEPLOY_HOST: ${{ secrets.DEPLOY_HOST }}
DEPLOY_USER: ${{ secrets.DEPLOY_USER }}
REGISTRY_USERNAME: ${{ gitea.actor }}
REGISTRY_PASSWORD: ${{ secrets.GITEA_TOKEN }}
REGISTRY_USERNAME: ${{ secrets.REGISTRY_USERNAME }}
REGISTRY_PASSWORD: ${{ secrets.REGISTRY_PASSWORD }}
GITEA_REF: ${{ gitea.ref }}
GITEA_SHA: ${{ gitea.sha }}
run: |
@@ -59,7 +59,7 @@ jobs:
IMAGE_REF=git.dumas.ddns.net/chris.dumas/comfyui-portal-next:sha-${GITEA_SHA}
if [ -z "$REGISTRY_USERNAME" ] || [ -z "$REGISTRY_PASSWORD" ]; then
echo 'Gitea Actions token is unavailable for registry authentication'
echo 'REGISTRY_USERNAME and REGISTRY_PASSWORD are required for registry authentication'
exit 1
fi
+1 -1
View File
@@ -15,4 +15,4 @@ The first run seeds `data/users.json` from `ADMIN_USERNAME` and `ADMIN_PASSWORD`
Gitea Actions deploys `develop`, `qa`, and `main` to the existing ComfyUiPortal target directories and preserves the existing 7002/6002/5002 port contract. On first startup of a fresh data directory, provide `ADMIN_USERNAME` and `ADMIN_PASSWORD` in the deployment host environment. Existing target data is retained during repository cutover.
The deployment workflow builds an immutable image tagged with the source commit SHA and publishes it to the Gitea container registry. If that SHA-tagged image already exists, the workflow reuses it instead of rebuilding. The workflow uses Gitea's built-in `GITEA_TOKEN` with package-write permission. Compose receives the exact image reference through `IMAGE_REF`, so the same artifact can be redeployed or promoted without rebuilding.
The deployment workflow builds an immutable image tagged with the source commit SHA and publishes it to the Gitea container registry. If that SHA-tagged image already exists, the workflow reuses it instead of rebuilding. Configure the masked `REGISTRY_USERNAME` and `REGISTRY_PASSWORD` repository Actions secrets with a Gitea account/token that can write container packages. Compose receives the exact image reference through `IMAGE_REF`, so the same artifact can be redeployed or promoted without rebuilding.