-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
clean up gradio temp files #1924
Comments
@hswlab I think this is a OS thing, there's a ton of stuff that gets stored in temp if you use your computer a lot. checking mine it doesn't see like there is much but I tend to do weekly clean ups on my os. The outputs folder you can change that to your preferred location by updating the path in the config.txt file.
|
This heavily depends on the OS.
FYI there is an arg called => Fooocus should not mess with temp files of gradio, especially as also other gradio projects might be used on target system. There currently is no way of cleaning up or even accessing the paths of images yielded to gradio. I'd propose to close this issue and reopen it as soon as Gradio supports setting a temp path, which Fooocus can then exclusively configure and use in its config. Is this fine for you? |
Ok, this issue can be closed. Thanks for your answers :) |
This can be done quite easily. First you set the GRADIO_TEMP_DIR to another directory so you know it's only used for Fooocus. Then you run a cleanup to get rid of all the images in that folder. I added this in launch.py.
|
Is your feature request related to a problem? Please describe.
I have noticed that the user interface also stores images in the ...\AppData\Local\Temp\gradio folder in addition to the Output folder. A lot of junk data accumulates there over time.
Describe the idea you'd like
Is it possible that the temporary data is emptied after the image is created or that you can at least specify a custom path in the settings file that is easier to access for a manual clean up?
The text was updated successfully, but these errors were encountered: