Add a comfyui service to docker-compose.yml: ROCm-capable image, on the
ai-stack network (same pattern as llama-server), host port 8138 published
(for the future external nginx -> comfy.home route — nginx itself is outside
this stack, just the port mapping is needed here). Register it with
OmniRoute as a provider (same manual dashboard/API registration pattern used
for llama-server and searxng-search per docs/proxy-key-onboarding.md).
Verify a CLI request can reach ComfyUI's image-gen endpoint through
OmniRoute using an API key.
Part of #38
## Question
Add a comfyui service to docker-compose.yml: ROCm-capable image, on the
ai-stack network (same pattern as llama-server), host port 8138 published
(for the future external nginx -> comfy.home route — nginx itself is outside
this stack, just the port mapping is needed here). Register it with
OmniRoute as a provider (same manual dashboard/API registration pattern used
for llama-server and searxng-search per docs/proxy-key-onboarding.md).
Verify a CLI request can reach ComfyUI's image-gen endpoint through
OmniRoute using an API key.
Compose scaffolding done and pushed (ed83fca): comfyui service (yurisasc/comfyui-rocm7.1, gfx1201-tuned), ai-stack network, host port 8138 published, GID/UID auto-resolved in scripts/update.sh.
Remaining — needs to happen on the actual R9700 box, no shell access to it from this session:
git pull && ./scripts/update.sh on the server.
Register comfyui as an OmniRoute provider (base URL http://comfyui:8188) via the dashboard — same manual flow already used for llama-server, per docs/proxy-key-onboarding.md.
Mint/reuse an API key and confirm a CLI request reaches ComfyUI's image-gen endpoint through OmniRoute.
Leaving open until that's confirmed — ping when done and I'll close it out.
Compose scaffolding done and pushed (ed83fca): comfyui service (yurisasc/comfyui-rocm7.1, gfx1201-tuned), ai-stack network, host port 8138 published, GID/UID auto-resolved in scripts/update.sh.
Remaining — needs to happen on the actual R9700 box, no shell access to it from this session:
1. `git pull && ./scripts/update.sh` on the server.
2. Register comfyui as an OmniRoute provider (base URL `http://comfyui:8188`) via the dashboard — same manual flow already used for llama-server, per docs/proxy-key-onboarding.md.
3. Mint/reuse an API key and confirm a CLI request reaches ComfyUI's image-gen endpoint through OmniRoute.
Leaving open until that's confirmed — ping when done and I'll close it out.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #38
Question
Add a comfyui service to docker-compose.yml: ROCm-capable image, on the
ai-stack network (same pattern as llama-server), host port 8138 published
(for the future external nginx -> comfy.home route — nginx itself is outside
this stack, just the port mapping is needed here). Register it with
OmniRoute as a provider (same manual dashboard/API registration pattern used
for llama-server and searxng-search per docs/proxy-key-onboarding.md).
Verify a CLI request can reach ComfyUI's image-gen endpoint through
OmniRoute using an API key.
Compose scaffolding done and pushed (
ed83fca): comfyui service (yurisasc/comfyui-rocm7.1, gfx1201-tuned), ai-stack network, host port 8138 published, GID/UID auto-resolved in scripts/update.sh.Remaining — needs to happen on the actual R9700 box, no shell access to it from this session:
git pull && ./scripts/update.shon the server.http://comfyui:8188) via the dashboard — same manual flow already used for llama-server, per docs/proxy-key-onboarding.md.Leaving open until that's confirmed — ping when done and I'll close it out.