Different UI / Settings for shared (online) usage and personal usage

[ResleyZ]

Hello,

I've been running this for quite a while now, and as someone without any Python experience, I'm absolutely in love with all of this stuff.

I've been trying to add some stuff myself, change settings outside of the standard ones, but one thing that I would like to implement myself, or see implemented, is more "easy" options for changing the UI, or an easier availabability to do so.

I've tried to change some of these myselfs, for example hiding/removing the History tab from the ui.py, but I ended up with multiple errors because it would require changing the code from other .py files as well, which ended up in a huge rabbit hole.

Right now I have three .bat files;

• webui.bat - exact same as the repo one
• webui-user.bat - certain arguments added like '--xformers --allow code --no-half-vae'
• webui-online.bat, same as user.bat, except with '--share arguments' and '--hide-ui-dir-config' arguments added.

I would like to change the show/hide these settings based on which .bat I start.

• Settings Tab visible / hidden - combined with the '--ui-settings-file' argument?
• History (I can sorta change this by having 2 different output directories, but I haven't found out how to change this based on which .bat I start with)
• Checkpoint/model selector - Can also change this with --ckpt-dir "model location folder"' argument, but that would require duplicate models, which isn't the end of the world.
• Checkpoint Merger
• Train

I've tried looking into the files and changing it myself, but after multiple errors, and multiple copies of the .py files, I kinda gave up, so hopefully someone with more python / gradio knowledge could have a look at this, or point me in the right direction where I don't mess up a lot of files.

[fortypercnt]

Why not just use two installs, one for sharing, one for personal? That seems way simpler than trying to mess with the UI / cramming two configs into one install.

[ResleyZ]

While that would mean they can't change my settings, they could still change them in the online batch.
It would still allow others using it to use the Checkpoint Merger and Train tabs, something that I want to disable so they won't overload my PC.

You could tell someone "don't use that", some people don't really care about that, and you can't exactly see who made it.
I already had one person try to generate 10 batches of 8 images at 1024x1024 resolution with 100 steps, with the excuse that "he's just a simple user, so he's testing it out".

[fortypercnt]

Oh, I see your use case is a bit different than what I thought of. A simple way to hide tabs would be to comment them out in ui.py line 1546-1555. Like so

    interfaces = [
        (txt2img_interface, "txt2img", "txt2img"),
        (img2img_interface, "img2img", "img2img"),
        (extras_interface, "Extras", "extras"),
        (pnginfo_interface, "PNG Info", "pnginfo"),
        #(images_history, "History", "images_history"),
        #(modelmerger_interface, "Checkpoint Merger", "modelmerger"),
        #(train_interface, "Train", "ti"),
        #(settings_interface, "Settings", "settings"),
    ]

You can add command line options in modules/shared.py. E.g.

parser.add_argument("--reduced-ui", action='store_true', help="hide some tabs from webui", default=False)

And then use them like this

    if cmd_opts.reduced_ui:
        interfaces = [
            (txt2img_interface, "txt2img", "txt2img"),
            (img2img_interface, "img2img", "img2img"),
            (extras_interface, "Extras", "extras"),
            (pnginfo_interface, "PNG Info", "pnginfo"),
        ]
    else:
        interfaces = [
            (txt2img_interface, "txt2img", "txt2img"),
            (img2img_interface, "img2img", "img2img"),
            (extras_interface, "Extras", "extras"),
            (pnginfo_interface, "PNG Info", "pnginfo"),
            (images_history, "History", "images_history"),
            (modelmerger_interface, "Checkpoint Merger", "modelmerger"),
            (train_interface, "Train", "ti"),
            (settings_interface, "Settings", "settings"),
        ]

P.S. I hope you are sure that your users are non-malicious. RCE exploits have already been demonstrated when using --share, and I'm sure the software is swiss cheese in terms of security.

[ResleyZ]

Oooh, I'll try this out, thanks! Maybe a specific install for this would be useful then, or I could tinker more with the .bats pointing to different stuff, but maybe that'd also be a lot of hassle.

And regarding the users, yeah, it's a fair point, but I've only set it up with a username and password, and only give it to people I know, not shared in a public space as well, but thanks for the reminder.

[Humanoidme]

Hi, did you implement the code suggested by @fortypercnt ? Did it work ? Thanks

[ResleyZ]

Hi, did you implement the code suggested by @fortypercnt ? Did it work ? Thanks

I ended up making a seperate .bat for other people to use, which would call a seperate list of extensions, models, etc. however, with the growth of the WebUI itself, extensions, models, etc. I decided to stop sharing it with other people, mainly to focus more on my own ease-of-use, rather than accessibility towards people who might use it every so often.

Right now, if I do want to share it others, the best way seems to use something like Stable Horde
https://github.com/natanjunges/stable-diffusion-webui-stable-horde
https://github.com/sdwebui-w-horde/sd-webui-stable-horde-worker