You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues and checked the recent builds/commits
What would your feature do?
If the path configured in config.txt does not exist, automatically create the corresponding folder instead of using the default path, e.g., ../models/embeddings/.
Otherwise,
It may give the illusion that the configuration in config.txt is ineffective.
When starting based on Docker and if mounting is required, all folders need to be pre-created on the host machine.
Proposed workflow
By default, automatic creation can be enabled.
Alternatively, use an environment variable to control whether automatic creation is enabled or not.
Additional information
No response
The text was updated successfully, but these errors were encountered:
I ran into the issue where it seemed like I had to manually create the folders with Docker. Using instead of a bind mount a volume, as is suggested by the documentation, the issue disappeared and the folders were automatically created.
If you only created the models folder on the host and mounted it (e.g. -v ${PATH}/models:/app/data/models), then only the checkpoints and loras folders will exist within the models folder. Other folders under /app/data/models (such as embeddings) will not be present in ${PATH}/models.
Is there an existing issue for this?
What would your feature do?
If the path configured in config.txt does not exist, automatically create the corresponding folder instead of using the default path, e.g., ../models/embeddings/.
Otherwise,
Proposed workflow
By default, automatic creation can be enabled.
Alternatively, use an environment variable to control whether automatic creation is enabled or not.
Additional information
No response
The text was updated successfully, but these errors were encountered: