When using redis for caching purposes the librechat.yaml file does not respect file edits, because the contents are loaded into the cache once and never invalidated.
The getCustomConfig code executes on startup and finds the alterations made and even logs out the new file, but when calling the /api/config endpoint no changes are observed.
Steps to Reproduce
Write librechat.yaml file
Enable Redis caching
Alter librechat.yaml file (e.g. model specs)
No Changes found on /api/config
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Screenshots
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct
What happened?
When using redis for caching purposes the
librechat.yamlfile does not respect file edits, because the contents are loaded into the cache once and never invalidated.The
getCustomConfigcode executes on startup and finds the alterations made and even logs out the new file, but when calling the/api/configendpoint no changes are observed.Steps to Reproduce
librechat.yamlfilelibrechat.yamlfile (e.g. model specs)/api/configWhat browsers are you seeing the problem on?
No response
Relevant log output
No response
Screenshots
No response
Code of Conduct