feat: Order/disable endpoints with ENDPOINTS env var #1206
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
In your .env file,
Uncomment the
ENDPOINTS
variable to determine which endpoints are available.Listed here are the only accepted values, which are all enabled if an authentication
option is provided, whether user provided or admin provided in this .env file.
Note: the first value is considered the default value.
Also note that clicking on a conversation will make that conversation's endpoint the target endpoint for a new chat, and saves this in local storage.
Also closes #1205
From discussion #1158
Change Type
Testing
Manual testing
Checklist