Make ai-stack the only deployment shape

Drops the duplicate standalone compose / .env.example / SETUP.md at the
repo root. Bring-up content folded into deployments/ai-stack/README.md
so there's exactly one set of deployment instructions, sitting next to
the files it describes. Root README is now just the repo overview and a
pointer at the deployment.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
57_WolveandClaude Opus 4.7 committed 2026-04-19 10:45:23 -05:00
1 parent b1c9bff15f
commit 97547c783c
5 files changed
+173 -333

No files matched your search

+22 -39
View File
@@ -1,50 +1,33 @@
# comfyui-nvidia
ComfyUI image-generation backend, NVIDIA-accelerated, fronted by Open WebUI for
multi-user chat and image generation/editing.
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](https://docs.comfy.org/installation/manual_install#nvidia) — no third-
party base image. Two services on one bridge network:
NVIDIA](https://docs.comfy.org/installation/manual_install#nvidia) — no
third-party base image. CI publishes the image to
`git.anomalous.dev/alphacentri/comfyui-nvidia` on every `v*` tag (see
[.gitea/workflows/release.yml](.gitea/workflows/release.yml)).
| Service | Port (host) | Role |
| ----------- | ----------- | ----------------------------------------------- |
| `comfyui` | `8188` | ComfyUI server + native web UI |
| `open-webui`| `3000` | Multi-user chat with txt2img / img2img panel |
## Repository layout
Open WebUI submits ComfyUI workflows directly via the documented integration —
no MCP shim, no API translation layer. Workflow templates live in
[`workflows/`](workflows/) and get pasted into Open WebUI's admin panel during
setup.
| Path | What |
| -------------------------- | ----------------------------------------------------- |
| `Dockerfile` | ComfyUI on NVIDIA, manual-install pattern |
| `workflows/` | txt2img + img2img workflow JSONs and node mappings |
| `deployments/ai-stack/` | The deployment — compose, Caddyfile, env, model preseed |
| `.gitea/workflows/` | Release pipeline (build & push image on tag) |
## Quick start
## Deploy
```sh
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](.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](SETUP.md).
## Deployment examples
- **Repo root** (`docker-compose.yml`) — minimal `comfyui` + `open-webui`
bridge for kicking the tyres on a single-purpose box.
- **[`deployments/ai-stack/`](deployments/ai-stack/)** — production-shaped
multi-service stack: Caddy (TLS + reverse proxy), Ollama (with one-shot
model preseeding), ComfyUI, Open WebUI, optional Anubis anti-bot. Mirrors
the live `srvno.de` deployment.
The full stack — Caddy + Ollama + ComfyUI + Open WebUI (+ optional
Anubis) — lives under [`deployments/ai-stack/`](deployments/ai-stack/).
Bring-up steps, host prerequisites, Open WebUI workflow wiring, and
gotchas are in [`deployments/ai-stack/README.md`](deployments/ai-stack/README.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.
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.