[Feature Request] Make disabling the settings interface a command line option

[lethargus]

Can adding the settings_interface to the list of interfaces in ui.py be a command line option?

I have this running on an exposed endpoint accessible by some friends. I trust them (mostly) but I don't trust their security practices and having the ability to change where output is written feels like a solid vulnerability.

Right now I simply comment out the settings_interface in the interfaces list declaration in ui.py but I have to undo that change every pull. Would it be possible to make disabling that interface a command line option?

[EyeDeck]

There's --hide-ui-dir-config, which I added a few weeks ago.
Need to make a PR to get it to cover the newish Batch img2img tab...

[EyeDeck]

Ok, #988
As I wrote in the pull request comments:

I do wonder if --share and/or --listen should imply (at least the functionality of) --hide-ui-dir-config, and we change the flag to --show-ui-dir-config or something for turning on arbitrary directory access in those cases. I don't think it's good practice an obvious security vulnerability to be opt-out.

Thoughs? If it were solely up to me, I would make that change without a second thought, because I don't want to be the one blamed when someone's machine gets f**ked because they didn't have some obscure command line flag turned on for what should obviously be default functionality.

Perhaps, at the very least, --share and/or --listen without --gradio-auth should imply --hide-ui-dir-config.

[lethargus]

It makes sense to me and would get my vote, but I also know people don't look for flags so the number of "what happened to the settings page?" posts would be extreme.

To be fair, I didn't know about --hide-ui-dir-config either, and I thought I had been through the wiki documentation. I see it in there now, but perhaps I was focusing more on disabling ALL settings changes. This flag definitely addresses my main concern, though.

[lethargus]

--hide-ui-dir-config appears to do nothing to the new textual inversion tab. It still reveals the entire directory structure.

Perhaps two additional switches, one to completely disable the settings tab, and one to completely disable the textual inversion tab would be a good idea after all. Otherwise there's an extreme amount of trust placed on having this exposed in any way (through share or proxy/port forwarding)