enh: config.json to db #1756

New Issue

2025-11-11T14:51:50-06:00

GiteaMirror commented

2025-11-11 14:51:50 -06:00

Originally created by @crizCraig on GitHub (Aug 12, 2024).

Originally assigned to: @tjbck on GitHub.

Is your feature request related to a problem? Please describe.
config.json is currently a source controlled file that may contain user-specific keys. it also does not seem to be suitable for distributed deployments where web servers are on multiple machines (unless the file is symlinked to EFS or similar)

Describe the solution you'd like
It seems like config should be stored in the DB so that distributed deployments can access it in a central location. This would also make sense to put keys in since it's not source controlled

Describe alternatives you've considered
The file could be removed from git and centralized via EFS or persistent store or some shared disk, but this seems like a bandaid.

Additional context
I've only been working with open webui for a couple weeks.

Originally created by @crizCraig on GitHub (Aug 12, 2024). Originally assigned to: @tjbck on GitHub. **Is your feature request related to a problem? Please describe.** config.json is currently a source controlled file that may contain user-specific keys. it also does not seem to be suitable for distributed deployments where web servers are on multiple machines (unless the file is symlinked to EFS or similar) **Describe the solution you'd like** It seems like config should be stored in the DB so that distributed deployments can access it in a central location. This would also make sense to put keys in since it's not source controlled **Describe alternatives you've considered** The file could be removed from git and centralized via EFS or persistent store or some shared disk, but this seems like a bandaid. **Additional context** I've only been working with open webui for a couple weeks.

GiteaMirror closed this issue

2025-11-11 14:51:51 -06:00

GiteaMirror commented

2025-11-11 14:51:51 -06:00

@crizCraig commented on GitHub (Aug 16, 2024):

It looks like OPENAI_API_KEYS, OPENAI_API_BASE_URLS, and other PersistentConfig can be pulled from .env as semi-colon separated values. So that's a workaround to the version control part of this issue.

@crizCraig commented on GitHub (Aug 16, 2024): It looks like `OPENAI_API_KEYS`, `OPENAI_API_BASE_URLS`, and other `PersistentConfig` can be pulled from `.env` as semi-colon separated values. So that's a workaround to the version control part of this issue.

GiteaMirror commented

2025-11-11 14:51:52 -06:00

@asdf8675309 commented on GitHub (Aug 21, 2024):

Glad to see this is addressed - I put them in a docker-compose.yml file - not sure that's any better.

@asdf8675309 commented on GitHub (Aug 21, 2024): Glad to see this is addressed - I put them in a docker-compose.yml file - not sure that's any better.

GiteaMirror commented

2025-11-11 14:51:52 -06:00