@lobehub/chat 0.147.0 → 0.147.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 +50 -0
- package/README.md +8 -8
- package/README.zh-CN.md +8 -8
- package/docs/self-hosting/advanced/analytics.mdx +1 -0
- package/docs/self-hosting/advanced/analytics.zh-CN.mdx +1 -0
- package/docs/self-hosting/advanced/authentication.mdx +7 -6
- package/docs/self-hosting/advanced/authentication.zh-CN.mdx +7 -6
- package/docs/self-hosting/advanced/sso-providers/auth0.mdx +58 -32
- package/docs/self-hosting/advanced/sso-providers/auth0.zh-CN.mdx +60 -32
- package/docs/self-hosting/advanced/sso-providers/authentik.mdx +33 -29
- package/docs/self-hosting/advanced/sso-providers/authentik.zh-CN.mdx +30 -27
- package/docs/self-hosting/advanced/sso-providers/github.mdx +49 -20
- package/docs/self-hosting/advanced/sso-providers/github.zh-CN.mdx +57 -31
- package/docs/self-hosting/advanced/sso-providers/microsoft-entra-id.mdx +53 -35
- package/docs/self-hosting/advanced/sso-providers/microsoft-entra-id.zh-CN.mdx +43 -31
- package/docs/self-hosting/advanced/sso-providers/zitadel.mdx +64 -34
- package/docs/self-hosting/advanced/sso-providers/zitadel.zh-CN.mdx +62 -36
- package/docs/self-hosting/advanced/upstream-sync.mdx +32 -23
- package/docs/self-hosting/advanced/upstream-sync.zh-CN.mdx +32 -23
- package/docs/self-hosting/environment-variables/analytics.mdx +1 -0
- package/docs/self-hosting/environment-variables/analytics.zh-CN.mdx +1 -0
- package/docs/self-hosting/environment-variables/auth.mdx +1 -0
- package/docs/self-hosting/environment-variables/auth.zh-CN.mdx +1 -0
- package/docs/self-hosting/environment-variables/basic.mdx +1 -0
- package/docs/self-hosting/environment-variables/basic.zh-CN.mdx +1 -0
- package/docs/self-hosting/environment-variables/model-provider.mdx +1 -0
- package/docs/self-hosting/environment-variables/model-provider.zh-CN.mdx +1 -0
- package/docs/self-hosting/environment-variables.mdx +1 -0
- package/docs/self-hosting/environment-variables.zh-CN.mdx +1 -0
- package/docs/self-hosting/examples/azure-openai.mdx +12 -8
- package/docs/self-hosting/examples/azure-openai.zh-CN.mdx +12 -8
- package/docs/self-hosting/examples/ollama.mdx +1 -0
- package/docs/self-hosting/examples/ollama.zh-CN.mdx +1 -0
- package/docs/self-hosting/faq/no-v1-suffix.mdx +1 -0
- package/docs/self-hosting/faq/no-v1-suffix.zh-CN.mdx +1 -0
- package/docs/self-hosting/faq/proxy-with-unable-to-verify-leaf-signature.mdx +1 -0
- package/docs/self-hosting/faq/proxy-with-unable-to-verify-leaf-signature.zh-CN.mdx +1 -0
- package/docs/self-hosting/platform/docker-compose.mdx +80 -73
- package/docs/self-hosting/platform/docker-compose.zh-CN.mdx +79 -73
- package/docs/self-hosting/platform/docker.mdx +85 -85
- package/docs/self-hosting/platform/docker.zh-CN.mdx +84 -85
- package/docs/self-hosting/platform/netlify.mdx +91 -42
- package/docs/self-hosting/platform/netlify.zh-CN.mdx +88 -38
- package/docs/self-hosting/platform/railway.mdx +8 -6
- package/docs/self-hosting/platform/railway.zh-CN.mdx +8 -6
- package/docs/self-hosting/platform/repocloud.mdx +8 -6
- package/docs/self-hosting/platform/repocloud.zh-CN.mdx +8 -6
- package/docs/self-hosting/platform/sealos.mdx +8 -6
- package/docs/self-hosting/platform/sealos.zh-CN.mdx +8 -6
- package/docs/self-hosting/platform/vercel.mdx +9 -7
- package/docs/self-hosting/platform/vercel.zh-CN.mdx +9 -7
- package/docs/self-hosting/platform/zeabur.mdx +8 -6
- package/docs/self-hosting/platform/zeabur.zh-CN.mdx +8 -6
- package/docs/self-hosting/start.mdx +11 -1
- package/docs/self-hosting/start.zh-CN.mdx +2 -1
- package/docs/usage/agents/concepts.mdx +13 -2
- package/docs/usage/agents/concepts.zh-CN.mdx +13 -2
- package/docs/usage/agents/custom-agent.mdx +9 -2
- package/docs/usage/agents/custom-agent.zh-CN.mdx +8 -4
- package/docs/usage/agents/model.mdx +3 -3
- package/docs/usage/agents/model.zh-CN.mdx +6 -5
- package/docs/usage/agents/prompt.mdx +7 -5
- package/docs/usage/agents/prompt.zh-CN.mdx +7 -5
- package/docs/usage/agents/topics.mdx +9 -1
- package/docs/usage/agents/topics.zh-CN.mdx +9 -1
- package/docs/usage/features/agent-market.mdx +5 -5
- package/docs/usage/features/agent-market.zh-CN.mdx +1 -0
- package/docs/usage/features/local-llm.mdx +6 -1
- package/docs/usage/features/local-llm.zh-CN.mdx +6 -1
- package/docs/usage/features/mobile.mdx +5 -1
- package/docs/usage/features/mobile.zh-CN.mdx +6 -1
- package/docs/usage/features/more.mdx +1 -0
- package/docs/usage/features/more.zh-CN.mdx +1 -0
- package/docs/usage/features/multi-ai-providers.mdx +11 -2
- package/docs/usage/features/multi-ai-providers.zh-CN.mdx +12 -2
- package/docs/usage/features/plugin-system.mdx +8 -7
- package/docs/usage/features/plugin-system.zh-CN.mdx +9 -7
- package/docs/usage/features/pwa.mdx +10 -4
- package/docs/usage/features/pwa.zh-CN.mdx +11 -4
- package/docs/usage/features/text-to-image.zh-CN.mdx +1 -0
- package/docs/usage/features/theme.mdx +6 -1
- package/docs/usage/features/theme.zh-CN.mdx +7 -1
- package/docs/usage/features/tts.zh-CN.mdx +1 -0
- package/docs/usage/features/vision.zh-CN.mdx +1 -0
- package/docs/usage/plugins/basic-usage.mdx +31 -7
- package/docs/usage/plugins/basic-usage.zh-CN.mdx +31 -7
- package/docs/usage/plugins/custom-plugin.mdx +1 -0
- package/docs/usage/plugins/custom-plugin.zh-CN.mdx +1 -0
- package/docs/usage/plugins/development.mdx +79 -30
- package/docs/usage/plugins/development.zh-CN.mdx +80 -31
- package/docs/usage/plugins/store.mdx +11 -2
- package/docs/usage/plugins/store.zh-CN.mdx +11 -2
- package/docs/usage/providers/groq.mdx +32 -12
- package/docs/usage/providers/groq.zh-CN.mdx +30 -12
- package/docs/usage/providers/ollama/gemma.mdx +27 -11
- package/docs/usage/providers/ollama/gemma.zh-CN.mdx +28 -11
- package/docs/usage/providers/ollama/qwen.mdx +30 -16
- package/docs/usage/providers/ollama/qwen.zh-CN.mdx +25 -11
- package/docs/usage/providers/ollama.mdx +27 -14
- package/docs/usage/providers/ollama.zh-CN.mdx +27 -14
- package/package.json +1 -1
- package/src/app/settings/llm/Azure/index.tsx +1 -1
- package/src/app/settings/llm/components/ProviderConfig/index.tsx +1 -1
- package/src/app/settings/llm/components/ProviderModelList/CustomModelOption.tsx +1 -1
- package/src/app/settings/llm/components/ProviderModelList/ModelConfigModal.tsx +1 -1
- package/src/app/settings/llm/components/ProviderModelList/ModelFetcher.tsx +3 -3
- package/src/app/settings/llm/components/ProviderModelList/index.tsx +2 -2
- package/src/features/AgentSetting/AgentConfig/ModelSelect.tsx +1 -1
- package/src/features/Conversation/Error/APIKeyForm/ProviderApiKeyForm.tsx +2 -2
- package/src/features/ModelSwitchPanel/index.tsx +1 -1
- package/src/locales/resources.test.ts +49 -0
- package/src/locales/resources.ts +7 -20
- package/src/services/_auth.ts +5 -3
- package/src/services/_header.ts +3 -4
- package/src/services/chat.ts +1 -1
- package/src/services/ollama.ts +3 -2
- package/src/store/global/slices/settings/actions/llm.test.ts +1 -1
- package/src/store/global/slices/settings/actions/llm.ts +2 -2
- package/src/store/global/slices/settings/selectors/modelConfig.test.ts +35 -14
- package/src/store/global/slices/settings/selectors/modelConfig.ts +55 -118
|
@@ -10,6 +10,7 @@ tags:
|
|
|
10
10
|
- OpenAI API Key
|
|
11
11
|
- 环境配置
|
|
12
12
|
---
|
|
13
|
+
|
|
13
14
|
# 使用 Netlify 部署
|
|
14
15
|
|
|
15
16
|
如果想在 Netlify 上部署 LobeChat,可以按照以下步骤进行操作:
|
|
@@ -19,76 +20,125 @@ tags:
|
|
|
19
20
|
<Steps>
|
|
20
21
|
### Fork LobeChat 仓库
|
|
21
22
|
|
|
22
|
-
|
|
23
|
+
点击 Fork 按钮,将 LobeChat 仓库 Fork 到你的 GitHub 账号下。
|
|
23
24
|
|
|
24
|
-
|
|
25
|
+
### 准备好你的 OpenAI API Key
|
|
25
26
|
|
|
26
|
-
|
|
27
|
+
前往 [OpenAI API Key](https://platform.openai.com/account/api-keys) 获取你的 OpenAI API Key
|
|
27
28
|
|
|
28
|
-
|
|
29
|
+
### 在 Netlify 工作台导入
|
|
29
30
|
|
|
30
|
-
|
|
31
|
+
<Callout>经过测试,暂不支持类似 Vercel/Zeabur 的一键部署按钮,原因未知。因此需要手动导入</Callout>
|
|
31
32
|
|
|
32
|
-
|
|
33
|
+
点击 「Import from git」
|
|
33
34
|
|
|
34
|
-
|
|
35
|
+
<Image
|
|
36
|
+
alt={'在 Netflix 工作台点击 「Import from git」'}
|
|
37
|
+
height={362}
|
|
38
|
+
inStep
|
|
39
|
+
src={'https://github.com/lobehub/lobe-chat/assets/28616219/31b999e5-2a74-45fc-935b-f036e72a684d'}
|
|
40
|
+
/>
|
|
35
41
|
|
|
36
|
-
|
|
42
|
+
然后点击 「Deploy with Github」,并授权 Netlify 访问你的 GitHub 账号
|
|
37
43
|
|
|
38
|
-
|
|
44
|
+
<Image
|
|
45
|
+
alt={'授权 Netlify 访问你的 GitHub 账号'}
|
|
46
|
+
height={273}
|
|
47
|
+
inStep
|
|
48
|
+
src={'https://github.com/lobehub/lobe-chat/assets/28616219/c9c58141-5ec6-43f1-8d97-0a84a04dcdba'}
|
|
49
|
+
/>
|
|
39
50
|
|
|
40
|
-
|
|
51
|
+
然后选择 LobeChat 项目:
|
|
41
52
|
|
|
42
|
-
|
|
53
|
+
<Image
|
|
54
|
+
alt={'选择 LobeChat github 项目'}
|
|
55
|
+
height={228}
|
|
56
|
+
inStep
|
|
57
|
+
src={'https://github.com/lobehub/lobe-chat/assets/28616219/6c3968a8-fbbb-4268-a587-edaced2d96af'}
|
|
58
|
+
/>
|
|
43
59
|
|
|
44
|
-
|
|
60
|
+
### 配置站点名称与环境变量
|
|
45
61
|
|
|
46
|
-
|
|
62
|
+
在这一步,你需要配置你的站点,包括站点名称、构建命令、发布目录等。在「Site Name」字段填写上你的站点名称。其余配置如果没有特殊要求,无需修改,我们已经设定好了默认配置。
|
|
47
63
|
|
|
48
|
-
|
|
64
|
+
<Image
|
|
65
|
+
alt={'配置 LobeChat 站点名称'}
|
|
66
|
+
height={712}
|
|
67
|
+
inStep
|
|
68
|
+
src={'https://github.com/lobehub/lobe-chat/assets/28616219/f3885537-6d43-422f-b1b8-e70732401025'}
|
|
69
|
+
/>
|
|
49
70
|
|
|
50
|
-
|
|
71
|
+
点击 「Add environment variables」按钮,添加站点环境变量:
|
|
51
72
|
|
|
52
|
-
|
|
73
|
+
<Image
|
|
74
|
+
alt={'添加 LobeChat 站点环境变量'}
|
|
75
|
+
height={537}
|
|
76
|
+
inStep
|
|
77
|
+
src={'https://github.com/lobehub/lobe-chat/assets/28616219/3b607482-4d99-455a-bc10-3090dd4fe3c5'}
|
|
78
|
+
/>
|
|
53
79
|
|
|
54
|
-
|
|
80
|
+
以配置 OpenAI 为例,你需要添加的环境变量如下:
|
|
55
81
|
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
82
|
+
| 环境变量 | 类型 | 描述 | 示例 |
|
|
83
|
+
| --- | --- | --- | --- |
|
|
84
|
+
| `OPENAI_API_KEY` | 必选 | 这是你在 OpenAI 账户页面申请的 API 密钥 | `sk-xxxxxx...xxxxxx` |
|
|
85
|
+
| `ACCESS_CODE` | 必选 | 添加访问此服务的密码,你可以设置一个长密码以防被爆破,该值用逗号分隔时为密码数组 | `awCT74` 或 `e3@09!` or `code1,code2,code3` |
|
|
86
|
+
| `OPENAI_PROXY_URL` | 可选 | 如果你手动配置了 OpenAI 接口代理,可以使用此配置项来覆盖默认的 OpenAI API 请求基础 URL | `https://aihubmix.com/v1` ,默认值:`https://api.openai.com/v1` |
|
|
61
87
|
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
88
|
+
<Callout type={'tip'}>
|
|
89
|
+
LobeChat 支持的完整环境变量列表请参考 [📘 环境变量](/zh/self-hosting/environment-variables) 部分
|
|
65
90
|
</Callout>
|
|
66
91
|
|
|
67
|
-
|
|
92
|
+
添加完成后,最后点击「Deploy lobe-chat」 进入部署阶段。
|
|
68
93
|
|
|
69
|
-
|
|
94
|
+
<Image
|
|
95
|
+
alt={'环境变量添加完成'}
|
|
96
|
+
height={600}
|
|
97
|
+
inStep
|
|
98
|
+
src={'https://github.com/lobehub/lobe-chat/assets/28616219/c9f74ec4-ce63-4ce9-b9e2-34bda6fda10b'}
|
|
99
|
+
/>
|
|
70
100
|
|
|
71
|
-
|
|
101
|
+
### 等待部署完成
|
|
72
102
|
|
|
73
|
-
|
|
103
|
+
点击部署后,会进入站点详情页面,你可以点击青色字样的「Deploying your site」或者 「Building」 黄色标签查看部署进度。
|
|
74
104
|
|
|
75
|
-
|
|
105
|
+
<Image
|
|
106
|
+
alt={'Netlify 站点详情页'}
|
|
107
|
+
height={396}
|
|
108
|
+
inStep
|
|
109
|
+
src={'https://github.com/lobehub/lobe-chat/assets/28616219/a7fd85d5-fd32-4756-814e-ff7ab7567fe1'}
|
|
110
|
+
/>
|
|
76
111
|
|
|
77
|
-
|
|
112
|
+
进入部署详情,你会看到下述界面,这意味着你的 LobeChat 正在部署中,只需等待部署完成即可。
|
|
78
113
|
|
|
79
|
-
|
|
114
|
+
<Image
|
|
115
|
+
alt={'LobeChat 部署构建中'}
|
|
116
|
+
height={325}
|
|
117
|
+
inStep
|
|
118
|
+
src={'https://github.com/lobehub/lobe-chat/assets/28616219/1ed8b13d-046e-47c8-bd61-116ffdf5d01b'}
|
|
119
|
+
/>
|
|
80
120
|
|
|
81
|
-
|
|
121
|
+
部署构建过程中:
|
|
82
122
|
|
|
83
|
-
|
|
123
|
+
<Image
|
|
124
|
+
alt={'部署构建中'}
|
|
125
|
+
height={558}
|
|
126
|
+
inStep
|
|
127
|
+
src={'https://github.com/lobehub/lobe-chat/assets/28616219/1c82d707-cb6f-4924-b246-a5235a919864'}
|
|
128
|
+
/>
|
|
84
129
|
|
|
85
|
-
|
|
130
|
+
### 部署成功,开始使用
|
|
86
131
|
|
|
87
|
-
|
|
132
|
+
如果你的界面中的 Deploy Log 如下所示,意味着你的 LobeChat 部署成功了。
|
|
88
133
|
|
|
89
|
-
|
|
134
|
+
<Image
|
|
135
|
+
alt={'部署成功'}
|
|
136
|
+
height={558}
|
|
137
|
+
inStep
|
|
138
|
+
src={'https://github.com/lobehub/lobe-chat/assets/28616219/c1f945d1-f3e2-4100-b6bb-24d4cb13c438'}
|
|
139
|
+
/>
|
|
90
140
|
|
|
91
|
-
|
|
141
|
+
此时,你可以点击「Open production deploy」,即可访问你的 LobeChat 站点
|
|
92
142
|
|
|
93
143
|
<Image alt={'访问你的 LobeChat 站点'} height={527} inStep src={'https://github.com/lobehub/lobe-chat/assets/28616219/b04723eb-64ad-4028-a901-dc4e4ee2d0c1'} />
|
|
94
144
|
</Steps>
|
|
@@ -10,6 +10,7 @@ tags:
|
|
|
10
10
|
- OpenAI API Key
|
|
11
11
|
- Custom Domain Binding
|
|
12
12
|
---
|
|
13
|
+
|
|
13
14
|
# Deploy LobeChat with Railway
|
|
14
15
|
|
|
15
16
|
If you want to deploy LobeChat on Railway, you can follow the steps below:
|
|
@@ -19,15 +20,16 @@ If you want to deploy LobeChat on Railway, you can follow the steps below:
|
|
|
19
20
|
<Steps>
|
|
20
21
|
### Prepare your OpenAI API Key
|
|
21
22
|
|
|
22
|
-
|
|
23
|
+
Go to [OpenAI API Key](https://platform.openai.com/account/api-keys) to get your OpenAI API Key.
|
|
24
|
+
|
|
25
|
+
### Click the button below to deploy
|
|
23
26
|
|
|
24
|
-
|
|
27
|
+
[](https://railway.app/template/FB6HrV?referralCode=9bD9mT)
|
|
25
28
|
|
|
26
|
-
|
|
29
|
+
### Once deployed, you can start using it
|
|
27
30
|
|
|
28
|
-
|
|
31
|
+
### Bind a custom domain (optional)
|
|
29
32
|
|
|
30
|
-
|
|
33
|
+
You can use the subdomain provided by Railway, or choose to bind a custom domain. Currently, the domains provided by Railway have not been contaminated, and most regions can connect directly.
|
|
31
34
|
|
|
32
|
-
You can use the subdomain provided by Railway, or choose to bind a custom domain. Currently, the domains provided by Railway have not been contaminated, and most regions can connect directly.
|
|
33
35
|
</Steps>
|
|
@@ -9,6 +9,7 @@ tags:
|
|
|
9
9
|
- API Key
|
|
10
10
|
- 自定义域名
|
|
11
11
|
---
|
|
12
|
+
|
|
12
13
|
# 使用 Railway 部署
|
|
13
14
|
|
|
14
15
|
如果想在 Railway 上部署 LobeChat,可以按照以下步骤进行操作:
|
|
@@ -18,15 +19,16 @@ tags:
|
|
|
18
19
|
<Steps>
|
|
19
20
|
### 准备好你的 OpenAI API Key
|
|
20
21
|
|
|
21
|
-
|
|
22
|
+
前往 [OpenAI API Key](https://platform.openai.com/account/api-keys) 获取你的 OpenAI API Key
|
|
23
|
+
|
|
24
|
+
### 点击下方按钮进行部署
|
|
22
25
|
|
|
23
|
-
|
|
26
|
+
[](https://railway.app/template/FB6HrV?referralCode=9bD9mT)
|
|
24
27
|
|
|
25
|
-
|
|
28
|
+
### 部署完毕后,即可开始使用
|
|
26
29
|
|
|
27
|
-
|
|
30
|
+
### 绑定自定义域名(可选)
|
|
28
31
|
|
|
29
|
-
|
|
32
|
+
你可以使用 Railway 提供的子域名,也可以选择绑定自定义域名。目前 Railway 提供的域名还未被污染,大多数地区都可以直连。
|
|
30
33
|
|
|
31
|
-
你可以使用 Railway 提供的子域名,也可以选择绑定自定义域名。目前 Railway 提供的域名还未被污染,大多数地区都可以直连。
|
|
32
34
|
</Steps>
|
|
@@ -10,6 +10,7 @@ tags:
|
|
|
10
10
|
- OpenAI API Key
|
|
11
11
|
- Custom Domain Binding
|
|
12
12
|
---
|
|
13
|
+
|
|
13
14
|
# Deploy LobeChat with RepoCloud
|
|
14
15
|
|
|
15
16
|
If you want to deploy LobeChat on RepoCloud, you can follow the steps below:
|
|
@@ -19,17 +20,18 @@ If you want to deploy LobeChat on RepoCloud, you can follow the steps below:
|
|
|
19
20
|
<Steps>
|
|
20
21
|
### Prepare your OpenAI API Key
|
|
21
22
|
|
|
22
|
-
|
|
23
|
+
Go to [OpenAI API Key](https://platform.openai.com/account/api-keys) to get your OpenAI API Key.
|
|
24
|
+
|
|
25
|
+
### One-click to deploy
|
|
23
26
|
|
|
24
|
-
|
|
27
|
+
[![][deploy-button-image]][deploy-link]
|
|
25
28
|
|
|
26
|
-
|
|
29
|
+
### Once deployed, you can start using it
|
|
27
30
|
|
|
28
|
-
|
|
31
|
+
### Bind a custom domain (optional)
|
|
29
32
|
|
|
30
|
-
|
|
33
|
+
You can use the subdomain provided by RepoCloud, or choose to bind a custom domain. Currently, the domains provided by RepoCloud have not been contaminated, and most regions can connect directly.
|
|
31
34
|
|
|
32
|
-
You can use the subdomain provided by RepoCloud, or choose to bind a custom domain. Currently, the domains provided by RepoCloud have not been contaminated, and most regions can connect directly.
|
|
33
35
|
</Steps>
|
|
34
36
|
|
|
35
37
|
[deploy-button-image]: https://d16t0pc4846x52.cloudfront.net/deploy.svg
|
|
@@ -8,6 +8,7 @@ tags:
|
|
|
8
8
|
- OpenAI API Key
|
|
9
9
|
- 自定义域名
|
|
10
10
|
---
|
|
11
|
+
|
|
11
12
|
# 使用 RepoCloud 部署
|
|
12
13
|
|
|
13
14
|
如果想在 RepoCloud 上部署 LobeChat,可以按照以下步骤进行操作:
|
|
@@ -17,17 +18,18 @@ tags:
|
|
|
17
18
|
<Steps>
|
|
18
19
|
### 准备好你的 OpenAI API Key
|
|
19
20
|
|
|
20
|
-
|
|
21
|
+
前往 [OpenAI API Key](https://platform.openai.com/account/api-keys) 获取你的 OpenAI API Key
|
|
22
|
+
|
|
23
|
+
### 点击下方按钮进行部署
|
|
21
24
|
|
|
22
|
-
|
|
25
|
+
[![][deploy-button-image]][deploy-link]
|
|
23
26
|
|
|
24
|
-
|
|
27
|
+
### 部署完毕后,即可开始使用
|
|
25
28
|
|
|
26
|
-
|
|
29
|
+
### 绑定自定义域名(可选)
|
|
27
30
|
|
|
28
|
-
|
|
31
|
+
你可以使用 RepoCloud 提供的子域名,也可以选择绑定自定义域名。目前 RepoCloud 提供的域名还未被污染,大多数地区都可以直连。
|
|
29
32
|
|
|
30
|
-
你可以使用 RepoCloud 提供的子域名,也可以选择绑定自定义域名。目前 RepoCloud 提供的域名还未被污染,大多数地区都可以直连。
|
|
31
33
|
</Steps>
|
|
32
34
|
|
|
33
35
|
[deploy-button-image]: https://d16t0pc4846x52.cloudfront.net/deploy.svg
|
|
@@ -9,6 +9,7 @@ tags:
|
|
|
9
9
|
- OpenAI API Key
|
|
10
10
|
- Custom Domain Binding
|
|
11
11
|
---
|
|
12
|
+
|
|
12
13
|
# Deploy LobeChat with SealOS
|
|
13
14
|
|
|
14
15
|
If you want to deploy LobeChat on SealOS, you can follow the steps below:
|
|
@@ -18,17 +19,18 @@ If you want to deploy LobeChat on SealOS, you can follow the steps below:
|
|
|
18
19
|
<Steps>
|
|
19
20
|
### Prepare your OpenAI API Key
|
|
20
21
|
|
|
21
|
-
|
|
22
|
+
Go to [OpenAI](https://platform.openai.com/account/api-keys) to get your OpenAI API Key.
|
|
23
|
+
|
|
24
|
+
### Click the button below to deploy
|
|
22
25
|
|
|
23
|
-
|
|
26
|
+
[![][deploy-button-image]][deploy-link]
|
|
24
27
|
|
|
25
|
-
|
|
28
|
+
### After deployment, you can start using it
|
|
26
29
|
|
|
27
|
-
|
|
30
|
+
### Bind a custom domain (optional)
|
|
28
31
|
|
|
29
|
-
|
|
32
|
+
You can use the subdomain provided by SealOS, or choose to bind a custom domain. Currently, the domains provided by SealOS have not been contaminated, and can be directly accessed in most regions.
|
|
30
33
|
|
|
31
|
-
You can use the subdomain provided by SealOS, or choose to bind a custom domain. Currently, the domains provided by SealOS have not been contaminated, and can be directly accessed in most regions.
|
|
32
34
|
</Steps>
|
|
33
35
|
|
|
34
36
|
[deploy-button-image]: https://raw.githubusercontent.com/labring-actions/templates/main/Deploy-on-Sealos.svg
|
|
@@ -8,6 +8,7 @@ tags:
|
|
|
8
8
|
- 部署流程
|
|
9
9
|
- 自定义域名
|
|
10
10
|
---
|
|
11
|
+
|
|
11
12
|
# 使用 SealOS 部署
|
|
12
13
|
|
|
13
14
|
如果想在 SealOS 上部署 LobeChat,可以按照以下步骤进行操作:
|
|
@@ -17,17 +18,18 @@ tags:
|
|
|
17
18
|
<Steps>
|
|
18
19
|
### 准备好你的 OpenAI API Key
|
|
19
20
|
|
|
20
|
-
|
|
21
|
+
前往 [OpenAI](https://platform.openai.com/account/api-keys) 获取你的 OpenAI API Key
|
|
22
|
+
|
|
23
|
+
### 点击下方按钮进行部署
|
|
21
24
|
|
|
22
|
-
|
|
25
|
+
[![][deploy-button-image]][deploy-link]
|
|
23
26
|
|
|
24
|
-
|
|
27
|
+
### 部署完毕后,即可开始使用
|
|
25
28
|
|
|
26
|
-
|
|
29
|
+
### 绑定自定义域名(可选)
|
|
27
30
|
|
|
28
|
-
|
|
31
|
+
你可以使用 SealOS 提供的子域名,也可以选择绑定自定义域名。目前 SealOS 提供的域名还未被污染,大多数地区都可以直连。
|
|
29
32
|
|
|
30
|
-
你可以使用 SealOS 提供的子域名,也可以选择绑定自定义域名。目前 SealOS 提供的域名还未被污染,大多数地区都可以直连。
|
|
31
33
|
</Steps>
|
|
32
34
|
|
|
33
35
|
[deploy-button-image]: https://raw.githubusercontent.com/labring-actions/templates/main/Deploy-on-Sealos.svg
|
|
@@ -10,6 +10,7 @@ tags:
|
|
|
10
10
|
- OpenAI API Key
|
|
11
11
|
- Custom Domain Binding
|
|
12
12
|
---
|
|
13
|
+
|
|
13
14
|
# Deploy LobeChat with Vercel
|
|
14
15
|
|
|
15
16
|
If you want to deploy LobeChat on Vercel, you can follow the steps below:
|
|
@@ -19,19 +20,20 @@ If you want to deploy LobeChat on Vercel, you can follow the steps below:
|
|
|
19
20
|
<Steps>
|
|
20
21
|
### Prepare your OpenAI API Key
|
|
21
22
|
|
|
22
|
-
|
|
23
|
+
Go to [OpenAI API Key](https://platform.openai.com/account/api-keys) to get your OpenAI API Key.
|
|
24
|
+
|
|
25
|
+
### Click the button below to deploy
|
|
23
26
|
|
|
24
|
-
|
|
27
|
+
[![][deploy-button-image]][deploy-link]
|
|
25
28
|
|
|
26
|
-
|
|
29
|
+
Simply log in with your GitHub account, and remember to fill in `OPENAI_API_KEY` (required) and `ACCESS_CODE` (recommended) in the environment variables page.
|
|
27
30
|
|
|
28
|
-
|
|
31
|
+
### After deployment, you can start using it
|
|
29
32
|
|
|
30
|
-
|
|
33
|
+
### Bind a custom domain (optional)
|
|
31
34
|
|
|
32
|
-
|
|
35
|
+
Vercel's assigned domain DNS may be polluted in some regions, so binding a custom domain can establish a direct connection.
|
|
33
36
|
|
|
34
|
-
Vercel's assigned domain DNS may be polluted in some regions, so binding a custom domain can establish a direct connection.
|
|
35
37
|
</Steps>
|
|
36
38
|
|
|
37
39
|
## Automatic Synchronization of Updates
|
|
@@ -9,6 +9,7 @@ tags:
|
|
|
9
9
|
- 自定义域名
|
|
10
10
|
- 自动同步更新
|
|
11
11
|
---
|
|
12
|
+
|
|
12
13
|
# Vercel 部署指引
|
|
13
14
|
|
|
14
15
|
如果想在 Vercel 上部署 LobeChat,可以按照以下步骤进行操作:
|
|
@@ -18,19 +19,20 @@ tags:
|
|
|
18
19
|
<Steps>
|
|
19
20
|
### 准备好你的 OpenAI API Key
|
|
20
21
|
|
|
21
|
-
|
|
22
|
+
前往 [OpenAI API Key](https://platform.openai.com/account/api-keys) 获取你的 OpenAI API Key
|
|
23
|
+
|
|
24
|
+
### 点击下方按钮进行部署
|
|
22
25
|
|
|
23
|
-
|
|
26
|
+
[![][deploy-button-image]][deploy-link]
|
|
24
27
|
|
|
25
|
-
|
|
28
|
+
直接使用 GitHub 账号登录即可,记得在环境变量页填入 `OPENAI_API_KEY` (必填) and `ACCESS_CODE`(推荐);
|
|
26
29
|
|
|
27
|
-
|
|
30
|
+
### 部署完毕后,即可开始使用
|
|
28
31
|
|
|
29
|
-
|
|
32
|
+
### 绑定自定义域名(可选)
|
|
30
33
|
|
|
31
|
-
|
|
34
|
+
Vercel 分配的域名 DNS 在某些区域被污染了,绑定自定义域名即可直连。
|
|
32
35
|
|
|
33
|
-
Vercel 分配的域名 DNS 在某些区域被污染了,绑定自定义域名即可直连。
|
|
34
36
|
</Steps>
|
|
35
37
|
|
|
36
38
|
## 自动同步更新
|
|
@@ -9,6 +9,7 @@ tags:
|
|
|
9
9
|
- OpenAI API Key
|
|
10
10
|
- Custom Domain Binding
|
|
11
11
|
---
|
|
12
|
+
|
|
12
13
|
# Deploy LobeChat with Zeabur
|
|
13
14
|
|
|
14
15
|
If you want to deploy LobeChat on Zeabur, you can follow the steps below:
|
|
@@ -18,17 +19,18 @@ If you want to deploy LobeChat on Zeabur, you can follow the steps below:
|
|
|
18
19
|
<Steps>
|
|
19
20
|
### Prepare your OpenAI API Key
|
|
20
21
|
|
|
21
|
-
|
|
22
|
+
Go to [OpenAI API Key](https://platform.openai.com/account/api-keys) to get your OpenAI API Key.
|
|
23
|
+
|
|
24
|
+
### Click the button below to deploy
|
|
22
25
|
|
|
23
|
-
|
|
26
|
+
[![][deploy-button-image]][deploy-link]
|
|
24
27
|
|
|
25
|
-
|
|
28
|
+
### Once deployed, you can start using it
|
|
26
29
|
|
|
27
|
-
|
|
30
|
+
### Bind a custom domain (optional)
|
|
28
31
|
|
|
29
|
-
|
|
32
|
+
You can use the subdomain provided by Zeabur, or choose to bind a custom domain. Currently, the domains provided by Zeabur have not been contaminated, and most regions can connect directly.
|
|
30
33
|
|
|
31
|
-
You can use the subdomain provided by Zeabur, or choose to bind a custom domain. Currently, the domains provided by Zeabur have not been contaminated, and most regions can connect directly.
|
|
32
34
|
</Steps>
|
|
33
35
|
|
|
34
36
|
[deploy-button-image]: https://zeabur.com/button.svg
|
|
@@ -8,6 +8,7 @@ tags:
|
|
|
8
8
|
- 部署流程
|
|
9
9
|
- 自定义域名
|
|
10
10
|
---
|
|
11
|
+
|
|
11
12
|
# 使用 Zeabur 部署
|
|
12
13
|
|
|
13
14
|
如果想在 Zeabur 上部署 LobeChat,可以按照以下步骤进行操作:
|
|
@@ -17,17 +18,18 @@ tags:
|
|
|
17
18
|
<Steps>
|
|
18
19
|
### 准备好你的 OpenAI API Key
|
|
19
20
|
|
|
20
|
-
|
|
21
|
+
前往 [OpenAI API Key](https://platform.openai.com/account/api-keys) 获取你的 OpenAI API Key
|
|
22
|
+
|
|
23
|
+
### 点击下方按钮进行部署
|
|
21
24
|
|
|
22
|
-
|
|
25
|
+
[![][deploy-button-image]][deploy-link]
|
|
23
26
|
|
|
24
|
-
|
|
27
|
+
### 部署完毕后,即可开始使用
|
|
25
28
|
|
|
26
|
-
|
|
29
|
+
### 绑定自定义域名(可选)
|
|
27
30
|
|
|
28
|
-
|
|
31
|
+
你可以使用 Zeabur 提供的子域名,也可以选择绑定自定义域名。目前 Zeabur 提供的域名还未被污染,大多数地区都可以直连。
|
|
29
32
|
|
|
30
|
-
你可以使用 Zeabur 提供的子域名,也可以选择绑定自定义域名。目前 Zeabur 提供的域名还未被污染,大多数地区都可以直连。
|
|
31
33
|
</Steps>
|
|
32
34
|
|
|
33
35
|
[deploy-button-image]: https://zeabur.com/button.svg
|
|
@@ -10,6 +10,7 @@ tags:
|
|
|
10
10
|
- Docker
|
|
11
11
|
- Docker Compose
|
|
12
12
|
---
|
|
13
|
+
|
|
13
14
|
# Build your own Lobe Chat
|
|
14
15
|
|
|
15
16
|
Choose your favorite platform to get started.
|
|
@@ -18,4 +19,13 @@ Choose your favorite platform to get started.
|
|
|
18
19
|
|
|
19
20
|
LobeChat support multiple deployment platforms, including Vercel, Docker, and Docker Compose and so on, you can choose the deployment platform that suits you.
|
|
20
21
|
|
|
21
|
-
<PlatformCards
|
|
22
|
+
<PlatformCards
|
|
23
|
+
docker={'Docker'}
|
|
24
|
+
dockerCompose={'Docker Compose'}
|
|
25
|
+
netlify={'Netlify'}
|
|
26
|
+
railway={'Railway'}
|
|
27
|
+
repocloud={'RepoCloud'}
|
|
28
|
+
sealos={'SealOS'}
|
|
29
|
+
vercel={'Vercel'}
|
|
30
|
+
zeabur={'Zeabur'}
|
|
31
|
+
/>
|
|
@@ -11,6 +11,7 @@ tags:
|
|
|
11
11
|
- Vercel
|
|
12
12
|
- 个性化
|
|
13
13
|
---
|
|
14
|
+
|
|
14
15
|
# 构建属于自己的 Lobe Chat
|
|
15
16
|
|
|
16
17
|
选择自己喜爱的平台,构建属于自己的 Lobe Chat。
|
|
@@ -23,7 +24,7 @@ LobeChat 支持多种部署平台,包括 Vercel、Docker 和 Docker Compose
|
|
|
23
24
|
docker={'Docker 部署'}
|
|
24
25
|
dockerCompose={'Docker Compose 部署'}
|
|
25
26
|
netlify={'Netlify 部署'}
|
|
26
|
-
railway={'Railway 部署'}
|
|
27
|
+
railway={'Railway 部署'}
|
|
27
28
|
repocloud={'Repocloud 部署'}
|
|
28
29
|
sealos={'SealOS 部署'}
|
|
29
30
|
vercel={'Vercel 部署'}
|
|
@@ -11,13 +11,19 @@ tags:
|
|
|
11
11
|
- Task Handling
|
|
12
12
|
- Historical Conversations
|
|
13
13
|
---
|
|
14
|
+
|
|
14
15
|
# Topics and Assistants
|
|
15
16
|
|
|
16
17
|
## ChatGPT and "Topics"
|
|
17
18
|
|
|
18
19
|
In the official ChatGPT application, there is only the concept of "topics." As shown in the image, the user's historical conversation topics are listed in the sidebar.
|
|
19
20
|
|
|
20
|
-
<Image
|
|
21
|
+
<Image
|
|
22
|
+
alt={'ChatGPT and Topics'}
|
|
23
|
+
src={
|
|
24
|
+
'https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/279602474-fe7cb3f3-8eb7-40d3-a69f-6615393bbd4e.png'
|
|
25
|
+
}
|
|
26
|
+
/>
|
|
21
27
|
|
|
22
28
|
However, in our usage, we have found that this model has many issues. For example, the information indexing of historical conversations is too scattered. Additionally, when dealing with repetitive tasks, it is difficult to have a stable entry point. For instance, if I want ChatGPT to help me translate a document, in this model, I would need to constantly create new topics and then set up the translation prompt I had previously created. When there are high-frequency tasks, this will result in a very inefficient interaction format.
|
|
23
29
|
|
|
@@ -25,6 +31,11 @@ However, in our usage, we have found that this model has many issues. For exampl
|
|
|
25
31
|
|
|
26
32
|
Therefore, in LobeChat, we have introduced the concept of **Agents**. An agent is a complete functional module, each with its own responsibilities and tasks. Assistants can help you handle various tasks and provide professional advice and guidance.
|
|
27
33
|
|
|
28
|
-
<Image
|
|
34
|
+
<Image
|
|
35
|
+
alt={'Topics and Agent'}
|
|
36
|
+
src={
|
|
37
|
+
'https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/279602489-89893e61-2791-4083-9b57-ed80884ad58b.png'
|
|
38
|
+
}
|
|
39
|
+
/>
|
|
29
40
|
|
|
30
41
|
At the same time, we have integrated topics into each agent. The benefit of this approach is that each agent has an independent topic list. You can choose the corresponding agent based on the current task and quickly switch between historical conversation records. This method is more in line with users' habits in common chat software, improving interaction efficiency.
|
|
@@ -8,13 +8,19 @@ tags:
|
|
|
8
8
|
- 历史对话记录
|
|
9
9
|
- 信息索引
|
|
10
10
|
---
|
|
11
|
+
|
|
11
12
|
# 话题与助手
|
|
12
13
|
|
|
13
14
|
## ChatGPT 与「话题」
|
|
14
15
|
|
|
15
16
|
在 ChatGPT 官方应用中,只存在话题的概念,如图所示,在侧边栏中是用户的历史对话话题列表。
|
|
16
17
|
|
|
17
|
-
<Image
|
|
18
|
+
<Image
|
|
19
|
+
alt={'ChatGPT 与「话题」'}
|
|
20
|
+
src={
|
|
21
|
+
'https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/279602474-fe7cb3f3-8eb7-40d3-a69f-6615393bbd4e.png'
|
|
22
|
+
}
|
|
23
|
+
/>
|
|
18
24
|
|
|
19
25
|
但在我们的使用过程中其实会发现这种模式存在很多问题,比如历史对话的信息索引过于分散问题,同时当处理一些重复任务时很难有一个稳定的入口,比如我希望有一个稳定的入口可以让 ChatGPT 帮助我翻译文档,在这个模式下,我需要不断新建新的话题同时再设置我之前创建好的翻译 Prompt 设定,当有高频任务存在时,这将是一个效率很低的交互形式。
|
|
20
26
|
|
|
@@ -22,6 +28,11 @@ tags:
|
|
|
22
28
|
|
|
23
29
|
因此在 LobeChat 中,我们引入了 **助手** 的概念。助手是一个完整的功能模块,每个助手都有自己的职责和任务。助手可以帮助你处理各种任务,并提供专业的建议和指导。
|
|
24
30
|
|
|
25
|
-
<Image
|
|
31
|
+
<Image
|
|
32
|
+
alt={'「话题」与「助手」'}
|
|
33
|
+
src={
|
|
34
|
+
'https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/279602489-89893e61-2791-4083-9b57-ed80884ad58b.png'
|
|
35
|
+
}
|
|
36
|
+
/>
|
|
26
37
|
|
|
27
38
|
与此同时,我们将话题索引到每个助手内部。这样做的好处是,每个助手都有一个独立的话题列表,你可以根据当前任务选择对应的助手,并快速切换历史对话记录。这种方式更符合用户对常见聊天软件的使用习惯,提高了交互的效率。
|