Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Configurability for Site or Tenant #14

Closed
stoerr opened this issue Jul 17, 2023 · 1 comment
Closed

Configurability for Site or Tenant #14

stoerr opened this issue Jul 17, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@stoerr
Copy link
Member

stoerr commented Jul 17, 2023 •
edited
Loading

We need a configuration for the OpenAI key per site or tenant for the case that somebody wants to use it seriously. The common key is for trying it out, but shouldn't be used for all time.

While we'r at site specific configurations: It's sensible to add a possibility to configure additional prompts, which could be put there as well.

Open points: the OpenAI key is a secret - how to make sure not every editor can see it?
@stoerr stoerr added the enhancement New feature or request label Jul 17, 2023
@stoerr
Copy link
Member Author

stoerr commented Nov 7, 2023

This is essentially implemented with #36 using Sling Context Aware Configuration with configuration com.composum.ai.backend.slingbase.model.OpenAIConfig "Composum AI OpenAI Configuration" .

@stoerr stoerr closed this as completed Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stoerr