Fix Ollama provider authentication and API endpoint for Docker setup

[DarkMenacer]

Related GitHub Issue

Closes: #1935

Description

Hi @hannesrudolph @daniel-lxs
I believe I have figured out the bug and come up with a temporary fix

By changing this, I was able to resolve the bug

But clearly I cannot hard-code my JWT Token as the apiKey
Additionally, the base url seems to be off too
(I have currently set up ollama using docker which has the url path as api/chat/completion instead of v1/chat/completion)
Maybe there are other installation methods which give me the latter url suffix (exploring this parallely)

Test Procedure

To test this fix,

1. Firstly install ollama (and open web ui) through docker.
2. Once those containers are running, go to http://localhost:3000 (the open web ui localhost)
3. Sign up
4. After signing up, copy the jwt token for the account (in the avatar -> settings -> account -> api keys)
5. Copy the JWT Token and replace it with the api key I have pasted.
6. Run the application with a configuration profile of ollama to get the results

Type of Change

• 🐛 Bug Fix: Non-breaking change that fixes an issue.
• ✨ New Feature: Non-breaking change that adds functionality.
• 💥 Breaking Change: Fix or feature that would cause existing functionality to not work as expected.
• ♻️ Refactor: Code change that neither fixes a bug nor adds a feature.
• 💅 Style: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
• 📚 Documentation: Updates to documentation files.
• ⚙️ Build/CI: Changes to the build process or CI configuration.
• 🧹 Chore: Other changes that don't modify src or test files.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Code Quality:
  • My code adheres to the project's style guidelines.
  • There are no new linting errors or warnings (npm run lint).
  • All debug code (e.g., console.log) has been removed.
• Testing:
  • New and/or updated tests have been added to cover my changes.
  • All tests pass locally (npm test).
  • The application builds successfully with my changes.
• Branch Hygiene: My branch is up-to-date (rebased) with the main branch.
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Changeset: A changeset has been created using npm run changeset if this PR includes user-facing changes or dependency updates.
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Before:

After:

Documentation Updates

Additional Notes

Get in Touch

[hannesrudolph]

stale