@lobehub/chat 1.55.1 → 1.55.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +25 -0
- package/changelog/v1.json +9 -0
- package/docs/changelog/2025-02-02-deepseek-r1.mdx +4 -4
- package/docs/self-hosting/advanced/auth/next-auth/casdoor.mdx +4 -3
- package/docs/self-hosting/advanced/auth/next-auth/casdoor.zh-CN.mdx +4 -3
- package/docs/self-hosting/advanced/auth/next-auth/logto.mdx +9 -9
- package/docs/self-hosting/advanced/auth/next-auth/logto.zh-CN.mdx +9 -9
- package/docs/self-hosting/advanced/model-list.zh-CN.mdx +6 -6
- package/docs/self-hosting/advanced/observability/langfuse.zh-CN.mdx +70 -0
- package/docs/self-hosting/environment-variables/auth.mdx +3 -3
- package/docs/self-hosting/environment-variables/auth.zh-CN.mdx +3 -2
- package/docs/self-hosting/platform/btpanel.mdx +1 -1
- package/docs/self-hosting/platform/btpanel.zh-CN.mdx +1 -1
- package/docs/self-hosting/platform/tencentcloud-lighthouse.mdx +9 -9
- package/docs/self-hosting/platform/tencentcloud-lighthouse.zh-CN.mdx +6 -8
- package/docs/self-hosting/server-database.mdx +1 -1
- package/docs/usage/providers/wenxin.mdx +1 -0
- package/docs/usage/providers/wenxin.zh-CN.mdx +1 -0
- package/package.json +1 -1
- package/src/features/Conversation/Messages/Assistant/index.tsx +5 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,31 @@
|
|
|
2
2
|
|
|
3
3
|
# Changelog
|
|
4
4
|
|
|
5
|
+
### [Version 1.55.2](https://github.com/lobehub/lobe-chat/compare/v1.55.1...v1.55.2)
|
|
6
|
+
|
|
7
|
+
<sup>Released on **2025-02-15**</sup>
|
|
8
|
+
|
|
9
|
+
#### 🐛 Bug Fixes
|
|
10
|
+
|
|
11
|
+
- **misc**: Avoid blank reasoning with OpenRouter.
|
|
12
|
+
|
|
13
|
+
<br/>
|
|
14
|
+
|
|
15
|
+
<details>
|
|
16
|
+
<summary><kbd>Improvements and Fixes</kbd></summary>
|
|
17
|
+
|
|
18
|
+
#### What's fixed
|
|
19
|
+
|
|
20
|
+
- **misc**: Avoid blank reasoning with OpenRouter, closes [#6153](https://github.com/lobehub/lobe-chat/issues/6153) ([c2278d1](https://github.com/lobehub/lobe-chat/commit/c2278d1))
|
|
21
|
+
|
|
22
|
+
</details>
|
|
23
|
+
|
|
24
|
+
<div align="right">
|
|
25
|
+
|
|
26
|
+
[](#readme-top)
|
|
27
|
+
|
|
28
|
+
</div>
|
|
29
|
+
|
|
5
30
|
### [Version 1.55.1](https://github.com/lobehub/lobe-chat/compare/v1.55.0...v1.55.1)
|
|
6
31
|
|
|
7
32
|
<sup>Released on **2025-02-15**</sup>
|
package/changelog/v1.json
CHANGED
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
---
|
|
2
2
|
title: >-
|
|
3
|
-
LobeChat Integrates DeepSeek R1, Bringing a Revolutionary Chain of Thought
|
|
4
|
-
|
|
3
|
+
LobeChat Integrates DeepSeek R1, Bringing a Revolutionary Chain of Thought
|
|
4
|
+
Experience
|
|
5
5
|
description: >-
|
|
6
|
-
LobeChat v1.49.12 fully supports the DeepSeek R1 model, providing users with
|
|
7
|
-
|
|
6
|
+
LobeChat v1.49.12 fully supports the DeepSeek R1 model, providing users with
|
|
7
|
+
an unprecedented interactive experience in the chain of thought.
|
|
8
8
|
tags:
|
|
9
9
|
- LobeChat
|
|
10
10
|
- DeepSeek
|
|
@@ -113,12 +113,13 @@ If you are deploying using a public network, the following assumptions apply:
|
|
|
113
113
|
- Method: `POST`
|
|
114
114
|
- Content Type: `application/json`
|
|
115
115
|
- Headers: `casdoor-secret`: `Your Webhook Secret`
|
|
116
|
-
|
|
116
|
+
|
|
117
|
+
> The secret is generated by yourself, you can visit [https://generate-secret.vercel.app/10](https://generate-secret.vercel.app/10) to generate a 10 bit secret.
|
|
117
118
|
|
|
118
119
|
- Event: `update-user`
|
|
119
120
|
- Is user extented: `true`
|
|
120
121
|
|
|
121
|
-
Save and Exit, then copy the Webhook secret and fill it in the environment variable
|
|
122
|
+
Save and Exit, then copy the Webhook secret and fill it in the environment variable \`CASDOOR\_WEBHOOK\_SECRET.
|
|
122
123
|
|
|
123
124
|
### Configure Environment Variables
|
|
124
125
|
|
|
@@ -140,7 +141,7 @@ If you are deploying using a public network, the following assumptions apply:
|
|
|
140
141
|
| `AUTH_CASDOOR_SECRET` | Required | The client secret from the Casdoor application details page. |
|
|
141
142
|
| `AUTH_CASDOOR_ISSUER` | Required | The OpenID Connect issuer for the Casdoor provider. |
|
|
142
143
|
| `NEXTAUTH_URL` | Required | This URL specifies the callback address for Auth.js during OAuth verification and needs to be set only if the default generated redirect address is incorrect. `https://lobe.example.com/api/auth` |
|
|
143
|
-
| `CASDOOR_WEBHOOK_SECRET` | Optional | A key used to verify whether the request sent by Casdoor is legal.
|
|
144
|
+
| `CASDOOR_WEBHOOK_SECRET` | Optional | A key used to verify whether the request sent by Casdoor is legal. |
|
|
144
145
|
|
|
145
146
|
<Callout type={'tip'}>
|
|
146
147
|
Visit [📘 Environment Variables](/docs/self-hosting/environment-variables/auth#casdoor) for
|
|
@@ -102,7 +102,8 @@ tags:
|
|
|
102
102
|
- 方法：`POST`
|
|
103
103
|
- 内容类型：`application/json`
|
|
104
104
|
- 协议头：`casdoor-secret`: `你的Webhook密钥`
|
|
105
|
-
|
|
105
|
+
|
|
106
|
+
> 密钥由你自己生成，用于验证 Casdoor 发送的请求是否合法。 可以前往 [https://generate-secret.vercel.app/10](https://generate-secret.vercel.app/10) 生成一个 10 位的密钥。
|
|
106
107
|
|
|
107
108
|
- 事件：`update-user`
|
|
108
109
|
- 拓展用户字段：`true`
|
|
@@ -112,7 +113,7 @@ tags:
|
|
|
112
113
|
### 关闭注册
|
|
113
114
|
|
|
114
115
|
为了保证你的应用安全，建议关闭 Casdoor 的注册功能，改为由管理员手动添加用户。
|
|
115
|
-
|
|
116
|
+
|
|
116
117
|
前往 `身份认证` -> `应用`，将 `启用注册` 设置为 `否`。
|
|
117
118
|
|
|
118
119
|
<Callout type={'warning'}>
|
|
@@ -139,7 +140,7 @@ tags:
|
|
|
139
140
|
| `AUTH_CASDOOR_SECRET` | 必选 | Casdoor 应用详情页的客户端密钥 |
|
|
140
141
|
| `AUTH_CASDOOR_ISSUER` | 必选 | Casdoor 提供程序的 OpenID Connect 颁发者。 |
|
|
141
142
|
| `NEXTAUTH_URL` | 必选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://lobe.example.com/api/auth` |
|
|
142
|
-
| `CASDOOR_WEBHOOK_SECRET` | 可选 | 用于验证 Casdoor 发送的 Webhook 请求是否合法的密钥。
|
|
143
|
+
| `CASDOOR_WEBHOOK_SECRET` | 可选 | 用于验证 Casdoor 发送的 Webhook 请求是否合法的密钥。 |
|
|
143
144
|
|
|
144
145
|
<Callout type={'tip'}>
|
|
145
146
|
前往 [📘 环境变量](/zh/docs/self-hosting/environment-variables/auth#casdoor) 可查阅相关变量详情。
|
|
@@ -67,15 +67,15 @@ If you are using Logto Cloud, assume its endpoint domain is `https://example.log
|
|
|
67
67
|
|
|
68
68
|
When deploying LobeChat, you need to configure the following environment variables:
|
|
69
69
|
|
|
70
|
-
| Environment Variable
|
|
71
|
-
|
|
|
72
|
-
| `NEXT_AUTH_SECRET`
|
|
73
|
-
| `NEXT_AUTH_SSO_PROVIDERS`
|
|
74
|
-
| `AUTH_LOGTO_ID`
|
|
75
|
-
| `AUTH_LOGTO_SECRET`
|
|
76
|
-
| `AUTH_LOGTO_ISSUER`
|
|
77
|
-
| `NEXTAUTH_URL`
|
|
78
|
-
| `LOGTO_WEBHOOK_SIGNING_KEY` | Optional | The key used to verify the legality of Webhook requests sent by Logto.
|
|
70
|
+
| Environment Variable | Type | Description |
|
|
71
|
+
| --------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
72
|
+
| `NEXT_AUTH_SECRET` | Required | The key used to encrypt Auth.js session tokens. You can generate a key using the command: `openssl rand -base64 32` |
|
|
73
|
+
| `NEXT_AUTH_SSO_PROVIDERS` | Required | Select the single sign-on provider for LobeChat. For Logto, enter `logto`. |
|
|
74
|
+
| `AUTH_LOGTO_ID` | Required | The Client ID from the Logto App details page |
|
|
75
|
+
| `AUTH_LOGTO_SECRET` | Required | The Client Secret from the Logto App details page |
|
|
76
|
+
| `AUTH_LOGTO_ISSUER` | Required | OpenID Connect issuer of the Logto provider |
|
|
77
|
+
| `NEXTAUTH_URL` | Required | This URL specifies the callback address for Auth.js during OAuth verification, needed only if the default generated redirect address is incorrect. `https://lobe.example.com/api/auth` |
|
|
78
|
+
| `LOGTO_WEBHOOK_SIGNING_KEY` | Optional | The key used to verify the legality of Webhook requests sent by Logto. |
|
|
79
79
|
|
|
80
80
|
<Callout type={'tip'}>
|
|
81
81
|
Visit [📘 Environment Variables](/docs/self-hosting/environment-variables/auth#logto) for details on related variables.
|
|
@@ -64,15 +64,15 @@ tags:
|
|
|
64
64
|
|
|
65
65
|
在部署 LobeChat 时，你需要配置以下环境变量：
|
|
66
66
|
|
|
67
|
-
| 环境变量
|
|
68
|
-
|
|
|
69
|
-
| `NEXT_AUTH_SECRET`
|
|
70
|
-
| `NEXT_AUTH_SSO_PROVIDERS`
|
|
71
|
-
| `AUTH_LOGTO_ID`
|
|
72
|
-
| `AUTH_LOGTO_SECRET`
|
|
73
|
-
| `AUTH_LOGTO_ISSUER`
|
|
74
|
-
| `NEXTAUTH_URL`
|
|
75
|
-
| `LOGTO_WEBHOOK_SIGNING_KEY` | 可选 | 用于验证 Logto 发送的 Webhook 请求是否合法的密钥。
|
|
67
|
+
| 环境变量 | 类型 | 描述 |
|
|
68
|
+
| --------------------------- | -- | ------------------------------------------------------------------------------------------------ |
|
|
69
|
+
| `NEXT_AUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32` |
|
|
70
|
+
| `NEXT_AUTH_SSO_PROVIDERS` | 必选 | 选择 LoboChat 的单点登录提供商。使用 Logto 请填写 `logto`。 |
|
|
71
|
+
| `AUTH_LOGTO_ID` | 必选 | Logto App 详情页的 Client ID |
|
|
72
|
+
| `AUTH_LOGTO_SECRET` | 必选 | Logto App 详情页的 Client Secret |
|
|
73
|
+
| `AUTH_LOGTO_ISSUER` | 必选 | Logto 提供程序的 OpenID Connect 颁发者 |
|
|
74
|
+
| `NEXTAUTH_URL` | 必选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://lobe.example.com/api/auth` |
|
|
75
|
+
| `LOGTO_WEBHOOK_SIGNING_KEY` | 可选 | 用于验证 Logto 发送的 Webhook 请求是否合法的密钥。 |
|
|
76
76
|
|
|
77
77
|
<Callout type={'tip'}>
|
|
78
78
|
前往 [📘 环境变量](/zh/docs/self-hosting/environment-variables/auth#logto) 可查阅相关变量详情。
|
|
@@ -43,9 +43,9 @@ id=displayName<maxToken:vision:reasoning:fc:file>
|
|
|
43
43
|
|
|
44
44
|
目前支持的扩展能力有：
|
|
45
45
|
|
|
46
|
-
| --- | 描述
|
|
47
|
-
| ----------- |
|
|
48
|
-
| `fc` | 函数调用（function calling）
|
|
49
|
-
| `vision` | 视觉识别
|
|
50
|
-
| `reasoning` | 支持推理
|
|
51
|
-
| `file` | 文件上传（比较 hack，不建议日常使用）
|
|
46
|
+
| --- | 描述 |
|
|
47
|
+
| ----------- | ---------------------- |
|
|
48
|
+
| `fc` | 函数调用（function calling） |
|
|
49
|
+
| `vision` | 视觉识别 |
|
|
50
|
+
| `reasoning` | 支持推理 |
|
|
51
|
+
| `file` | 文件上传（比较 hack，不建议日常使用） |
|
|
@@ -0,0 +1,70 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: LobeChat 的可观测性和追踪
|
|
3
|
+
description: 使用 Langfuse 为你的 LobeChat 应用增强开源可观测性和追踪功能。自动捕获每个请求的详细追踪和指标，以优化和调试你的对话。
|
|
4
|
+
tags:
|
|
5
|
+
- 可观测性
|
|
6
|
+
- 追踪
|
|
7
|
+
- Langfuse
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
# 使用 Langfuse 监控你的 LobeChat 应用
|
|
11
|
+
|
|
12
|
+
## 什么是 Langfuse？
|
|
13
|
+
|
|
14
|
+
[Langfuse](https://langfuse.com/) 是一个 **开源的 LLM 可观测性平台**。启用 Langfuse 集成后，你可以追踪应用数据，以开发、监控和优化 LobeChat 的使用，包括：
|
|
15
|
+
|
|
16
|
+
- 应用 [追踪](https://langfuse.com/docs/tracing)
|
|
17
|
+
- 使用模式
|
|
18
|
+
- 按用户和模型的成本数据
|
|
19
|
+
- [评估](https://langfuse.com/docs/scores/overview)
|
|
20
|
+
|
|
21
|
+
## 快速开始
|
|
22
|
+
|
|
23
|
+
<Steps>
|
|
24
|
+
### 设置 Langfuse
|
|
25
|
+
|
|
26
|
+
通过注册 [Langfuse Cloud](https://cloud.langfuse.com) 或 [自托管](https://langfuse.com/docs/deployment/self-host) Langfuse 来获取你的 Langfuse API 密钥。
|
|
27
|
+
|
|
28
|
+
### 设置 LobeChat
|
|
29
|
+
|
|
30
|
+
有多种方式可以 [自托管 LobeChat](https://lobehub.com/docs/self-hosting/start)。在本示例中，我们将使用 Docker Desktop 部署。
|
|
31
|
+
|
|
32
|
+
<Tabs items={["环境变量", "Docker Desktop 示例"]}>
|
|
33
|
+
<Tab>
|
|
34
|
+
在部署 LobeChat 之前，使用你在上一步创建的 Langfuse API 密钥设置以下四个环境变量。
|
|
35
|
+
|
|
36
|
+
```sh
|
|
37
|
+
ENABLE_LANGFUSE = '1'
|
|
38
|
+
LANGFUSE_SECRET_KEY = 'sk-lf...'
|
|
39
|
+
LANGFUSE_PUBLIC_KEY = 'pk-lf...'
|
|
40
|
+
LANGFUSE_HOST = 'https://cloud.langfuse.com'
|
|
41
|
+
```
|
|
42
|
+
</Tab>
|
|
43
|
+
|
|
44
|
+
<Tab>
|
|
45
|
+
在运行 Docker 容器之前，在 Docker Desktop 中设置环境变量，并填入你在上一步创建的 Langfuse API 密钥。
|
|
46
|
+
|
|
47
|
+
<Image alt={'Docker Desktop 中的环境变量'} src={'https://langfuse.com/images/docs/lobechat-docker-desktop-env.png'} />
|
|
48
|
+
</Tab>
|
|
49
|
+
</Tabs>
|
|
50
|
+
|
|
51
|
+
### 在设置中启用分析功能
|
|
52
|
+
|
|
53
|
+
当 LobeChat 运行后，进入 **设置** 中的 **关于** 选项卡，并启用分析功能。这是将追踪数据发送到 Langfuse 所必需的。
|
|
54
|
+
|
|
55
|
+
<Image alt={'LobeChat 设置'} src={'https://langfuse.com/images/docs/lobechat-settings.png'} />
|
|
56
|
+
|
|
57
|
+
### 在 Langfuse 中查看聊天追踪
|
|
58
|
+
|
|
59
|
+
设置好 LLM 模型密钥后，你就可以开始与 LobeChat 进行交互。
|
|
60
|
+
|
|
61
|
+
<Image alt={'LobeChat 对话'} src={'https://langfuse.com/images/docs/lobechat-converstation.png'} />
|
|
62
|
+
|
|
63
|
+
所有对话都会被自动追踪并发送到 Langfuse。你可以在 Langfuse UI 的 [追踪部分](https://langfuse.com/docs/tracing) 查看这些数据。
|
|
64
|
+
|
|
65
|
+
<Image alt={'LobeChat Trace 示例'} src={'https://langfuse.com/images/docs/lobechat-example-trace.png'} />
|
|
66
|
+
</Steps>
|
|
67
|
+
|
|
68
|
+
## 反馈
|
|
69
|
+
|
|
70
|
+
如果你有任何反馈或需求，请在 GitHub 上创建 [Issue](https://langfuse.com/issue)，或在 [Discord](https://discord.langfuse.com/) 上与 Langfuse 社区分享你的想法。
|
|
@@ -23,11 +23,11 @@ LobeChat provides a complete authentication service capability when deployed. Th
|
|
|
23
23
|
|
|
24
24
|
- Changes after v1.52.0.
|
|
25
25
|
|
|
26
|
-
- For users who deploy with Vercel using Next Auth, it is necessary to add the environment variable
|
|
27
|
-
- For users who use Clerk in their self-built image, it is necessary to configure the environment variable NEXT_PUBLIC_ENABLE_NEXT_AUTH=0 to disable Next Auth.\n
|
|
28
|
-
- Other standard deployment scenarios (using Clerk on Vercel and next-auth in Docker) are not affected
|
|
26
|
+
- For users who deploy with Vercel using Next Auth, it is necessary to add the environment variable NEXT\_PUBLIC\_ENABLE\_NEXT\_AUTH=1 to ensure that Next Auth is enabled.
|
|
29
27
|
|
|
28
|
+
- For users who use Clerk in their self-built image, it is necessary to configure the environment variable NEXT\_PUBLIC\_ENABLE\_NEXT\_AUTH=0 to disable Next Auth.\n
|
|
30
29
|
|
|
30
|
+
- Other standard deployment scenarios (using Clerk on Vercel and next-auth in Docker) are not affected
|
|
31
31
|
|
|
32
32
|
#### `NEXT_AUTH_SECRET`
|
|
33
33
|
|
|
@@ -18,9 +18,10 @@ LobeChat 在部署时提供了完善的身份验证服务能力，以下是相
|
|
|
18
18
|
### 通用设置
|
|
19
19
|
|
|
20
20
|
#### `NEXT_PUBLIC_ENABLE_NEXT_AUTH`
|
|
21
|
+
|
|
21
22
|
- v1.52.0 之后有变更
|
|
22
|
-
- 针对使用 Vercel 部署中使用 next-auth 的用户，需要额外添加
|
|
23
|
-
- 针对使用自构建镜像中使用 clerk 的用户，需要额外配置
|
|
23
|
+
- 针对使用 Vercel 部署中使用 next-auth 的用户，需要额外添加 NEXT\_PUBLIC\_ENABLE\_NEXT\_AUTH=1 环境变量来确保开启 Next Auth
|
|
24
|
+
- 针对使用自构建镜像中使用 clerk 的用户，需要额外配置 NEXT\_PUBLIC\_ENABLE\_NEXT\_AUTH=0 环境变量来关闭 Next Auth
|
|
24
25
|
- 其他标准部署场景（Vercel 中使用 Clerk 与 Docker 中使用 next-auth ）不受影响
|
|
25
26
|
|
|
26
27
|
#### `NEXT_AUTH_SECRET`
|
|
@@ -37,7 +37,7 @@ To install aaPanel, go to the [aaPanel](https://www.aapanel.com/new/download.htm
|
|
|
37
37
|
6. After submission, the panel will automatically initialize the application, which will take about `1-3` minutes. It can be accessed after the initialization is completed.
|
|
38
38
|
|
|
39
39
|
<Callout type="warning">
|
|
40
|
-
⚠️ Do not enable any form of cache in the reverse proxy settings of the panel to avoid affecting the normal operation of the service. Read more at https://github.com/lobehub/lobe-chat/discussions/5986
|
|
40
|
+
⚠️ Do not enable any form of cache in the reverse proxy settings of the panel to avoid affecting the normal operation of the service. Read more at [https://github.com/lobehub/lobe-chat/discussions/5986](https://github.com/lobehub/lobe-chat/discussions/5986)
|
|
41
41
|
</Callout>
|
|
42
42
|
|
|
43
43
|
## Visit LobeChat
|
|
@@ -41,7 +41,7 @@ tags:
|
|
|
41
41
|
5. 提交后面板会自动进行应用初始化，大概需要`1-3`分钟，初始化完成后即可访问。
|
|
42
42
|
|
|
43
43
|
<Callout type="warning">
|
|
44
|
-
⚠️ 请不要在面板的反向代理设置中开启任何形式的缓存，以免影响服务的正常运行。详情请见 https://github.com/lobehub/lobe-chat/discussions/5986
|
|
44
|
+
⚠️ 请不要在面板的反向代理设置中开启任何形式的缓存，以免影响服务的正常运行。详情请见 [https://github.com/lobehub/lobe-chat/discussions/5986](https://github.com/lobehub/lobe-chat/discussions/5986)
|
|
45
45
|
</Callout>
|
|
46
46
|
|
|
47
47
|
## 访问 LobeChat
|
|
@@ -1,6 +1,9 @@
|
|
|
1
1
|
---
|
|
2
2
|
title: Deploy LobeChat on TencentCloud Lighthouse
|
|
3
|
-
description:
|
|
3
|
+
description: >-
|
|
4
|
+
Learn how to deploy the LobeChat application on TencentCloud Lighthouse,
|
|
5
|
+
including preparing the large model API Key, clicking the deploy button, and
|
|
6
|
+
other operations.
|
|
4
7
|
tags:
|
|
5
8
|
- TencentCloud Lighthouse
|
|
6
9
|
- TencentCloud
|
|
@@ -15,18 +18,15 @@ If you want to deploy LobeChat on TencentCloud Lighthouse, you can follow the st
|
|
|
15
18
|
## Tencent Cloud Deployment Process
|
|
16
19
|
|
|
17
20
|
<Steps>
|
|
21
|
+
### Prepare your API Key
|
|
18
22
|
|
|
19
|
-
|
|
23
|
+
Go to [OpenAI API Key](https://platform.openai.com/account/api-keys) to get your OpenAI API Key.
|
|
20
24
|
|
|
21
|
-
|
|
25
|
+
### One-click to deploy
|
|
22
26
|
|
|
27
|
+
[![][deploy-button-image]][deploy-link]
|
|
23
28
|
|
|
24
|
-
###
|
|
25
|
-
|
|
26
|
-
[![][deploy-button-image]][deploy-link]
|
|
27
|
-
|
|
28
|
-
### Once deployed, you can start using it
|
|
29
|
-
|
|
29
|
+
### Once deployed, you can start using it
|
|
30
30
|
</Steps>
|
|
31
31
|
|
|
32
32
|
[deploy-button-image]: https://cloudcache.tencent-cloud.com/qcloud/ui/static/static_source_business/d65fb782-4fb0-4348-ad85-f2943d6bee8f.svg
|
|
@@ -16,18 +16,16 @@ tags:
|
|
|
16
16
|
## 腾讯轻量云 部署流程
|
|
17
17
|
|
|
18
18
|
<Steps>
|
|
19
|
+
### 准备好你的 API Key
|
|
19
20
|
|
|
20
|
-
|
|
21
|
+
前往 [OpenAI API Key](https://platform.openai.com/account/api-keys) 获取你的 OpenAI API Key
|
|
21
22
|
|
|
22
|
-
|
|
23
|
+
### 点击下方按钮进行部署
|
|
23
24
|
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
[![][deploy-button-image]][deploy-link]
|
|
27
|
-
|
|
28
|
-
### 部署完毕后，即可开始使用
|
|
25
|
+
[![][deploy-button-image]][deploy-link]
|
|
29
26
|
|
|
27
|
+
### 部署完毕后，即可开始使用
|
|
30
28
|
</Steps>
|
|
31
29
|
|
|
32
30
|
[deploy-button-image]: https://cloudcache.tencent-cloud.com/qcloud/ui/static/static_source_business/d65fb782-4fb0-4348-ad85-f2943d6bee8f.svg
|
|
33
|
-
[deploy-link]: https://buy.cloud.tencent.com/lighthouse?blueprintType=APP_OS&
|
|
31
|
+
[deploy-link]: https://buy.cloud.tencent.com/lighthouse?blueprintType=APP_OS&blueprintOfficialId=lhbp-6u0ti132®ionId=8&zone=ap-beijing-3&bundleId=bundle_starter_mc_med2_01&loginSet=AUTO&rule=true&from=lobechat
|
|
@@ -95,7 +95,7 @@ Since we support file-based conversations/knowledge base conversations, we need
|
|
|
95
95
|
|
|
96
96
|
<Callout type={'info'}>
|
|
97
97
|
You can generate a random 32-character string as the value of `KEY_VAULTS_SECRET` using `openssl
|
|
98
|
-
|
|
98
|
+
rand -base64 32`.
|
|
99
99
|
</Callout>
|
|
100
100
|
</Steps>
|
|
101
101
|
|
|
@@ -35,6 +35,7 @@ This article will guide you on how to use Wenxin Qianfan in LobeChat.
|
|
|
35
35
|
- Copy the `API Key` and keep it safe
|
|
36
36
|
|
|
37
37
|
<Image alt={'Create API Key'} inStep src={'https://github.com/user-attachments/assets/6d068fe0-8100-4b43-b0c3-7934f54e688f'} />
|
|
38
|
+
|
|
38
39
|
<Image alt={'Copy API Key'} inStep src={'https://github.com/user-attachments/assets/629adf4e-e9e1-40dc-b9e5-d7b908878170'} />
|
|
39
40
|
|
|
40
41
|
### Step 2: Configure Wenxin Qianfan in LobeChat
|
|
@@ -33,6 +33,7 @@ tags:
|
|
|
33
33
|
- 复制 `API Key` 并妥善保存
|
|
34
34
|
|
|
35
35
|
<Image alt={'创建密钥'} inStep src={'https://github.com/user-attachments/assets/6d068fe0-8100-4b43-b0c3-7934f54e688f'} />
|
|
36
|
+
|
|
36
37
|
<Image alt={'复制密钥'} inStep src={'https://github.com/user-attachments/assets/629adf4e-e9e1-40dc-b9e5-d7b908878170'} />
|
|
37
38
|
|
|
38
39
|
### 步骤二：在 LobeChat 中配置文心千帆
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lobehub/chat",
|
|
3
|
-
"version": "1.55.
|
|
3
|
+
"version": "1.55.2",
|
|
4
4
|
"description": "Lobe Chat - an open-source, high-performance chatbot framework that supports speech synthesis, multimodal, and extensible Function Call plugin system. Supports one-click free deployment of your private ChatGPT/LLM web application.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"framework",
|
|
@@ -27,7 +27,11 @@ export const AssistantMessage = memo<
|
|
|
27
27
|
|
|
28
28
|
const isReasoning = useChatStore(aiChatSelectors.isMessageInReasoning(id));
|
|
29
29
|
|
|
30
|
-
|
|
30
|
+
// remove \n to avoid empty content
|
|
31
|
+
// refs: https://github.com/lobehub/lobe-chat/pull/6153
|
|
32
|
+
const showReasoning =
|
|
33
|
+
(!!props.reasoning && props.reasoning.content?.trim() !== '') ||
|
|
34
|
+
(!props.reasoning && isReasoning);
|
|
31
35
|
|
|
32
36
|
return editing ? (
|
|
33
37
|
<DefaultMessage
|