Open camoody1 opened 2 weeks ago
I think the reason why we did not implement the random folder access is that for cloud hosted servers, we probably don't want all users to gain access to the full server file system access. But this feature is definitely valid. We just need to add an extra cmd flag to distinguish execution environment (Self-hosted vs Remote-hosted), and give the self-hosted server script the full access to the file system.
I think the reason why we did not implement the random folder access is that for cloud hosted servers, we probably don't want all users to gain access to the full server file system access. But this feature is definitely valid. We just need to add an extra cmd flag to distinguish execution environment (Self-hosted vs Remote-hosted), and give the self-hosted server script the full access to the file system.
Sir, you are 100x more knowledgeable than me regarding the minutia of how to accomplish this, so I trust you'll be able to find a way to make it possible. Thank you for the consideration and all the hard work you and your coworkers are putting into this.
If I understood correctly, @camoody1 just wants to point comfyui to use his workflow folder instead. We could use a cmd flag to set the target workflow folder, and keep file access restricted.
If I understood correctly, @camoody1 just wants to point comfyui to use his workflow folder instead. We could use a cmd flag to set the target workflow folder, and keep file access restricted.
Correct. This is all I am wanting to do.
Is there an existing issue for this?
What would your feature do ?
Allow a different folder location for our Workflows list. I keep my workflows in a separate folder structure outside of Comfy. But the new UI seems to only look in that one location under \ComfyUI\user\default\workflows. I would like to have a setting to make Comfy look in an alternative folder location.
Proposed workflow
Additional information
No response