You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't want Ollama automatically installed but I still want to set a base URL and have the API enabled.
A change went into the 3.1.x version of the chart that sets ENABLE_OLLAMA_API to false if ollama.enabled is false. The commit message seems to imply the opposite though, 2062a5d but it is not setting the URL if Ollama isn't set to be automatically deployed. See this comment https://github.com/open-webui/helm-charts/blob/main/charts/open-webui/values.yaml#L4 for how enabling ollama is to deploy it vs. just to use the API.
Rolling the chart back to 3.1.18 fixes this for me. I am unable to go up to 3.2.x because my ODIC log in stops working after the change to config maps but since this issue was introduced first (and looks to be copied into the ConfigMap change) I'll look more into that after this.
Thanks!
The text was updated successfully, but these errors were encountered:
Thanks for the report @thaynes43, that's definitely an oversight. I'll have time to fix this over the weekend, PR welcome if you want to beat me to it though. Thank you!
Hey @thaynes43, you are right, need to take into account that you still can use API the without deploying it.
Looks like #88, fix both OIDC and OLLAMA URL. I'm following this one.
p.s.: @0xThresh, feel free to tag me, I'll take a look right away.
I don't want Ollama automatically installed but I still want to set a base URL and have the API enabled.
A change went into the 3.1.x version of the chart that sets ENABLE_OLLAMA_API to false if ollama.enabled is false. The commit message seems to imply the opposite though, 2062a5d but it is not setting the URL if Ollama isn't set to be automatically deployed. See this comment https://github.com/open-webui/helm-charts/blob/main/charts/open-webui/values.yaml#L4 for how enabling ollama is to deploy it vs. just to use the API.
Rolling the chart back to
3.1.18
fixes this for me. I am unable to go up to3.2.x
because my ODIC log in stops working after the change to config maps but since this issue was introduced first (and looks to be copied into the ConfigMap change) I'll look more into that after this.Thanks!
The text was updated successfully, but these errors were encountered: