feat: use OPENAI_API_URL from env to support custom OpenAI API endpoint #1522
Conversation
This file contains 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
odilitime
approved these changes
Dec 28, 2024
|
Hello |
1to3for5vi7ate9x
pushed a commit
to 1to3for5vi7ate9x/eliza
that referenced
this pull request
Jan 26, 2025
feat: use OPENAI_API_URL from env to support custom OpenAI API endpoint
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Relates to:
Risks
Low
Background
There are some scenarios that require the use of the custom OpenAI API endpoint
What does this PR do?
Support custom OpenAI API endpoint URL using OPENAI_API_URL in env
What kind of change is this?
Documentation changes needed?
Added documentation for OPENAI_API_URL environment variable，
OPENAI_API_URL= # OpenAI API Endpoint (optional), Default: https://api.openai.com/v1
Testing
Where should a reviewer start?
Detailed testing steps