I think if we had them as environment variables it would be easy to deploy.
Alternatives Considered
Another option since it might be a potentiall N sized list is to have a config file
Additional Context
No response
Originally created by @rschwabLEK on GitHub (Jul 28, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16100
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
It would be useful if I could configure these rather than them being hard coded here:
https://github.com/open-webui/open-webui/blob/b8912aa671281ee577981a2a481d8c2b233d2938/src/lib/components/chat/Messages/RateComment.svelte#L178
### Desired Solution you'd like
I think if we had them as environment variables it would be easy to deploy.
### Alternatives Considered
Another option since it might be a potentiall N sized list is to have a config file
### Additional Context
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @rschwabLEK on GitHub (Jul 28, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16100
Check Existing Issues
Problem Description
It would be useful if I could configure these rather than them being hard coded here:
https://github.com/open-webui/open-webui/blob/b8912aa671281ee577981a2a481d8c2b233d2938/src/lib/components/chat/Messages/RateComment.svelte#L178
Desired Solution you'd like
I think if we had them as environment variables it would be easy to deploy.
Alternatives Considered
Another option since it might be a potentiall N sized list is to have a config file
Additional Context
No response