You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mentioning the user provided key warning https://www.librechat.ai/docs/configuration/dotenv#general-config, in the Custom Endpoints Intro File, would greatly enhance the documentation, because in all other doc file it looks like 'user_provided' must be set e.g. in the "Custom Endpoints" file .
" />
Also clearly differentiating what config file sets what setting would be very helpful.
Its never mentioned anywhere if I should use my own .env file, the docker-compose.override.yml file or the librechat.yaml file for setting the the authentication keys.
I do think if the docs where way more clearly structured and not partly outdated, this great project would enjoy way more popularity by more novice people. Thanks for keeping up the good work!
The text was updated successfully, but these errors were encountered:
Mentioning the user provided key warning https://www.librechat.ai/docs/configuration/dotenv#general-config, in the Custom Endpoints Intro File, would greatly enhance the documentation, because in all other doc file it looks like 'user_provided' must be set e.g. in the "Custom Endpoints" file .
" />
Also clearly differentiating what config file sets what setting would be very helpful.
E.g at first it seems like end point mus be set in docker-compose.override.yml https://www.librechat.ai/docs/configuration/dotenv#general-config, but later in another file
it becomes clear that librechat.yaml is used for that.
Another example is: where do i set the authencation keys mentioned here: https://www.librechat.ai/docs/configuration/dotenv#registration-and-login ?
Its never mentioned anywhere if I should use my own .env file, the docker-compose.override.yml file or the librechat.yaml file for setting the the authentication keys.
I do think if the docs where way more clearly structured and not partly outdated, this great project would enjoy way more popularity by more novice people. Thanks for keeping up the good work!
The text was updated successfully, but these errors were encountered: