Skip to content

Conversation

@eljamm
Copy link
Contributor

@eljamm eljamm commented Jun 15, 2024

Any OpenAI-compatible backend is supported, so it would be better to maintain them in a single script and have seperate scripts for the ones that aren't compatible.

This would also be clearer for users which might wrongly assume that only one backend is supported.

This change also automatically adds the OpenAI endpoint to the base URL because all compatible backends support it already. Therefore, users only need to provide the local address.

Any OpenAI-compatible backend is supported, so it would be better to
maintain them in a single script and have seperate scripts for the ones
that aren't compatible.

This would also be clearer for users which might wrongly assume that
only one backend is supported.

This change also automatically adds the OpenAI endpoint to the base URL
because all compatible backends support it already. Therefore, users
only need to provide the local address.
@pbek
Copy link
Member

pbek commented Jun 15, 2024

The problem is that you can only have one script with the same id. Means, if you have multiple different local (or remote) backends, then you can only use one with this script. So if you want to make one script for all use cases, please create a new script that supports multiple backends and also give hints about the API end points of the different backends...

I, for example, wasn't aware that the chat API of ollama was not the OpenAI compatible API!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants