Replies: 1 comment 2 replies
-
That’s a great idea. I never considered using the repo to serve a fetchable file like that. There is one thing we have to keep in mind. Changes to the models.json file are not handled solely with INSERTs. Some existing lines will change, like the default model, and those require UPDATEs to existing records. But that won’t be too tricky the sync code could just iterate through all of them. We have a few PRs where we’ve done this (for the past model changes) so we can use these as a guide. Is this something you could take the lead on creating a PR for? I can help review and test it out. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It's another week and there are new openai/anthropic/groq models available and some price changes, etc.
Currently we have
LanguageModel
(perUser
) and I think the only way to programmatically populate this model is via migrations.I'd propose that we document the available models in this repo, in a
models.json
file, which could then be fetched via HTTP at any time, by any running hostedgpt app to get latest values.For example, to fetch the raw value of
fly.toml
in the root of the repo, visit https://raw.githubusercontent.com/AllYourBot/hostedgpt/refs/heads/main/fly.tomlSo a
models.json
would be HTTP retrievable at https://raw.githubusercontent.com/AllYourBot/hostedgpt/refs/heads/main/models.jsonAn airlocked HostedGPT could just load the models for new Users from this file.
An internet-based HostedGPT could fetch the file from the trusted
main
branch from github.The Language Models page could have a "Sync from Github" button
Beta Was this translation helpful? Give feedback.
All reactions