-
Notifications
You must be signed in to change notification settings - Fork 382
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
feat: Allow deployment of langfuse with given API token #517
Comments
Idea if the database schema seems kinda stable to @marcklingen: how about provisionning a DB for langfuse, in which we inject credential data on start? |
Agree, this would be super useful! Context
Fastest route
|
@matthieudelaro have you made an attempt to add this? Happy to contribute or help |
Hello, I've tried implement this feature in a new PR. |
When do you plan to submit this pull request? @marcklingen |
Hi everyone, I'm super sorry for moving slow on this. I'm currently thinking about how to best achieve this. This PR is a solid approach but also quite hacky as we rely on the seeder. To make this more maintainable, provisioning projects via an API would be much better based on an org: #1930 |
Hey there! I'm coming from a project where we use Terraform to deploy to QA and PROD environments to ensure the deployments are reproducible. In addition, we have to self-host everything that contains user data. Terraform simultaneously deploys both Langfuse and the chatbot service that tries to authenticate with Langfuse. Thus, it's not feasible to manually create a project and an API key in Langfuse, since the API key has to be known before the deployment of the chatbot service. Besides, developers are forbidden to make any infrastructure changes manually on QA or PROD. This feature request is as close as it gets to my problem across the Langfuse documentation. Or am I missing something? @marcklingen please advise if this automatically deployed self-hosted Langfuse use-case is supported in the current version of Langfuse, and what would be the best way to achieve that. Or should we wait for this feature request to be implemented? |
Describe the feature you'd like to request
I would like to be able to spawn a new instance of langfuse with docker-compose / k8s.
I also want to spawn langchain services (langflow, python scripts) which are going to connect to this langfuse.
Describe the solution you'd like to see
So I would like to provide langfuse with the API keys which it will accept connections from.
(Ideally, there would also be automatic creation of users. But maybe it's better to keep that in a separate PR.)
Additional information
I'm open to contributing by creating a PR, if clear instructions are given about the arch of langfuse which is relevant to the issues, and locations in the source code where I should put modifications.
Contribute
The text was updated successfully, but these errors were encountered: