Take my money Wil:))))
Please make a support for us folks that have comfy on other local machines, we could call those comfy with its Ips?
Super thank you @gasparm for open source base-line for us. would you mind adding a LICENSE file to the repo? It helps Git detect the license properly and ensures we’re fully compliant with the MIT terms when we use it. Since you mentioned mit on the readme. Thanks again, well done.
Two new path fields in Settings — “ComfyUI Input (remote)” and “ComfyUI Output (remote)”. These are the same NAS folders but as seen from the Remote machine. So you set:
Per-workflow path injection — when Flame submits a workflow, it injects the remote paths directly into the LoadFromFlame and SendToFlame nodes inside the workflow JSON. This means multiple Flame machines can point to the same ComfyUI without overwriting each other’s config.
~/.comfy_flame_paths.json — a config file on the Linux ComfyUI machine to set paths independently of Flame.
As soon as I have a moment, I’ll make a little video to show the differents configuration you can have. But I have too much work for now.
Hello !
Thank you @gasparm for sharing this promising work.
I tried It with a Flux Klein 9B Edit Workflow but I think we need the LoadFromFlame custom node to import image into Comfy ?
Maybe I’m wrong.
Do you have a workflow json to get this work ?
Hey, yes indeed, you need to put the Loadfromflame custom node and the Sendtoflame custom node in your workflow to make it work. They are on GitHub, just be sure to put them on the computer you are using for Comfy.
the ‘flame_integration’ folder should be copied to your comfyui/custom_nodes/ folder on your comfy machine. It’s on GitHub here (you’ll prob have to restart the comfy server afterwards)