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
Since the website will be running in a production environment, it will be better that admin is able add or remove model through UI instead of a production deployment for a minor .env.local update.
The text was updated successfully, but these errors were encountered:
TriEyeMonster
changed the title
Feature Request: Manage model through UI instead of .env.local
Feature Request: Manage model through UI instead of updating .env.local
Jun 14, 2024
Yeah that would be definitely be nice, I think it was on our roadmap a while ago but never got prioritized. If there's strong demand we could try to tackle this! It would make life a lot easier for self-hosting users.
@nsarrazin how do you think we should handle endpoints array in the Modal collection? Currently, we have a union of Endpoint types (I think it will be hard to create one unified collection from them).
So,
do we want to have an additional mongo collection for each endpoint type (with their own schema): AwsEndpointSchema, OpenaiEndpointSchema, AnthropicEndpointSchema
or, just create a collection with type (aws, openai, anthropic) and json (each endpoint schema will have it's own structure) and validate it from the frontend side (like we do right now)?
Since the website will be running in a production environment, it will be better that admin is able add or remove model through UI instead of a production deployment for a minor .env.local update.
The text was updated successfully, but these errors were encountered: