-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: Persistent Storage / Modify the Installation Path #706
Comments
I have now changed the Windows system variables (for the environment), the lower part, added three entries HF_HOME, HUGGINGFACE_HUB_CACHE, TRANSFORMERS_CACHE with the value leading to my shared diffusers folder (D:\models\diffusers). That's a workaround to use my D: drive offline. |
You can disable huggingface connections by setting the |
--ad-no-huggingface = I did that, but you can't use it offline because Automatic1111 doesn't start then, you can delete the command of course but it doesn't change the problem: the files should be stored persistent within a webui runtime. HF_HUB_OFFLINE = I'm not doing it because that would prevent other single downloads from HF. I put it instead in the environment variable to link it to my other harddrive, the one I use offline. |
Originally posted by @Bing-su in #650 (comment)
For Automatic/Stable Diffusion WEBUI
[Feature Request]: Persistent Storage / Modify the Installation Path
Symlinked files in the CACHE can't be moved or copied (not on Windows, don't know about other OS). Users cannot influence the chosen Huggingsface path which is harddrive C: (except they edit a script?).
Most of the yolov-models are already in my ULTRALYTICS or GFPGAN folders. The extension scans the folders as set in the settings for Adetailer ("Extra paths to scan adetailer models separated by vertical bars") but it's only for use inside the Adetailer in WEBUI, yes it works, they can be used. But it should scan while launching WEBUI to avoid downloading again into the .CACHE folder on C: because WEBUI is supposed to work offline too. Other extensions accept that and download to where the WEBUI is located, to make it easier for portable use.
My wish?
An option for COMMANDLINE_ARGS, for example (using the ad_extra_models_dir name as called in config.json) to use it like that:
--ad-extra-models-dir "D:\stable-diffusion-webui\models\adetailer" --ad-extra-models-dir "D:\stable-diffusion-webui\models\ultralytics"
Or maybe direct everything coming from Yolov into a Yolov folder in the WEBUI?
In Stable Diffusion FORGE however I use the same settings for Adetailer (Extra paths) and it's recognizing them obviously on launch, if I delete the cache folder it doesn't reload the yolov files and Adetailer works correct.
But why? The main difference in my settings between those two WEBUIs is that in FORGE I can use a COMMANDLINE_ARGS called --text-encoder-dir (I use it to direct to the 'diffusers' folder, where FORGE stores Bingsu and some other content), that would be also an alternative to the current setup with HF's cache. If Automatic1111/SD-WEBUI could add --text-encoder-dir to the COMMANDLINE_ARGS options at start.
The text was updated successfully, but these errors were encountered: