allow configuring LOCALAGI to use a custom base url#469
Open
bhulsken wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Allow a customer base URL for LocalAGI using environment variable LOCALAGI_BASE_URL. Defaults to ":3000" which is the hardcoded address at the moment.
Update README.md accordingly, in particular to distinguish LOCALAGI_LOCALRAG_URL from LOCALAGI_BASE_URL, I think there is a mix up between the two in the current documentation, where LOCALAGI_BASE_URL is described to affect the RAG URL (but doesn't actually do anything), while LOCALAGI_LOCALRAG_URL is implemented but not described in the README.