William Gill
09fcec7c07
CI builds and pushes the comfyui-nvidia image to the Gitea container registry on every v* tag, mirroring the figment release workflow. Compose now references the registry image (with build context kept for local iteration) and the docs reflect the pull-by-default flow. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
comfyui-nvidia
ComfyUI image-generation backend, NVIDIA-accelerated, fronted by Open WebUI for multi-user chat and image generation/editing.
Built from the official ComfyUI manual install for NVIDIA — no third- party base image. Two services on one bridge network:
| Service | Port (host) | Role |
|---|---|---|
comfyui |
8188 |
ComfyUI server + native web UI |
open-webui |
3000 |
Multi-user chat with txt2img / img2img panel |
Open WebUI submits ComfyUI workflows directly via the documented integration —
no MCP shim, no API translation layer. Workflow templates live in
workflows/ and get pasted into Open WebUI's admin panel during
setup.
Quick start
cp .env.example .env
# edit .env — set OPEN_WEBUI_SECRET_KEY at minimum
docker compose up -d
compose up pulls the prebuilt ComfyUI image from
git.anomalous.dev/alphacentri/comfyui-nvidia (CI publishes it on every
v* tag — see .gitea/workflows/release.yml).
Use docker compose build to rebuild locally when iterating on the Dockerfile.
Then drop a checkpoint into the comfyui-models volume and finish the Open
WebUI ComfyUI configuration. Full walkthrough in SETUP.md.
Replaces
This repo supersedes the previous figment + segment + Forge stack. ComfyUI's node graph covers everything those services provided (txt2img, img2img, inpaint, mask generation via SAM/GroundingDINO custom nodes), and Open WebUI talks to it natively.