[Feature] Allow choosing easily between new ui and stable-ui

[Gerporgl]

Feature Summary

I would like to have the old UI, and keep it supported as well... at least for now (please)

Detailed Description

Right now with the latest version of stable-diffusion, I need to patch the submodule to put back https://github.com/leejet/stable-ui.git

My issue is that the new UI does not seem ready, there is no dark style (I could have missed it), and more importantly, it does not seems to work like before with llama-swap, it show 404s and that the server is not up... but it is.
Perhaps it has issues with being proxied. Also, it is unclear if it has the same features as stable-ui, such as storing images in the local browser storage (and can they share both the same database and format? or at least import and export?)

Alternatives you considered

No response

Additional context

No response

[wbruna]

In the meantime, you can use Koboldcpp: it includes the stable-ui, which supports pointing to another image generation server.

Launch the sd-server in another port; then, launch Koboldcpp with --nomodel. On the browser, go to the Options tab, and change the base URL to point to the sd-server URL (without the sdapi part).

[Gerporgl]

In the meantime, you can use Koboldcpp: it includes the stable-ui, which supports pointing to another image generation server.

Launch the sd-server in another port; then, launch Koboldcpp with --nomodel. On the browser, go to the Options tab, and change the base URL to point to the sd-server URL (without the sdapi part).

I also discovered Koboldcpp project yesterday, after looking at the original forks of stable-ui. It seemed more like a front-end GUI when I tried it quickly, but thanks for mentioning this, I might add this to my llama-swap image as another tool.

[Green-Sky]

https://github.com/leejet/stable-diffusion.cpp/tree/master/examples/server#using-an-external-frontend

You can serve any frontend you like with the existing binary.

[Gerporgl]

Thanks for pointing that out!
I didn't know, but I thought this should be possible... I should have searched properly.

Using the default project binaries provided would greatly help me with my lxc container build, since compiling for all rocm GPUs takes long time on github actions, or even locally on a 16 core or more CPU.
I would just have to bundle the front-end that works for me.

[wbruna]

Since #1415 was merged, one alternative is building the embedded header in an old sd.cpp version, and copy it to the new one.

I also discovered Koboldcpp project yesterday, after looking at the original forks of stable-ui. It seemed more like a front-end GUI when I tried it quickly, but thanks for mentioning this, I might add this to my llama-swap image as another tool.

Koboldcpp actually bundles both front-ends and engines for AI generation (including an internal copy of sd.cpp); but the frontends can be configured to point to different API servers.