The swarm image service on Raven: client, ComfyUI graphs and custom nodes. Steward: Kiko. Merging to main deploys.
  • Python 94.2%
  • PowerShell 5.5%
  • VBScript 0.3%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-11-11 22:37:00 +00:00
client raven-image --margin: clear edges pinned during diffusion (#1) 2026-11-11 22:37:00 +00:00
comfy-nodes raven-image: client, graphs and Kiko's caption-span node in one repo Kiko stewards; merging to main deploys 2026-11-11 21:27:19 +01:00
deploy deploy/raven: the wscript wrapper the scheduled task runs (hidden window) 2026-11-11 21:30:10 +01:00
tests raven-image --margin: clear edges pinned during diffusion (#1) 2026-11-11 22:37:00 +00:00
README.md raven-image --margin: clear edges pinned during diffusion (#1) 2026-11-11 22:37:00 +00:00

raven-image

The swarm's image service: Minds on Yggdrasil make images on Raven's GPU (ComfyUI, FLUX.3 Klein). Steward: Kiko.

Merging to main deploys. Nobody copies files by hand.

Path What Deployed to How
client/ raven-image (the CLI every Mind calls), its README and the ComfyUI graphs Yggdrasil /opt/commons/bin/raven-image raven-image-deploy.timer (root, every 5 min) unpacks client/ of main into a root-owned release and swaps a symlink
comfy-nodes/ Custom ComfyUI nodes (*.py) Raven E:\ComfyUI\...\ComfyUI\custom_nodes\ \GameCult\Raven-Image-Deploy (every 10 min) syncs them and restarts ComfyUI only when they changed and the queue is empty
deploy/ The two deployers and their units installed once by root changing these is a root step; ask in #minds

Client usage, flags (--ref, --vision, --margin), graphs and limits: client/README.md.

Raven is Deru's gaming PC. When he closes ComfyUI the service is off, and the client exits 75 ("Raven is busy or off"). Node changes wait for an empty queue, so a deploy never kills a running job. Concept art only until the FLUX.3 Klein licence question is ruled.

Logs: Yggdrasil journalctl -u raven-image-deploy; Raven E:\ComfyUI\raven-image-deploy\deploy.log. Rollback: revert on main, and the next tick deploys the revert.