ComfyUI
ComfyUI copied to clipboard
comfyanonymous
Is it possible to have checkpoints, embeddings, models, vae, etc. on an external drive?
I keep all of the above files on an external drive due to the large space requirements. Is there an option to select a custom directory where all my models are located, or even directly select a checkpoint/embedding/vae by absolute filesystem path?
While it may not be ideal for some, what I do is keep my large files on a NAS and I soft link them to the local checkpoint folder. Works like a charm.
ComfyUI does not and will never use gradio. The code that searches for the checkpoints/etc.. should follow symlinks without any issue.
The plan is to have an option to add search paths but that isn't implemented yet.
So, since it supports symlinks, please put this into readme.md Document.
Custom Model Folder
Symlinks is supported. For windows, symlinks can be used as mklink command in cmd window. Search "Windows mklink" in google for tutorial.
So, since it supports symlinks, please put this into readme.md Document.
Custom Model Folder
Symlinks is supported. For windows, symlinks can be used as mklink command in cmd window. Search "Windows mklink" in google for tutorial.
symlinks are an OS feature supported by every program, they have nothing to do with this one.
So, since it supports symlinks, please put this into readme.md Document.
Custom Model Folder
Symlinks is supported. For windows, symlinks can be used as mklink command in cmd window. Search "Windows mklink" in google for tutorial.
symlinks are an OS feature supported by every program, they have nothing to do with this one.
Given that there are multiple issues regarding this subject, I don't think it'll hurt to add this information into the README. If we left only pertinent information in README files that were not available anywhere else, that would defeat the purpose of a README.
So, since it supports symlinks, please put this into readme.md Document.
Custom Model Folder
Symlinks is supported. For windows, symlinks can be used as mklink command in cmd window. Search "Windows mklink" in google for tutorial.
symlinks are an OS feature supported by every program, they have nothing to do with this one.
Given that there are multiple issues regarding this subject, I don't think it'll hurt to add this information into the README. If we left only pertinent information in README files that were not available anywhere else, that would defeat the purpose of a README.
yeah as a workflow thing it makes allot of sense
This was fixed with: https://github.com/comfyanonymous/ComfyUI/blob/master/extra_model_paths.yaml.example
