The instructions provided to make comfy desktop available on local network brick the install on Windows 11 Pro - no available network ports between x and y. I would suggest:
Provide users with a process to restore the installation (i.e. delete the comfy.settings.json file)
Re-test what is being written to the config file when user elects to enable local network access.
After deleting the file and restarting I was able to see what the vanilla config should look like. There was a a section for launchargs and I added listen: 0.0.0.0 and that worked.
note: what the config file originally had in it was nothing like this.
Ah, I see. It is an excellent resource, that site, but not something we control.
The short version is that ComfyUI can be used as a server. Using the desktop app as a server only works because ComfyUI Desktop is built on top of ComfyUI.
It is not something we’re recommending at the moment. The desktop app is just that - a desktop app. Its server process is killed when the app window is closed.
We’ve no plans to actively block this unintentional feature, but it’s simply not what the app is for. If it gets in the way of adding an actual desktop feature, it is unlikely to survive the encounter.
But by the same logic, if there’s actual demand for this as a feature, we’ll just do it.
Ok that makes sense. In my case I ended up pivoting away from the desktop install for my use case; running Krita on mac while running comfy on PC. I ended up having to let Krita install the comfy it wants. All of this to say your thoughts above on the direction of comfy desktop hold true.
That said, it was easy to enough to add the listen param to the config file. I’ll leave to the wiki owners to provide those instructions.