Open
Conversation
Author
|
@NeptuneHub if you find a spare 10 minutes could you take a quick look at these PRs? 🙏 |
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.
Self-hosted AI solutions seem to strongly favour the OpenAI API spec rather than Ollama's API. With that in mind, this PR adds the three relevant environment variables to the helm chart.
OPENAI_API_KEYis another secret, included in the flask and worker pods. This isn't really relevant for self-hosting, but seems to be the best route through the AI code which uses the presence of an api-key to decide if we're using an OpenAI compatible API or an Ollama API.OPENAI_SERVER_URLandOPENAI_MODEL_NAMEare then regular environment variables.Screenshot of my playlists generating locally with these changes and
qwen-30b-a3b-instruct: