Consider forking the web UI to make an API server out of it

[philpax]

The A1111 web UI has a lot of features I don't care about (namely the web UI), and the API is not the best, especially for multi-tenant scenarios. The user experience might be improved if I forked it, excised all of the web UI stuff, and built a solid API on top of it, hopefully in such a way that keeping the fork inline with upstream is doable.

Features I'd want:

• Model switching in queue: [Feature Request]: API method to queue a options change AUTOMATIC1111/stable-diffusion-webui#5847
• Generation jobs getting their own ID that specific progress can be queried for: [Feature Request]: API Queuing (maybe v2 API?) AUTOMATIC1111/stable-diffusion-webui#3786
• Consistent API design
• No leaky abstractions
• Expose all configuration (including embeddings) through the API
• Remove any features designed for users (artists, prompt styles)
• Queue manipulation functions, including viewing and deleting jobs

[dsully]

Don't forget - rewritten in Rust, perhaps using PyO3 to interface with torch and diffusers. :)

[philpax]

I'd much rather use https://github.com/LaurentMazare/diffusers-rs in that case ;)

[dsully]

Fair enough!

[dcvz]

Have you done anything towards the queue jobs via API @philpax ?

[philpax]

No, I'm afraid not. I figured I'd wait and see if someone else built a decent API server.