Files
ComfyUiPortalNext/README.md
T
chris.dumas b00985aac2
Test, build, and deploy ComfyUI Jobs / test-build (push) Successful in 11m21s
Test, build, and deploy ComfyUI Jobs / deploy (push) Failing after 8s
Use built-in Gitea token for registry deploys
2026-10-02 21:40:38 +00:00

19 lines
1.2 KiB
Markdown

# ComfyUI Jobs
The next ComfyUI portal is intentionally limited to authenticated, read-only remote job monitoring. It does not expose prompt submission, workflow authoring, imports, or admin mutation routes.
## Local development
```sh
npm ci
ADMIN_USERNAME=admin ADMIN_PASSWORD='set-locally' npm run dev
```
The first run seeds `data/users.json` from `ADMIN_USERNAME` and `ADMIN_PASSWORD`; subsequent runs use the persisted hashed record. Do not commit `data/` or credentials.
## Deployment
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.