Replies: 10 comments 1 reply
-
Thanks for raising this, I understand the need. Do you suggest to introduce user-level api keys that can be used to create projects and project-level api keys? |
Beta Was this translation helpful? Give feedback.
-
@marcklingen, yes, I see this as the only way to control the possibility of creating projects, thank you and sorry for longer response |
Beta Was this translation helpful? Give feedback.
-
Thanks for the clarification! Does a default project/user solve the problem for you or do you need to create multiple projects while and api keys while the container is already running? @maxxte |
Beta Was this translation helpful? Give feedback.
-
This looks promising. |
Beta Was this translation helpful? Give feedback.
-
Adding to this, it's best to support create, delete and manage (manage authorization, etc.) APIs. |
Beta Was this translation helpful? Give feedback.
-
Additionally to creating projects/keys, which I guess will be authorized via let's say |
Beta Was this translation helpful? Give feedback.
-
Adding to this conversation, how about a master API key that can be used for all Langfuse projects? This may already solve the issue of not being able to create projects/keys via an API, for some users, including us. Currently, we need to manually create each Langfuse project, generate the associated API key, copy them to our secret management tool and have extra business logic in our infrastructure and deployment scripts, that assigns the correct Langchain key to each containerized application. All this would be instantly solved if we could use one master API key. |
Beta Was this translation helpful? Give feedback.
-
There's a PR that seeds the database with default parameters and an initial project that has not been looked for #1109 This may help to solve the problem of creating the first project manually but still has the problem of not giving full control to the user in the future. Although i would like the seed PR to be merged since it is what i need to use for docker compose in production |
Beta Was this translation helpful? Give feedback.
-
Hi all, we are currently working on |
Beta Was this translation helpful? Give feedback.
-
Describe the feature you'd like to request
While automatically setting different environments we would like to add observability in automatic way, this means to create project in langfuse and get secret and public keys, to pass them later to application
Describe the solution you'd like to see
Introduce new Projects endpoint POST with parameters (project name) to create new project
And endpoint for creating API keys, which will consume project name/id and respond with secret and public keys.
Additional information
No response
Contribute
Beta Was this translation helpful? Give feedback.
All reactions