-
Notifications
You must be signed in to change notification settings - Fork 13
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
docs: deploy langfuse for development #347
base: main
Are you sure you want to change the base?
Conversation
Note(s) for PR Auther:
Note(s) for PR Reviewer(s):
|
```json | ||
"REDIS_PASSWORD": "myredissecret", | ||
"REDIS_DB_NUMBER": "1", | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please indent the code block.
open http://localhost:3000/auth/sign-up | ||
``` | ||
|
||
Create an account, then hit the `+ New Organization` button. Give your organization a name, hit `Next` in the `Invite Members` page, find a name for you project an hit `Create`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Create an account, then hit the `+ New Organization` button. Give your organization a name, hit `Next` in the `Invite Members` page, find a name for you project an hit `Create`. | |
4. Create an account, and choose **+ New Organization**. Give your organization a name, and choose **Next**. | |
5. On the **Invite Members** page, give your project a name, and choose **Create**. |
``` | ||
|
||
Create an account, then hit the `+ New Organization` button. Give your organization a name, hit `Next` in the `Invite Members` page, find a name for you project an hit `Create`. | ||
On the next page, hit the `API Keys` menu point, then hit the `+ Create new API keys` button. Copy the `Secret Key`, `Secret Key` and `Host` and paste them as values in to your `kyma-companion`'s `config/config.json` for your `LANGFUSE_HOST`, `LANGFUSE_SECRET_KEY`, `LANGFUSE_PUBLIC_KEY` keys: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the next page, hit the `API Keys` menu point, then hit the `+ Create new API keys` button. Copy the `Secret Key`, `Secret Key` and `Host` and paste them as values in to your `kyma-companion`'s `config/config.json` for your `LANGFUSE_HOST`, `LANGFUSE_SECRET_KEY`, `LANGFUSE_PUBLIC_KEY` keys: | |
6. Go to **API Keys**, and choose **+ Create new API keys**. Copy the `Secret Key`, `Public Key`, and `Host`, and paste them as values into your Kyma Companion's `config/config.json` for , **LANGFUSE_SECRET_KEY**, **LANGFUSE_PUBLIC_KEY**, and **LANGFUSE_HOST**: |
```json | ||
... | ||
"LANGFUSE_HOST": "https://localhost:3000", | ||
"LANGFUSE_SECRET_KEY": "<your secret key>", | ||
"LANGFUSE_PUBLIC_KEY": "<your public key>", | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please indent the code block.
"LANGFUSE_PUBLIC_KEY": "<your public key>", | ||
``` | ||
|
||
## Deploy on Kubernetes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Deploy on Kubernetes | |
## Deploy LangFuse on Kubernetes |
For the whole section, please create a step-by-step instruction with an ordered list of steps and indented code blocks.
|
||
## Deploy on Kubernetes | ||
|
||
### For development purpose |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### For development purpose |
Is there any other purpose?
Co-authored-by: Małgorzata Świeca <malgorzata.swieca@sap.com>
Co-authored-by: Małgorzata Świeca <malgorzata.swieca@sap.com>
Co-authored-by: Małgorzata Świeca <malgorzata.swieca@sap.com>
Co-authored-by: Małgorzata Świeca <malgorzata.swieca@sap.com>
Description
Changes proposed in this pull request:
Related issue(s)
#49