Is there an existing issue for this?
What would your feature do ?
I am currently running 2 instances of the WebUI locally, and that (for performance reasons) both use different hardware for different tasks. I interact with those via a backend communicating with the API. When I create an embedding on one instance it needs a manual refresh (e.g. refreshing the browser window, using the button in the UI etc) before the other instance can use it.
As far as I know its currently possible to do something like refreshing via the API only for Checkpoints and VAE's, not for embeddings.
An API endpoint for refreshing the embeddings would be a big problem solver for not only my use-case but lots of others in terms of automation.
Proposed workflow
In my case:
- Perform an operation on an embedding that needs a refresh to be accessed somewhere else (e.g. another instance)
- Make a request to the corresponding URL for refreshing embeddings as shown in the API docs
- Use the newly available embedding any way you want in your preferred location
Additional information
No response
Is there an existing issue for this?
What would your feature do ?
I am currently running 2 instances of the WebUI locally, and that (for performance reasons) both use different hardware for different tasks. I interact with those via a backend communicating with the API. When I create an embedding on one instance it needs a manual refresh (e.g. refreshing the browser window, using the button in the UI etc) before the other instance can use it.
As far as I know its currently possible to do something like refreshing via the API only for Checkpoints and VAE's, not for embeddings.
An API endpoint for refreshing the embeddings would be a big problem solver for not only my use-case but lots of others in terms of automation.
Proposed workflow
In my case:
Additional information
No response