feat: added api key support to ollama backend. #107
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
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.
This PR adds api key support to the ollama backend. Ollama itself does not support any authentication (as far as I know), but it can easily be added by a reverse proxy or other software like Open WebUI, which proxies the ollama queries.
I tested against my local Open WebUI instance using http://myhost/ollama URL and seems to be working fine, in fact much better than raw ollama (I'm getting a lot of errors loading the model, though it already is loaded). This PR allows me to control access to my server using open webui and not to expose publicly the ollama instance.
Closes issue #106 .