-
-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Docs] Include all provider variables in config.toml #315
Comments
I'd rather not duplicate a bunch of examples, it's just env vars after all. You think it's enough if we just link to the doc on providers?
What do you mean?
That exists at https://gptme.org/docs/providers.html. Which doc pages did you read? What exactly would you want changed? Easiest would be if you submit a PR to https://github.com/ErikBjare/gptme/blob/master/docs/providers.rst |
I hear you, however for first time setup and if you don't have one of the ones in the example, you fail to get started.
That may help also, however for me it would have been best to have all the examples as comments in the config file to begin with.
Many other projects had only OpenAI support, and if using a compatible API, one can simply replace the OAI API key with another service, adjusting the base URL to get things working.
Yes it does exist there, just not explicitly. Hence the ask for clarity. I don't have things working yet (gptme-server crashes), so I hesitate to edit with examples that worked for me before they do. |
Ah! I see how that is confusing. I'll try to make the example in
Logs? Is it just missing |
I updated the docs for |
config.toml looks good (nice addition for DeepSeek), however the providers page has a few issues:
As to the gptme-server, it doesn't seem to pick up the XAI_API_KEY in the config or the shell export ;-/ |
Since I started without those (XAI & GROQ) it was painful figuring it out.
Overloading the OPENAI vars with other keys didn't work.
I only found the CLI export examples after a few hours ;-/
Also, please include examples of calling providers from CLI as well as providers/model combo.
Note that some providers don't have a default fallback and need more specificity.
The text was updated successfully, but these errors were encountered: