Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use static config file instead of local storage #509

Closed
aaaaalexis opened this issue Jan 26, 2024 · 4 comments
Closed

Use static config file instead of local storage #509

aaaaalexis opened this issue Jan 26, 2024 · 4 comments

Comments

@aaaaalexis
Copy link

Problem
Current implementation saves configuration in local storage, which causes inconvenience when using dynamic Gradio or ngrok link, as the settings would reset everytime a new instance opens. Furhermore, local storage takes up space that won't be cleared automatically.

Solution
Adding a new file for config only OR merge configuration with .env

The static file is prioritized and be the default state. An option to re-enable saving to local storage should be included.

@zanllp
Copy link
Owner

zanllp commented Mar 27, 2024

This feature will be implemented in the future. Currently, the main concern is that when switching to the local version, the user's existing settings may be lost.

@molegris
Copy link

hmmm, interesting. Is this why Global settings are never saved?
I have to set "Default Grid Cell Width (px)" and "Toggle Selection of Tag like" every time I restart the WebUI.

@zanllp
Copy link
Owner

zanllp commented Jun 23, 2024

hmmm, interesting. Is this why Global settings are never saved?
I have to set "Default Grid Cell Width (px)" and "Toggle Selection of Tag like" every time I restart the WebUI.

Normally, you shouldn't need to set it every time, unless you are accessing it through different origin each time (i.e., protocols, domains, ports).

@zanllp
Copy link
Owner

zanllp commented Jun 23, 2024

@aaaaalexis @molegris This issue has been resolved in the latest version.

However, it is not implemented through a configuration file. The current mechanism is that when you modify the setting on the IIB global setting page, it will synchronize the setting to the backend. Then, the next time you run IIB, it will pull and overwrite the local setting from the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants