mirror of
https://github.com/lobehub/lobehub
synced 2026-04-21 09:37:28 +00:00
feat: Update user guide & changelog (#11518)
* feat: Redesign doc
* chore: uopdate site
* chore: uopdate site
* chore: uopdate site
* chore: uopdate site
* chore: uopdate site
* feat: Uopdate content
* chore: New doc
* chore: Update content
* chore: Update content
* chore: add images
* chore: add images
* chore: add images
* chore: add images
* feat: Add more images
* feat: Add more images
* fix: Cannot reach end
* chore: Update content
* chore: Update content
* chore: Update content
* chore: Update content
* chore: Update content
* Revise README content and structure
Updated README to reflect changes in project description and removed outdated notes.
* Revise 'Getting Started' and TOC in README
Updated the 'Getting Started' section and modified the table of contents.
* chore: Update content
* Revise README structure and content
Updated the Getting Started section and removed the Table of Contents. Adjusted the Local Development instructions.
* Remove custom themes section from README
Removed section about custom themes from README.
* Update README.md
* Refine introduction and highlight cloud version
Updated wording for clarity and added recommendation for cloud version.
* chore: Update content
* chore: Update content
* chore: Update content
* chore: Update content
* chore: Update content
* chore: Update content
* chore: Update content
* fix: add missing translation
* 🔀 chore: Move README changes to feat/readme branch
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* fix: add missing translation
* chore: update cdn
* docs: add migration guide from v1.x local database to v2.x and update help sections
Signed-off-by: Innei <tukon479@gmail.com>
* fix: add missing translation
* fix: add missing images
* fix: add missing changelogs
* fix: add missing changelogs
* fix: add missing changelogs
* fix: add missing changelogs
* fix: add missing changelogs
* style: update cdn
---------
Signed-off-by: Innei <tukon479@gmail.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: canisminor1990 <i@canisminor.cc>
Co-authored-by: Innei <tukon479@gmail.com>
This commit is contained in:
René Wang
GitHub
parent
cd029eb45b
commit
3dfc86fd0f
485 changed files with 9118 additions and 9051 deletions
|
|
@ -30,6 +30,7 @@ config.overrides = [
|
|||
files: ['*.mdx'],
|
||||
rules: {
|
||||
'@typescript-eslint/no-unused-vars': 1,
|
||||
'micromark-extension-mdx-jsx': 0,
|
||||
'no-undef': 0,
|
||||
'react/jsx-no-undef': 0,
|
||||
'react/no-unescaped-entities': 0,
|
||||
|
|
|
|||
15
.i18nrc.js
15
.i18nrc.js
|
|
@ -33,18 +33,13 @@ module.exports = defineConfig({
|
|||
},
|
||||
markdown: {
|
||||
reference:
|
||||
'你需要保持 mdx 的组件格式，输出文本不需要在最外层包裹任何代码块语法。\n' +
|
||||
'You need to maintain the component format of the mdx file; the output text does not need to be wrapped in any code block syntax on the outermost layer.\n' +
|
||||
fs.readFileSync(path.join(__dirname, 'docs/glossary.md'), 'utf-8'),
|
||||
entry: ['./README.zh-CN.md', './contributing/**/*.zh-CN.md', './docs/**/*.zh-CN.mdx'],
|
||||
entryLocale: 'zh-CN',
|
||||
outputLocales: ['en-US'],
|
||||
entry: ['./README.md', './docs/**/*.md', './docs/**/*.mdx'],
|
||||
entryLocale: 'en-US',
|
||||
outputLocales: ['zh-CN'],
|
||||
includeMatter: true,
|
||||
exclude: [
|
||||
'./src/**/*',
|
||||
'./contributing/_Sidebar.md',
|
||||
'./contributing/_Footer.md',
|
||||
'./contributing/Home.md',
|
||||
],
|
||||
exclude: ['./README.zh-CN.md', './docs/**/*.zh-CN.md', './docs/**/*.zh-CN.mdx'],
|
||||
outputExtensions: (locale, { filePath }) => {
|
||||
if (filePath.includes('.mdx')) {
|
||||
if (locale === 'en-US') return '.mdx';
|
||||
|
|
|
|||
|
|
@ -2,5 +2,5 @@ const config = require('@lobehub/lint').remarklint;
|
|||
|
||||
module.exports = {
|
||||
...config,
|
||||
plugins: ['remark-mdx', ...config.plugins],
|
||||
plugins: ['remark-mdx', ...config.plugins, ['remark-lint-file-extension', false]],
|
||||
};
|
||||
|
|
|
|||
|
|
@ -422,11 +422,13 @@ Regardless of which database you choose, LobeChat can provide you with an excell
|
|||
|
||||
### [Support Multi-User Management][docs-feat-auth]
|
||||
|
||||
LobeChat supports multi-user management and provides flexible user authentication solutions:
|
||||
LobeChat supports multi-user management and provides two main user authentication and management solutions to meet different needs:
|
||||
|
||||
- **Better Auth**: LobeChat integrates `Better Auth`, a modern and flexible authentication library that supports multiple authentication methods, including OAuth, email login, credential login, magic link, and more. With `Better Auth`, you can easily implement user registration, login, session management, social login, multi-factor authentication (MFA), and other functions to ensure the security and privacy of user data.
|
||||
- **next-auth**: LobeChat integrates `next-auth`, a flexible and powerful identity verification library that supports multiple authentication methods, including OAuth, email login, credential login, etc. With `next-auth`, you can easily implement user registration, login, session management, social login, and other functions to ensure the security and privacy of user data.
|
||||
|
||||
- **next-auth**: LobeChat also supports `next-auth`, a widely-used identity verification library with extensive OAuth provider support and flexible session management options.
|
||||
- [**Clerk**](https://go.clerk.com/exgqLG0): For users who need more advanced user management features, LobeChat also supports `Clerk`, a modern user management platform. `Clerk` provides richer functions, such as multi-factor authentication (MFA), user profile management, login activity monitoring, etc. With `Clerk`, you can get higher security and flexibility, and easily cope with complex user management needs.
|
||||
|
||||
Regardless of which user management solution you choose, LobeChat can provide you with an excellent user experience and powerful functional support.
|
||||
|
||||
<div align="right">
|
||||
|
||||
|
|
|
|||
|
|
@ -1,26 +1,429 @@
|
|||
{
|
||||
"https://file.rene.wang/clipboard-1768907980491-9cc0669fc3a38.png": "/blog/assets8be3a46c8f9c5d3b61bc541f44b7f245.webp",
|
||||
"https://file.rene.wang/clipboard-1768908081787-ed9eb1cb78bdb.png": "/blog/assetsab009b79dd794f02aec24b7607f342e8.webp",
|
||||
"https://file.rene.wang/clipboard-1768908121691-b3517bf882633.png": "/blog/assetsd3cae44cba0d3f57df6440b46246e5e7.webp",
|
||||
"https://file.rene.wang/clipboard-1768908209289-9d3ecff50142f.png": "/blog/assets75a5cf08b3e432d2477899d30acc9d47.webp",
|
||||
"https://file.rene.wang/clipboard-1768908230723-3fce0ae5baf9b.png": "/blog/assets8e9b164fa30c795850ce8fa8ef7e7c24.webp",
|
||||
"https://file.rene.wang/clipboard-1768908420554-e3b90ce1a2e5.png": "/blog/assets98cddf4b80b8bac0c250a5236062d198.webp",
|
||||
"https://file.rene.wang/clipboard-1768908630618-30748e3c30adf.png": "/blog/assetsdd913561927c64d32bd390cee6846f9a.webp",
|
||||
"https://file.rene.wang/clipboard-1768908653789-cc68b35708f2b.png": "/blog/assets3c160860feef0bd7c653eeb46f683445.webp",
|
||||
"https://file.rene.wang/clipboard-1768908678216-fb89263572506.png": "/blog/assets974acc551878f2f395518a3fbb9bd924.webp",
|
||||
"https://file.rene.wang/clipboard-1768908724824-2812deaf9e521.png": "/blog/assets62f82cba03d5dcad5465ec6c626aeb05.webp",
|
||||
"https://file.rene.wang/clipboard-1768908820019-98c5a12b19fd6.png": "/blog/assets99a30932374a5f6193de7c842a34850f.webp",
|
||||
"https://file.rene.wang/clipboard-1768908871983-94def40e520bb.png": "/blog/assets8b75f09941172c3a8620617cddfb7a4b.webp",
|
||||
"https://file.rene.wang/clipboard-1768908943850-00bc4e05bc6bb.png": "/blog/assets7caf7e0d83b8a4f3d177283bb0bc55d1.webp",
|
||||
"https://file.rene.wang/clipboard-1768960626260-35c3384ade91c.png": "/blog/assetsbcd98b0913d2dfc30d5a2b5523115d33.webp",
|
||||
"https://file.rene.wang/clipboard-1768961800651-151a9b076745c.png": "/blog/assets6ebefe8183f31de4de5bac1a921fb153.webp",
|
||||
"https://file.rene.wang/clipboard-1768961895831-d380de3507b63.png": "/blog/assets27b2bf8596f8e65d545322c66a0d81a2.webp",
|
||||
"https://file.rene.wang/clipboard-1768961929559-f1d7d74c54ca1.png": "/blog/assets07820089deb72e5636024ae7e3d1855f.webp",
|
||||
"https://file.rene.wang/clipboard-1768962259734-dc28b56340cb1.png": "/blog/assetseb9b70814679291052dfa4618a44a856.webp",
|
||||
"https://file.rene.wang/clipboard-1768962364687-81d03308f7b3f.png": "/blog/assetse14ddb728d66905c164664b8b5e044d3.webp",
|
||||
"https://file.rene.wang/clipboard-1768962379267-f580e519a03f2.png": "/blog/assetsd6eba2b1881977c9533ba86c1cd3dfce.webp",
|
||||
"https://file.rene.wang/clipboard-1768963219814-ba3d14d1facf3.png": "/blog/assets2964497066067ca0588a7767eb4c1709.webp",
|
||||
"https://file.rene.wang/clipboard-1768963283361-5b62ccd3a1862.png": "/blog/assetsbcd98b0913d2dfc30d5a2b5523115d33.webp",
|
||||
"https://file.rene.wang/clipboard-1768976299511-a09372a7e6fd9.png": "/blog/assets60bf3667e56862024d047444d9b4c2fb.webp",
|
||||
"https://file.rene.wang/clipboard-1768976422506-24d64ffd3fd26.png": "/blog/assets7bf0102f1cae47bf24aeb01eaa2796d9.webp",
|
||||
"https://file.rene.wang/clipboard-1768976706650-e810aaaa86f44.png": "/blog/assets7caf7e0d83b8a4f3d177283bb0bc55d1.webp",
|
||||
"https://file.rene.wang/clipboard-1769000274218-d02c4c8024709.png": "/blog/assets3cdf933016e6f53bca12b8cedb17061f.webp",
|
||||
"https://file.rene.wang/clipboard-1769000328858-48f0503640245.png": "/blog/assets04d6fae3d9aa3c33697028f1cc9f4706.webp",
|
||||
"https://file.rene.wang/clipboard-1769001225111-af0244fff25f3.png": "/blog/assetsb811f2aae8e8346aef16793d6bd10f88.webp",
|
||||
"https://file.rene.wang/clipboard-1769049968016-4a62699ad0b36.png": "/blog/assetsa88afc117d283790187c366f29d03284.webp",
|
||||
"https://file.rene.wang/clipboard-1769050621749-3709f9939d7d4.png": "/blog/assetsc89931ace11a936d87d0b87a6bca1069.webp",
|
||||
"https://file.rene.wang/clipboard-1769050642741-4b72fd17934cf.png": "/blog/assetsdc6362a2c6db476fc1b7b9d6bf443af2.webp",
|
||||
"https://file.rene.wang/clipboard-1769050808722-bd6e724a5b54b.png": "/blog/assets55bea1dc3e938580591d75d72908835a.webp",
|
||||
"https://file.rene.wang/clipboard-1769050853107-750be5f83cbe3.png": "/blog/assetse6139c4d5b1b26b05f41a579d98fc6f3.webp",
|
||||
"https://file.rene.wang/clipboard-1769052898732-b7bb78ae1f1f8.png": "/blog/assetsafa74c85aafea8a057e6047b0823e280.webp",
|
||||
"https://file.rene.wang/clipboard-1769056077960-cac34bc157a65.png": "/blog/assetsa8e173bec038d1d21d413f6fa0ace342.webp",
|
||||
"https://file.rene.wang/clipboard-1769155711708-710967bee57bc.png": "/blog/assets7f3b38c1d76cceb91edb29d6b1eb60db.webp",
|
||||
"https://file.rene.wang/clipboard-1769155737647-1b4fc6558f029.png": "/blog/assets3a7f0b29839603336e39e923b423409b.webp",
|
||||
"https://file.rene.wang/clipboard-1769155791342-7f43b72cc6b42.png": "/blog/assets35e6aa692b0c16009c61964279514166.webp",
|
||||
"https://file.rene.wang/clipboard-1769155818070-7eb403550b6c7.png": "/blog/assetsce5d6dc93676f974be2e162e8ace03f0.webp",
|
||||
"https://file.rene.wang/clipboard-1769155880302-272fbd2c5290b.png": "/blog/assetsdf48eed9de76b7e37c269b294285f09d.webp",
|
||||
"https://file.rene.wang/clipboard-1769155935435-93dab92dd0f44.png": "/blog/assets902eb746fe2042fc2ea831c71002be72.webp",
|
||||
"https://file.rene.wang/clipboard-1769155973881-ff1ee142d5b8f.png": "/blog/assets5cc27b8cae995074da20d4ffe06a1460.webp",
|
||||
"https://file.rene.wang/clipboard-1769156005535-c2e79e11f4b56.png": "/blog/assets2a36d86a4eed6e7938dd6e9c684701ed.webp",
|
||||
"https://file.rene.wang/clipboard-1769156036607-2b4fe37c4b56c.png": "/blog/assetsc0efdb82443556ae3acefe00099b3f23.webp",
|
||||
"https://file.rene.wang/clipboard-1769156050787-ecf4f48474ae2.png": "/blog/assetse743f0a47127390dde766a0a790476db.webp",
|
||||
"https://file.rene.wang/lobehub/467951f5-ad65-498d-aea9-fca8f35a4314.png": "/blog/assets907ea775d228958baca38e2dbb65939a.webp",
|
||||
"https://file.rene.wang/lobehub/58d91528-373a-4a42-b520-cf6cb1f8ce1e.png": "/blog/assets7dccdd4df55aede71001da649639437f.webp",
|
||||
"https://file.rene.wang/lobehub/ee700103-3c08-41dc-9ddf-c7705bb7bc6a.png": "/blog/assets196d679bc7071abbf71f2a8566f05aa3.webp",
|
||||
"https://file.rene.wang/lobehub/image-2.png": "/blog/assets58737403bd41f2f0ea70bdea609e9169.webp",
|
||||
"https://file.rene.wang/lobehub/image-3.png": "/blog/assets9e2139a302264b278eb3f4296640fe8a.webp",
|
||||
"https://file.rene.wang/lobehub/image-4.png": "/blog/assets095af3a0a0f850fc206fc3bbc19a4095.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/13883964/48a0b702-05bd-4ce4-a007-a8ad00a36e5a": "/blog/assets13883964/48a0b702-05bd-4ce4-a007-a8ad00a36e5a.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/13883964/4f9d83bd-b3fc-4abc-bcf4-ccbad65c219d": "/blog/assets13883964/4f9d83bd-b3fc-4abc-bcf4-ccbad65c219d.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/13883964/c9d66fa0-158c-4bd3-a1fa-969e638259d2": "/blog/assets13883964/c9d66fa0-158c-4bd3-a1fa-969e638259d2.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/0c2c399f-2ed3-44b5-97c8-53e007e8c095": "/blog/assets17870709/0c2c399f-2ed3-44b5-97c8-53e007e8c095.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/1148639c-2687-4a9c-9950-8ca8672f34b6": "/blog/assets17870709/1148639c-2687-4a9c-9950-8ca8672f34b6.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/15e09e71-5899-4805-9c5e-1f7c57be04ae": "/blog/assets17870709/15e09e71-5899-4805-9c5e-1f7c57be04ae.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/1d840e27-fa74-4e71-b777-330bf41d6dff": "/blog/assets17870709/1d840e27-fa74-4e71-b777-330bf41d6dff.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/21b94782-875b-4dee-a572-3c5843f3e1e3": "/blog/assets17870709/21b94782-875b-4dee-a572-3c5843f3e1e3.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/385f663f-cae2-4383-9bb0-52c45e5d7d7a": "/blog/assets17870709/385f663f-cae2-4383-9bb0-52c45e5d7d7a.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/3f31bc33-509f-4ad2-ba81-280c2a6ec5fa": "/blog/assets17870709/3f31bc33-509f-4ad2-ba81-280c2a6ec5fa.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/4e56e080-9b8c-42e1-87e1-11123dbb9067": "/blog/assets17870709/4e56e080-9b8c-42e1-87e1-11123dbb9067.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/4fae3e6f-e680-4471-93c4-987c19d7170a": "/blog/assets17870709/4fae3e6f-e680-4471-93c4-987c19d7170a.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/51f8f8f6-5d8a-4cf0-a2e5-d96c69fe05b8": "/blog/assets17870709/51f8f8f6-5d8a-4cf0-a2e5-d96c69fe05b8.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/5efa34c2-6523-43e6-9ade-70ab5d802e13": "/blog/assets17870709/5efa34c2-6523-43e6-9ade-70ab5d802e13.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/620b956b-dcb2-442a-8bb1-9aa22681dfa4": "/blog/assets17870709/620b956b-dcb2-442a-8bb1-9aa22681dfa4.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/63d9f6d4-5b78-4c65-8cd1-ff8b7f143406": "/blog/assets17870709/63d9f6d4-5b78-4c65-8cd1-ff8b7f143406.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/65d2dd2a-fdcf-4f3f-a6af-4ed5164a510d": "/blog/assets17870709/65d2dd2a-fdcf-4f3f-a6af-4ed5164a510d.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/6cdc5c0e-0508-44ed-a283-03f6b538ed8a": "/blog/assets17870709/6cdc5c0e-0508-44ed-a283-03f6b538ed8a.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/79faa59a-dfc0-4365-a679-5fc12c12bc70": "/blog/assets17870709/79faa59a-dfc0-4365-a679-5fc12c12bc70.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/80e22593-dc0f-482c-99bf-69acdb62d952": "/blog/assets17870709/80e22593-dc0f-482c-99bf-69acdb62d952.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/82cf4f5c-be5c-4126-a475-3a03468a9c39": "/blog/assets17870709/82cf4f5c-be5c-4126-a475-3a03468a9c39.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/a3f9f63a-48f8-4567-b960-7f3636c0d4ed": "/blog/assets17870709/a3f9f63a-48f8-4567-b960-7f3636c0d4ed.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/a77b0fb2-87d7-4527-a804-2f7ad3634aa5": "/blog/assets17870709/a77b0fb2-87d7-4527-a804-2f7ad3634aa5.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/ab94a7b5-6bc4-41e0-97bc-724ee8e315db": "/blog/assets17870709/ab94a7b5-6bc4-41e0-97bc-724ee8e315db.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/ac10d9dd-a977-43fb-8397-b2bbdee6a1a1": "/blog/assets17870709/ac10d9dd-a977-43fb-8397-b2bbdee6a1a1.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/b4a01219-e7b1-48a0-888c-f0271b18e3a6": "/blog/assets17870709/b4a01219-e7b1-48a0-888c-f0271b18e3a6.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/ba8e688a-e0c1-4567-9013-94205f83fc60": "/blog/assets17870709/ba8e688a-e0c1-4567-9013-94205f83fc60.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/c9e5eafc-ca22-496b-a88d-cc0ae53bf720": "/blog/assets17870709/c9e5eafc-ca22-496b-a88d-cc0ae53bf720.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/ddb44517-8696-4492-acd9-25b590f6069c": "/blog/assets17870709/ddb44517-8696-4492-acd9-25b590f6069c.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/e1b5f84f-015e-437c-98cc-a3431fa3b077": "/blog/assets17870709/e1b5f84f-015e-437c-98cc-a3431fa3b077.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/e6a429cb-96e1-4e85-9aa3-1334ffcad8c0": "/blog/assets17870709/e6a429cb-96e1-4e85-9aa3-1334ffcad8c0.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/eb7273f8-f0ed-4b9b-884e-96d29c406cb7": "/blog/assets17870709/eb7273f8-f0ed-4b9b-884e-96d29c406cb7.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/f579b39b-e771-402c-a1d1-620e57a10c75": "/blog/assets17870709/f579b39b-e771-402c-a1d1-620e57a10c75.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/ff7ebacf-27f0-42d7-810b-00314499a084": "/blog/assets17870709/ff7ebacf-27f0-42d7-810b-00314499a084.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/17870709/ff9c3eb8-412b-4275-80be-177ae7b7acbc": "/blog/assets17870709/ff9c3eb8-412b-4275-80be-177ae7b7acbc.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/1845053/fe34fdfe-c2e4-4d6a-84d7-4ebc61b2516a": "/blog/assets1845053/fe34fdfe-c2e4-4d6a-84d7-4ebc61b2516a.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/0249ea56-ab17-4aa9-a56c-9ebd556c2645": "/blog/assets28616219/0249ea56-ab17-4aa9-a56c-9ebd556c2645.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/034a328c-8465-4499-8f93-fdcdb03343cd": "/blog/assets28616219/034a328c-8465-4499-8f93-fdcdb03343cd.mp4",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/1c689738-809b-4199-b305-ba5770d39da7": "/blog/assets28616219/1c689738-809b-4199-b305-ba5770d39da7.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/1c82d707-cb6f-4924-b246-a5235a919864": "/blog/assets28616219/1c82d707-cb6f-4924-b246-a5235a919864.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/1ed8b13d-046e-47c8-bd61-116ffdf5d01b": "/blog/assets28616219/1ed8b13d-046e-47c8-bd61-116ffdf5d01b.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/2bfa13df-6e20-4768-97c0-4dad06c85a2f": "/blog/assets28616219/2bfa13df-6e20-4768-97c0-4dad06c85a2f.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/2ceb210c-eca0-4439-ba27-8734d4ebb3ee": "/blog/assets28616219/2ceb210c-eca0-4439-ba27-8734d4ebb3ee.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/31b999e5-2a74-45fc-935b-f036e72a684d": "/blog/assets28616219/31b999e5-2a74-45fc-935b-f036e72a684d.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/31e5f625-8dc4-4a5f-a5fd-d28d0457782d": "/blog/assets28616219/31e5f625-8dc4-4a5f-a5fd-d28d0457782d.mp4",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/3b607482-4d99-455a-bc10-3090dd4fe3c5": "/blog/assets28616219/3b607482-4d99-455a-bc10-3090dd4fe3c5.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/41f7f677-0153-4a96-b849-5ac9b7ebefee": "/blog/assets28616219/41f7f677-0153-4a96-b849-5ac9b7ebefee.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/4e81decc-776c-43b8-9a54-dfb43e9f601a": "/blog/assets28616219/4e81decc-776c-43b8-9a54-dfb43e9f601a.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/54b3696b-5b13-4761-8c1b-1e664867b2dd": "/blog/assets28616219/54b3696b-5b13-4761-8c1b-1e664867b2dd.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/5fdc9479-007f-46ab-9d6e-a9603e949116": "/blog/assets28616219/5fdc9479-007f-46ab-9d6e-a9603e949116.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/69414c79-642e-4323-9641-bfa43a74fcc8": "/blog/assets28616219/69414c79-642e-4323-9641-bfa43a74fcc8.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/6c3968a8-fbbb-4268-a587-edaced2d96af": "/blog/assets28616219/6c3968a8-fbbb-4268-a587-edaced2d96af.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/7049a811-a08b-45d3-8491-970f579c2ebd": "/blog/assets28616219/7049a811-a08b-45d3-8491-970f579c2ebd.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/763b18f9-2b5f-44bb-a479-9b56d46f7397": "/blog/assets28616219/763b18f9-2b5f-44bb-a479-9b56d46f7397.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/7b0ea46c-5157-40a8-888f-f47664a4884f": "/blog/assets28616219/7b0ea46c-5157-40a8-888f-f47664a4884f.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/7f9a9a9f-fd91-4f59-aac9-3f26c6d49a1e": "/blog/assets28616219/7f9a9a9f-fd91-4f59-aac9-3f26c6d49a1e.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/89883703-7a1a-4a11-b944-5d804544e57c": "/blog/assets28616219/89883703-7a1a-4a11-b944-5d804544e57c.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/95828c11-0ae5-4dfa-84ed-854124e927a6": "/blog/assets28616219/95828c11-0ae5-4dfa-84ed-854124e927a6.mp4",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/9c0d184c-3169-40fa-9115-011cfffb9ca7": "/blog/assets28616219/9c0d184c-3169-40fa-9115-011cfffb9ca7.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/9cb5150d-6e1e-4c59-9a18-4e418dce1a5d": "/blog/assets28616219/9cb5150d-6e1e-4c59-9a18-4e418dce1a5d.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/a7fd85d5-fd32-4756-814e-ff7ab7567fe1": "/blog/assets28616219/a7fd85d5-fd32-4756-814e-ff7ab7567fe1.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/ab008be7-26b2-4b78-8bd9-24301bf34d23": "/blog/assets28616219/ab008be7-26b2-4b78-8bd9-24301bf34d23.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/b04723eb-64ad-4028-a901-dc4e4ee2d0c1": "/blog/assets28616219/b04723eb-64ad-4028-a901-dc4e4ee2d0c1.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/b3a78112-adc8-4837-b4e3-48f67058f16e": "/blog/assets28616219/b3a78112-adc8-4837-b4e3-48f67058f16e.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/b6b8226b-183f-4249-8255-663a5e9f5af4": "/blog/assets28616219/b6b8226b-183f-4249-8255-663a5e9f5af4.mp4",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/bb9cd00f-b20c-4d7b-9c60-b921d350e319": "/blog/assets28616219/bb9cd00f-b20c-4d7b-9c60-b921d350e319.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/bdeb678e-6502-4667-86b1-504221ee7ded": "/blog/assets28616219/bdeb678e-6502-4667-86b1-504221ee7ded.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/be0c95c0-6693-44ee-a490-7e8dfaa8b34d": "/blog/assets28616219/be0c95c0-6693-44ee-a490-7e8dfaa8b34d.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/c1f945d1-f3e2-4100-b6bb-24d4cb13c438": "/blog/assets28616219/c1f945d1-f3e2-4100-b6bb-24d4cb13c438.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/c32b56db-c6a1-4876-9bc3-acbd37ec0c0c": "/blog/assets28616219/c32b56db-c6a1-4876-9bc3-acbd37ec0c0c.mp4",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/c9c58141-5ec6-43f1-8d97-0a84a04dcdba": "/blog/assets28616219/c9c58141-5ec6-43f1-8d97-0a84a04dcdba.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/c9f74ec4-ce63-4ce9-b9e2-34bda6fda10b": "/blog/assets28616219/c9f74ec4-ce63-4ce9-b9e2-34bda6fda10b.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/cd74152d-0ae8-44fd-b815-3307c56a3c18": "/blog/assets28616219/cd74152d-0ae8-44fd-b815-3307c56a3c18.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/d4a710cd-6404-4196-90d0-cd08ca385074": "/blog/assets28616219/d4a710cd-6404-4196-90d0-cd08ca385074.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/d6f5a918-7b50-4d6e-83a6-3894ab930ddf": "/blog/assets28616219/d6f5a918-7b50-4d6e-83a6-3894ab930ddf.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/da84edc3-46f7-4e2b-a0cd-dc33a98bf5cb": "/blog/assets28616219/da84edc3-46f7-4e2b-a0cd-dc33a98bf5cb.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/dfcc2cb3-2958-4498-a8a4-51bec584fe7d": "/blog/assets28616219/dfcc2cb3-2958-4498-a8a4-51bec584fe7d.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/e0608cca-f62f-414a-bc55-28a61ba21f14": "/blog/assets28616219/e0608cca-f62f-414a-bc55-28a61ba21f14.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/f29475a3-f346-4196-a435-41a6373ab9e2": "/blog/assets/28616219/f29475a3-f346-4196-a435-41a6373ab9e2.mp4",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/f3885537-6d43-422f-b1b8-e70732401025": "/blog/assets28616219/f3885537-6d43-422f-b1b8-e70732401025.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/f50f47fb-5e8e-4930-bf4e-8cf6f5b8afb9": "/blog/assets28616219/f50f47fb-5e8e-4930-bf4e-8cf6f5b8afb9.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/28616219/fab4abb2-584b-49de-9340-813382951635": "/blog/assets28616219/fab4abb2-584b-49de-9340-813382951635.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/30863298/0beda150-d0b6-43cf-a9f1-fce928b83a96": "/blog/assets30863298/0beda150-d0b6-43cf-a9f1-fce928b83a96.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/30863298/3e0082df-9b6f-46f3-b67f-bdc79e1eb2cc": "/blog/assets30863298/3e0082df-9b6f-46f3-b67f-bdc79e1eb2cc.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/30863298/62fbd09f-a69a-4460-949b-0f6285fa65b9": "/blog/assets30863298/62fbd09f-a69a-4460-949b-0f6285fa65b9.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/30863298/880749a6-5ba4-4e20-a968-b583a54de7fa": "/blog/assets30863298/880749a6-5ba4-4e20-a968-b583a54de7fa.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/30863298/9891347e-a338-4aa9-8714-f16c8dbcfcec": "/blog/assets30863298/9891347e-a338-4aa9-8714-f16c8dbcfcec.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/30863298/df4cea85-616a-46f5-b2de-42725d9b82a6": "/blog/assets30863298/df4cea85-616a-46f5-b2de-42725d9b82a6.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/30863298/f068190f-0027-4d3b-8667-d632e43d5a86": "/blog/assets30863298/f068190f-0027-4d3b-8667-d632e43d5a86.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/0275a552-f189-42b5-bf40-f9891c428b3d": "/blog/assets34400653/0275a552-f189-42b5-bf40-f9891c428b3d.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/094d701f-ce80-464a-bbbc-0a5ecc8d08e3": "/blog/assets34400653/094d701f-ce80-464a-bbbc-0a5ecc8d08e3.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/0cc6c9b8-4688-472b-a80f-f84c5ebbc719": "/blog/assets34400653/0cc6c9b8-4688-472b-a80f-f84c5ebbc719.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/11442ce4-a615-49c4-937a-ca2ae93dd27c": "/blog/assets34400653/11442ce4-a615-49c4-937a-ca2ae93dd27c.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/164b34b5-671e-418d-b34a-3b70f1156d06": "/blog/assets34400653/164b34b5-671e-418d-b34a-3b70f1156d06.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/198217a6-84fa-441c-bcbe-8cded1106d6c": "/blog/assets34400653/198217a6-84fa-441c-bcbe-8cded1106d6c.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/22ce5a72-bc46-41f3-b402-bda6dee90184": "/blog/assets34400653/22ce5a72-bc46-41f3-b402-bda6dee90184.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/28d89add-cb18-4b86-9807-f2a5ed65ceba": "/blog/assets34400653/28d89add-cb18-4b86-9807-f2a5ed65ceba.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/28e025dd-367b-4add-85b6-499f4aacda61": "/blog/assets34400653/28e025dd-367b-4add-85b6-499f4aacda61.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/2afffe79-1d37-423c-9363-f09605d5e640": "/blog/assets34400653/2afffe79-1d37-423c-9363-f09605d5e640.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/33d8ce3b-0083-48aa-9a66-3825e726c4de": "/blog/assets34400653/33d8ce3b-0083-48aa-9a66-3825e726c4de.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/34d92da4-783f-4f16-8c4a-9d8e9a03c8da": "/blog/assets34400653/34d92da4-783f-4f16-8c4a-9d8e9a03c8da.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/3c64b747-f6f1-4ed2-84bc-bfa8e5d90966": "/blog/assets34400653/3c64b747-f6f1-4ed2-84bc-bfa8e5d90966.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/40520a43-ac03-4954-8a4d-282fbb946066": "/blog/assets34400653/40520a43-ac03-4954-8a4d-282fbb946066.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/4485fbc3-c309-4c4e-83ee-cb82392307a1": "/blog/assets34400653/4485fbc3-c309-4c4e-83ee-cb82392307a1.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/470e5669-650b-46cf-8024-a1476c166059": "/blog/assets34400653/470e5669-650b-46cf-8024-a1476c166059.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/497e3b20-57ca-4963-b6f4-897c9710c16e": "/blog/assets34400653/497e3b20-57ca-4963-b6f4-897c9710c16e.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/4e057b43-1e3e-4e96-a948-7cdbff303dcb": "/blog/assets34400653/4e057b43-1e3e-4e96-a948-7cdbff303dcb.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/4e0e87d1-4970-45c5-a9ef-287098f6a198": "/blog/assets34400653/4e0e87d1-4970-45c5-a9ef-287098f6a198.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/4f8d0102-7ca7-4f23-b96f-3fc5cf2cd66e": "/blog/assets34400653/4f8d0102-7ca7-4f23-b96f-3fc5cf2cd66e.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/50b73232-01fc-4ef0-939a-3e06354d1b5a": "/blog/assets34400653/50b73232-01fc-4ef0-939a-3e06354d1b5a.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/5707b392-1ee6-4db6-95cb-9d6c902747d2": "/blog/assets34400653/5707b392-1ee6-4db6-95cb-9d6c902747d2.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/5c3898ab-23d7-44c2-bbd9-b255e25e400c": "/blog/assets34400653/5c3898ab-23d7-44c2-bbd9-b255e25e400c.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/663335d0-fb37-4882-9c7f-ebbd53275644": "/blog/assets34400653/663335d0-fb37-4882-9c7f-ebbd53275644.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/6942287e-fbb1-4a10-a1ce-caaa6663da1e": "/blog/assets34400653/6942287e-fbb1-4a10-a1ce-caaa6663da1e.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/6d6f2bc5-1407-471d-95a8-fb03193edbdb": "/blog/assets34400653/6d6f2bc5-1407-471d-95a8-fb03193edbdb.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/703f170b-c03b-4c71-b57d-c2357596bdfb": "/blog/assets34400653/703f170b-c03b-4c71-b57d-c2357596bdfb.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/72f165f4-d529-4f01-a3ac-163c66e5ea73": "/blog/assets34400653/72f165f4-d529-4f01-a3ac-163c66e5ea73.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/7468594b-3355-4cb9-85bc-c9dace137653": "/blog/assets34400653/7468594b-3355-4cb9-85bc-c9dace137653.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/74768b36-28ca-4ec3-a42d-b32abe2c7057": "/blog/assets34400653/74768b36-28ca-4ec3-a42d-b32abe2c7057.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/750b5cd1-f16a-4330-b899-c27b28b1e837": "/blog/assets34400653/750b5cd1-f16a-4330-b899-c27b28b1e837.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/77b5feee-3f46-486d-9a36-31ff60efa5e9": "/blog/assets34400653/77b5feee-3f46-486d-9a36-31ff60efa5e9.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/7a012a11-87bd-4366-a567-0ebf6d12ae10": "/blog/assets34400653/7a012a11-87bd-4366-a567-0ebf6d12ae10.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/88948a3a-6681-4a8d-9734-a464e09e4957": "/blog/assets34400653/88948a3a-6681-4a8d-9734-a464e09e4957.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/8bf73498-4649-4c4d-a95b-b68447599781": "/blog/assets34400653/8bf73498-4649-4c4d-a95b-b68447599781.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/94836b32-7fc5-45ca-8556-7a23f53b15f9": "/blog/assets34400653/94836b32-7fc5-45ca-8556-7a23f53b15f9.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/95717e2b-1a55-4fca-a96b-b1c186ed4563": "/blog/assets34400653/95717e2b-1a55-4fca-a96b-b1c186ed4563.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/9a8dc1d4-152b-415f-a7cd-8f0c8fbb9913": "/blog/assets34400653/9a8dc1d4-152b-415f-a7cd-8f0c8fbb9913.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/a024af40-e1d9-4df0-b998-0e6e87cebe5b": "/blog/assets34400653/a024af40-e1d9-4df0-b998-0e6e87cebe5b.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/ac2ed716-d270-43f6-856b-3ff81265f4e6": "/blog/assets34400653/ac2ed716-d270-43f6-856b-3ff81265f4e6.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/b4d12904-9d5d-46de-bd66-901eeb9c8e52": "/blog/assets34400653/b4d12904-9d5d-46de-bd66-901eeb9c8e52.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/b695f26a-5bcd-477c-af08-bf03adb717c2": "/blog/assets34400653/b695f26a-5bcd-477c-af08-bf03adb717c2.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/b839e04e-0cef-46a3-bb84-0484a3f51c69": "/blog/assets34400653/b839e04e-0cef-46a3-bb84-0484a3f51c69.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/b83da559-73d1-4734-87d5-5e22955a9da2": "/blog/assets34400653/b83da559-73d1-4734-87d5-5e22955a9da2.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/ba3595e3-d9cb-4d0d-b414-8306b16df186": "/blog/assets34400653/ba3595e3-d9cb-4d0d-b414-8306b16df186.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/c1d1d816-6339-41a6-9bc9-e2c3b2762291": "/blog/assets34400653/c1d1d816-6339-41a6-9bc9-e2c3b2762291.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/c2e6a58b-95eb-4f40-8add-83f4316a719b": "/blog/assets34400653/c2e6a58b-95eb-4f40-8add-83f4316a719b.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/cbc23ca9-1188-4b85-8ef0-e75ac7d74b92": "/blog/assets34400653/cbc23ca9-1188-4b85-8ef0-e75ac7d74b92.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/cec2e032-54e1-49b1-a212-4d9736927156": "/blog/assets34400653/cec2e032-54e1-49b1-a212-4d9736927156.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/e6058456-8f9d-40c1-9ae5-1e9d5eeb9476": "/blog/assets34400653/e6058456-8f9d-40c1-9ae5-1e9d5eeb9476.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/eb57ca57-4f45-4409-91ce-9fa9c7c626d6": "/blog/assets34400653/eb57ca57-4f45-4409-91ce-9fa9c7c626d6.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/eee046cb-189b-4635-ac94-19d50b17a18a": "/blog/assets34400653/eee046cb-189b-4635-ac94-19d50b17a18a.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/ef9ed1b8-6828-4dd6-b86b-bb0b4fa40619": "/blog/assets34400653/ef9ed1b8-6828-4dd6-b86b-bb0b4fa40619.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/f4a23c2a-503e-4731-bc4d-922bce0b6039": "/blog/assets34400653/f4a23c2a-503e-4731-bc4d-922bce0b6039.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/f539d104-6d64-4cc7-8781-3b36b00d32d0": "/blog/assets34400653/f539d104-6d64-4cc7-8781-3b36b00d32d0.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/f6e46f1c-0ac9-42ae-8e83-ddb0cc6c5bf8": "/blog/assets34400653/f6e46f1c-0ac9-42ae-8e83-ddb0cc6c5bf8.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/f7d59c7a-abd0-4ebd-8c72-ca10c47a0f1a": "/blog/assets34400653/f7d59c7a-abd0-4ebd-8c72-ca10c47a0f1a.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/f892fe64-c734-4944-91ff-9916a41bd1c9": "/blog/assets34400653/f892fe64-c734-4944-91ff-9916a41bd1c9.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/f9a5a394-c8f8-4567-9d51-cf84811418ca": "/blog/assets34400653/f9a5a394-c8f8-4567-9d51-cf84811418ca.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/fa725e49-4c17-4055-82bc-98a31e73fa54": "/blog/assets34400653/fa725e49-4c17-4055-82bc-98a31e73fa54.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/fb0f7574-c2f5-40d6-8613-3749e85ce881": "/blog/assets34400653/fb0f7574-c2f5-40d6-8613-3749e85ce881.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/fcdcda9b-8668-4eac-b5cb-04803a888e92": "/blog/assets34400653/fcdcda9b-8668-4eac-b5cb-04803a888e92.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/34400653/fd06c0aa-4bd3-4f4e-bf2b-38374dfe775d": "/blog/assets34400653/fd06c0aa-4bd3-4f4e-bf2b-38374dfe775d.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/64475363/23131ca1-9e84-4a89-a840-ef79c4bc0251": "/blog/assets64475363/23131ca1-9e84-4a89-a840-ef79c4bc0251.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/64475363/2f919f99-2aaa-4fa7-9938-169d3ed09db7": "/blog/assets64475363/2f919f99-2aaa-4fa7-9938-169d3ed09db7.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/64475363/358bca8d-3d82-4e76-9a5e-90d16a39efde": "/blog/assets64475363/358bca8d-3d82-4e76-9a5e-90d16a39efde.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/64475363/6d69bdca-7d18-4cbc-b3e0-220d8815cd29": "/blog/assets64475363/6d69bdca-7d18-4cbc-b3e0-220d8815cd29.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/64475363/995780cb-9096-4a36-ab17-d422703ab970": "/blog/assets64475363/995780cb-9096-4a36-ab17-d422703ab970.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/64475363/c6108133-a918-48b0-ab1a-e3fa607572a4": "/blog/assets64475363/c6108133-a918-48b0-ab1a-e3fa607572a4.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/64475363/d7ef5ad1-b1a3-435e-b1bc-4436d2b6fecd": "/blog/assets64475363/d7ef5ad1-b1a3-435e-b1bc-4436d2b6fecd.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/67304509/4244634e-5f68-48d5-aac0-e5f4b06d1c4b": "/blog/assets67304509/4244634e-5f68-48d5-aac0-e5f4b06d1c4b.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/12451b47-8dcd-40a9-b18d-2806b07efecc": "/blog/assets8692892/12451b47-8dcd-40a9-b18d-2806b07efecc.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/14ecaa12-74a1-4e2f-b171-9d9ac09d3d63": "/blog/assets8692892/14ecaa12-74a1-4e2f-b171-9d9ac09d3d63.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/1699bf46-0c8d-4238-9eb5-34282bfe529a": "/blog/assets8692892/1699bf46-0c8d-4238-9eb5-34282bfe529a.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/20a257b5-d086-46f3-b5c2-f76394b11f55": "/blog/assets8692892/20a257b5-d086-46f3-b5c2-f76394b11f55.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/3564110d-bef9-47f3-b775-e5f28b4275b2": "/blog/assets8692892/3564110d-bef9-47f3-b775-e5f28b4275b2.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/375b3d73-6796-465c-9063-f2762093f763": "/blog/assets8692892/375b3d73-6796-465c-9063-f2762093f763.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/407b4eed-7f21-4aa6-b68f-9bae2faf09d0": "/blog/assets8692892/407b4eed-7f21-4aa6-b68f-9bae2faf09d0.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/40bb6b4c-18e0-4ae5-abae-ae0cf202cf08": "/blog/assets8692892/40bb6b4c-18e0-4ae5-abae-ae0cf202cf08.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/4ff3c3a0-9ca0-45ff-8f3a-219f4445098b": "/blog/assets8692892/4ff3c3a0-9ca0-45ff-8f3a-219f4445098b.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/5a0e6c58-9e6f-4ffb-8af2-32e48cfb45b0": "/blog/assets8692892/5a0e6c58-9e6f-4ffb-8af2-32e48cfb45b0.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/79c55d44-8dcb-429c-a072-d3eb014bbceb": "/blog/assets8692892/79c55d44-8dcb-429c-a072-d3eb014bbceb.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/9d5cb651-ad10-47c7-8c8b-2256163c5521": "/blog/assets8692892/9d5cb651-ad10-47c7-8c8b-2256163c5521.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/b05473ad-04a6-4ebc-9810-116c778d4448": "/blog/assets8692892/b05473ad-04a6-4ebc-9810-116c778d4448.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/bee24764-aa42-47d9-ad43-bcb8e7b35bc3": "/blog/assets8692892/bee24764-aa42-47d9-ad43-bcb8e7b35bc3.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/d12a2661-7b98-484f-8f3d-07e84d42ae08": "/blog/assets8692892/d12a2661-7b98-484f-8f3d-07e84d42ae08.webp",
|
||||
"https://github.com/lobehub/lobe-chat/assets/8692892/d84235b1-45f6-447d-bdd9-58ab9527dc9b": "/blog/assets8692892/d84235b1-45f6-447d-bdd9-58ab9527dc9b.webp",
|
||||
"https://github.com/user-attachments/assets/00c02637-873e-4e7e-9dc3-a95085b16dd7": "/blog/assets05d786345e99f92d11baae5667a04a62.webp",
|
||||
"https://github.com/user-attachments/assets/03433283-08a5-481a-8f6c-069b2fc6bace": "/blog/assets/8d4c2cc0ce8654fa8ac06cc036a7f941.webp",
|
||||
"https://github.com/user-attachments/assets/08ced88b-4968-46e8-b1da-0c04ddf5b743": "/blog/assets5fd5fb937b9b05d50ce8659cea3210a4.webp",
|
||||
"https://github.com/user-attachments/assets/09be499c-3b04-4dd6-a161-6e8ebe788354": "/blog/assets65003d69fa745e7cac376a79ea4bb742.webp",
|
||||
"https://github.com/user-attachments/assets/09c994cf-78f8-46ea-9fef-a06022c0f6d7": "/blog/assets6b6c251a2d4a77784c08fb07fc51abf9.webp",
|
||||
"https://github.com/user-attachments/assets/0af85438-ac99-4c95-b888-a17e88ede043": "/blog/assetsf1e1ca1adaac36881ec6c3b2ce1a099e.webp",
|
||||
"https://github.com/user-attachments/assets/0c73c453-6ee3-4f90-bc5d-119c52c38fef": "/blog/assets2a74d926ae05faf2ee9f8da858bec3f6.webp",
|
||||
"https://github.com/user-attachments/assets/0e2fdc5d-9623-4a74-a7f6-dcb802d52297": "/blog/assets61324ea13398c8920f798b97ac19d58f.webp",
|
||||
"https://github.com/user-attachments/assets/0e3a7174-6b66-4432-a319-dff60b033c24": "/blog/assets/39d7890f8cbe21e77db8d3c94f7f22e4.webp",
|
||||
"https://github.com/user-attachments/assets/0f79c266-cce5-4936-aabd-4c8f19196d91": "/blog/assets6b67dabe7b9226cdff1bace5a3b8ab18.webp",
|
||||
"https://github.com/user-attachments/assets/1028aa1a-6c19-4191-b28a-2020e5637155": "/blog/assetsd9e6fe2197270f0f774accd6abcf4019.webp",
|
||||
"https://github.com/user-attachments/assets/1077bee5-b379-4063-b7bd-23b98ec146e2": "/blog/assetsa74aedc4fbbfb2caf6b51f286922b576.webp",
|
||||
"https://github.com/user-attachments/assets/12863a0e-a1ee-406d-8dee-011b20701fd6": "/blog/assets513c9045fef49b4d46549f485e69f505.webp",
|
||||
"https://github.com/user-attachments/assets/12c1957d-f050-4235-95da-d55ddedfa6c9": "/blog/assets74f5de8ee68e57b472d1fc56a2df40d5.webp",
|
||||
"https://github.com/user-attachments/assets/143ff392-97b5-427a-97a7-f2f577915728": "/blog/assetsc52da5833158f3b3143e40bf2a534ac7.webp",
|
||||
"https://github.com/user-attachments/assets/14696698-03f7-4856-b36c-9a53997eb12c": "/blog/assets710bf5a4704e520976b19dd2466fa56a.webp",
|
||||
"https://github.com/user-attachments/assets/15af6d94-af4f-4aa9-bbab-7a46e9f9e837": "/blog/assetsffb84575674e2bc5dfdd07af8f41e794.webp",
|
||||
"https://github.com/user-attachments/assets/15d92756-92f0-45da-8f95-bfe725d13003": "/blog/assets653a83fe7d837e0d225c1de12e60cf92.webp",
|
||||
"https://github.com/user-attachments/assets/162bc64e-0d34-4a4e-815a-028247b73143": "/blog/assets308f9fd45d0e8a140c1c18e6c92a1a57.webp",
|
||||
"https://github.com/user-attachments/assets/16cd9aef-c87b-48a4-95c0-b666082e7515": "/blog/assets0ceb7e446f9a850df283093563ba7803.webp",
|
||||
"https://github.com/user-attachments/assets/199b862a-5de4-4a54-83b2-f4dbf69be902": "/blog/assetsb9d1f02ab6c26f8a2c7873a949b4dd3c.webp",
|
||||
"https://github.com/user-attachments/assets/1a7e9600-cd0f-4c82-9d32-4e61bbb351cc": "/blog/assets5997a6461e20103f5bc9d6b78b872833.webp",
|
||||
"https://github.com/user-attachments/assets/1bf1a5f0-32ad-418c-a8d1-6c54740f50b9": "/blog/assets4d0d191b487c114abf084eb7f2dc381c.webp",
|
||||
"https://github.com/user-attachments/assets/1c6a3e42-8e24-4148-b2c3-0bfe60a8cf77": "/blog/assets8096422e62e10dcd58efe75c616f9e88.webp",
|
||||
"https://github.com/user-attachments/assets/1d77cca4-7363-4a46-9ad5-10604e111d7c": "/blog/assets1049abec5850cebf8ce12cd50199b9c5.webp",
|
||||
"https://github.com/user-attachments/assets/1e33aff2-6186-4e1f-80a8-4a2c855d8cc1": "/blog/assets6f2a84bee4245ca507e98e96247d5c5e.webp",
|
||||
"https://github.com/user-attachments/assets/1fb5df18-5261-483e-a445-96f52f80dd20": "/blog/assets69146738e31a47ac6425070208ebd906.webp",
|
||||
"https://github.com/user-attachments/assets/2048b4c2-4a56-4029-acf9-71e35ff08652": "/blog/assets/d9cbfcbef130183bc490d515d8a38aa4.webp",
|
||||
"https://github.com/user-attachments/assets/21c52e2a-b2f8-4de8-a5d4-cf3444608db7": "/blog/assets50607dece1bbffe80fdcbe76324ff9b6.webp",
|
||||
"https://github.com/user-attachments/assets/22e1a039-5e6e-4c40-8266-19821677618a": "/blog/assets89b45345c84f8b7c3bf4d554169689ac.webp",
|
||||
"https://github.com/user-attachments/assets/237864d6-cc5d-4fe4-8a2b-c278016855c5": "/blog/assetsf3e7c2e961d1d2886fe231a4ac59e2f1.webp",
|
||||
"https://github.com/user-attachments/assets/2787824c-a13c-466c-ba6f-820bddfe099f": "/blog/assets/8d6c17a6ea5e784edf4449fb18ca3f76.webp",
|
||||
"https://github.com/user-attachments/assets/28590f7f-bfee-4215-b50b-8feddbf72366": "/blog/assets89a8dadc85902334ce8d2d5b78abf709.webp",
|
||||
"https://github.com/user-attachments/assets/29508dda-2382-430f-bc81-fb23f02149f8": "/blog/assets/29b13dc042e3b839ad8865354afe2fac.webp",
|
||||
"https://github.com/user-attachments/assets/2a4116a7-15ad-43e5-b801-cc62d8da2012": "/blog/assets/37d85fdfccff9ed56e9c6827faee01c7.webp",
|
||||
"https://github.com/user-attachments/assets/2bb4c09d-75bb-4c46-bb2f-faf538308305": "/blog/assetsf0ebf396dbe9559eb3478f48f648a6e2.webp",
|
||||
"https://github.com/user-attachments/assets/2dd3cde5-fa0d-4f52-b82b-28d9e89379a0": "/blog/assets66b0dfa56c1f5b3063b5ba740dd3ef8d.webp",
|
||||
"https://github.com/user-attachments/assets/2f7c5c45-ec6a-4393-8fa9-19a4c5f52f7a": "/blog/assets89168f61edcb2ee92d2ad7064da218b2.webp",
|
||||
"https://github.com/user-attachments/assets/3050839a-cb16-485d-8bae-1bc2f9ade632": "/blog/assetsf117203c39294f45930785d85773c83e.webp",
|
||||
"https://github.com/user-attachments/assets/30c33426-412d-4dec-b096-317fe5880e79": "/blog/assets66829206b15b6c36fa3344835659c041.webp",
|
||||
"https://github.com/user-attachments/assets/328e9755-8da9-4849-8569-e099924822fe": "/blog/assetsf78c85b0a0183a3ae3f2e916d59c0a67.webp",
|
||||
"https://github.com/user-attachments/assets/35164b25-c964-42ce-9cb0-32f6ebe1d07c": "/blog/assetsb6af626eeb0e1e638d80dc9ff7a6eba9.webp",
|
||||
"https://github.com/user-attachments/assets/37251adf-949b-4aec-bc49-bf4647e119da": "/blog/assetscd53b161a6d02424d03f8c5dcadc3dd5.webp",
|
||||
"https://github.com/user-attachments/assets/378df8df-8ec4-436e-8451-fbc52705faee": "/blog/assetsba0243e75b0421b6dd7dadad02e4b0d6.webp",
|
||||
"https://github.com/user-attachments/assets/385eaca6-daea-484a-9bea-ba7270b4753d": "/blog/assets/d6129350de510a62fe87b2d2f0fb9477.webp",
|
||||
"https://github.com/user-attachments/assets/3ad2655e-dd20-4534-bf6d-080b3677df86": "/blog/assets48b5c19e20fb870c7bdd34bd3aefbb21.webp",
|
||||
"https://github.com/user-attachments/assets/3c1a492d-a3d4-4570-9e74-785c2942ca41": "/blog/assets9880145be3e52b8f9dcd8343cd34a6ca.webp",
|
||||
"https://github.com/user-attachments/assets/3d80e0f5-d32a-4412-85b2-e709731460a0": "/blog/assets2d409f43b58953ad5396c6beab8a0719.webp",
|
||||
"https://github.com/user-attachments/assets/3da4c8c4-88c6-40a9-8005-6a0a44aa3b1f": "/blog/assetse717764a3618df4e56212e447a6c20cd.webp",
|
||||
"https://github.com/user-attachments/assets/3ed3226c-3d4c-49ef-b2c0-8953dac8a92e": "/blog/assets7dbd100dac8e2614ef6b297885b3c9e2.webp",
|
||||
"https://github.com/user-attachments/assets/411e2002-61f0-4010-9841-18e88ca895ec": "/blog/assets7c3eab218c0823fa353b1cd23afe21c3.webp",
|
||||
"https://github.com/user-attachments/assets/420379cd-d8a4-4ab3-9a46-75dcc3d56920": "/blog/assets0ca3e3989fb3884658765ee0ef2587a0.webp",
|
||||
"https://github.com/user-attachments/assets/4257e123-9018-4562-ac66-0f39278906f5": "/blog/assetsadbc0db573a0f581b22c30ecf243f721.webp",
|
||||
"https://github.com/user-attachments/assets/433fdce4-0af5-417f-b80d-163c2d4f02f6": "/blog/assets4aaf8d5d092608b649230e0e6fc92df6.webp",
|
||||
"https://github.com/user-attachments/assets/452d0b48-5ff7-4f42-a46e-68a62b87632b": "/blog/assets78232916d13ddc942ab3d0b62b639509.webp",
|
||||
"https://github.com/user-attachments/assets/467bb431-ca0d-4bb4-ac17-e5e2b764a770": "/blog/assetsff480f9009cf873852a43c252ac36828.webp",
|
||||
"https://github.com/user-attachments/assets/484f28f4-017c-4ed7-948b-4a8d51f0b63a": "/blog/assets/5bbb4b421d6df63780b3c7a05f5a102d.webp",
|
||||
"https://github.com/user-attachments/assets/4c792f62-5203-4f13-8f23-df228f70d67f": "/blog/assets94f55c97a24a08c7a5923c23ee2d7eef.webp",
|
||||
"https://github.com/user-attachments/assets/4cbbbcce-36be-48ff-bb0b-31607a0bba5c": "/blog/assetsb33085e7553d2b7194005b102184553e.webp",
|
||||
"https://github.com/user-attachments/assets/4d671a7c-5d94-4c4b-b4fd-71a5a0e9d227": "/blog/assetsc74cf5c8daee1515c37a85bce087f0d6.webp",
|
||||
"https://github.com/user-attachments/assets/4e04928d-0171-48d1-afff-e22fc2faaf4e": "/blog/assetsb26b68a4875a6510ddc202dd4b40d010.webp",
|
||||
"https://github.com/user-attachments/assets/530c7c96-bac3-456d-a429-f60e7d2ade66": "/blog/assets6541bab7e0047f9c5dbad98dc272d64d.webp",
|
||||
"https://github.com/user-attachments/assets/5321f987-2c64-4211-8549-bd30ca9b59b9": "/blog/assetsaf57d31364a41634b10c243ed9b1f8f8.webp",
|
||||
"https://github.com/user-attachments/assets/533f7a5e-8a93-4a57-a62f-8233897d72b5": "/blog/assets/9498087e85f27e692716a63cb3b58d79.webp",
|
||||
"https://github.com/user-attachments/assets/539349dd-2c16-4f42-b525-cca74e113541": "/blog/assetsd8927338578c426b833e5cb57e0b57ec.webp",
|
||||
"https://github.com/user-attachments/assets/55028fe5-44db-49e2-93c5-5dabbd664f10": "/blog/assets8f3458d794828c38220e88b66e994e2a.webp",
|
||||
"https://github.com/user-attachments/assets/55230f32-b8dd-47db-a2ba-b3fe7e533dc8": "/blog/assetsc1d4290f05fe474dba74577409cad6e9.webp",
|
||||
"https://github.com/user-attachments/assets/5abcf21d-5a6c-4fc8-8de6-bc47d4d2fa98": "/blog/assetsbd39adddc9a1cdb85ce4a0e37fa595c1.webp",
|
||||
"https://github.com/user-attachments/assets/5b816379-c07b-40ea-bde4-df16e2e4e523": "/blog/assets2d41542b390020209bbd5814009abcdf.webp",
|
||||
"https://github.com/user-attachments/assets/5d672e8b-566f-4f82-bdce-947168726bc0": "/blog/assetsd89998edb6b2dc8311d8d86664d5cd4d.webp",
|
||||
"https://github.com/user-attachments/assets/5ea37821-4ea8-437c-a15e-3b182d10f19e": "/blog/assets273112caa08528852992b81dd8f3b75d.webp",
|
||||
"https://github.com/user-attachments/assets/5f344314-ecbc-41e6-9120-520a2d5352ff": "/blog/assets01dbe69cc092163f7ac782afb7d314c5.webp",
|
||||
"https://github.com/user-attachments/assets/5fe4c373-ebd0-42a9-bdca-0ab7e0a2e747": "/blog/assets18168d5fe64ea34905a7e52fd82d0e9d.webp",
|
||||
"https://github.com/user-attachments/assets/6069332b-8e15-4d3c-8a77-479e8bc09c23": "/blog/assets/603fefbb944bc6761ebdab5956fc0084.webp",
|
||||
"https://github.com/user-attachments/assets/6234428d-5633-4b2f-be22-1a1772a69a55": "/blog/assets67a17a6c66592ad85dbcf190e73b182d.webp",
|
||||
"https://github.com/user-attachments/assets/629adf4e-e9e1-40dc-b9e5-d7b908878170": "/blog/assets257e1a3a0d99ee043a4c6cb90e160a2b.webp",
|
||||
"https://github.com/user-attachments/assets/635f1c74-6327-48a8-a8d9-68d7376c7749": "/blog/assets/f6d047a345e47a52592cff916c9a64ce.webp",
|
||||
"https://github.com/user-attachments/assets/638dcd7c-2bff-4adb-bade-da2aaef872bf": "/blog/assets95e6fe7c19ebfb9ead1c5a267aaf2a4e.webp",
|
||||
"https://github.com/user-attachments/assets/639ed70b-abc5-476f-9eb0-10c739e5a115": "/blog/assets/b2845057b23bccfec3bfea90e43ac381.webp",
|
||||
"https://github.com/user-attachments/assets/63e5ced7-1d23-44e1-b933-cc3b5df47eab": "/blog/assets5f1a6cb003752055b9ed131c1715154c.webp",
|
||||
"https://github.com/user-attachments/assets/659b5ac1-82f1-43bd-9d4b-a98491e05794": "/blog/assets856bd407c8a1510f616a4bdb1e02a883.webp",
|
||||
"https://github.com/user-attachments/assets/669c68bf-3f85-4a6f-bb08-d0d7fb7f7417": "/blog/assets02dce7325584974cdba327fe2f996b9e.webp",
|
||||
"https://github.com/user-attachments/assets/692e7c67-f173-45da-86ef-5c69e17988e4": "/blog/assets6b01801b405c366fa4ebe683a77f289d.webp",
|
||||
"https://github.com/user-attachments/assets/6935e155-4a1d-4ab7-a61a-2b813d65bb7b": "/blog/assets/6ee2609d79281b6b915e317461013f31.webp",
|
||||
"https://github.com/user-attachments/assets/6d068fe0-8100-4b43-b0c3-7934f54e688f": "/blog/assets87c281587b15f05b6b4e1afcd5bb47e8.webp",
|
||||
"https://github.com/user-attachments/assets/6dbf4560-3f62-4b33-9f41-96e12b5087b1": "/blog/assets03f3f52817a626339071e6329b445cb3.webp",
|
||||
"https://github.com/user-attachments/assets/6e383b75-09e3-42d1-8a6c-5fb7cf558f00": "/blog/assets15ecc1bbe365f3e02702631e28c7b764.webp",
|
||||
"https://github.com/user-attachments/assets/6f9f400a-72e0-49de-94cb-5069fddf1163": "/blog/assets9db16311eb6772ea74eb63dd2d397bc0.webp",
|
||||
"https://github.com/user-attachments/assets/702c191f-8250-4462-aed7-accb18b18dea": "/blog/assetsd56d1af67bb2be60b0c580be0a6c7110.webp",
|
||||
"https://github.com/user-attachments/assets/71035610-0706-434e-9488-ab5819b55330": "/blog/assets18bb134dbc5792d6a624199cca8bf7d3.webp",
|
||||
"https://github.com/user-attachments/assets/7239d611-1989-414b-a51c-444e47096d75": "/blog/assets8669131e67e5276fe0744754ba4b1645.webp",
|
||||
"https://github.com/user-attachments/assets/7257eb0e-4e2c-4db2-981d-354598e2c60f": "/blog/assets2ad69e4e124f49710fcedf8e9827f2f3.webp",
|
||||
"https://github.com/user-attachments/assets/72da7af1-e180-4759-84a5-a6f6ca28392e": "/blog/assets688e6e10904ad46cf7f44bba6359f90c.webp",
|
||||
"https://github.com/user-attachments/assets/72f02ce5-9991-425b-9864-9113ee1ed6bf": "/blog/assetsfa2c650be15522ac2fd71a3e434a1b2e.webp",
|
||||
"https://github.com/user-attachments/assets/7350f211-61ce-488e-b0e2-f0fcac25caeb": "/blog/assetsf9ed064fe764cbeff2f46910e7099a91.webp",
|
||||
"https://github.com/user-attachments/assets/76ad163e-ee19-4f95-a712-85bea764d3ec": "/blog/assets5205b6dd0f80b8ba02c297fcdfc1aecb.webp",
|
||||
"https://github.com/user-attachments/assets/796c94af-9bad-4e3c-b1c7-dbb17c215c56": "/blog/assetsbd8c97ef67055e3ff93c56e46c33fa8d.webp",
|
||||
"https://github.com/user-attachments/assets/798ddb18-50c7-462a-a083-0c6841351d26": "/blog/assets11a8089b511aaa61e8982dea0a3665c5.webp",
|
||||
"https://github.com/user-attachments/assets/7cb3019b-78c1-48e0-a64c-a6a4836affd9": "/blog/assets3ca963d92475f34b0789cfa50071bc52.webp",
|
||||
"https://github.com/user-attachments/assets/808f8849-5738-4a60-8ccf-01e300b0dc88": "/blog/assets0f893c504377ba45a9f5cdbb5ccb1612.webp",
|
||||
"https://github.com/user-attachments/assets/81d0349a-44fe-4dfc-bbc4-8e9a1e09567d": "/blog/assets29de82efbe7657a8b9ba7daf0904585d.webp",
|
||||
"https://github.com/user-attachments/assets/82a7ebe0-69ad-43b6-8767-1316b443fa03": "/blog/assets5374759bfe39ca7fc864e72ddfce98d0.webp",
|
||||
"https://github.com/user-attachments/assets/82bfc467-e0c6-4d99-9b1f-18e4aea24285": "/blog/assets/eb477e62217f4d1b644eff975c7ac168.webp",
|
||||
"https://github.com/user-attachments/assets/840442b1-bf56-4a5f-9700-b3608b16a8a5": "/blog/assetsc6ff27b7134f280727e1fd7ff83ed2fa.webp",
|
||||
"https://github.com/user-attachments/assets/84a5c971-1262-4639-b79f-c8b138530803": "/blog/assetsb09a1f1dc99b86343ae196fcfdcc3fe1.webp",
|
||||
"https://github.com/user-attachments/assets/8570db14-dac6-4279-ab71-04a072c15490": "/blog/assetsc376d2e9e97f9ea9d788589f0a9e23d6.webp",
|
||||
"https://github.com/user-attachments/assets/868df2eb-0c44-4419-a76a-e173094e1e17": "/blog/assetsf3ccd42bf36b1c75f06f925ffe049f0c.webp",
|
||||
"https://github.com/user-attachments/assets/872756dc-305e-4e63-9fb7-60550280fc12": "/blog/assets56e5331e7fae3754820790c824cdc480.webp",
|
||||
"https://github.com/user-attachments/assets/8787716c-833e-44ab-b506-922ddb6121de": "/blog/assets217222e643d99ab3ba01fe92906f3314.webp",
|
||||
"https://github.com/user-attachments/assets/88e14294-20a6-47c6-981e-fb65453b57cd": "/blog/assets6ef9f3f3627633bb5282fe9df1d31a4a.webp",
|
||||
"https://github.com/user-attachments/assets/8910186f-4609-4798-a588-2780dcf8db60": "/blog/assets4175fc55c2093d635f15a3287e89e977.webp",
|
||||
"https://github.com/user-attachments/assets/899a4393-db41-45a6-97ec-9813e1f9879d": "/blog/assets88248c034ef28ca9b909219d2e7ef32a.webp",
|
||||
"https://github.com/user-attachments/assets/8a0225e0-16ed-40ce-9cd5-553dda561679": "/blog/assets74fbd94a0dc865d2178954662dc964ae.webp",
|
||||
"https://github.com/user-attachments/assets/8ce79bd6-f1a3-48bb-b3d0-5271c84801c2": "/blog/assets5f8cc99da9c3c1eaca284411833c99e3.webp",
|
||||
"https://github.com/user-attachments/assets/8d90ae64-cf8e-4d90-8a31-c18ab484740b": "/blog/assets04ab03ac7920031925f7ee27846b3f7d.webp",
|
||||
"https://github.com/user-attachments/assets/8ec7656e-1e3d-41e0-95a0-f6883135c2fc": "/blog/assets71b5cfd165bc907f437bf807048a3e67.webp",
|
||||
"https://github.com/user-attachments/assets/91fe32a8-e5f0-47ff-b8ae-d036c8a7bff1": "/blog/assets1837dd567f75fcc083553a1078c0f088.webp",
|
||||
"https://github.com/user-attachments/assets/9336d6c5-2a83-4aa9-854e-75e245b665cb": "/blog/assetsc16177645281b332883403e7f193f6e3.webp",
|
||||
"https://github.com/user-attachments/assets/97899819-278f-42fd-804a-144d521d4b4f": "/blog/assets7006b60baaf62aa0d95cd40456e24afe.webp",
|
||||
"https://github.com/user-attachments/assets/9a78bbb9-7c96-4f32-9b66-e57f92660410": "/blog/assets0e9c7125960a2d00b8c3c3d15d88f0a7.webp",
|
||||
"https://github.com/user-attachments/assets/9b70b292-6c52-4715-b844-ff5df78d16b9": "/blog/assetsbfe7d519c29884b6699e89866e1db7e2.webp",
|
||||
"https://github.com/user-attachments/assets/9baacac6-5af4-460b-862d-682b76c18459": "/blog/assets195200c7bc42360675e78a6bfa9fe320.webp",
|
||||
"https://github.com/user-attachments/assets/9cb27b68-f2ac-4ff9-8f97-d96314b1af03": "/blog/assetsd3fefc9a525701b9d0f25116cea2ff00.webp",
|
||||
"https://github.com/user-attachments/assets/9f989104-bb8e-4acd-9721-6b1db1017d2b": "/blog/assets5d3551635c580d8781e31256e1fb0f2e.webp",
|
||||
"https://github.com/user-attachments/assets/a00f06cc-da7c-41e8-a4d5-d4b675a22673": "/blog/assetse0d53ba2bfb6ba5bf33f2b8a547f4e41.webp",
|
||||
"https://github.com/user-attachments/assets/a1af5778-f47a-4fdc-baf5-ca2a1e66f48e": "/blog/assets97ac48dab1a35e45e034fefe0a1a1006.webp",
|
||||
"https://github.com/user-attachments/assets/a1ba8ec0-e259-4da4-8980-0cf82ca5f52b": "/blog/assetsbd69842ebb37848ecd50c242aad835b0.webp",
|
||||
"https://github.com/user-attachments/assets/a42ba52b-491e-4993-8e2f-217aa1776e0f": "/blog/assets0f847842a5dedf7bef1f534278aec584.webp",
|
||||
"https://github.com/user-attachments/assets/a53deb11-2c14-441a-8a5c-a0f3a74e2a63": "/blog/assets65c86d6e63ddd5dd9896a6a67c054c0d.webp",
|
||||
"https://github.com/user-attachments/assets/a9de7780-d0cb-47d5-ad9c-fcbbec14b940": "/blog/assets79e8fff075490d2a4535590a02333316.webp",
|
||||
"https://github.com/user-attachments/assets/aa91ca54-65fc-4e33-8c76-999f0a5d2bee": "/blog/assetsf625540e8340bafe69ccbb89ad75707a.webp",
|
||||
"https://github.com/user-attachments/assets/aaa3e2c5-7f16-4cfb-86b6-2814a1aafe3a": "/blog/assets93da89c4892a80e2e5a6caa49d80af5f.webp",
|
||||
"https://github.com/user-attachments/assets/ab87120c-15ff-4bc7-bb28-4b0b43cfe91a": "/blog/assetsec0f694c9f6140620217bde441440170.webp",
|
||||
"https://github.com/user-attachments/assets/ae03eab5-a319-4d2a-a5f6-1683ab7739ee": "/blog/assetsa25c48c9faa225bf6f72658e5bd58d64.webp",
|
||||
"https://github.com/user-attachments/assets/aea782b1-27bd-4d9c-b521-c172c2095fe6": "/blog/assets52c8de6425a785409464561c09f8c98d.webp",
|
||||
"https://github.com/user-attachments/assets/aead3c6c-891e-47c3-9f34-bdc33875e0c2": "/blog/assetsb6959f725c38f86053e4b07c9188d825.webp",
|
||||
"https://github.com/user-attachments/assets/aee846d5-b5ee-46cb-9dd0-d952ea708b67": "/blog/assets/8a8d361b4c0cce6da350cc0de65c0ad6.webp",
|
||||
"https://github.com/user-attachments/assets/b2b36128-6a43-4a1f-9c08-99fe73fb565f": "/blog/assets85af5a2a51b851fe125055d374cc8263.webp",
|
||||
"https://github.com/user-attachments/assets/b3ab6e35-4fbc-468d-af10-e3e0c687350f": "/blog/assets4cd6d49afb0ab1354156961d396195a1.webp",
|
||||
"https://github.com/user-attachments/assets/b49ed0c1-d6bf-4f46-b9df-5f7c730afaa3": "/blog/assets74000cc1bc59ee4a15e8f0304afbf866.webp",
|
||||
"https://github.com/user-attachments/assets/b4e89dd4-877b-43fe-aa42-4680de17ba8e": "/blog/assets1b9283f9cc5fc5073ff9cffc24880e96.webp",
|
||||
"https://github.com/user-attachments/assets/b6e6a3eb-13c6-46f0-9c7c-69a20deae30f": "/blog/assets768ec6fd300785186b202437985857c4.webp",
|
||||
"https://github.com/user-attachments/assets/b824b741-f2d8-42c8-8cb9-1266862affa7": "/blog/assets89d0dcbf5ffccd21086845cea3a514cc.webp",
|
||||
"https://github.com/user-attachments/assets/b9da065e-f964-44f2-8260-59e182be2729": "/blog/assets80a8b9627374fc345f4bf8e3adf11074.webp",
|
||||
"https://github.com/user-attachments/assets/bd399cef-283c-4706-bdc8-de9de662de41": "/blog/assets4224bf4978bea84e82b3b3aec77656f0.webp",
|
||||
"https://github.com/user-attachments/assets/bd6d0c82-8f14-4167-ad09-2a841f1e34e4": "/blog/assets/d7e57f8e69f97b76b3c2414f3441b6e4.webp",
|
||||
"https://github.com/user-attachments/assets/be06e348-8d4c-440c-b59f-b71120f21335": "/blog/assetsd9f99f2adff9051313ca44205b022d8c.webp",
|
||||
"https://github.com/user-attachments/assets/be7dcd49-0165-4f7b-bf90-0739cc9dd212": "/blog/assetsf069368b9162f58247318dde850c0807.webp",
|
||||
"https://github.com/user-attachments/assets/bfda556a-d3fc-409f-8647-e718788f2fb8": "/blog/assets2cfe64ead120815f7ba7100bc3dcfd48.webp",
|
||||
"https://github.com/user-attachments/assets/c44b6894-70cb-4876-b792-2e76e75ac542": "/blog/assets94499977be2f01c795b9876e4fe60709.webp",
|
||||
"https://github.com/user-attachments/assets/c4fe4430-7860-4339-b014-4d8d264a12c0": "/blog/assets87010372bdf39890a7478a7a8cd4a9f0.webp",
|
||||
"https://github.com/user-attachments/assets/c6319e83-c4e7-48cf-9625-2edfc4aa77b3": "/blog/assetsfae60ba54155478a1c363f0065ce76a6.webp",
|
||||
"https://github.com/user-attachments/assets/c68e88e4-cf2e-4122-82bc-89ba193b1eb4": "/blog/assets/1f6c4f1c5e6211735ca4924c7807aca1.webp",
|
||||
"https://github.com/user-attachments/assets/c75eb19e-e0f5-4135-91e4-55be8be8a996": "/blog/assets0f97d1dfccd5ba07172aff71ff9acd7b.webp",
|
||||
"https://github.com/user-attachments/assets/c77fcf70-9039-49ff-86e4-f8eaa267bbf6": "/blog/assets5a2f360c19fcf9a037b2d1609479b713.webp",
|
||||
"https://github.com/user-attachments/assets/cb4ba5fe-c223-4b9f-a662-de93e4a536d1": "/blog/assets45d90e73abffd7ae7d85808f81827bb9.webp",
|
||||
"https://github.com/user-attachments/assets/cc1f6146-8063-4a4d-947a-7fd6b9133c0c": "/blog/assets28749075f0c4d62c1642694a4ed9ec08.webp",
|
||||
"https://github.com/user-attachments/assets/cf3bfd44-9c13-4026-95cd-67f54f40ce6c": "/blog/assetsc557d9ee77afeb958d198abf5ca79761.webp",
|
||||
"https://github.com/user-attachments/assets/d0a5e152-160a-4862-8393-546f4e2e5387": "/blog/assets06d4e543cbaca9a2762923a23b2cae67.webp",
|
||||
"https://github.com/user-attachments/assets/d3626294-74ba-4944-9a63-052e6cf719ab": "/blog/assets0f244d5fe648127774636a54ae9ffafc.webp",
|
||||
"https://github.com/user-attachments/assets/d524c20d-306a-45bc-971b-96920b87fab4": "/blog/assetsbeefe4dbe3e6f141e09c62064c6dc397.webp",
|
||||
"https://github.com/user-attachments/assets/d643af6d-ca0f-4abd-9dd2-977dacecb25d": "/blog/assets34424062ad6ab98df7f56c9e61341be5.webp",
|
||||
"https://github.com/user-attachments/assets/d693be02-e08c-43ae-8bde-1294f180aaf6": "/blog/assets4169b5d9f7534f9f89c8426445e9a080.webp",
|
||||
"https://github.com/user-attachments/assets/d6ace96f-0398-4847-83e1-75c3004a0e8b": "/blog/assetsf7007eebef93bc1d8a29aaf9080ab404.webp",
|
||||
"https://github.com/user-attachments/assets/d7666e2a-0202-4b45-8338-9806ddffa44e": "/blog/assets8f95f09ce51ad5917107d84db1e980ab.webp",
|
||||
"https://github.com/user-attachments/assets/d7d65e32-679d-4e50-a933-28cf5dde1330": "/blog/assetsc51018f1581b769727ad1bb3bb641567.webp",
|
||||
"https://github.com/user-attachments/assets/d902b5df-edb1-48d6-b659-daf948a97aed": "/blog/assets1e640c898e897bfb4ce4b66d5377010b.webp",
|
||||
"https://github.com/user-attachments/assets/d961f2af-47b0-4806-8288-b1e8f7ee8a47": "/blog/assets9c1839eb146b89e9e2d262ca95d24323.webp",
|
||||
"https://github.com/user-attachments/assets/db59a5e7-32ed-49d7-a791-8f8ee6618c01": "/blog/assetsf601ee6fa15bed25e17d6b6879691f0f.webp",
|
||||
"https://github.com/user-attachments/assets/dba58ea6-7df8-4971-b6d4-b24d5f486ba7": "/blog/assetsbbe90aa719d182d3d2f327e4182732c5.webp",
|
||||
"https://github.com/user-attachments/assets/dd6bc4a4-3c20-4162-87fd-5cac57e5d7e7": "/blog/assetseebf66254337ce88357629c34e78c08d.webp",
|
||||
"https://github.com/user-attachments/assets/dde2c9c5-cdda-4a65-8f32-b6f4da907df2": "/blog/assets/d47654360d626f80144cdedb979a3526.webp",
|
||||
"https://github.com/user-attachments/assets/dec6665a-b3ec-4c50-a57f-7c7eb3160e7b": "/blog/assets8d4fbb776e2209a1ec58c6b3516351a1.webp",
|
||||
"https://github.com/user-attachments/assets/dfc45807-2ed6-43eb-af4c-47df66dfff7d": "/blog/assetscad58c557fda04b9379000cbbaa4c493.webp",
|
||||
"https://github.com/user-attachments/assets/e269bd27-d323-43ba-811b-c0f5e4137903": "/blog/assetse12925fba0dda232168e695e6a5e4384.webp",
|
||||
"https://github.com/user-attachments/assets/e3f44bc8-2fa5-441d-8934-943481472450": "/blog/assets3c54d6f2d55fae843fbbfdc0bd7ffec7.webp",
|
||||
"https://github.com/user-attachments/assets/e43dacf6-313e-499c-8888-f1065c53e424": "/blog/assets89b0698da3476c6df24ba1f0a07e438e.webp",
|
||||
"https://github.com/user-attachments/assets/e617def1-ce50-4acc-974b-12f5ed592a0e": "/blog/assets3386e7adc46d19be5cc6dae46533d9bd.webp",
|
||||
"https://github.com/user-attachments/assets/e70c2db6-05c9-43ea-b111-6f6f99e0ae88": "/blog/assets/944c671604833cd2457445b211ebba33.webp",
|
||||
"https://github.com/user-attachments/assets/e887fa04-c553-45f1-917f-5c123ac9c68b": "/blog/assets73ba166f1e6d54e8c860b91f61c23355.webp",
|
||||
"https://github.com/user-attachments/assets/e89d2a56-4bf0-4bff-ac39-0d44789fa858": "/blog/assets9f6d4113be26efbcab41d83ed39dcb14.webp",
|
||||
"https://github.com/user-attachments/assets/eaa2a1fb-41ad-473d-ac10-a39c05886425": "/blog/assetsf5a62c963127764ebdf1cd226fac3dac.webp",
|
||||
"https://github.com/user-attachments/assets/eaed3762-136f-4297-b161-ca92a27c4982": "/blog/assets/50b38eac1769ae6f13aef72f3d725eec.webp",
|
||||
"https://github.com/user-attachments/assets/eb027093-5ceb-4a9d-8850-b791fbf69a71": "/blog/assetsd0c4369f894abb5ad6e514059b8f378e.webp",
|
||||
"https://github.com/user-attachments/assets/eb3f3d8a-79ce-40aa-a206-2c846206c0c0": "/blog/assets/f10a4b98782e36797c38071eed785c6f.webp",
|
||||
"https://github.com/user-attachments/assets/fa8fab19-ace2-4f85-8428-a3a0e28845bb": "/blog/assets/2d678631c55369ba7d753c3ffcb73782.webp"
|
||||
"https://github.com/user-attachments/assets/eb41f77f-ccdd-4a48-a8a2-7badac868c03": "/blog/assets0a81d34f707bd87cee3852f26a3d14f0.webp",
|
||||
"https://github.com/user-attachments/assets/ebdbc01a-a6b5-4bbc-b7ff-240d6015fbfc": "/blog/assets13656829368732a95940edeff9ddfca6.webp",
|
||||
"https://github.com/user-attachments/assets/ed6965c8-6884-4adf-a457-573a96755f55": "/blog/assets2f83a9f03f13e73b7393641078627cf1.webp",
|
||||
"https://github.com/user-attachments/assets/f0b2e72d-9eee-46a8-b094-4834b78764df": "/blog/assets8d6bb40d21d74cfa0312bdec347a11d0.webp",
|
||||
"https://github.com/user-attachments/assets/f3068287-8ade-4eca-9841-ea67d8ff1226": "/blog/assetsa343af49a2d7da73a3fa51f2086afdd4.webp",
|
||||
"https://github.com/user-attachments/assets/f3177ce2-281c-4ed4-a061-239547b466c6": "/blog/assets86924c724c66931cf61417dbdcc04ee8.webp",
|
||||
"https://github.com/user-attachments/assets/f4dbbadb-7461-4370-a836-09c487fdd206": "/blog/assets94397c91265c37b9f313dc439b90125f.webp",
|
||||
"https://github.com/user-attachments/assets/f54c912d-3ee9-4f85-b8bf-619790e51b49": "/blog/assets620c308554394e72034d27ea743f8bff.webp",
|
||||
"https://github.com/user-attachments/assets/f67180c2-47ba-4b04-9f12-d274c7821085": "/blog/assetscbda3a61a2d158eeb6046e1d1bf9972f.webp",
|
||||
"https://github.com/user-attachments/assets/f878355f-710b-452e-8606-0c75c47f29d2": "/blog/assets3e2af0090f02059c687b6add6b73a90b.webp",
|
||||
"https://github.com/user-attachments/assets/f9ccce84-4fd4-48ca-9450-40660112d0d7": "/blog/assetsd94f3e0cf32639bea46dbf92e0862f89.webp",
|
||||
"https://github.com/user-attachments/assets/f9f7ed26-e506-4c52-a118-e0bb5e0918db": "/blog/assetse5dff9a2e16a134d85e891e4eb98fe55.webp",
|
||||
"https://github.com/user-attachments/assets/fa8fab19-ace2-4f85-8428-a3a0e28845bb": "/blog/assets/2d678631c55369ba7d753c3ffcb73782.webp",
|
||||
"https://github.com/user-attachments/assets/facdc83c-e789-4649-8060-7f7a10a1b1dd": "/blog/assets05b20e40c03ced0ec8707fed2e8e0f25.webp",
|
||||
"https://github.com/user-attachments/assets/fcdfb9c5-819a-488f-b28d-0857fe861219": "/blog/assets8477415ecec1f37e38ab38ff1217d0a7.webp"
|
||||
}
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
title: LobeChat Plugin Ecosystem - Functionality Extensions and Development Resources
|
||||
title: LobeHub Plugin Ecosystem - Functionality Extensions and Development Resources
|
||||
description: >-
|
||||
Discover how the LobeChat plugin ecosystem enhances the utility and
|
||||
flexibility of the LobeChat assistant, along with the development resources
|
||||
and plugin development guidelines provided.
|
||||
Discover how the LobeHub plugin ecosystem enhances the utility and flexibility
|
||||
of the LobeHub assistant, along with the development resources and plugin
|
||||
development guidelines provided.
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- Plugins
|
||||
- Real-time Information
|
||||
- Voice Options
|
||||
|
|
@ -13,11 +13,11 @@ tags:
|
|||
|
||||
# Supported Plugin System
|
||||
|
||||
The LobeChat plugin ecosystem is a significant extension of its core functionalities, greatly enhancing the utility and flexibility of the LobeChat assistant.
|
||||
The LobeHub plugin ecosystem is a significant extension of its core functionalities, greatly enhancing the utility and flexibility of the LobeHub assistant.
|
||||
|
||||
<Video src="https://github.com/lobehub/lobe-chat/assets/28616219/f29475a3-f346-4196-a435-41a6373ab9e2" />
|
||||
<Video src="/blog/assets/28616219/f29475a3-f346-4196-a435-41a6373ab9e2.mp4" />
|
||||
|
||||
By leveraging plugins, the LobeChat assistants are capable of accessing and processing real-time information, such as searching online for data and providing users with timely and relevant insights.
|
||||
By leveraging plugins, the LobeHub assistants are capable of accessing and processing real-time information, such as searching online for data and providing users with timely and relevant insights.
|
||||
|
||||
Moreover, these plugins are not solely limited to news aggregation; they can also extend to other practical functionalities, such as quickly retrieving documents, generating images, obtaining data from various platforms such as Bilibili and Steam, and interacting with an array of third-party services.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: LobeChat 插件生态系统 - 功能扩展与开发资源
|
||||
description: 了解 LobeChat 插件生态系统如何增强 LobeChat 助手的实用性和灵活性，以及提供的开发资源和插件开发指南。
|
||||
title: LobeHub 插件生态系统 - 功能扩展与开发资源
|
||||
description: 了解 LobeHub 插件生态系统如何增强 LobeHub 助手的实用性和灵活性，以及提供的开发资源和插件开发指南。
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- 插件系统
|
||||
- 实时信息
|
||||
- 第三方服务
|
||||
|
|
@ -10,11 +10,11 @@ tags:
|
|||
|
||||
# 支持插件系统
|
||||
|
||||
LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地增强了 LobeChat 助手的实用性和灵活性。
|
||||
LobeHub 的插件生态系统是其核心功能的重要扩展，它极大地增强了 LobeHub 助手的实用性和灵活性。
|
||||
|
||||
<Video src="https://github.com/lobehub/lobe-chat/assets/28616219/f29475a3-f346-4196-a435-41a6373ab9e2" />
|
||||
<Video src="/blog/assets/28616219/f29475a3-f346-4196-a435-41a6373ab9e2.mp4" />
|
||||
|
||||
通过利用插件，LobeChat 的助手们能够实现实时信息的获取和处理，例如搜索网络信息，为用户提供即时且相关的资讯。
|
||||
通过利用插件，LobeHub 的助手们能够实现实时信息的获取和处理，例如搜索网络信息，为用户提供即时且相关的资讯。
|
||||
|
||||
此外，这些插件不仅局限于新闻聚合，还可以扩展到其他实用的功能，如快速检索文档、生成图片、获取 Bilibili 、Steam 等各种平台数据，以及与其他各式各样的第三方服务交互。
|
||||
|
||||
|
|
|
|||
|
|
@ -1,15 +1,15 @@
|
|||
---
|
||||
title: >-
|
||||
LobeChat Supports Multimodal Interaction: Visual Recognition Enhances
|
||||
LobeHub Supports Multimodal Interaction: Visual Recognition Enhances
|
||||
Intelligent Dialogue
|
||||
description: >-
|
||||
LobeChat supports various large language models with visual recognition
|
||||
LobeHub supports various large language models with visual recognition
|
||||
capabilities, allowing users to upload or drag and drop images. The assistant
|
||||
will recognize the content and engage in intelligent dialogue, creating a more
|
||||
intelligent and diverse chat environment.
|
||||
tags:
|
||||
- Visual Recognition
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- GPT-4 Vision
|
||||
- Google Gemini Pro
|
||||
- Multimodal Interaction
|
||||
|
|
@ -17,6 +17,6 @@ tags:
|
|||
|
||||
# Supported Models for Visual Recognition
|
||||
|
||||
LobeChat now supports several large language models with visual recognition capabilities, including OpenAI's [`gpt-4-vision`](https://platform.openai.com/docs/guides/vision), Google Gemini Pro vision, and Zhiyuan GLM-4 Vision. This empowers LobeChat with multimodal interaction capabilities. Users can effortlessly upload images or drag and drop them into the chat window, where the assistant can recognize the image content and engage in intelligent dialogue, building a smarter and more diverse chat experience.
|
||||
LobeHub now supports several large language models with visual recognition capabilities, including OpenAI's [`gpt-4-vision`](https://platform.openai.com/docs/guides/vision), Google Gemini Pro vision, and Zhiyuan GLM-4 Vision. This empowers LobeHub with multimodal interaction capabilities. Users can effortlessly upload images or drag and drop them into the chat window, where the assistant can recognize the image content and engage in intelligent dialogue, building a smarter and more diverse chat experience.
|
||||
|
||||
This feature opens up new avenues for interaction, allowing communication that extends beyond text to include rich visual elements. Whether sharing images during everyday use or interpreting graphics in specific industries, the assistant delivers an exceptional conversational experience. Additionally, we have carefully selected a range of high-quality voice options (OpenAI Audio, Microsoft Edge Speech) to cater to users from different regions and cultural backgrounds. Users can choose a suitable voice based on personal preferences or specific contexts, thus receiving a more personalized communication experience.
|
||||
|
|
|
|||
|
|
@ -1,16 +1,16 @@
|
|||
---
|
||||
title: LobeChat 支持多模态交互：视觉识别助力智能对话
|
||||
description: LobeChat 支持多种具有视觉识别能力的大语言模型，用户可上传或拖拽图片，助手将识别内容并展开智能对话，打造更智能、多元化的聊天场景。
|
||||
title: LobeHub 支持多模态交互：视觉识别助力智能对话
|
||||
description: LobeHub 支持多种具有视觉识别能力的大语言模型，用户可上传或拖拽图片，助手将识别内容并展开智能对话，打造更智能、多元化的聊天场景。
|
||||
tags:
|
||||
- 视觉识别
|
||||
- 多模态交互
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- GPT-4
|
||||
- Google Gemini Pro
|
||||
---
|
||||
|
||||
# 支持模型视觉识别
|
||||
|
||||
LobeChat 已经支持 OpenAI 的 [`gpt-4-vision`](https://platform.openai.com/docs/guides/vision) 、Google Gemini Pro vision、智谱 GLM-4 Vision 等具有视觉识别能力的大语言模型，这使得 LobeChat 具备了多模态交互的能力。用户可以轻松上传图片或者拖拽图片到对话框中，助手将能够识别图片内容，并在此基础上进行智能对话，构建更智能、更多元化的聊天场景。
|
||||
LobeHub 已经支持 OpenAI 的 [`gpt-4-vision`](https://platform.openai.com/docs/guides/vision) 、Google Gemini Pro vision、智谱 GLM-4 Vision 等具有视觉识别能力的大语言模型，这使得 LobeHub 具备了多模态交互的能力。用户可以轻松上传图片或者拖拽图片到对话框中，助手将能够识别图片内容，并在此基础上进行智能对话，构建更智能、更多元化的聊天场景。
|
||||
|
||||
这一特性打开了新的互动方式，使得交流不再局限于文字，而是可以涵盖丰富的视觉元素。无论是日常使用中的图片分享，还是在特定行业内的图像解读，助手都能提供出色的对话体验。，我们精心挑选了一系列高品质的声音选项 (OpenAI Audio, Microsoft Edge Speech)，以满足不同地域和文化背景用户的需求。用户可以根据个人喜好或者特定场景来选择合适的语音，从而获得个性化的交流体验。
|
||||
|
|
|
|||
|
|
@ -1,19 +1,19 @@
|
|||
---
|
||||
title: LobeChat Text-to-Image Generation Technology
|
||||
title: LobeHub Text-to-Image Generation Technology
|
||||
description: >-
|
||||
LobeChat supports Text-to-Speech (TTS) and Speech-to-Text (STT) technologies,
|
||||
LobeHub supports Text-to-Speech (TTS) and Speech-to-Text (STT) technologies,
|
||||
offering high-quality voice options for a personalized communication
|
||||
experience. Learn more about Lobe TTS Toolkit.
|
||||
tags:
|
||||
- TTS
|
||||
- STT
|
||||
- Voice Conversations
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- Audio Technology
|
||||
---
|
||||
|
||||
# Supporting TTS & STT Voice Conversations
|
||||
|
||||
LobeChat supports Text-to-Speech (TTS) and Speech-to-Text (STT) technologies, allowing our application to transform textual information into clear voice output. Users can interact with our conversational agents as if they were talking to a real person. There are various voice options for users to choose from, providing the right audio source for their assistant. Additionally, for those who prefer auditory learning or seek to gain information while on the go, TTS offers an excellent solution.
|
||||
LobeHub supports Text-to-Speech (TTS) and Speech-to-Text (STT) technologies, allowing our application to transform textual information into clear voice output. Users can interact with our conversational agents as if they were talking to a real person. There are various voice options for users to choose from, providing the right audio source for their assistant. Additionally, for those who prefer auditory learning or seek to gain information while on the go, TTS offers an excellent solution.
|
||||
|
||||
In LobeChat, we have carefully curated a selection of high-quality voice options (OpenAI Audio, Microsoft Edge Speech) to cater to users from different regions and cultural backgrounds. Users can select suitable voices based on personal preferences or specific scenarios, thus achieving a personalized communication experience.
|
||||
In LobeHub, we have carefully curated a selection of high-quality voice options (OpenAI Audio, Microsoft Edge Speech) to cater to users from different regions and cultural backgrounds. Users can select suitable voices based on personal preferences or specific scenarios, thus achieving a personalized communication experience.
|
||||
|
|
|
|||
|
|
@ -1,17 +1,17 @@
|
|||
---
|
||||
title: LobeChat 文生图：文本转图片生成技术
|
||||
description: LobeChat 支持文字转语音（TTS）和语音转文字（STT）技术，提供高品质声音选项，个性化交流体验。了解更多关于 Lobe TTS 工具包。
|
||||
title: LobeHub 文生图：文本转图片生成技术
|
||||
description: LobeHub 支持文字转语音（TTS）和语音转文字（STT）技术，提供高品质声音选项，个性化交流体验。了解更多关于 Lobe TTS 工具包。
|
||||
tags:
|
||||
- TTS
|
||||
- STT
|
||||
- 语音会话
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- 文字转语音
|
||||
- 语音转文字
|
||||
---
|
||||
|
||||
# 支持 TTS & STT 语音会话
|
||||
|
||||
LobeChat 支持文字转语音（Text-to-Speech，TTS）和语音转文字（Speech-to-Text，STT）技术，我们的应用能够将文本信息转化为清晰的语音输出，用户可以像与真人交谈一样与我们的对话代理进行交流。用户可以从多种声音中选择，给助手搭配合适的音源。 同时，对于那些倾向于听觉学习或者想要在忙碌中获取信息的用户来说，TTS 提供了一个极佳的解决方案。
|
||||
LobeHub 支持文字转语音（Text-to-Speech，TTS）和语音转文字（Speech-to-Text，STT）技术，我们的应用能够将文本信息转化为清晰的语音输出，用户可以像与真人交谈一样与我们的对话代理进行交流。用户可以从多种声音中选择，给助手搭配合适的音源。 同时，对于那些倾向于听觉学习或者想要在忙碌中获取信息的用户来说，TTS 提供了一个极佳的解决方案。
|
||||
|
||||
在 LobeChat 中，我们精心挑选了一系列高品质的声音选项 (OpenAI Audio, Microsoft Edge Speech)，以满足不同地域和文化背景用户的需求。用户可以根据个人喜好或者特定场景来选择合适的语音，从而获得个性化的交流体验。
|
||||
在 LobeHub 中，我们精心挑选了一系列高品质的声音选项 (OpenAI Audio, Microsoft Edge Speech)，以满足不同地域和文化背景用户的需求。用户可以根据个人喜好或者特定场景来选择合适的语音，从而获得个性化的交流体验。
|
||||
|
|
|
|||
|
|
@ -1,14 +1,14 @@
|
|||
---
|
||||
title: 'LobeChat Text-to-Image: Text-to-Image Generation Technology'
|
||||
title: 'LobeHub Text-to-Image: Text-to-Image Generation Technology'
|
||||
description: >-
|
||||
LobeChat now supports the latest text-to-image generation technology, allowing
|
||||
LobeHub now supports the latest text-to-image generation technology, allowing
|
||||
users to directly invoke the text-to-image tool during conversations with the
|
||||
assistant for creative purposes. By utilizing AI tools such as DALL-E 3,
|
||||
MidJourney, and Pollinations, assistants can turn your ideas into images,
|
||||
making the creative process more intimate and immersive.
|
||||
tags:
|
||||
- Text-to-Image
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- AI Tools
|
||||
- DALL-E 3
|
||||
- MidJourney
|
||||
|
|
@ -16,4 +16,4 @@ tags:
|
|||
|
||||
# Support for Text-to-Image Generation
|
||||
|
||||
The latest text-to-image generation technology is now supported, enabling LobeChat users to directly use the text-to-image tool during conversations with their assistant. By harnessing the capabilities of AI tools like [`DALL-E 3`](https://openai.com/dall-e-3), [`MidJourney`](https://www.midjourney.com/), and [`Pollinations`](https://pollinations.ai/), assistants can now transform your ideas into images. This allows for a more intimate and immersive creative process.
|
||||
The latest text-to-image generation technology is now supported, enabling LobeHub users to directly use the text-to-image tool during conversations with their assistant. By harnessing the capabilities of AI tools like [`DALL-E 3`](https://openai.com/dall-e-3), [`MidJourney`](https://www.midjourney.com/), and [`Pollinations`](https://pollinations.ai/), assistants can now transform your ideas into images. This allows for a more intimate and immersive creative process.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: LobeChat 文生图：文本转图片生成技术
|
||||
title: LobeHub 文生图：文本转图片生成技术
|
||||
description: >-
|
||||
LobeChat 现在支持最新的文本到图片生成技术，让用户可以在与助手对话中直接调用文生图工具进行创作。利用 DALL-E 3、MidJourney 和
|
||||
LobeHub 现在支持最新的文本到图片生成技术，让用户可以在与助手对话中直接调用文生图工具进行创作。利用 DALL-E 3、MidJourney 和
|
||||
Pollinations 等 AI 工具，助手们可以将你的想法转化为图像，让创作过程更私密和沉浸式。
|
||||
tags:
|
||||
- Text to Image
|
||||
|
|
@ -11,4 +11,4 @@ tags:
|
|||
|
||||
# 支持 Text to Image 文生图
|
||||
|
||||
现已支持最新的文本到图片生成技术，LobeChat 现在能够让用户在与助手对话中直接调用文成图工具进行创作。通过利用 [`DALL-E 3`](https://openai.com/dall-e-3)、[`MidJourney`](https://www.midjourney.com/) 和 [`Pollinations`](https://pollinations.ai/) 等 AI 工具的能力， 助手们现在可以将你的想法转化为图像。同时可以更私密和沉浸式的完成你的创造过程。
|
||||
现已支持最新的文本到图片生成技术，LobeHub 现在能够让用户在与助手对话中直接调用文成图工具进行创作。通过利用 [`DALL-E 3`](https://openai.com/dall-e-3)、[`MidJourney`](https://www.midjourney.com/) 和 [`Pollinations`](https://pollinations.ai/) 等 AI 工具的能力， 助手们现在可以将你的想法转化为图像。同时可以更私密和沉浸式的完成你的创造过程。
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: LobeChat Supports Multi-User Management with Clerk and Next-Auth
|
||||
title: LobeHub Supports Multi-User Management with Clerk and Next-Auth
|
||||
description: >-
|
||||
LobeChat offers various user authentication and management solutions,
|
||||
including Clerk and Next-Auth, to meet the diverse needs of different users.
|
||||
LobeHub offers various user authentication and management solutions, including
|
||||
Clerk and Next-Auth, to meet the diverse needs of different users.
|
||||
tags:
|
||||
- User Management
|
||||
- Next-Auth
|
||||
|
|
@ -13,11 +13,11 @@ tags:
|
|||
|
||||
# Support for Multi-User Management with Clerk and Next-Auth
|
||||
|
||||
In modern applications, user management and authentication are crucial features. To cater to the diverse needs of users, LobeChat provides two primary user authentication and management solutions: `next-auth` and `Clerk`. Whether you're looking for simple user registration and login or need more advanced multi-factor authentication and user management, LobeChat can flexibly accommodate your requirements.
|
||||
In modern applications, user management and authentication are crucial features. To cater to the diverse needs of users, LobeHub provides two primary user authentication and management solutions: `next-auth` and `Clerk`. Whether you're looking for simple user registration and login or need more advanced multi-factor authentication and user management, LobeHub can flexibly accommodate your requirements.
|
||||
|
||||
## Next-Auth: A Flexible and Powerful Authentication Library
|
||||
|
||||
LobeChat integrates `next-auth`, a flexible and powerful authentication library that supports various authentication methods, including OAuth, email login, and credential-based login. With `next-auth`, you can easily implement the following features:
|
||||
LobeHub integrates `next-auth`, a flexible and powerful authentication library that supports various authentication methods, including OAuth, email login, and credential-based login. With `next-auth`, you can easily implement the following features:
|
||||
|
||||
- **User Registration and Login**: Supports multiple authentication methods to meet different user needs.
|
||||
- **Session Management**: Efficiently manage user sessions to ensure security.
|
||||
|
|
@ -26,7 +26,7 @@ LobeChat integrates `next-auth`, a flexible and powerful authentication library
|
|||
|
||||
## Clerk: A Modern User Management Platform
|
||||
|
||||
For users who require more advanced user management capabilities, LobeChat also supports [Clerk](https://clerk.com), a modern user management platform. Clerk offers a richer set of features, helping you achieve enhanced security and flexibility:
|
||||
For users who require more advanced user management capabilities, LobeHub also supports [Clerk](https://clerk.com), a modern user management platform. Clerk offers a richer set of features, helping you achieve enhanced security and flexibility:
|
||||
|
||||
- **Multi-Factor Authentication (MFA)**: Provides an additional layer of security.
|
||||
- **User Profile Management**: Easily manage user information and settings.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: LobeChat 支持 Clerk 与 Next-Auth 多用户管理支持
|
||||
description: LobeChat 提供 Clerk 和 Next-Auth 等多种用户认证和管理方案，以满足不同用户的需求。
|
||||
title: LobeHub 支持 Clerk 与 Next-Auth 多用户管理支持
|
||||
description: LobeHub 提供 Clerk 和 Next-Auth 等多种用户认证和管理方案，以满足不同用户的需求。
|
||||
tags:
|
||||
- 用户管理
|
||||
- 身份验证
|
||||
|
|
@ -11,11 +11,11 @@ tags:
|
|||
|
||||
# 支持 Clerk 与 Next-Auth 多用户管理支持
|
||||
|
||||
在现代应用中，用户管理和身份验证是至关重要的功能。为满足不同用户的多样化需求，LobeChat 提供了两种主要的用户认证和管理方案：`next-auth` 和 `Clerk`。无论您是追求简便的用户注册登录，还是需要更高级的多因素认证和用户管理，LobeChat 都可以灵活实现。
|
||||
在现代应用中，用户管理和身份验证是至关重要的功能。为满足不同用户的多样化需求，LobeHub 提供了两种主要的用户认证和管理方案：`next-auth` 和 `Clerk`。无论您是追求简便的用户注册登录，还是需要更高级的多因素认证和用户管理，LobeHub 都可以灵活实现。
|
||||
|
||||
## next-auth：灵活且强大的身份验证库
|
||||
|
||||
LobeChat 集成了 `next-auth`，一个灵活且强大的身份验证库，支持多种身份验证方式，包括 OAuth、邮件登录、凭证登录等。通过 `next-auth`，您可以轻松实现以下功能：
|
||||
LobeHub 集成了 `next-auth`，一个灵活且强大的身份验证库，支持多种身份验证方式，包括 OAuth、邮件登录、凭证登录等。通过 `next-auth`，您可以轻松实现以下功能：
|
||||
|
||||
- **用户注册和登录**：支持多种认证方式，满足不同用户的需求。
|
||||
- **会话管理**：高效管理用户会话，确保安全性。
|
||||
|
|
@ -24,7 +24,7 @@ LobeChat 集成了 `next-auth`，一个灵活且强大的身份验证库，支
|
|||
|
||||
## Clerk：现代化用户管理平台
|
||||
|
||||
对于需要更高级用户管理功能的用户，LobeChat 还支持 [Clerk](https://clerk.com) ，一个现代化的用户管理平台。Clerk 提供了更丰富的功能，帮助您实现更高的安全性和灵活性：
|
||||
对于需要更高级用户管理功能的用户，LobeHub 还支持 [Clerk](https://clerk.com) ，一个现代化的用户管理平台。Clerk 提供了更丰富的功能，帮助您实现更高的安全性和灵活性：
|
||||
|
||||
- **多因素认证 (MFA)**：提供更高的安全保障。
|
||||
- **用户配置文件管理**：便捷管理用户信息和配置。
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
---
|
||||
title: LobeChat Supports Ollama for Local Large Language Model (LLM) Calls
|
||||
description: LobeChat v0.127.0 supports using Ollama to call local large language models.
|
||||
title: LobeHub Supports Ollama for Local Large Language Model (LLM) Calls
|
||||
description: LobeHub v0.127.0 supports using Ollama to call local large language models.
|
||||
tags:
|
||||
- Ollama AI
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- Local LLMs
|
||||
- AI Conversations
|
||||
- GPT-4
|
||||
|
|
@ -11,15 +11,15 @@ tags:
|
|||
|
||||
# Support for Ollama Calls to Local Large Language Models 🦙
|
||||
|
||||
With the release of LobeChat v0.127.0, we're excited to introduce a fantastic new feature—Ollama AI support! 🤯 Thanks to the robust infrastructure provided by [Ollama AI](https://ollama.ai/) and the [efforts of the community](https://github.com/lobehub/lobe-chat/pull/1265), you can now interact with local LLMs (Large Language Models) within LobeChat! 🤩
|
||||
With the release of LobeHub v0.127.0, we're excited to introduce a fantastic new feature—Ollama AI support! 🤯 Thanks to the robust infrastructure provided by [Ollama AI](https://ollama.ai/) and the [efforts of the community](https://github.com/lobehub/lobe-chat/pull/1265), you can now interact with local LLMs (Large Language Models) within LobeHub! 🤩
|
||||
|
||||
We are thrilled to unveil this revolutionary feature to all LobeChat users at this special moment. The integration of Ollama AI not only represents a significant leap in our technology but also reaffirms our commitment to continuously seek more efficient and intelligent ways of communication with our users.
|
||||
We are thrilled to unveil this revolutionary feature to all LobeHub users at this special moment. The integration of Ollama AI not only represents a significant leap in our technology but also reaffirms our commitment to continuously seek more efficient and intelligent ways of communication with our users.
|
||||
|
||||
## 💡 How to Start a Conversation with Local LLMs?
|
||||
|
||||
If you're facing challenges with private deployments, we strongly recommend trying out the LobeChat Cloud service. We offer comprehensive model support to help you easily embark on your AI conversation journey.
|
||||
If you're facing challenges with private deployments, we strongly recommend trying out the LobeHub Cloud service. We offer comprehensive model support to help you easily embark on your AI conversation journey.
|
||||
|
||||
Experience the newly upgraded LobeChat v1.6 and feel the powerful conversational capabilities brought by GPT-4!
|
||||
Experience the newly upgraded LobeHub v1.6 and feel the powerful conversational capabilities brought by GPT-4!
|
||||
|
||||
```bash
|
||||
docker run -d -p 3210:3210 -e OLLAMA_PROXY_URL=http://host.docker.internal:11434/v1 lobehub/lobe-chat
|
||||
|
|
|
|||
|
|
@ -1,24 +1,24 @@
|
|||
---
|
||||
title: LobeChat 支持 Ollama 调用本地大语言模型（LLM）
|
||||
description: LobeChat vLobeChat v0.127.0 支持 Ollama 调用本地大语言模型。
|
||||
title: LobeHub 支持 Ollama 调用本地大语言模型（LLM）
|
||||
description: LobeHub vLobeHub v0.127.0 支持 Ollama 调用本地大语言模型。
|
||||
tags:
|
||||
- Ollama AI
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- 大语言模型
|
||||
- AI 对话
|
||||
---
|
||||
|
||||
# 支持 Ollama 调用本地大语言模型 🦙
|
||||
|
||||
随着 LobeChat v0.127.0 的发布，我们迎来了一个激动人心的特性 —— Ollama AI 支持！🤯 在 [Ollama AI](https://ollama.ai/) 强大的基础设施和 [社区的共同努力](https://github.com/lobehub/lobe-chat/pull/1265) 下，现在您可以在 LobeChat 中与本地 LLM (Large Language Model) 进行交流了！🤩
|
||||
随着 LobeHub v0.127.0 的发布，我们迎来了一个激动人心的特性 —— Ollama AI 支持！🤯 在 [Ollama AI](https://ollama.ai/) 强大的基础设施和 [社区的共同努力](https://github.com/lobehub/lobe-chat/pull/1265) 下，现在您可以在 LobeHub 中与本地 LLM (Large Language Model) 进行交流了！🤩
|
||||
|
||||
我们非常高兴能在这个特别的时刻，向所有 LobeChat 用户介绍这项革命性的特性。Ollama AI 的集成不仅标志着我们技术上的一个巨大飞跃，更是向用户承诺，我们将不断追求更高效、更智能的沟通方式。
|
||||
我们非常高兴能在这个特别的时刻，向所有 LobeHub 用户介绍这项革命性的特性。Ollama AI 的集成不仅标志着我们技术上的一个巨大飞跃，更是向用户承诺，我们将不断追求更高效、更智能的沟通方式。
|
||||
|
||||
## 💡 如何启动与本地 LLM 的对话？
|
||||
|
||||
如果您在私有化部署方面遇到困难，强烈推荐尝试 LobeChat Cloud 服务。我们提供全方位的模型支持，让您轻松开启 AI 对话之旅。
|
||||
如果您在私有化部署方面遇到困难，强烈推荐尝试 LobeHub Cloud 服务。我们提供全方位的模型支持，让您轻松开启 AI 对话之旅。
|
||||
|
||||
赶快来体验全新升级的 LobeChat v1.6，感受 GPT-4 带来的强大对话能力！
|
||||
赶快来体验全新升级的 LobeHub v1.6，感受 GPT-4 带来的强大对话能力！
|
||||
|
||||
```bash
|
||||
docker run -d -p 3210:3210 -e OLLAMA_PROXY_URL=http://host.docker.internal:11434/v1 lobehub/lobe-chat
|
||||
|
|
|
|||
|
|
@ -1,29 +1,29 @@
|
|||
---
|
||||
title: 'LobeChat 1.0: New Architecture and New Possibilities'
|
||||
title: 'LobeHub 1.0: New Architecture and New Possibilities'
|
||||
description: >-
|
||||
LobeChat 1.0 brings a brand-new architecture and features for server-side
|
||||
LobeHub 1.0 brings a brand-new architecture and features for server-side
|
||||
databases and user authentication management, opening up new possibilities. On
|
||||
this basis, LobeChat Cloud has entered beta testing.
|
||||
this basis, LobeHub Cloud has entered beta testing.
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- Version 1.0
|
||||
- Server-Side Database
|
||||
- User Authentication
|
||||
- Cloud Beta Testing
|
||||
---
|
||||
|
||||
# LobeChat 1.0: New Architecture and New Possibilities
|
||||
# LobeHub 1.0: New Architecture and New Possibilities
|
||||
|
||||
Since announcing our move towards version 1.0 in March, we’ve been busy upgrading every aspect of our platform. After two months of intensive development, we are excited to announce the official release of LobeChat 1.0! Let’s take a look at our new features.
|
||||
Since announcing our move towards version 1.0 in March, we’ve been busy upgrading every aspect of our platform. After two months of intensive development, we are excited to announce the official release of LobeHub 1.0! Let’s take a look at our new features.
|
||||
|
||||
## Server-Side Database Support
|
||||
|
||||
The most significant feature of LobeChat 1.0 is the support for server-side databases. In the 0.x era, the lack of persistent storage on the server side made it challenging, if not impossible, to implement many features that users urgently needed, such as knowledge bases, cross-device synchronization, and private assistant markets.
|
||||
The most significant feature of LobeHub 1.0 is the support for server-side databases. In the 0.x era, the lack of persistent storage on the server side made it challenging, if not impossible, to implement many features that users urgently needed, such as knowledge bases, cross-device synchronization, and private assistant markets.
|
||||
|
||||
## User Authentication Management
|
||||
|
||||
In the 0.x era, the most requested feature to be paired with server-side databases was user authentication management. Previously, we had integrated next-auth and Clerk as our authentication solutions. In response to demands for multi-user management, we have restructured the settings interface into a user panel, consolidating relevant user information within the new user interface.
|
||||
|
||||
## LobeChat Cloud Beta Testing
|
||||
## LobeHub Cloud Beta Testing
|
||||
|
||||
LobeChat Cloud is our commercial version based on the open-source LobeChat, and all the features from version 1.0 are now live in LobeChat Cloud, which has entered beta testing. If you’re interested, you can join our waitlist here. During the beta testing period, a limited number of access slots will be released daily for testing opportunities.
|
||||
LobeHub Cloud is our commercial version based on the open-source LobeHub, and all the features from version 1.0 are now live in LobeHub Cloud, which has entered beta testing. If you’re interested, you can join our waitlist here. During the beta testing period, a limited number of access slots will be released daily for testing opportunities.
|
||||
|
|
|
|||
|
|
@ -1,27 +1,27 @@
|
|||
---
|
||||
title: LobeChat 1.0：新的架构与新的可能
|
||||
title: LobeHub 1.0：新的架构与新的可能
|
||||
description: >-
|
||||
LobeChat 1.0 带来了服务端数据库、用户鉴权管理的全新架构与特性，开启了新的可能 。在此基础上， LobeChat Cloud 开启 Beta
|
||||
LobeHub 1.0 带来了服务端数据库、用户鉴权管理的全新架构与特性，开启了新的可能 。在此基础上， LobeHub Cloud 开启 Beta
|
||||
版测试。
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- 服务端数据库
|
||||
- 用户鉴权
|
||||
- Beta 测试
|
||||
---
|
||||
|
||||
# LobeChat 1.0：新的架构与新的可能
|
||||
# LobeHub 1.0：新的架构与新的可能
|
||||
|
||||
自从 3 月份宣布迈向 1.0 ，我们就开始着手全方面的升级。经过 2 个月的密集研发，我们很高兴地宣布 LobeChat 1.0 正式发布了！一起来看看我们的全新样貌吧～
|
||||
自从 3 月份宣布迈向 1.0 ，我们就开始着手全方面的升级。经过 2 个月的密集研发，我们很高兴地宣布 LobeHub 1.0 正式发布了！一起来看看我们的全新样貌吧～
|
||||
|
||||
## 服务端数据库支持
|
||||
|
||||
在 LobeChat 1.0 中，最大的特性是支持了服务端数据库。在 0.x 时代，由于缺乏服务端持久化存储，许多用户迫切需要的功能实现困难，或完全无法实现，例如知识库、跨端同步、私有助手市场等等。
|
||||
在 LobeHub 1.0 中，最大的特性是支持了服务端数据库。在 0.x 时代，由于缺乏服务端持久化存储，许多用户迫切需要的功能实现困难，或完全无法实现，例如知识库、跨端同步、私有助手市场等等。
|
||||
|
||||
## 用户鉴权管理
|
||||
|
||||
在 0.x 时代，和服务端数据库搭配的呼声最高的特性就是用户鉴权管理。在此之前，我们已经接入了 next-auth 和 clerk 作为鉴权解决方案。并针对多用户管理的诉求，将设置界面重构为了用户面板，在新的用户面板中整合了相关的用户信息。
|
||||
|
||||
## LobeChat Cloud 开启 Beta 测试
|
||||
## LobeHub Cloud 开启 Beta 测试
|
||||
|
||||
LobeChat Cloud 是我们基于 LobeChat 开源版的商业化版本，上述 1.0 的功能在 LobeChat Cloud 中均已上线，目前已开启 Beta 测试。如果你感兴趣，可以在这里加入我们的 waitlist ， Beta 测试期间每天都会发放体验名额。
|
||||
LobeHub Cloud 是我们基于 LobeHub 开源版的商业化版本，上述 1.0 的功能在 LobeHub Cloud 中均已上线，目前已开启 Beta 测试。如果你感兴趣，可以在这里加入我们的 waitlist ， Beta 测试期间每天都会发放体验名额。
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
title: 'LobeChat Fully Enters the GPT-4 Era: GPT-4o Mini Officially Launched'
|
||||
title: 'LobeHub Fully Enters the GPT-4 Era: GPT-4o Mini Officially Launched'
|
||||
description: >-
|
||||
LobeChat v1.6 has been released with support for GPT-4o mini, while LobeChat
|
||||
LobeHub v1.6 has been released with support for GPT-4o mini, while LobeHub
|
||||
Cloud services have been fully upgraded to provide users with a more powerful
|
||||
AI conversation experience.
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- GPT-4o Mini
|
||||
- AI Conversation
|
||||
- Cloud Service
|
||||
|
|
@ -13,18 +13,18 @@ tags:
|
|||
|
||||
# GPT-4o Mini Makes a Stunning Debut, Ushering in a New GPT-4 Era 🚀
|
||||
|
||||
We are excited to announce that LobeChat v1.6 is now officially released! This update brings thrilling and significant upgrades:
|
||||
We are excited to announce that LobeHub v1.6 is now officially released! This update brings thrilling and significant upgrades:
|
||||
|
||||
## 🌟 Major Updates
|
||||
|
||||
- **GPT-4o Mini Officially Launched**: OpenAI's entire model lineup has been upgraded to GPT-4
|
||||
- **LobeChat Cloud Service Upgrade**:
|
||||
- **LobeHub Cloud Service Upgrade**:
|
||||
- GPT-3.5-turbo has been upgraded to GPT-4o Mini as the default model
|
||||
- Providing users with a superior conversation experience
|
||||
|
||||
## 🎯 Cloud Service Highlights
|
||||
|
||||
LobeChat Cloud offers you a convenient one-stop AI conversation service:
|
||||
LobeHub Cloud offers you a convenient one-stop AI conversation service:
|
||||
|
||||
- 📦 **Ready to Use**: Free registration for immediate experience
|
||||
- 🤖 **Multi-Model Support**:
|
||||
|
|
@ -35,6 +35,6 @@ LobeChat Cloud offers you a convenient one-stop AI conversation service:
|
|||
|
||||
## 💡 Usage Recommendations
|
||||
|
||||
If you encounter difficulties with private deployment, we highly recommend trying the LobeChat Cloud service. We provide comprehensive model support to help you easily embark on your AI conversation journey.
|
||||
If you encounter difficulties with private deployment, we highly recommend trying the LobeHub Cloud service. We provide comprehensive model support to help you easily embark on your AI conversation journey.
|
||||
|
||||
Come and experience the newly upgraded LobeChat v1.6, and feel the powerful conversational capabilities brought by GPT-4!
|
||||
Come and experience the newly upgraded LobeHub v1.6, and feel the powerful conversational capabilities brought by GPT-4!
|
||||
|
|
|
|||
|
|
@ -1,28 +1,28 @@
|
|||
---
|
||||
title: LobeChat 全面进入 GPT-4 时代：GPT-4o mini 正式上线
|
||||
title: LobeHub 全面进入 GPT-4 时代：GPT-4o mini 正式上线
|
||||
description: >-
|
||||
LobeChat v1.6 重磅发布 GPT-4o mini 支持，同时 LobeChat Cloud 服务全面升级默认模型，为用户带来更强大的 AI
|
||||
LobeHub v1.6 重磅发布 GPT-4o mini 支持，同时 LobeHub Cloud 服务全面升级默认模型，为用户带来更强大的 AI
|
||||
对话体验。
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- GPT-4o mini
|
||||
- AI 对话服务
|
||||
---
|
||||
|
||||
# GPT-4o mini 震撼登场，开启全新 GPT-4 时代 🚀
|
||||
|
||||
我们很高兴地宣布，LobeChat v1.6 现已正式发布！这次更新带来了激动人心的重大升级：
|
||||
我们很高兴地宣布，LobeHub v1.6 现已正式发布！这次更新带来了激动人心的重大升级：
|
||||
|
||||
## 🌟 主要更新
|
||||
|
||||
- **GPT-4o mini 正式上线**：OpenAI 全系列模型实现 GPT-4 升级
|
||||
- **LobeChat Cloud 服务升级**：
|
||||
- **LobeHub Cloud 服务升级**：
|
||||
- GPT-3.5-turbo 升级为 GPT-4o mini 作为默认模型
|
||||
- 为用户带来更优质的对话体验
|
||||
|
||||
## 🎯 Cloud 服务亮点
|
||||
|
||||
LobeChat Cloud 为您提供便捷的一站式 AI 对话服务：
|
||||
LobeHub Cloud 为您提供便捷的一站式 AI 对话服务：
|
||||
|
||||
- 📦 **开箱即用**：免费注册，即刻体验
|
||||
- 🤖 **多模型支持**：
|
||||
|
|
@ -33,6 +33,6 @@ LobeChat Cloud 为您提供便捷的一站式 AI 对话服务：
|
|||
|
||||
## 💡 使用建议
|
||||
|
||||
如果您在私有化部署方面遇到困难，强烈推荐尝试 LobeChat Cloud 服务。我们提供全方位的模型支持，让您轻松开启 AI 对话之旅。
|
||||
如果您在私有化部署方面遇到困难，强烈推荐尝试 LobeHub Cloud 服务。我们提供全方位的模型支持，让您轻松开启 AI 对话之旅。
|
||||
|
||||
赶快来体验全新升级的 LobeChat v1.6，感受 GPT-4 带来的强大对话能力！
|
||||
赶快来体验全新升级的 LobeHub v1.6，感受 GPT-4 带来的强大对话能力！
|
||||
|
|
|
|||
|
|
@ -1,20 +1,20 @@
|
|||
---
|
||||
title: LobeChat Database Docker Image Official Release
|
||||
title: LobeHub Database Docker Image Official Release
|
||||
description: >-
|
||||
LobeChat v1.8.0 launches the official database Docker image, supporting cloud
|
||||
LobeHub v1.8.0 launches the official database Docker image, supporting cloud
|
||||
data synchronization and user management, along with comprehensive
|
||||
self-deployment documentation.
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- Docker Image
|
||||
- Cloud Deployment
|
||||
- Database
|
||||
- Postgres
|
||||
---
|
||||
|
||||
# LobeChat Database Docker Image: The Final Piece of the Cloud Deployment Puzzle
|
||||
# LobeHub Database Docker Image: The Final Piece of the Cloud Deployment Puzzle
|
||||
|
||||
We are excited to announce the official release of the long-awaited database Docker image for LobeChat v1.8.0! This marks a significant milestone in our server database offerings, providing users with a complete cloud deployment solution.
|
||||
We are excited to announce the official release of the long-awaited database Docker image for LobeHub v1.8.0! This marks a significant milestone in our server database offerings, providing users with a complete cloud deployment solution.
|
||||
|
||||
## 🚀 Core Features
|
||||
|
||||
|
|
@ -31,10 +31,10 @@ To ensure users can complete the deployment smoothly, we have optimized the stru
|
|||
- Detailed deployment case studies
|
||||
- Comprehensive self-deployment operation guide
|
||||
|
||||
You can start deploying your own LobeChat service by visiting the [official documentation](https://lobehub.com/en/docs/self-hosting/server-database).
|
||||
You can start deploying your own LobeHub service by visiting the [official documentation](https://lobehub.com/en/docs/self-hosting/server-database).
|
||||
|
||||
## 🔮 Future Outlook
|
||||
|
||||
Our knowledge base feature is also in development, so stay tuned for more exciting updates!
|
||||
|
||||
This update marks a significant breakthrough for LobeChat in cloud deployment solutions, making private deployment easier than ever. We appreciate the community's patience, and we will continue to strive to provide users with a better experience.
|
||||
This update marks a significant breakthrough for LobeHub in cloud deployment solutions, making private deployment easier than ever. We appreciate the community's patience, and we will continue to strive to provide users with a better experience.
|
||||
|
|
|
|||
|
|
@ -1,16 +1,16 @@
|
|||
---
|
||||
title: LobeChat Database Docker 镜像正式发布
|
||||
description: LobeChat v1.8.0 推出官方数据库 Docker 镜像，支持云端数据同步与用户管理，并提供完整的自部署文档指南。
|
||||
title: LobeHub Database Docker 镜像正式发布
|
||||
description: LobeHub v1.8.0 推出官方数据库 Docker 镜像，支持云端数据同步与用户管理，并提供完整的自部署文档指南。
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- Docker 镜像
|
||||
- 云端部署
|
||||
- 数据库
|
||||
---
|
||||
|
||||
# LobeChat Database Docker 镜像：云端部署的最后一块拼图
|
||||
# LobeHub Database Docker 镜像：云端部署的最后一块拼图
|
||||
|
||||
我们很高兴地宣布，LobeChat v1.8.0 正式发布了期待已久的数据库 Docker 镜像！这是我们在服务端数据库领域的重要里程碑，为用户提供了完整的云端部署解决方案。
|
||||
我们很高兴地宣布，LobeHub v1.8.0 正式发布了期待已久的数据库 Docker 镜像！这是我们在服务端数据库领域的重要里程碑，为用户提供了完整的云端部署解决方案。
|
||||
|
||||
## 🚀 核心特性
|
||||
|
||||
|
|
@ -27,10 +27,10 @@ tags:
|
|||
- 详细的部署案例指引
|
||||
- 完整的自部署操作指南
|
||||
|
||||
现在，您可以通过访问 [官方文档](https://lobehub.com/zh/docs/self-hosting/server-database) 开始部署您自己的 LobeChat 服务。
|
||||
现在，您可以通过访问 [官方文档](https://lobehub.com/zh/docs/self-hosting/server-database) 开始部署您自己的 LobeHub 服务。
|
||||
|
||||
## 🔮 未来展望
|
||||
|
||||
我们的知识库功能也正在开发中，敬请期待更多激动人心的更新！
|
||||
|
||||
这次更新标志着 LobeChat 在云端部署方案上的重要突破，让私有部署变得前所未有的简单。感谢社区的耐心等待，我们将继续努力为用户带来更好的体验。
|
||||
这次更新标志着 LobeHub 在云端部署方案上的重要突破，让私有部署变得前所未有的简单。感谢社区的耐心等待，我们将继续努力为用户带来更好的体验。
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
---
|
||||
title: >-
|
||||
LobeChat Launches Knowledge Base Feature: A New Experience in Intelligent File
|
||||
LobeHub Launches Knowledge Base Feature: A New Experience in Intelligent File
|
||||
Management and Dialogue
|
||||
description: >-
|
||||
LobeChat introduces a brand new knowledge base feature that supports all types
|
||||
LobeHub introduces a brand new knowledge base feature that supports all types
|
||||
of file management, intelligent vectorization, and file dialogue, making
|
||||
knowledge management and information retrieval easier and smarter.
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- Knowledge Base
|
||||
- File Management
|
||||
- Open Source
|
||||
|
|
@ -16,7 +16,7 @@ tags:
|
|||
|
||||
# Major Release of Knowledge Base Feature: A Revolution in Intelligent File Management and Dialogue
|
||||
|
||||
We are excited to announce that the highly anticipated LobeChat knowledge base feature is now officially launched! 🎉 This feature is now available in both the open-source version and the Cloud version (lobechat.com).
|
||||
We are excited to announce that the highly anticipated LobeHub knowledge base feature is now officially launched! 🎉 This feature is now available in both the open-source version and the Cloud version (LobeHub.com).
|
||||
|
||||
## A Brand New File Management Experience
|
||||
|
||||
|
|
@ -38,4 +38,4 @@ We are excited to announce that the highly anticipated LobeChat knowledge base f
|
|||
- 🎯 **Real-Time Feedback**: An optimized upload experience provides clear progress feedback.
|
||||
- ☁️ **Two Versions Available**: Offers both an open-source self-hosted version and an official Cloud version to meet different user needs.
|
||||
|
||||
All features are open-sourced on the [GitHub repository](https://github.com/lobehub/lobe-chat). We invite you to visit [LobeChat Cloud](http://lobechat.com) to experience the full functionality.
|
||||
All features are open-sourced on the [GitHub repository](https://github.com/lobehub/lobe-chat). We invite you to visit [LobeHub Cloud](http://LobeHub.com) to experience the full functionality.
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: LobeChat 重磅发布知识库功能：打造智能文件管理与对话新体验
|
||||
description: LobeChat 推出全新知识库功能，支持全类型文件管理、智能向量化和文件对话，让知识管理和信息检索更轻松、更智能。
|
||||
title: LobeHub 重磅发布知识库功能：打造智能文件管理与对话新体验
|
||||
description: LobeHub 推出全新知识库功能，支持全类型文件管理、智能向量化和文件对话，让知识管理和信息检索更轻松、更智能。
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- 知识库
|
||||
- 文件管理
|
||||
- 智能处理
|
||||
|
|
@ -10,7 +10,7 @@ tags:
|
|||
|
||||
# 知识库功能重磅发布：智能文件管理与对话的革新
|
||||
|
||||
我们很高兴地宣布，备受期待的 LobeChat 知识库功能现已正式发布！🎉 该功能已同步在开源版和 Cloud 版（lobechat.com）中上线。
|
||||
我们很高兴地宣布，备受期待的 LobeHub 知识库功能现已正式发布！🎉 该功能已同步在开源版和 Cloud 版（LobeHub.com）中上线。
|
||||
|
||||
## 全新的文件管理体验
|
||||
|
||||
|
|
@ -32,4 +32,4 @@ tags:
|
|||
- 🎯 **实时反馈**：优化的上传体验，提供清晰的进度反馈
|
||||
- ☁️ **双版本可选**：提供开源自部署版本和官方 Cloud 版本，满足不同用户需求
|
||||
|
||||
所有功能均已在 [GitHub 仓库](https://github.com/lobehub/lobe-chat) 开源，欢迎访问 [LobeChat Cloud](http://lobechat.com) 体验完整功能。
|
||||
所有功能均已在 [GitHub 仓库](https://github.com/lobehub/lobe-chat) 开源，欢迎访问 [LobeHub Cloud](http://LobeHub.com) 体验完整功能。
|
||||
|
|
|
|||
|
|
@ -1,19 +1,19 @@
|
|||
---
|
||||
title: LobeChat Perfectly Adapts to OpenAI O1 Series Models
|
||||
title: LobeHub Perfectly Adapts to OpenAI O1 Series Models
|
||||
description: >-
|
||||
LobeChat v1.17.0 now supports OpenAI's latest o1-preview and o1-mini models,
|
||||
LobeHub v1.17.0 now supports OpenAI's latest o1-preview and o1-mini models,
|
||||
bringing users enhanced coding and mathematical capabilities.
|
||||
tags:
|
||||
- OpenAI O1
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- AI Models
|
||||
- Code Writing
|
||||
- Mathematical Problem Solving
|
||||
---
|
||||
|
||||
# OpenAI O1 Series Models Now Available on LobeChat
|
||||
# OpenAI O1 Series Models Now Available on LobeHub
|
||||
|
||||
We are excited to announce that LobeChat v1.17.0 fully supports OpenAI's newly launched O1 series models. Whether you are a community edition user or a [Cloud version](https://lobechat.com) subscriber, you can experience this significant update.
|
||||
We are excited to announce that LobeHub v1.17.0 fully supports OpenAI's newly launched O1 series models. Whether you are a community edition user or a [Cloud version](https://LobeHub.com) subscriber, you can experience this significant update.
|
||||
|
||||
## New Model Support
|
||||
|
||||
|
|
@ -34,4 +34,4 @@ The O1 series models excel in the following areas:
|
|||
- 🌐 Cloud version subscribers can start using it immediately
|
||||
- 🔧 Self-hosted users can begin experiencing it by updating to v1.17.0
|
||||
|
||||
This update marks an important step for LobeChat in supporting the latest AI models. We look forward to seeing how the O1 series models can help users unlock new possibilities!
|
||||
This update marks an important step for LobeHub in supporting the latest AI models. We look forward to seeing how the O1 series models can help users unlock new possibilities!
|
||||
|
|
|
|||
|
|
@ -1,17 +1,17 @@
|
|||
---
|
||||
title: LobeChat 完美适配 OpenAI O1 系列模型
|
||||
description: LobeChat v1.17.0 现已支持 OpenAI 最新发布的 o1-preview 和 o1-mini 模型，为用户带来更强大的代码和数学能力。
|
||||
title: LobeHub 完美适配 OpenAI O1 系列模型
|
||||
description: LobeHub v1.17.0 现已支持 OpenAI 最新发布的 o1-preview 和 o1-mini 模型，为用户带来更强大的代码和数学能力。
|
||||
tags:
|
||||
- OpenAI O1
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- AI 模型
|
||||
- 代码编写
|
||||
- 数学问题
|
||||
---
|
||||
|
||||
# OpenAI O1 系列模型现已登陆 LobeChat
|
||||
# OpenAI O1 系列模型现已登陆 LobeHub
|
||||
|
||||
我们很高兴地宣布，LobeChat v1.17.0 已完整支持 OpenAI 最新推出的 O1 系列模型。无论是社区版还是 [Cloud 版本](https://lobechat.com)用户，都可以体验到这一重大更新。
|
||||
我们很高兴地宣布，LobeHub v1.17.0 已完整支持 OpenAI 最新推出的 O1 系列模型。无论是社区版还是 [Cloud 版本](https://LobeHub.com)用户，都可以体验到这一重大更新。
|
||||
|
||||
## 新增模型支持
|
||||
|
||||
|
|
@ -29,7 +29,7 @@ O1 系列模型在以下方面表现出色：
|
|||
|
||||
## 立即体验
|
||||
|
||||
- 🌐 [Cloud 版本](https://lobechat.com) 订阅用户现已可以直接使用
|
||||
- 🌐 [Cloud 版本](https://LobeHub.com) 订阅用户现已可以直接使用
|
||||
- 🔧 自部署用户可通过更新至 v1.17.0 开始体验
|
||||
|
||||
这次更新让 LobeChat 在支持最新 AI 模型方面又迈出了重要一步。我们期待 O1 系列模型能够帮助用户实现更多可能！
|
||||
这次更新让 LobeHub 在支持最新 AI 模型方面又迈出了重要一步。我们期待 O1 系列模型能够帮助用户实现更多可能！
|
||||
|
|
|
|||
|
|
@ -1,24 +1,24 @@
|
|||
---
|
||||
title: 'Major Update: LobeChat Enters the Era of Artifacts'
|
||||
title: 'Major Update: LobeHub Enters the Era of Artifacts'
|
||||
description: >-
|
||||
LobeChat v1.19 brings significant updates, including full feature support for
|
||||
LobeHub v1.19 brings significant updates, including full feature support for
|
||||
Claude Artifacts, a brand new discovery page design, and support for GitHub
|
||||
Models providers, greatly enhancing the capabilities of the AI assistant.
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- AI Assistant
|
||||
- Artifacts
|
||||
- GitHub Models
|
||||
- Interactive Experience
|
||||
---
|
||||
|
||||
# Major Update: LobeChat Enters the Era of Artifacts
|
||||
# Major Update: LobeHub Enters the Era of Artifacts
|
||||
|
||||
We are excited to announce the official release of LobeChat v1.19! This update introduces several important features that elevate the interactive experience of the AI assistant.
|
||||
We are excited to announce the official release of LobeHub v1.19! This update introduces several important features that elevate the interactive experience of the AI assistant.
|
||||
|
||||
## 🎨 Artifacts Support: Unlocking New Creative Dimensions
|
||||
|
||||
In this version, we have nearly fully replicated the core features of Claude Artifacts. Now, you can experience the following in LobeChat:
|
||||
In this version, we have nearly fully replicated the core features of Claude Artifacts. Now, you can experience the following in LobeHub:
|
||||
|
||||
- SVG graphic generation and display
|
||||
- HTML page generation and real-time rendering
|
||||
|
|
@ -26,7 +26,7 @@ In this version, we have nearly fully replicated the core features of Claude Art
|
|||
|
||||
It is worth mentioning that the Python code execution feature has also been developed and will be available in future versions. At that time, users will be able to utilize both Claude Artifacts and OpenAI Code Interpreter, significantly enhancing the practicality of the AI assistant.
|
||||
|
||||
|
||||
|
||||
|
||||
## 🔍 New Discovery Page: Explore More Possibilities
|
||||
|
||||
|
|
@ -45,7 +45,7 @@ This redesign not only increases the information density of the page but also op
|
|||
|
||||
## 🚀 GitHub Models Support: More Model Choices
|
||||
|
||||
Thanks to community member [@CloudPassenger](https://github.com/CloudPassenger) for their contributions, LobeChat now supports GitHub Models providers. Users simply need to:
|
||||
Thanks to community member [@CloudPassenger](https://github.com/CloudPassenger) for their contributions, LobeHub now supports GitHub Models providers. Users simply need to:
|
||||
|
||||
1. Prepare a GitHub Personal Access Token (PAT)
|
||||
2. Configure provider information in the settings
|
||||
|
|
@ -55,10 +55,10 @@ The addition of this feature greatly expands the range of models available to us
|
|||
|
||||
## 🔜 Future Outlook
|
||||
|
||||
We will continue to focus on enhancing the functionality and user experience of LobeChat. In upcoming versions, we plan to:
|
||||
We will continue to focus on enhancing the functionality and user experience of LobeHub. In upcoming versions, we plan to:
|
||||
|
||||
- Improve the Python code execution feature
|
||||
- Add support for more types of Artifacts
|
||||
- Expand the content dimensions of the discovery page
|
||||
|
||||
Thank you to every user for your support and feedback. Let’s look forward to more surprises from LobeChat together!
|
||||
Thank you to every user for your support and feedback. Let’s look forward to more surprises from LobeHub together!
|
||||
|
|
|
|||
|
|
@ -1,23 +1,23 @@
|
|||
---
|
||||
title: 重磅更新：LobeChat 迎来 Artifacts 时代
|
||||
title: 重磅更新：LobeHub 迎来 Artifacts 时代
|
||||
description: >-
|
||||
LobeChat v1.19 带来了重大更新，包括 Claude Artifacts 完整特性支持、全新的发现页面设计，以及 GitHub Models
|
||||
LobeHub v1.19 带来了重大更新，包括 Claude Artifacts 完整特性支持、全新的发现页面设计，以及 GitHub Models
|
||||
服务商支持，让 AI 助手的能力得到显著提升。
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- Artifacts
|
||||
- AI 助手
|
||||
- 更新
|
||||
- GitHub Models
|
||||
---
|
||||
|
||||
# 重磅更新：LobeChat 迎来 Artifacts 时代
|
||||
# 重磅更新：LobeHub 迎来 Artifacts 时代
|
||||
|
||||
我们很高兴地宣布 LobeChat v1.19 版本正式发布！这次更新带来了多项重要功能，让 AI 助手的交互体验更上一层楼。
|
||||
我们很高兴地宣布 LobeHub v1.19 版本正式发布！这次更新带来了多项重要功能，让 AI 助手的交互体验更上一层楼。
|
||||
|
||||
## 🎨 Artifacts 支持：解锁全新创作维度
|
||||
|
||||
在这个版本中，我们几乎完整还原了 Claude Artifacts 的核心特性。现在，您可以在 LobeChat 中体验到：
|
||||
在这个版本中，我们几乎完整还原了 Claude Artifacts 的核心特性。现在，您可以在 LobeHub 中体验到：
|
||||
|
||||
- SVG 图形生成与展示
|
||||
- HTML 页面生成与实时渲染
|
||||
|
|
@ -25,7 +25,7 @@ tags:
|
|||
|
||||
值得一提的是，Python 代码执行功能也已完成开发，将在后续版本中与大家见面。届时，用户将能够同时运用 Claude Artifacts 和 OpenAI Code Interpreter 这两大强大工具，极大提升 AI 助手的实用性。
|
||||
|
||||
|
||||
|
||||
|
||||
## 🔍 全新发现页面：探索更多可能
|
||||
|
||||
|
|
@ -44,7 +44,7 @@ tags:
|
|||
|
||||
## 🚀 GitHub Models 支持：更多模型选择
|
||||
|
||||
感谢社区成员 [@CloudPassenger](https://github.com/CloudPassenger) 的贡献，现在 LobeChat 已经支持 GitHub Models 服务商。用户只需：
|
||||
感谢社区成员 [@CloudPassenger](https://github.com/CloudPassenger) 的贡献，现在 LobeHub 已经支持 GitHub Models 服务商。用户只需：
|
||||
|
||||
1. 准备 GitHub Personal Access Token (PAT)
|
||||
2. 在设置中配置服务商信息
|
||||
|
|
@ -54,10 +54,10 @@ tags:
|
|||
|
||||
## 🔜 未来展望
|
||||
|
||||
我们将持续致力于提升 LobeChat 的功能和用户体验。接下来的版本中，我们计划：
|
||||
我们将持续致力于提升 LobeHub 的功能和用户体验。接下来的版本中，我们计划：
|
||||
|
||||
- 完善 Python 代码执行功能
|
||||
- 增加更多 Artifacts 类型支持
|
||||
- 扩展发现页面的内容维度
|
||||
|
||||
感谢每一位用户的支持与反馈，让我们一起期待 LobeChat 带来更多惊喜！
|
||||
感谢每一位用户的支持与反馈，让我们一起期待 LobeHub 带来更多惊喜！
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: LobeChat Introduces Persistent Assistant Sidebar Feature
|
||||
title: LobeHub Introduces Persistent Assistant Sidebar Feature
|
||||
description: >-
|
||||
LobeChat v1.26.0 launches the persistent assistant sidebar feature, supporting
|
||||
LobeHub v1.26.0 launches the persistent assistant sidebar feature, supporting
|
||||
quick key switching for easy access to frequently used assistants,
|
||||
significantly enhancing efficiency.
|
||||
tags:
|
||||
|
|
@ -21,9 +21,9 @@ In version v1.26.0, we are excited to introduce a long-awaited new feature — t
|
|||
- **Space Optimization**: Activating the sidebar automatically hides the conversation list, providing you with a larger conversation area.
|
||||
- **Intelligent Display**: Automatically syncs pinned assistants to the sidebar, ensuring that important assistants are always within view.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## How to Use
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: LobeChat 新增助手常驻侧边栏功能
|
||||
description: LobeChat v1.26.0 推出助手常驻侧边栏功能，支持快捷键切换，让高频使用的助手触手可及，大幅提升使用效率。
|
||||
title: LobeHub 新增助手常驻侧边栏功能
|
||||
description: LobeHub v1.26.0 推出助手常驻侧边栏功能，支持快捷键切换，让高频使用的助手触手可及，大幅提升使用效率。
|
||||
tags:
|
||||
- 助手常驻侧边栏
|
||||
- 对话体验
|
||||
|
|
@ -17,9 +17,9 @@ tags:
|
|||
- **空间优化**：激活侧边栏时会自动隐藏会话列表，为您腾出更大的对话空间
|
||||
- **智能显示**：将置顶助手自动同步到侧边栏，让重要助手始终在视线范围内
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## 如何使用
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: LobeChat Supports Sharing Conversations in Text Format (Markdown/JSON)
|
||||
title: LobeHub Supports Sharing Conversations in Text Format (Markdown/JSON)
|
||||
description: >-
|
||||
LobeChat v1.28.0 introduces support for exporting conversations in Markdown
|
||||
and OpenAI format JSON, making it easy to convert conversation content into
|
||||
note materials, development debugging data, and training corpora,
|
||||
significantly enhancing the reusability of conversation content.
|
||||
LobeHub v1.28.0 introduces support for exporting conversations in Markdown and
|
||||
OpenAI format JSON, making it easy to convert conversation content into note
|
||||
materials, development debugging data, and training corpora, significantly
|
||||
enhancing the reusability of conversation content.
|
||||
tags:
|
||||
- Text Format Export
|
||||
- Markdown Export
|
||||
|
|
@ -17,11 +17,11 @@ In the latest version v1.28.0, we have launched the text format export feature f
|
|||
|
||||
The Markdown export feature meets users' needs for directly using conversation content in note-taking and document writing. You can easily save valuable conversation content and manage it across various note-taking applications for reuse.
|
||||
|
||||
|
||||
|
||||
|
||||
Additionally, we support exporting conversations in JSON format that complies with OpenAI messages specifications. This format can be used directly for API debugging and serves as high-quality training data for models.
|
||||
|
||||
|
||||
|
||||
|
||||
It is particularly noteworthy that we retain the original data of Tools Calling within the conversation, which is crucial for enhancing the model's tool invocation capabilities.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: LobeChat 支持分享对话为文本格式（Markdown/JSON）
|
||||
title: LobeHub 支持分享对话为文本格式（Markdown/JSON）
|
||||
description: >-
|
||||
LobeChat v1.28.0 新增 Markdown 和 OpenAI 格式 JSON
|
||||
LobeHub v1.28.0 新增 Markdown 和 OpenAI 格式 JSON
|
||||
导出支持，让对话内容能轻松转化为笔记素材、开发调试数据和训练语料，显著提升对话内容的复用价值。
|
||||
tags:
|
||||
- 对话内容
|
||||
|
|
@ -15,11 +15,11 @@ tags:
|
|||
|
||||
Markdown 格式导出功能满足了用户将对话内容直接用于笔记和文档撰写的需求。您可以轻松地将有价值的对话内容保存下来，并在各类笔记软件中进行管理和复用。
|
||||
|
||||
|
||||
|
||||
|
||||
同时，我们还支持将对话导出为符合 OpenAI messages 规范的 JSON 格式。这种格式不仅可以直接用于 API 调试，还能作为高质量的模型训练语料。
|
||||
|
||||
|
||||
|
||||
|
||||
特别值得一提的是，我们会完整保留对话中的 Tools Calling 原始数据，这对提升模型的工具调用能力具有重要价值。
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: New Model Providers Added to LobeChat in November
|
||||
title: New Model Providers Added to LobeHub in November
|
||||
description: >-
|
||||
LobeChat model providers now support Gitee AI, InternLM (ShuSheng PuYu), xAI,
|
||||
LobeHub model providers now support Gitee AI, InternLM (ShuSheng PuYu), xAI,
|
||||
and Cloudflare WorkersAI
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- AI Model Providers
|
||||
- Gitee AI
|
||||
- InternLM
|
||||
|
|
@ -12,9 +12,9 @@ tags:
|
|||
- Cloudflare Workers AI
|
||||
---
|
||||
|
||||
# New Model Providers Added to LobeChat in November 🎉
|
||||
# New Model Providers Added to LobeHub in November 🎉
|
||||
|
||||
We're excited to announce that LobeChat has expanded its AI model support with the following providers:
|
||||
We're excited to announce that LobeHub has expanded its AI model support with the following providers:
|
||||
|
||||
- **Gitee AI**: [https://ai.gitee.com](https://ai.gitee.com)
|
||||
- **InternLM**: [https://internlm.intern-ai.org.cn](https://internlm.intern-ai.org.cn)
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: LobeChat 11 月新增模型服务
|
||||
description: 'LobeChat 模型服务新增支持 Gitee AI, InternLM (书生浦语), xAI, Cloudflare WorkersAI'
|
||||
title: LobeHub 11 月新增模型服务
|
||||
description: 'LobeHub 模型服务新增支持 Gitee AI, InternLM (书生浦语), xAI, Cloudflare WorkersAI'
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- AI模型服务
|
||||
- Gitee AI
|
||||
- InternLM
|
||||
|
|
@ -10,9 +10,9 @@ tags:
|
|||
- Cloudflare Workers AI
|
||||
---
|
||||
|
||||
# LobeChat 11 月新增模型服务支持 🎉
|
||||
# LobeHub 11 月新增模型服务支持 🎉
|
||||
|
||||
我们很高兴地宣布，LobeChat 在 11 月份新增了以下 AI 模型服务的支持：
|
||||
我们很高兴地宣布，LobeHub 在 11 月份新增了以下 AI 模型服务的支持：
|
||||
|
||||
- **Gitee AI**: [https://ai.gitee.com](https://ai.gitee.com)
|
||||
- **InternLM (书生浦语)**: [https://internlm.intern-ai.org.cn](https://internlm.intern-ai.org.cn)
|
||||
|
|
|
|||
|
|
@ -1,17 +1,17 @@
|
|||
---
|
||||
title: LobeChat Supports Branching Conversations
|
||||
title: LobeHub Supports Branching Conversations
|
||||
description: >-
|
||||
LobeChat now allows you to create new conversation branches from any message,
|
||||
LobeHub now allows you to create new conversation branches from any message,
|
||||
freeing your thoughts.
|
||||
tags:
|
||||
- Branching Conversations
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- Chat Features
|
||||
---
|
||||
|
||||
# Exciting Launch of Branching Conversations Feature 🎉
|
||||
|
||||
We are thrilled to announce that LobeChat has introduced a brand new branching conversations feature, making your conversation experience smoother and more natural:
|
||||
We are thrilled to announce that LobeHub has introduced a brand new branching conversations feature, making your conversation experience smoother and more natural:
|
||||
|
||||
## Key Features
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: LobeChat 支持分支对话
|
||||
description: LobeChat 现已支持从任意消息创建新的对话分支，让您的思维不再受限
|
||||
title: LobeHub 支持分支对话
|
||||
description: LobeHub 现已支持从任意消息创建新的对话分支，让您的思维不再受限
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- 分支对话
|
||||
- 对话功能
|
||||
- 用户体验
|
||||
|
|
@ -10,7 +10,7 @@ tags:
|
|||
|
||||
# 重磅推出分支对话功能 🎉
|
||||
|
||||
我们很高兴地宣布，LobeChat 推出了全新的分支对话功能，让您的对话体验更加流畅自然：
|
||||
我们很高兴地宣布，LobeHub 推出了全新的分支对话功能，让您的对话体验更加流畅自然：
|
||||
|
||||
## 核心特性
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: LobeChat Supports User Data Statistics and Activity Sharing
|
||||
title: LobeHub Supports User Data Statistics and Activity Sharing
|
||||
description: >-
|
||||
LobeChat now supports multi-dimensional user data statistics and activity
|
||||
LobeHub now supports multi-dimensional user data statistics and activity
|
||||
sharing
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- User Statistics
|
||||
- Activity Sharing
|
||||
- AI Data
|
||||
|
|
@ -12,9 +12,9 @@ tags:
|
|||
|
||||
# User Data Statistics and Activity Sharing 💯
|
||||
|
||||
Want to know about your activity performance on LobeChat?
|
||||
Want to know about your activity performance on LobeHub?
|
||||
|
||||
Now, you can comprehensively understand your AI data through the statistics feature, and even generate personal activity sharing images to share your LobeChat activity with friends.
|
||||
Now, you can comprehensively understand your AI data through the statistics feature, and even generate personal activity sharing images to share your LobeHub activity with friends.
|
||||
|
||||
## 📊 Data Statistics
|
||||
|
||||
|
|
|
|||
|
|
@ -1,17 +1,17 @@
|
|||
---
|
||||
title: LobeChat 支持用户数据统计与活跃度分享
|
||||
description: LobeChat 现已支持多维度用户数据统计与活跃度分享
|
||||
title: LobeHub 支持用户数据统计与活跃度分享
|
||||
description: LobeHub 现已支持多维度用户数据统计与活跃度分享
|
||||
tags:
|
||||
- 用户数据统计
|
||||
- 活跃度分享
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
---
|
||||
|
||||
# 用户数据统计与活跃度分享 💯
|
||||
|
||||
想要了解自己在 LobeChat 上的活跃度表现吗？
|
||||
想要了解自己在 LobeHub 上的活跃度表现吗？
|
||||
|
||||
现在，您可以通过数据统计功能，全方位了解自己的 AI 数据，还可以生成个人活跃度分享图片，与好友分享您在 LobeChat 上的活跃度。
|
||||
现在，您可以通过数据统计功能，全方位了解自己的 AI 数据，还可以生成个人活跃度分享图片，与好友分享您在 LobeHub 上的活跃度。
|
||||
|
||||
## 📊 数据统计
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: LobeChat Launches New AI Provider Management System
|
||||
title: LobeHub Launches New AI Provider Management System
|
||||
description: >-
|
||||
LobeChat has revamped its AI Provider Management System, now supporting custom
|
||||
LobeHub has revamped its AI Provider Management System, now supporting custom
|
||||
AI providers and models.
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- AI Provider
|
||||
- Provider Management
|
||||
- Multimodal
|
||||
|
|
@ -12,7 +12,7 @@ tags:
|
|||
|
||||
# New AI Provider Management System 🎉
|
||||
|
||||
We are excited to announce that LobeChat has launched a brand new AI Provider Management System, now available in both the open-source version and the Cloud version ([lobechat.com](https://lobechat.com)):
|
||||
We are excited to announce that LobeHub has launched a brand new AI Provider Management System, now available in both the open-source version and the Cloud version ([LobeHub.com](https://LobeHub.com)):
|
||||
|
||||
## 🚀 Key Updates
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: LobeChat 推出全新 AI Provider 管理系统
|
||||
description: LobeChat 焕新全新 AI Provider 管理系统，已支持自定义 AI 服务商与自定义模型
|
||||
title: LobeHub 推出全新 AI Provider 管理系统
|
||||
description: LobeHub 焕新全新 AI Provider 管理系统，已支持自定义 AI 服务商与自定义模型
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- AI Provider
|
||||
- 服务商管理
|
||||
- 多模态
|
||||
|
|
@ -10,7 +10,7 @@ tags:
|
|||
|
||||
# 全新 AI Provider 管理系统 🎉
|
||||
|
||||
我们很高兴地宣布，LobeChat 推出了全新的 AI Provider 管理系统，已经在开源版与 Cloud 版（[lobechat.com](https://lobechat.com)）中可用：
|
||||
我们很高兴地宣布，LobeHub 推出了全新的 AI Provider 管理系统，已经在开源版与 Cloud 版（[LobeHub.com](https://LobeHub.com)）中可用：
|
||||
|
||||
## 🚀 主要更新
|
||||
|
||||
|
|
|
|||
|
|
@ -1,33 +1,33 @@
|
|||
---
|
||||
title: >-
|
||||
LobeChat Integrates DeepSeek R1, Bringing a Revolutionary Chain of Thought
|
||||
LobeHub Integrates DeepSeek R1, Bringing a Revolutionary Chain of Thought
|
||||
Experience
|
||||
description: >-
|
||||
LobeChat v1.49.12 fully supports the DeepSeek R1 model, providing users with
|
||||
an unprecedented interactive experience in the chain of thought.
|
||||
LobeHub v1.49.12 fully supports the DeepSeek R1 model, providing users with an
|
||||
unprecedented interactive experience in the chain of thought.
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- DeepSeek
|
||||
- Chain of Thought
|
||||
---
|
||||
|
||||
# Perfect Integration of DeepSeek R1 and it's Deep Thinking Experience 🎉
|
||||
|
||||
After nearly 10 days of meticulous refinement, LobeChat has fully integrated the DeepSeek R1 model in version v1.49.12, offering users a revolutionary interactive experience in the chain of thought!
|
||||
After nearly 10 days of meticulous refinement, LobeHub has fully integrated the DeepSeek R1 model in version v1.49.12, offering users a revolutionary interactive experience in the chain of thought!
|
||||
|
||||
## 🚀 Major Updates
|
||||
|
||||
- 🤯 **Comprehensive Support for DeepSeek R1**: Now fully integrated in both the Community and Cloud versions ([lobechat.com](https://lobechat.com)).
|
||||
- 🤯 **Comprehensive Support for DeepSeek R1**: Now fully integrated in both the Community and Cloud versions ([LobeHub.com](https://LobeHub.com)).
|
||||
- 🧠 **Real-Time Chain of Thought Display**: Transparently presents the AI's reasoning process, making the resolution of complex issues clear and visible.
|
||||
- ⚡️ **Deep Thinking Experience**: Utilizing Chain of Thought technology, it provides more insightful AI conversations.
|
||||
- 💫 **Intuitive Problem Analysis**: Makes the analysis of complex issues clear and easy to understand.
|
||||
|
||||
## 🌟 How to Use
|
||||
|
||||
1. Upgrade to LobeChat v1.49.12 or visit [lobechat.com](https://lobechat.com).
|
||||
1. Upgrade to LobeHub v1.49.12 or visit [LobeHub.com](https://LobeHub.com).
|
||||
2. Select the DeepSeek R1 model in the settings.
|
||||
3. Experience a whole new level of intelligent conversation!
|
||||
|
||||
## 📢 Feedback and Support
|
||||
|
||||
If you encounter any issues while using the application or have suggestions for new features, feel free to engage with us through GitHub Discussions. Let's work together to create a better LobeChat!
|
||||
If you encounter any issues while using the application or have suggestions for new features, feel free to engage with us through GitHub Discussions. Let's work together to create a better LobeHub!
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: LobeChat 重磅集成 DeepSeek R1，带来革命性思维链体验
|
||||
description: LobeChat v1.49.12 已完整支持 DeepSeek R1 模型，为用户带来前所未有的思维链交互体验
|
||||
title: LobeHub 重磅集成 DeepSeek R1，带来革命性思维链体验
|
||||
description: LobeHub v1.49.12 已完整支持 DeepSeek R1 模型，为用户带来前所未有的思维链交互体验
|
||||
tags:
|
||||
- DeepSeek R1
|
||||
- CoT
|
||||
|
|
@ -9,21 +9,21 @@ tags:
|
|||
|
||||
# 完美集成 DeepSeek R1 ，开启思维链新体验
|
||||
|
||||
经过近 10 天的精心打磨，LobeChat 已在 v1.49.12 版本中完整集成了 DeepSeek R1 模型，为用户带来革命性的思维链交互体验！
|
||||
经过近 10 天的精心打磨，LobeHub 已在 v1.49.12 版本中完整集成了 DeepSeek R1 模型，为用户带来革命性的思维链交互体验！
|
||||
|
||||
## 🚀 重大更新
|
||||
|
||||
- 🤯 **DeepSeek R1 全面支持**: 现已在社区版与 Cloud 版（[lobechat.com](https://lobechat.com)）中完整接入
|
||||
- 🤯 **DeepSeek R1 全面支持**: 现已在社区版与 Cloud 版（[LobeHub.com](https://LobeHub.com)）中完整接入
|
||||
- 🧠 **实时思维链展示**: 透明呈现 AI 的推理过程，让复杂问题的解决过程清晰可见
|
||||
- ⚡️ **深度思考体验**: 通过 Chain of Thought 技术，带来更具洞察力的 AI 对话
|
||||
- 💫 **直观的问题解析**: 让复杂问题的分析过程变得清晰易懂
|
||||
|
||||
## 🌟 使用方式
|
||||
|
||||
1. 升级到 LobeChat v1.49.12 或访问 [lobechat.com](https://lobechat.com)
|
||||
1. 升级到 LobeHub v1.49.12 或访问 [LobeHub.com](https://LobeHub.com)
|
||||
2. 在设置中选择 DeepSeek R1 模型
|
||||
3. 开启全新的智能对话体验！
|
||||
|
||||
## 📢 反馈与支持
|
||||
|
||||
如果您在使用过程中遇到任何问题，或对新功能有任何建议，欢迎通过 GitHub Discussions 与我们交流。让我们一起打造更好的 LobeChat！
|
||||
如果您在使用过程中遇到任何问题，或对新功能有任何建议，欢迎通过 GitHub Discussions 与我们交流。让我们一起打造更好的 LobeHub！
|
||||
|
|
|
|||
28
docs/changelog/2025-03-02-new-models.zh-CN.mdx
Normal file
28
docs/changelog/2025-03-02-new-models.zh-CN.mdx
Normal file
|
|
@ -0,0 +1,28 @@
|
|||
---
|
||||
title: 全面升级 AI 生态，50+ 模型与 10+ 服务商加入 🚀
|
||||
description: LobeHub v1.49.12 已完整支持 DeepSeek R1 模型，为用户带来前所未有的思维链交互体验
|
||||
tags:
|
||||
- DeepSeek R1
|
||||
- CoT
|
||||
- 思维链
|
||||
---
|
||||
|
||||
# 完美集成 DeepSeek R1 ，开启思维链新体验
|
||||
|
||||
LobeChat 在二月完成了史上最大规模的 AI 生态扩展，带来更强大、更灵活的 AI 对话体验。
|
||||
|
||||
## 🌟 重大更新
|
||||
|
||||
- 🔮 AI 服务商矩阵全面扩充：新增 10+ 个主流 AI 提供商，覆盖全球与国内主流平台
|
||||
- 🧠 推理模型全面接入：支持 Claude 3.7、OpenAI o3-mini 等新一代推理模型的思维链实时展示，优化 DeepSeek R1 多平台解析
|
||||
- 🌐 在线搜索能力革新：集成 SearchXNG、Perplexity 搜索，支持网页深度爬取，Gemini 2.0、Qwen 系列支持原生搜索
|
||||
|
||||
## 📊 模型库大更新
|
||||
|
||||
更新 50+ 个模型配置，包括：
|
||||
|
||||
- OpenAI gpt-4.5-preview
|
||||
- Claude 3.7 Sonnet & Haiku 3.5
|
||||
- Gemini 2.0 系列优化
|
||||
- 月之暗面、通义千问、MiniMax 等国内平台最新模型
|
||||
- Perplexity、Cloudflare、硅基流动等平台模型刷新
|
||||
32
docs/changelog/2025-04-06-exports.zh-CN.mdx
Normal file
32
docs/changelog/2025-04-06-exports.zh-CN.mdx
Normal file
|
|
@ -0,0 +1,32 @@
|
|||
---
|
||||
title: 快捷键设置、数据导出与多项功能优化 ⚡
|
||||
description: LobeHub v1.49.12 已完整支持 DeepSeek R1 模型，为用户带来前所未有的思维链交互体验
|
||||
tags:
|
||||
- LobeHub 快捷键
|
||||
- CoT
|
||||
- 思维链
|
||||
---
|
||||
|
||||
# 完美集成 DeepSeek R1 ，开启思维链新体验
|
||||
|
||||
LobeChat 在三月持续优化用户体验，新增快捷键自定义、数据导出等实用功能，并扩展 AI 服务商生态。
|
||||
|
||||
## 🌟 重要更新
|
||||
|
||||
- ⚡ 快捷键自定义：支持自定义键盘快捷键，打造个性化操作体验
|
||||
- 💾 数据导出功能：支持 PGlite 和 PostgreSQL 数据导出，数据安全更有保障
|
||||
- 🔮 AI 服务商扩展：新增 Xinference、Cohere、Search1API、Infini-AI、PPIO 等服务商
|
||||
- 🧠 推理模型优化：支持推理内容选择器，优化 Claude 3.7、DeepSeek R1 等模型的思维链展示
|
||||
- 🌐 网页爬取增强：特别支持 YouTube、Reddit、微信公众号链接，优化短内容爬取，新增 Search1API 爬虫实现
|
||||
|
||||
## 📊 模型库更新
|
||||
|
||||
新增了多个主流 AI 模型，包括 Google 的 Gemini 2.5 Pro Experimental 和 Gemini 2.0 Flash 系列变体，Anthropic 支持上下文缓存功能，OpenAI 的 gpt-4o-mini-tts 语音模型， DeepSeek-V3-0324 和 Hunyuan-T1-Latest，以及 QwQ、QVQ-Max、文心 ernie-x1-32k-preview 等模型。
|
||||
|
||||
## 💫 体验优化
|
||||
|
||||
- 界面改进：重构 Drawer 样式，优化编辑滚动体验，支持截图分享到剪贴板
|
||||
- 搜索增强：支持非函数调用模型（如 DeepSeek R1）使用在线搜索，Wenxin、Hunyuan 支持内置网络搜索
|
||||
- 文件处理：新增 EPUB 文件分块支持，优化 PDF 处理
|
||||
- 性能提升：重构 Agent Runtime 实现，优化数据库核心代码，修复 LiteLLM 流式使用统计
|
||||
- 稳定性修复：解决主题闪烁、知识库、微信登录等多个问题
|
||||
35
docs/changelog/2025-05-08-desktop-app.zh-CN.mdx
Normal file
35
docs/changelog/2025-05-08-desktop-app.zh-CN.mdx
Normal file
|
|
@ -0,0 +1,35 @@
|
|||
---
|
||||
title: 全新设计风格与桌面端发布 ✨
|
||||
description: LobeChat 正式发布桌面端应用，带来更现代、更流畅的使用体验
|
||||
tags:
|
||||
- 桌面端
|
||||
- LobeHub
|
||||
- 思维链
|
||||
---
|
||||
|
||||
# 全新设计风格与桌面端发布 ✨
|
||||
|
||||
LobeChat 在四月完成重大视觉升级，推出全新 Lobe UI v2 设计系统，并正式发布桌面端应用，带来更现代、更流畅的使用体验。
|
||||
|
||||
## 🌟 重大更新
|
||||
|
||||
- 🎨 全新设计系统：升级至 Lobe UI v2，带来更现代化的界面设计与交互体验
|
||||
- 💻 桌面端正式发布：支持 Windows、macOS 系统托盘、窗口控制等原生功能，提供更便捷的桌面使用体验
|
||||
- 🔌 MCP 协议增强：支持 Streamable HTTP MCP 服务器，优化 stdio MCP 服务器安装体验，新增环境变量参数支持
|
||||
- 🔍 搜索功能扩展：新增 Search1API 搜索服务商支持，优化 SearXNG 分类与时间范围选择
|
||||
- 🔑 SSO 认证扩展：新增 Keycloak 单点登录支持，改进 OIDC OAuth 工作流
|
||||
|
||||
## 📊 模型库更新
|
||||
|
||||
- OpenAI: GPT-4.1 系列、o3/o4-mini
|
||||
- Google: Gemini 2.5 Pro Experimental、推理 Token 统计支持
|
||||
- xAI: Grok 3 系列模型
|
||||
- Anthropic、Mistral、Qwen、Ollama 等平台最新模型
|
||||
|
||||
## 💫 体验优化
|
||||
|
||||
- 界面改进：支持系统角色折叠、优化移动端样式、整齐排列模型标签、错误时允许复制 / 编辑
|
||||
- 性能统计：显示 Token 生成性能、阿里云百炼 Token 使用追踪、Google Gemini 推理 Token 统计
|
||||
- 快捷键增强：新增清除聊天消息、删除消息等快捷键，支持自定义快捷键设置
|
||||
- 工具调用优化：支持更新工具调用参数并重新触发、本地文件插件新增写入文件功能
|
||||
- 网页爬取：新增小红书爬虫规则支持
|
||||
20
docs/changelog/2025-06-08-claude-4.zh-CN.mdx
Normal file
20
docs/changelog/2025-06-08-claude-4.zh-CN.mdx
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
---
|
||||
title: 提示词变量与 Claude 4 推理模型支持 🚀
|
||||
description: 支持 Claude 4 推理模型，并扩展多个 AI 服务商的搜索与推理能力
|
||||
tags:
|
||||
- DeepSeek R1
|
||||
- 提示词变量
|
||||
- Claude Sonnet 4
|
||||
---
|
||||
|
||||
# 提示词变量与 Claude 4 推理模型支持 🚀
|
||||
|
||||
LobeChat 在五月至六月持续优化核心功能，新增提示词变量系统、支持 Claude 4 推理模型，并扩展多个 AI 服务商的搜索与推理能力。
|
||||
|
||||
## 🌟 主要更新
|
||||
|
||||
- 💬 提示词变量系统：支持在提示词和输入框中使用占位符变量，实现动态内容替换
|
||||
- 🧠 Claude 4 系列支持：完整接入 Anthropic Claude 4 推理模型，支持 Web Search 工具与 Beta Header
|
||||
- 🔍 搜索能力扩展：新增 ModelScope 服务商，支持更多平台的搜索与爬虫功能
|
||||
- 📄 文件上传优化：支持直接将文件上传至聊天上下文，改进 PDF、XLSX 文件内容解析
|
||||
- 🔐 页面保护功能：支持页面访问保护，优化 Clerk 中间件路由保护
|
||||
28
docs/changelog/2025-07-08-mcp-market.zh-CN.mdx
Normal file
28
docs/changelog/2025-07-08-mcp-market.zh-CN.mdx
Normal file
|
|
@ -0,0 +1,28 @@
|
|||
---
|
||||
title: MCP 市场与搜索服务商扩展 🔍
|
||||
description: 新增多个搜索服务商支持，并集成 Amazon Cognito 与 Google SSO 认证，持续优化用户体验与开发者生态
|
||||
tags:
|
||||
- MCP 市场
|
||||
- Best MCP
|
||||
- CoT
|
||||
---
|
||||
|
||||
# MCP 市场与搜索服务商扩展 🔍
|
||||
|
||||
LobeChat 在六月至七月推出 MCP 插件市场，新增多个搜索服务商支持，并集成 Amazon Cognito 与 Google SSO 认证，持续优化用户体验与开发者生态。
|
||||
|
||||
## 🌟 重大更新
|
||||
|
||||
- 🛒 MCP 市场上线：桌面端支持 MCP 插件一键安装，提供丰富的插件生态与便捷的安装体验
|
||||
- 🔍 搜索服务商扩展：新增 Brave、Google PSE、Kagi 等内置搜索服务商，支持 Vertex AI Google Search Grounding
|
||||
- 🔐 认证系统增强：集成 Amazon Cognito 与 Google SSO 作为认证提供商，支持页面访问保护
|
||||
- 🤖 v0 (Vercel) 支持：新增 Vercel v0 服务商支持
|
||||
- 📊 数据分析框架：实现数据分析事件追踪框架，优化用户行为分析
|
||||
|
||||
## 💫 体验优化
|
||||
|
||||
- 界面改进：优化移动端模型选择布局、改进文本溢出处理、修复加载动画切换问题
|
||||
- 推理配置：优化 Gemini thinkingBudget 配置、正确处理 reasoning_effort 参数
|
||||
- 搜索优化：支持 Browserless blockAds 与 stealth 参数、修复 Firefox Mermaid 显示错误
|
||||
- 桌面端增强：改进多显示器窗口打开体验、修复主题问题、优化分块加载
|
||||
- 响应动画：改进响应动画合并逻辑、支持过渡动画开关
|
||||
28
docs/changelog/2025-08-08-image-generation.zh-CN.mdx
Normal file
28
docs/changelog/2025-08-08-image-generation.zh-CN.mdx
Normal file
|
|
@ -0,0 +1,28 @@
|
|||
---
|
||||
title: 全新设计风格与桌面端发布 ✨
|
||||
description: LobeHub v1.49.12 已完整支持 DeepSeek R1 模型，为用户带来前所未有的思维链交互体验
|
||||
tags:
|
||||
- DeepSeek R1
|
||||
- CoT
|
||||
- 思维链
|
||||
---
|
||||
|
||||
# AI 图像生成与桌面端增强 🎨
|
||||
|
||||
LobeChat 在七月至八月推出 AI 图像生成功能，新增多个服务商支持，并持续优化桌面端体验与认证系统。
|
||||
|
||||
## 🌟 重大更新
|
||||
|
||||
- 🎨 AI 图像生成：支持通过 Google Imagen、Qwen、Zhipu CogView4、MiniMax 等服务商生成图像
|
||||
- 🔐 认证系统扩展：新增 Amazon Cognito、Google SSO、Okta 认证支持
|
||||
- 🖥️ 桌面端优化：支持网络代理配置、自定义快捷键、OAuth 重构与远程聊天支持
|
||||
- 🔌 MCP 认证增强：支持 Streamable HTTP MCP Server 认证
|
||||
- 🔑 API Key 管理：实现完整的 API Key 管理功能
|
||||
|
||||
## 📊 模型库更新
|
||||
|
||||
新增 Claude Opus 4.1、Grok-4、Kimi K2、Ollama gpt-oss 支持，更新 Gemini 2.5 Flash-Lite GA、Hunyuan A13B thinking、Doubao 思维模型等
|
||||
|
||||
## 💫 体验优化
|
||||
|
||||
桌面端新增通知功能、优化设置窗口布局、改进多显示器体验；优化 MCP 插件调用与显示、修复 Gemini Artifacts 换行问题
|
||||
24
docs/changelog/2025-09-08-gemini.zh-CN.mdx
Normal file
24
docs/changelog/2025-09-08-gemini.zh-CN.mdx
Normal file
|
|
@ -0,0 +1,24 @@
|
|||
---
|
||||
title: Gemini 图像生成与非流式模式支持 🎨
|
||||
description: LobeHub v1.49.12 已完整支持 DeepSeek R1 模型，为用户带来前所未有的思维链交互体验
|
||||
tags:
|
||||
- Gemini
|
||||
- Nano banana
|
||||
- AI 生图
|
||||
---
|
||||
|
||||
# Gemini 图像生成与非流式模式支持 🎨
|
||||
|
||||
LobeChat 在八月至九月新增 Gemini 2.5 Flash Image 图像生成能力，支持非流式响应模式，并扩展多个 AI 服务商与模型支持。
|
||||
|
||||
## 🌟 重大更新
|
||||
|
||||
- 🎨 Gemini 图像生成：支持 Gemini 2.5 Flash Image（Nano Banana）、Imagen 4 GA 等图像生成模型
|
||||
- 🔄 非流式模式：新增非流式响应模式支持，适配更多使用场景
|
||||
- 🌐 服务商扩展：新增 Nebius、AkashChat、BFL 等图像生成服务商支持
|
||||
- 🖼️ Azure OpenAI 图像生成：支持通过 Azure OpenAI 生成图像
|
||||
- 🔧 HTML 预览：支持 HTML 内容预览功能 📊 模型库更新新增 GPT-5 系列、Claude Opus 4.1、Grok Code Fast 1、DeepSeek V3.1、Gemini URL Context Tool 支持
|
||||
|
||||
## 💫 体验优化
|
||||
|
||||
优化思维滚动遮罩效果、支持会话切换快捷键、改进移动端控件表单显示、优化 Gemini 错误提示
|
||||
29
docs/changelog/2025-10-08-python.zh-CN.mdx
Normal file
29
docs/changelog/2025-10-08-python.zh-CN.mdx
Normal file
|
|
@ -0,0 +1,29 @@
|
|||
---
|
||||
title: Claude Sonnet 4.5 与内置 Python 插件 🐍
|
||||
description: LobeHub v1.49.12 已完整支持 DeepSeek R1 模型，为用户带来前所未有的思维链交互体验
|
||||
tags:
|
||||
- Claude Sonnet 4.5
|
||||
- 思维链
|
||||
- Vercel AI Gateway
|
||||
---
|
||||
|
||||
# Claude Sonnet 4.5 与内置 Python 插件 🐍
|
||||
|
||||
LobeChat 在九月至十月新增 Claude Sonnet 4.5 模型支持，推出内置 Python 插件，并优化聊天列表导航与富文本编辑体验。
|
||||
|
||||
## 🌟 主要更新
|
||||
|
||||
- 🐍 内置 Python 插件：支持直接在聊天中执行 Python 代码
|
||||
- 🤖 Claude Sonnet 4.5：接入 Anthropic 最新推理模型
|
||||
- 🗺️ 聊天列表小地图：新增快速导航功能，提升长对话浏览效率
|
||||
- 📝 富文本编辑器：支持数学公式、任务列表、并行发送等功能
|
||||
- 🎨 Qwen 图像编辑：支持通过 Qwen 模型进行图像编辑
|
||||
- 🌐 Vercel AI Gateway：新增 Vercel AI Gateway 服务商支持
|
||||
|
||||
## 📊 模型库更新
|
||||
|
||||
新增 Seedream 4.0、CometAPI、NewAPI 等服务商，更新 Gemini 2.5 视频理解能力
|
||||
|
||||
## 💫 体验优化
|
||||
|
||||
优化聊天输入框支持调整大小、改进移动端标题显示、支持 Base64 图像语法、优化 .doc 文件解析
|
||||
28
docs/changelog/2025-11-08-comfy-ui.zh-CN.mdx
Normal file
28
docs/changelog/2025-11-08-comfy-ui.zh-CN.mdx
Normal file
|
|
@ -0,0 +1,28 @@
|
|||
---
|
||||
title: ComfyUI 集成与知识库优化 ⭐
|
||||
description: 集成 ComfyUI 工作流，新增多个 AI 服务商与模型支持，并持续优化知识库与用户体验
|
||||
tags:
|
||||
- AI 知识库
|
||||
- 工作流
|
||||
- ComfyUI
|
||||
---
|
||||
|
||||
# ComfyUI 集成与知识库优化 ⭐
|
||||
|
||||
LobeChat 在十月至十一月集成 ComfyUI 工作流，新增多个 AI 服务商与模型支持，并持续优化知识库与用户体验。
|
||||
|
||||
## 🌟 重要更新
|
||||
|
||||
- 🎨 ComfyUI 集成：支持 ComfyUI 工作流集成
|
||||
- 🤖 新增服务商：Cerebras、CometAPI 等服务商支持
|
||||
- 📄 PDF 导出：支持将对话导出为 PDF 格式
|
||||
- 🗂️ 知识库优化：新增瀑布流布局、支持上传时自动解压文件
|
||||
- 🖼️ 图像生成扩展：支持硅基流动、混元 Text-to-Image 3 等图像生成服务
|
||||
|
||||
## 📊 模型库更新
|
||||
|
||||
新增 Claude Haiku 4.5、GPT-5 Pro、MiniMax-M2、Imagen 4 for Vertex AI 等模型
|
||||
|
||||
## 💫 体验优化
|
||||
|
||||
优化富文本链接显示、改进搜索体验、支持禁用富文本编辑、新增删除与重新生成快捷键、改进更新通知
|
||||
26
docs/changelog/2025-12-20-mcp.zh-CN.mdx
Normal file
26
docs/changelog/2025-12-20-mcp.zh-CN.mdx
Normal file
|
|
@ -0,0 +1,26 @@
|
|||
---
|
||||
title: MCP 云端点与模型库扩展 🔌
|
||||
description: 新增多个 AI 服务商，并改进知识库功能。
|
||||
tags:
|
||||
- MCP
|
||||
- LobeHub
|
||||
- CoT
|
||||
- 思维链
|
||||
---
|
||||
|
||||
# MCP 云端点与模型库扩展 🔌
|
||||
|
||||
LobeChat 在十一月持续优化模型支持与用户体验，新增多个 AI 服务商，并改进知识库功能。
|
||||
|
||||
## 🌟 重要更新
|
||||
|
||||
- 🔌 MCP 云端点：支持市场云端点 MCP 集成，扩展工具生态
|
||||
- 🤖 新增服务商：支持 ZenMux、Nano Banana Pro、七牛云等多个 AI 服务商
|
||||
- 📚 知识库增强：支持创建页面、优化文件管理，改进 RAG 搜索体验
|
||||
- 🎨 图像生成：新增多个图像模型支持，优化图像生成配置
|
||||
- 🔐 认证优化：改进 OIDC 认证流程，优化桌面端登录体验
|
||||
- 💬 对话优化：支持话题超链接、改进消息编辑与删除功能
|
||||
|
||||
## 💫 体验优化
|
||||
|
||||
优化话题列表交互、改进工具调用显示、完善富文本编辑、优化 Token 使用统计动画、改进模型选择器排序
|
||||
|
|
@ -2,6 +2,66 @@
|
|||
"$schema": "https://github.com/lobehub/lobe-chat/blob/main/docs/changelog/schema.json",
|
||||
"cloud": [],
|
||||
"community": [
|
||||
{
|
||||
"image": "https://file.rene.wang/clipboard-1769155711708-710967bee57bc.png",
|
||||
"id": "2025-12-20-mcp",
|
||||
"date": "2025-12-20",
|
||||
"versionRange": ["1.142.8", "1.143"]
|
||||
},
|
||||
{
|
||||
"image": "https://file.rene.wang/clipboard-1769155737647-1b4fc6558f029.png",
|
||||
"id": "2025-11-08-comfy-ui",
|
||||
"date": "2025-11-08",
|
||||
"versionRange": ["1.133.5", "1.142.8"]
|
||||
},
|
||||
{
|
||||
"image": "https://file.rene.wang/clipboard-1769155791342-7f43b72cc6b42.png",
|
||||
"id": "2025-10-08-python",
|
||||
"date": "2025-10-08",
|
||||
"versionRange": ["1.120.7", "1.133.5"]
|
||||
},
|
||||
{
|
||||
"image": "https://file.rene.wang/clipboard-1769155818070-7eb403550b6c7.png",
|
||||
"id": "2025-09-08-gemini",
|
||||
"date": "2025-09-08",
|
||||
"versionRange": ["1.109.1", "1.120.7"]
|
||||
},
|
||||
{
|
||||
"image": "https://file.rene.wang/clipboard-1769155880302-272fbd2c5290b.png",
|
||||
"id": "2025-08-08-image-generation",
|
||||
"date": "2025-08-08",
|
||||
"versionRange": ["1.97.10", "1.109.1"]
|
||||
},
|
||||
{
|
||||
"image": "https://file.rene.wang/clipboard-1769155935435-93dab92dd0f44.png",
|
||||
"id": "2025-07-08-mcp-market",
|
||||
"date": "2025-07-08",
|
||||
"versionRange": ["1.93.3", "1.97.10"]
|
||||
},
|
||||
{
|
||||
"image": "https://file.rene.wang/clipboard-1769155973881-ff1ee142d5b8f.png",
|
||||
"id": "2025-06-08-claude-4",
|
||||
"date": "2025-06-08",
|
||||
"versionRange": ["1.84.27", "1.93.3"]
|
||||
},
|
||||
{
|
||||
"image": "https://file.rene.wang/clipboard-1769156005535-c2e79e11f4b56.png",
|
||||
"id": "2025-05-08-desktop-app",
|
||||
"date": "2025-05-08",
|
||||
"versionRange": ["1.77.17", "1.84.27"]
|
||||
},
|
||||
{
|
||||
"image": "https://file.rene.wang/clipboard-1769156036607-2b4fe37c4b56c.png",
|
||||
"id": "2025-04-06-exports",
|
||||
"date": "2025-04-06",
|
||||
"versionRange": ["1.67.2", "1.77.17"]
|
||||
},
|
||||
{
|
||||
"image": "https://file.rene.wang/clipboard-1769156050787-ecf4f48474ae2.png",
|
||||
"id": "2025-03-02-new-models",
|
||||
"date": "2025-03-02",
|
||||
"versionRange": ["1.49.13", "1.67.2"]
|
||||
},
|
||||
{
|
||||
"image": "https://github.com/user-attachments/assets/5fe4c373-ebd0-42a9-bdca-0ab7e0a2e747",
|
||||
"id": "2025-02-02-deepseek-r1",
|
||||
|
|
|
|||
|
|
@ -1,14 +1,21 @@
|
|||
---
|
||||
title: New Authentication Provider Guide
|
||||
description: Learn how to implement a new authentication provider using Auth.js in LobeHub.
|
||||
tags:
|
||||
- Authentication
|
||||
- Auth.js
|
||||
- LobeHub
|
||||
- Okta
|
||||
- OAuth
|
||||
---
|
||||
|
||||
# New Authentication Provider Guide
|
||||
|
||||
LobeChat uses [Better Auth](https://www.better-auth.com) as its authentication service. This document explains how to add new SSO authentication providers.
|
||||
LobeHub uses [Auth.js v5](https://authjs.dev/) as the external authentication service. Auth.js is an open-source authentication library that provides a simple way to implement authentication and authorization features. This document will introduce how to use Auth.js to implement a new authentication provider.
|
||||
|
||||
## Architecture Overview
|
||||
|
||||
Better Auth SSO providers fall into two categories:
|
||||
To add a new authentication provider in LobeHub (for example, adding Okta), you need to follow the steps below:
|
||||
|
||||
| Type | Description | Examples |
|
||||
| --------- | ------------------------------------------- | -------------------------------- |
|
||||
|
|
@ -176,20 +183,4 @@ AUTH_OKTA_SECRET=your-client-secret
|
|||
AUTH_OKTA_ISSUER=https://your-domain.okta.com
|
||||
```
|
||||
|
||||
## Debugging Tips
|
||||
|
||||
1. **Environment variable check fails**: Ensure all required environment variables are set
|
||||
2. **Callback URL errors**: Verify the callback URL configured in your OAuth application
|
||||
3. **User profile mapping**: Use `mapProfileToUser` to customize the mapping from OAuth profile to user info
|
||||
|
||||
## Related Files
|
||||
|
||||
| File | Description |
|
||||
| ----------------------------------------- | -------------------------------- |
|
||||
| `src/libs/better-auth/sso/providers/*.ts` | Provider definitions |
|
||||
| `src/libs/better-auth/sso/index.ts` | Provider registration |
|
||||
| `src/libs/better-auth/sso/types.ts` | Type definitions |
|
||||
| `src/libs/better-auth/sso/helpers.ts` | Helper functions |
|
||||
| `src/libs/better-auth/constants.ts` | Built-in provider constants |
|
||||
| `src/envs/auth.ts` | Environment variable definitions |
|
||||
| `src/libs/better-auth/define-config.ts` | Better Auth configuration |
|
||||
Now, you can use Okta as your provider to implement the authentication feature in LobeHub.
|
||||
|
|
|
|||
|
|
@ -1,12 +1,20 @@
|
|||
---
|
||||
title: 新身份验证提供商开发指南
|
||||
title: 新身份验证方式开发指南
|
||||
description: 学习如何在 LobeHub 中使用 Auth.js v5 添加新的身份验证提供者。
|
||||
tags:
|
||||
- 身份验证
|
||||
- Auth.js
|
||||
- Okta
|
||||
- 开发指南
|
||||
---
|
||||
|
||||
# 新身份验证提供商开发指南
|
||||
# 新身份验证方式开发指南
|
||||
|
||||
LobeHub 使用 [Auth.js v5](https://authjs.dev/) 作为外部身份验证服务。Auth.js 是一个开源的身份验证库，它提供了一种简单的方式来实现身份验证和授权功能。本文档将介绍如何使用 Auth.js 来实现新的身份验证方式。
|
||||
|
||||
LobeChat 使用 [Better Auth](https://www.better-auth.com) 作为身份验证服务。本文档介绍如何添加新的 SSO 身份验证提供商。
|
||||
|
||||
## 架构概述
|
||||
为了在 LobeHub 中添加新的身份验证提供者（例如添加 Okta)，你需要完成以下步骤：
|
||||
|
||||
Better Auth SSO 提供商分为两类：
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,12 @@
|
|||
---
|
||||
title: Adding New Image Models
|
||||
description: >-
|
||||
Explore how to add new image models for AI generation with standard
|
||||
parameters.
|
||||
tags:
|
||||
- AI Image Generation
|
||||
- Image Models
|
||||
- OpenAI Compatibility
|
||||
---
|
||||
|
||||
# Adding New Image Models
|
||||
|
|
|
|||
|
|
@ -1,5 +1,10 @@
|
|||
---
|
||||
title: 添加新的图像模型
|
||||
description: 了解如何添加新的图像模型并兼容 OpenAI 请求格式。
|
||||
tags:
|
||||
- 图像模型
|
||||
- AI 绘画
|
||||
- OpenAI 兼容
|
||||
---
|
||||
|
||||
# 添加新的图像模型
|
||||
|
|
|
|||
|
|
@ -1,41 +1,50 @@
|
|||
---
|
||||
title: Architecture Design
|
||||
description: >-
|
||||
Explore the architecture of LobeHub, an AI chat app built on Next.js,
|
||||
featuring frontend, APIs, and markets.
|
||||
tags:
|
||||
- LobeHub
|
||||
- AI Chat Application
|
||||
- Next.js
|
||||
- Architecture Design
|
||||
- Frontend Development
|
||||
---
|
||||
|
||||
# Architecture Design
|
||||
|
||||
LobeChat is an AI chat application built on the Next.js framework, aiming to provide an AI productivity platform that enables users to interact with AI through natural language. The following is an overview of the architecture design of LobeChat:
|
||||
LobeHub is an AI chat application built on the Next.js framework, aiming to provide an AI productivity platform that enables users to interact with AI through natural language. The following is an overview of the architecture design of LobeHub:
|
||||
|
||||
## Application Architecture Overview
|
||||
|
||||
The overall architecture of LobeChat consists of the frontend, EdgeRuntime API, Agents Market, Plugin Market, and independent plugins. These components collaborate to provide a complete AI experience.
|
||||
The overall architecture of LobeHub consists of the frontend, EdgeRuntime API, Agents Market, Plugin Market, and independent plugins. These components collaborate to provide a complete AI experience.
|
||||
|
||||
## Frontend Architecture
|
||||
|
||||
The frontend of LobeChat adopts the Next.js framework, leveraging its powerful server-side rendering (SSR) capability and routing functionality. The frontend utilizes a stack of technologies, including the antd component library, lobe-ui AIGC component library, zustand state management, swr request library, i18next internationalization library, and more. These technologies collectively support the functionality and features of LobeChat.
|
||||
The frontend of LobeHub adopts the Next.js framework, leveraging its powerful server-side rendering (SSR) capability and routing functionality. The frontend utilizes a stack of technologies, including the antd component library, lobe-ui AIGC component library, zustand state management, swr request library, i18next internationalization library, and more. These technologies collectively support the functionality and features of LobeHub.
|
||||
|
||||
The components in the frontend architecture include app, components, config, const, features, helpers, hooks, layout, locales, migrations, prompts, services, store, styles, types, and utils. Each component has specific responsibilities and collaborates with others to achieve different functionalities.
|
||||
|
||||
## Edge Runtime API
|
||||
|
||||
The Edge Runtime API is one of the core components of LobeChat, responsible for handling the core logic of AI conversations. It provides interaction interfaces with the AI engine, including natural language processing, intent recognition, and response generation. The EdgeRuntime API communicates with the frontend, receiving user input and returning corresponding responses.
|
||||
The Edge Runtime API is one of the core components of LobeHub, responsible for handling the core logic of AI conversations. It provides interaction interfaces with the AI engine, including natural language processing, intent recognition, and response generation. The EdgeRuntime API communicates with the frontend, receiving user input and returning corresponding responses.
|
||||
|
||||
## Agents Market
|
||||
|
||||
The Agents Market is a crucial part of LobeChat, providing various AI agents for different scenarios to handle specific tasks and domains. The Agents Market also offers functionality for discovering and uploading agents, allowing users to find agents created by others and easily share their own agents in the market.
|
||||
The Agents Market is a crucial part of LobeHub, providing various AI agents for different scenarios to handle specific tasks and domains. The Agents Market also offers functionality for discovering and uploading agents, allowing users to find agents created by others and easily share their own agents in the market.
|
||||
|
||||
## Plugin Market
|
||||
|
||||
The Plugin Market is another key component of LobeChat, offering various plugins to extend the functionality and features of LobeChat. Plugins can be independent functional modules or integrated with agents from the Agents Market. During conversations, the assistant automatically identifies user input, recognizes suitable plugins, and passes them to the corresponding plugins for processing and returns the results.
|
||||
The Plugin Market is another key component of LobeHub, offering various plugins to extend the functionality and features of LobeHub. Plugins can be independent functional modules or integrated with agents from the Agents Market. During conversations, the assistant automatically identifies user input, recognizes suitable plugins, and passes them to the corresponding plugins for processing and returns the results.
|
||||
|
||||
## Security and Performance Optimization
|
||||
|
||||
LobeChat's security strategy includes authentication and permission management. Users need to authenticate before using LobeChat, and operations are restricted based on the user's permissions.
|
||||
LobeHub's security strategy includes authentication and permission management. Users need to authenticate before using LobeHub, and operations are restricted based on the user's permissions.
|
||||
|
||||
To optimize performance, LobeChat utilizes Next.js SSR functionality to achieve fast page loading and response times. Additionally, a series of performance optimization measures are implemented, including code splitting, caching, and resource compression.
|
||||
To optimize performance, LobeHub utilizes Next.js SSR functionality to achieve fast page loading and response times. Additionally, a series of performance optimization measures are implemented, including code splitting, caching, and resource compression.
|
||||
|
||||
## Development and Deployment Process
|
||||
|
||||
LobeChat's development process includes version control, testing, continuous integration, and continuous deployment. The development team uses version control systems for code management and conducts unit and integration testing to ensure code quality. Continuous integration and deployment processes ensure rapid delivery and deployment of code.
|
||||
LobeHub's development process includes version control, testing, continuous integration, and continuous deployment. The development team uses version control systems for code management and conducts unit and integration testing to ensure code quality. Continuous integration and deployment processes ensure rapid delivery and deployment of code.
|
||||
|
||||
The above is a brief introduction to the architecture design of LobeChat, detailing the responsibilities and collaboration of each component, as well as the impact of design decisions on application functionality and performance.
|
||||
The above is a brief introduction to the architecture design of LobeHub, detailing the responsibilities and collaboration of each component, as well as the impact of design decisions on application functionality and performance.
|
||||
|
|
|
|||
|
|
@ -1,41 +1,48 @@
|
|||
---
|
||||
title: 架构设计
|
||||
description: 深入了解 LobeHub 的架构设计，包括前端、API 和市场组件。
|
||||
tags:
|
||||
- LobeHub
|
||||
- 架构设计
|
||||
- AI 聊天应用
|
||||
- Next.js
|
||||
- Edge Runtime API
|
||||
---
|
||||
|
||||
# 架构设计
|
||||
|
||||
LobeChat 是一个基于 Next.js 框架构建的 AI 聊天应用，旨在提供一个 AI 生产力平台，使用户能够与 AI 进行自然语言交互。以下是 LobeChat 的架构设计介稿：
|
||||
LobeHub 是一个基于 Next.js 框架构建的 AI 聊天应用，旨在提供一个 AI 生产力平台，使用户能够与 AI 进行自然语言交互。以下是 LobeHub 的架构设计介稿：
|
||||
|
||||
## 应用架构概览
|
||||
|
||||
LobeChat 的整体架构由前端、EdgeRuntime API、Agents 市场、插件市场和独立插件组成。这些组件相互协作，以提供完整的 AI 体验。
|
||||
LobeHub 的整体架构由前端、EdgeRuntime API、Agents 市场、插件市场和独立插件组成。这些组件相互协作，以提供完整的 AI 体验。
|
||||
|
||||
## 前端架构
|
||||
|
||||
LobeChat 的前端采用 Next.js 框架，利用其强大的 SSR（服务器端渲染）能力和路由功能。前端使用了一系列技术栈，包括 antd 组件库和 lobe-ui AIGC 组件库、zustand 状态管理、swr 请求库、i18next 国际化库等。这些技术栈共同支持了 LobeChat 的功能和特性。
|
||||
LobeHub 的前端采用 Next.js 框架，利用其强大的 SSR（服务器端渲染）能力和路由功能。前端使用了一系列技术栈，包括 antd 组件库和 lobe-ui AIGC 组件库、zustand 状态管理、swr 请求库、i18next 国际化库等。这些技术栈共同支持了 LobeHub 的功能和特性。
|
||||
|
||||
前端架构中的组件包括 app、components、config、const、features、helpers、hooks、layout、locales、migrations、prompts、services、store、styles、types 和 utils。每个组件都有特定的职责，并与其他组件协同工作，以实现不同的功能。
|
||||
|
||||
## Edge Runtime API
|
||||
|
||||
Edge Runtime API 是 LobeChat 的核心组件之一，负责处理 AI 会话的核心逻辑。它提供了与 AI 引擎的交互接口，包括自然语言处理、意图识别和回复生成等。EdgeRuntime API 与前端进行通信，接收用户的输入并返回相应的回复。
|
||||
Edge Runtime API 是 LobeHub 的核心组件之一，负责处理 AI 会话的核心逻辑。它提供了与 AI 引擎的交互接口，包括自然语言处理、意图识别和回复生成等。EdgeRuntime API 与前端进行通信，接收用户的输入并返回相应的回复。
|
||||
|
||||
## Agents 市场
|
||||
|
||||
Agents 市场是 LobeChat 的一个重要组成部分，它提供了各种不同场景的 AI Agent，用于处理特定的任务和领域。Agents 市场还提供了使用和上传 Agent 的功能，使用户能够发现其他人制作的 Agent ，也可以一键分享自己的 Agent 到市场上。
|
||||
Agents 市场是 LobeHub 的一个重要组成部分，它提供了各种不同场景的 AI Agent，用于处理特定的任务和领域。Agents 市场还提供了使用和上传 Agent 的功能，使用户能够发现其他人制作的 Agent ，也可以一键分享自己的 Agent 到市场上。
|
||||
|
||||
## 插件市场
|
||||
|
||||
插件市场是 LobeChat 的另一个关键组件，它提供了各种插件，用于扩展 LobeChat 的功能和特性。插件可以是独立的功能模块，也可以与 Agents 市场的 Agent 进行集成。在会话中，助手将自动识别用户的输入，并识别适合的插件并传递给相应的插件进行处理，并返回处理结果。
|
||||
插件市场是 LobeHub 的另一个关键组件，它提供了各种插件，用于扩展 LobeHub 的功能和特性。插件可以是独立的功能模块，也可以与 Agents 市场的 Agent 进行集成。在会话中，助手将自动识别用户的输入，并识别适合的插件并传递给相应的插件进行处理，并返回处理结果。
|
||||
|
||||
## 安全性和性能优化
|
||||
|
||||
LobeChat 的安全性策略包括身份验证和权限管理。用户需要进行身份验证后才能使用 LobeChat，同时根据用户的权限进行相应的操作限制。
|
||||
LobeHub 的安全性策略包括身份验证和权限管理。用户需要进行身份验证后才能使用 LobeHub，同时根据用户的权限进行相应的操作限制。
|
||||
|
||||
为了优化性能，LobeChat 使用了 Next.js 的 SSR 功能，实现了快速的页面加载和响应时间。此外，还采用了一系列的性能优化措施，包括代码分割、缓存和资源压缩等。
|
||||
为了优化性能，LobeHub 使用了 Next.js 的 SSR 功能，实现了快速的页面加载和响应时间。此外，还采用了一系列的性能优化措施，包括代码分割、缓存和资源压缩等。
|
||||
|
||||
## 开发和部署流程
|
||||
|
||||
LobeChat 的开发流程包括版本控制、测试、持续集成和持续部署。开发团队使用版本控制系统进行代码管理，并进行单元测试和集成测试以确保代码质量。持续集成和持续部署流程确保了代码的快速交付和部署。
|
||||
LobeHub 的开发流程包括版本控制、测试、持续集成和持续部署。开发团队使用版本控制系统进行代码管理，并进行单元测试和集成测试以确保代码质量。持续集成和持续部署流程确保了代码的快速交付和部署。
|
||||
|
||||
以上是 LobeChat 的架构设计介绍简介，详细解释了各个组件的职责和协作方式，以及设计决策对应用功能和性能的影响。
|
||||
以上是 LobeHub 的架构设计介绍简介，详细解释了各个组件的职责和协作方式，以及设计决策对应用功能和性能的影响。
|
||||
|
|
|
|||
|
|
@ -1,5 +1,13 @@
|
|||
---
|
||||
title: Lobe Chat API Client-Server Interaction Logic
|
||||
description: >-
|
||||
Explore the client-server interaction logic of Lobe Chat API, including event
|
||||
sequences.
|
||||
tags:
|
||||
- Lobe Chat API
|
||||
- Client-Server Interaction
|
||||
- Event Sequences
|
||||
- API Logic
|
||||
---
|
||||
|
||||
# Lobe Chat API Client-Server Interaction Logic
|
||||
|
|
@ -251,7 +259,7 @@ AgentRuntime is a core abstraction layer in Lobe Chat that encapsulates a unifie
|
|||
baseURL: OPENROUTER_BASE_URL,
|
||||
defaultHeaders: {
|
||||
'HTTP-Referer': 'https://github.com/lobehub/lobe-chat',
|
||||
'X-Title': 'LobeChat',
|
||||
'X-Title': 'LobeHub',
|
||||
},
|
||||
});
|
||||
this.baseURL = OPENROUTER_BASE_URL;
|
||||
|
|
|
|||
|
|
@ -1,5 +1,11 @@
|
|||
---
|
||||
title: Lobe Chat API 前后端交互逻辑
|
||||
description: 深入了解 Lobe Chat API 的前后端交互实现逻辑和核心组件。
|
||||
tags:
|
||||
- Lobe Chat API
|
||||
- 前后端交互
|
||||
- 事件序列
|
||||
- 核心组件
|
||||
---
|
||||
|
||||
# Lobe Chat API 前后端交互逻辑
|
||||
|
|
@ -251,7 +257,7 @@ AgentRuntime 是 Lobe Chat 中的一个核心抽象层，它封装了与不同 A
|
|||
baseURL: OPENROUTER_BASE_URL,
|
||||
defaultHeaders: {
|
||||
'HTTP-Referer': 'https://github.com/lobehub/lobe-chat',
|
||||
'X-Title': 'LobeChat',
|
||||
'X-Title': 'LobeHub',
|
||||
},
|
||||
});
|
||||
this.baseURL = OPENROUTER_BASE_URL;
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: ComfyUI Extension Development Guide
|
||||
description: >-
|
||||
Learn how to add new models, workflows, and features to LobeChat's ComfyUI
|
||||
Learn how to add new models, workflows, and features to LobeHub's ComfyUI
|
||||
integration
|
||||
tags:
|
||||
- ComfyUI
|
||||
|
|
@ -12,11 +12,11 @@ tags:
|
|||
|
||||
# ComfyUI Extension Development Guide
|
||||
|
||||
This guide is based on actual code implementation and helps developers extend LobeChat's ComfyUI integration functionality.
|
||||
This guide is based on actual code implementation and helps developers extend LobeHub's ComfyUI integration functionality.
|
||||
|
||||
## Architecture Overview
|
||||
|
||||
LobeChat ComfyUI integration uses a four-layer service architecture built around the main `LobeComfyUI` class:
|
||||
LobeHub ComfyUI integration uses a four-layer service architecture built around the main `LobeComfyUI` class:
|
||||
|
||||
```plaintext
|
||||
packages/model-runtime/src/providers/comfyui/
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: ComfyUI 扩展开发指南
|
||||
description: 学习如何为 LobeChat ComfyUI 集成添加新模型、工作流和功能扩展
|
||||
description: 学习如何为 LobeHub ComfyUI 集成添加新模型、工作流和功能扩展
|
||||
tags:
|
||||
- ComfyUI
|
||||
- 开发指南
|
||||
|
|
@ -10,11 +10,11 @@ tags:
|
|||
|
||||
# ComfyUI 扩展开发指南
|
||||
|
||||
本指南基于实际代码实现，帮助开发者扩展 LobeChat 的 ComfyUI 集成功能。
|
||||
本指南基于实际代码实现，帮助开发者扩展 LobeHub 的 ComfyUI 集成功能。
|
||||
|
||||
## 架构概览
|
||||
|
||||
LobeChat ComfyUI 集成采用四层服务架构，围绕 `LobeComfyUI` 主类构建：
|
||||
LobeHub ComfyUI 集成采用四层服务架构，围绕 `LobeComfyUI` 主类构建：
|
||||
|
||||
```plaintext
|
||||
packages/model-runtime/src/providers/comfyui/
|
||||
|
|
@ -995,4 +995,4 @@ const optimizedResult = await comfyUI.createImage({
|
|||
- 添加新模型时，请遵循测试架构指南确保测试完整性
|
||||
- 在提交代码前务必运行相关测试确保覆盖率达标
|
||||
|
||||
通过遵循这些指南，开发者可以有效地在 LobeChat 中使用和扩展 ComfyUI 功能，为用户提供强大的图像生成和处理能力。
|
||||
通过遵循这些指南，开发者可以有效地在 LobeHub 中使用和扩展 ComfyUI 功能，为用户提供强大的图像生成和处理能力。
|
||||
|
|
|
|||
|
|
@ -1,14 +1,23 @@
|
|||
---
|
||||
title: Code Style and Contribution Guidelines
|
||||
description: >-
|
||||
Learn about LobeHub's code style and contribution process for consistent
|
||||
coding.
|
||||
tags:
|
||||
- Code Style
|
||||
- Contribution Guidelines
|
||||
- LobeHub
|
||||
- ESLint
|
||||
- Prettier
|
||||
---
|
||||
|
||||
# Code Style and Contribution Guidelines
|
||||
|
||||
Welcome to the Code Style and Contribution Guidelines for LobeChat. This guide will help you understand our code standards and contribution process, ensuring code consistency and smooth project progression.
|
||||
Welcome to the Code Style and Contribution Guidelines for LobeHub. This guide will help you understand our code standards and contribution process, ensuring code consistency and smooth project progression.
|
||||
|
||||
## Code Style
|
||||
|
||||
In LobeChat, we use the [@lobehub/lint](https://github.com/lobehub/lobe-lint) package to maintain a unified code style. This package incorporates configurations for `ESLint`, `Prettier`, `remarklint`, and `stylelint` to ensure that our JavaScript, Markdown, and CSS files adhere to the same coding standards.
|
||||
In LobeHub, we use the [@lobehub/lint](https://github.com/lobehub/lobe-lint) package to maintain a unified code style. This package incorporates configurations for `ESLint`, `Prettier`, `remarklint`, and `stylelint` to ensure that our JavaScript, Markdown, and CSS files adhere to the same coding standards.
|
||||
|
||||
### ESLint
|
||||
|
||||
|
|
@ -36,7 +45,7 @@ You don't need to manually run these checks. The project is configured with husk
|
|||
|
||||
## Contribution Process
|
||||
|
||||
LobeChat follows the gitmoji and semantic release as our code submission and release process.
|
||||
LobeHub follows the gitmoji and semantic release as our code submission and release process.
|
||||
|
||||
### Gitmoji
|
||||
|
||||
|
|
|
|||
|
|
@ -1,14 +1,21 @@
|
|||
---
|
||||
title: 代码风格与贡献指南
|
||||
description: 了解 LobeHub 的代码规范和贡献流程，确保代码一致性。
|
||||
tags:
|
||||
- 代码风格
|
||||
- 贡献指南
|
||||
- LobeHub
|
||||
- ESLint
|
||||
- Prettier
|
||||
---
|
||||
|
||||
# 代码风格与贡献指南
|
||||
|
||||
欢迎来到 LobeChat 的代码风格与贡献指南。本指南将帮助您理解我们的代码规范和贡献流程，确保代码的一致性和项目的顺利进行。
|
||||
欢迎来到 LobeHub 的代码风格与贡献指南。本指南将帮助您理解我们的代码规范和贡献流程，确保代码的一致性和项目的顺利进行。
|
||||
|
||||
## 代码风格
|
||||
|
||||
在 LobeChat 中，我们使用 [@lobehub/lint](https://github.com/lobehub/lobe-lint) 程序包来统一代码风格。该程序包内置了 `ESLint`、`Prettier`、`remarklint` 和 `stylelint` 的配置，以确保我们的 JavaScript、Markdown 和 CSS 文件遵循相同的编码标准。
|
||||
在 LobeHub 中，我们使用 [@lobehub/lint](https://github.com/lobehub/lobe-lint) 程序包来统一代码风格。该程序包内置了 `ESLint`、`Prettier`、`remarklint` 和 `stylelint` 的配置，以确保我们的 JavaScript、Markdown 和 CSS 文件遵循相同的编码标准。
|
||||
|
||||
### ESLint
|
||||
|
||||
|
|
@ -36,7 +43,7 @@ Prettier 负责代码格式化，以保证代码的一致性。您可以在 `.pr
|
|||
|
||||
## 贡献流程
|
||||
|
||||
LobeChat 采用 gitmoji 和 semantic release 作为我们的代码提交和发布流程。
|
||||
LobeHub 采用 gitmoji 和 semantic release 作为我们的代码提交和发布流程。
|
||||
|
||||
### Gitmoji
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,19 @@
|
|||
---
|
||||
title: How to Develop a New Feature
|
||||
description: >-
|
||||
Learn how to implement the Chat Messages feature in LobeHub using Next.js and
|
||||
TypeScript.
|
||||
tags:
|
||||
- LobeHub
|
||||
- Next.js
|
||||
- TypeScript
|
||||
- Chat Feature
|
||||
- Zustand
|
||||
---
|
||||
|
||||
# How to Develop a New Feature
|
||||
|
||||
LobeChat is built on the Next.js framework and uses TypeScript as the primary development language. When developing a new feature, we need to follow a certain development process to ensure the quality and stability of the code. The general process can be divided into the following five steps:
|
||||
LobeHub is built on the Next.js framework and uses TypeScript as the primary development language. When developing a new feature, we need to follow a certain development process to ensure the quality and stability of the code. The general process can be divided into the following five steps:
|
||||
|
||||
1. Routing: Define routes (`src/app`).
|
||||
2. Data Structure: Define data structures (`src/types`).
|
||||
|
|
@ -80,7 +89,7 @@ const ChatPage = () => {
|
|||
renderItem={(message) => (
|
||||
<List.Item>
|
||||
<Typography.Text>{message.content}</Typography.Text>
|
||||
|
||||
|
||||
</List.Item>
|
||||
)}
|
||||
/>
|
||||
|
|
@ -90,7 +99,7 @@ const ChatPage = () => {
|
|||
export default ChatPage;
|
||||
```
|
||||
|
||||
> **Note on Feature Organization**: LobeChat uses two patterns for organizing features:
|
||||
> **Note on Feature Organization**: LobeHub uses two patterns for organizing features:
|
||||
>
|
||||
> - **Global features** (`src/features/`): Shared components like `ChatInput`, `Conversation` used across the app
|
||||
> - **Page-specific features** (`src/app/<page>/features/`): Components used only within a specific page route
|
||||
|
|
@ -119,12 +128,12 @@ const ChatPage = () => {
|
|||
renderItem={(message) => (
|
||||
<List.Item>
|
||||
<Typography.Text>{message.content}</Typography.Text>
|
||||
|
||||
|
||||
</List.Item>
|
||||
)}
|
||||
/>
|
||||
<Button onClick={handleSend}>Send</Button>
|
||||
|
||||
|
||||
</>
|
||||
);
|
||||
};
|
||||
|
|
@ -132,4 +141,4 @@ const ChatPage = () => {
|
|||
export default ChatPage;
|
||||
```
|
||||
|
||||
The above is the step to implement the "chat message" feature in LobeChat. Of course, in the actual development of LobeChat, the business requirements and scenarios faced in real situations are far more complex than the above demo. Please develop according to the actual situation.
|
||||
The above is the step to implement the "chat message" feature in LobeHub. Of course, in the actual development of LobeHub, the business requirements and scenarios faced in real situations are far more complex than the above demo. Please develop according to the actual situation.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,17 @@
|
|||
---
|
||||
title: 如何开发一个新功能：前端实现
|
||||
description: 学习如何在 LobeHub 中实现会话消息功能，使用 Next.js 和 TypeScript。
|
||||
tags:
|
||||
- 前端开发
|
||||
- Next.js
|
||||
- TypeScript
|
||||
- Zustand
|
||||
- 功能实现
|
||||
---
|
||||
|
||||
# 如何开发一个新功能：前端实现
|
||||
|
||||
LobeChat 基于 Next.js 框架构建，使用 TypeScript 作为主要开发语言。在开发新功能时，我们需要遵循一定的开发流程，以确保代码的质量和稳定性。大致的流程分为以下五步：
|
||||
LobeHub 基于 Next.js 框架构建，使用 TypeScript 作为主要开发语言。在开发新功能时，我们需要遵循一定的开发流程，以确保代码的质量和稳定性。大致的流程分为以下五步：
|
||||
|
||||
1. 路由：定义路由 (`src/app`)
|
||||
2. 数据结构： 定义数据结构 ( `src/types` )
|
||||
|
|
@ -80,7 +87,7 @@ const ChatPage = () => {
|
|||
renderItem={(message) => (
|
||||
<List.Item>
|
||||
<Typography.Text>{message.content}</Typography.Text>
|
||||
|
||||
|
||||
</List.Item>
|
||||
)}
|
||||
/>
|
||||
|
|
@ -90,7 +97,7 @@ const ChatPage = () => {
|
|||
export default ChatPage;
|
||||
```
|
||||
|
||||
> **关于功能组件组织方式的说明**：LobeChat 使用两种模式来组织功能组件：
|
||||
> **关于功能组件组织方式的说明**：LobeHub 使用两种模式来组织功能组件：
|
||||
>
|
||||
> - **全局功能**（`src/features/`）：跨应用共享的组件，如 `ChatInput`、`Conversation` 等
|
||||
> - **页面专属功能**（`src/app/<page>/features/`）：仅在特定页面路由中使用的组件
|
||||
|
|
@ -119,12 +126,12 @@ const ChatPage = () => {
|
|||
renderItem={(message) => (
|
||||
<List.Item>
|
||||
<Typography.Text>{message.content}</Typography.Text>
|
||||
|
||||
|
||||
</List.Item>
|
||||
)}
|
||||
/>
|
||||
<Button onClick={handleSend}>Send</Button>
|
||||
|
||||
|
||||
</>
|
||||
);
|
||||
};
|
||||
|
|
@ -132,4 +139,4 @@ const ChatPage = () => {
|
|||
export default ChatPage;
|
||||
```
|
||||
|
||||
以上就是在 LobeChat 中实现 "会话消息" 功能的步骤。当然，在 LobeChat 的实际开发中，真实场景所面临的业务诉求和场景远比上述 demo 复杂，请根据实际情况进行开发。
|
||||
以上就是在 LobeHub 中实现 "会话消息" 功能的步骤。当然，在 LobeHub 的实际开发中，真实场景所面临的业务诉求和场景远比上述 demo 复杂，请根据实际情况进行开发。
|
||||
|
|
|
|||
|
|
@ -1,10 +1,17 @@
|
|||
---
|
||||
title: LobeChat Feature Development Complete Guide
|
||||
title: LobeHub Feature Development Complete Guide
|
||||
description: A comprehensive guide for developers on implementing features in LobeHub.
|
||||
tags:
|
||||
- LobeHub
|
||||
- Feature Development
|
||||
- Developer Guide
|
||||
- Postgres
|
||||
- Drizzle ORM
|
||||
---
|
||||
|
||||
# LobeChat Feature Development Complete Guide
|
||||
# LobeHub Feature Development Complete Guide
|
||||
|
||||
This document aims to guide developers on how to develop a complete feature in LobeChat.
|
||||
This document aims to guide developers on how to develop a complete feature in LobeHub.
|
||||
|
||||
We will use [RFC 021 - Custom Assistant Opening Guidance](https://github.com/lobehub/lobe-chat/discussions/891) as an example to illustrate the complete implementation process.
|
||||
|
||||
|
|
@ -366,7 +373,7 @@ const OpeningQuestions = memo(() => {
|
|||
{isRepeat && (
|
||||
<p className={styles.repeatError}>{t('settingOpening.openingQuestions.repeat')}</p>
|
||||
)}
|
||||
|
||||
|
||||
</Flexbox>
|
||||
|
||||
<div className={styles.questionsList}>
|
||||
|
|
@ -383,7 +390,7 @@ const OpeningQuestions = memo(() => {
|
|||
onClick={() => removeQuestion(item.content)}
|
||||
type="text"
|
||||
/>
|
||||
|
||||
|
||||
</SortableList.Item>
|
||||
)}
|
||||
/>
|
||||
|
|
@ -393,9 +400,9 @@ const OpeningQuestions = memo(() => {
|
|||
description={t('settingOpening.openingQuestions.empty')}
|
||||
/>
|
||||
)}
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
</Flexbox>
|
||||
);
|
||||
});
|
||||
|
|
@ -448,7 +455,7 @@ const WelcomeMessage = () => {
|
|||
{chatItem}
|
||||
{/* Render guiding questions */}
|
||||
<OpeningQuestions mobile={mobile} questions={openingQuestions} />
|
||||
|
||||
|
||||
</Flexbox>
|
||||
) : (
|
||||
chatItem
|
||||
|
|
@ -467,4 +474,4 @@ For the current scenario, I recommend running the tests locally to see which tes
|
|||
|
||||
## Summary
|
||||
|
||||
The above is the complete implementation process for the LobeChat opening settings feature. Developers can refer to this document for the development and testing of related features.
|
||||
The above is the complete implementation process for the LobeHub opening settings feature. Developers can refer to this document for the development and testing of related features.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,16 @@
|
|||
---
|
||||
title: LobeChat 功能开发完全指南
|
||||
title: LobeHub 功能开发完全指南
|
||||
description: 了解如何在 LobeHub 中开发完整的功能需求，提升开发效率。
|
||||
tags:
|
||||
- LobeHub
|
||||
- 功能开发
|
||||
- 开发指南
|
||||
- 开场设置
|
||||
---
|
||||
|
||||
# LobeChat 功能开发完全指南
|
||||
# LobeHub 功能开发完全指南
|
||||
|
||||
本文档旨在指导开发者了解如何在 LobeChat 中开发一块完整的功能需求。
|
||||
本文档旨在指导开发者了解如何在 LobeHub 中开发一块完整的功能需求。
|
||||
|
||||
我们将以 [RFC 021 - 自定义助手开场引导](https://github.com/lobehub/lobe-chat/discussions/891) 为例，阐述完整的实现流程。
|
||||
|
||||
|
|
@ -366,7 +372,7 @@ const OpeningQuestions = memo(() => {
|
|||
{isRepeat && (
|
||||
<p className={styles.repeatError}>{t('settingOpening.openingQuestions.repeat')}</p>
|
||||
)}
|
||||
|
||||
|
||||
</Flexbox>
|
||||
|
||||
<div className={styles.questionsList}>
|
||||
|
|
@ -383,7 +389,7 @@ const OpeningQuestions = memo(() => {
|
|||
onClick={() => removeQuestion(item.content)}
|
||||
type="text"
|
||||
/>
|
||||
|
||||
|
||||
</SortableList.Item>
|
||||
)}
|
||||
/>
|
||||
|
|
@ -393,9 +399,9 @@ const OpeningQuestions = memo(() => {
|
|||
description={t('settingOpening.openingQuestions.empty')}
|
||||
/>
|
||||
)}
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
</Flexbox>
|
||||
);
|
||||
});
|
||||
|
|
@ -448,7 +454,7 @@ const WelcomeMessage = () => {
|
|||
{chatItem}
|
||||
{/* 渲染引导性问题 */}
|
||||
<OpeningQuestions mobile={mobile} questions={openingQuestions} />
|
||||
|
||||
|
||||
</Flexbox>
|
||||
) : (
|
||||
chatItem
|
||||
|
|
@ -467,4 +473,4 @@ export default WelcomeMessage;
|
|||
|
||||
## 总结
|
||||
|
||||
以上就是 LobeChat 开场设置功能的完整实现流程。开发者可以参考本文档进行相关功能的开发和测试。
|
||||
以上就是 LobeHub 开场设置功能的完整实现流程。开发者可以参考本文档进行相关功能的开发和测试。
|
||||
|
|
|
|||
|
|
@ -1,10 +1,19 @@
|
|||
---
|
||||
title: Directory Structure
|
||||
description: >-
|
||||
Explore the organized directory structure of LobeHub, including app,
|
||||
components, and services.
|
||||
tags:
|
||||
- LobeHub
|
||||
- Directory Structure
|
||||
- Next.js
|
||||
- App Router
|
||||
- API Architecture
|
||||
---
|
||||
|
||||
# Directory Structure
|
||||
|
||||
The directory structure of LobeChat is as follows:
|
||||
The directory structure of LobeHub is as follows:
|
||||
|
||||
```bash
|
||||
src
|
||||
|
|
|
|||
|
|
@ -1,10 +1,17 @@
|
|||
---
|
||||
title: 目录架构
|
||||
description: 深入了解 LobeHub 的文件夹目录架构及其功能模块。
|
||||
tags:
|
||||
- LobeHub
|
||||
- 目录架构
|
||||
- Next.js
|
||||
- API路由
|
||||
- 前端开发
|
||||
---
|
||||
|
||||
# 目录架构
|
||||
|
||||
LobeChat 的文件夹目录架构如下：
|
||||
LobeHub 的文件夹目录架构如下：
|
||||
|
||||
```bash
|
||||
src
|
||||
|
|
|
|||
|
|
@ -1,17 +1,26 @@
|
|||
---
|
||||
title: Resources and References
|
||||
description: >-
|
||||
Explore key resources and references for LobeHub's design and development
|
||||
process.
|
||||
tags:
|
||||
- LobeHub
|
||||
- OpenAI API
|
||||
- AI SDK
|
||||
- LangChain
|
||||
- Next.js
|
||||
---
|
||||
|
||||
# Resources and References
|
||||
|
||||
The design and development of LobeChat would not have been possible without the excellent projects in the community and ecosystem. We have used or referred to some outstanding resources and guides in the design and development process. Here are some key reference resources for developers to refer to during the development and learning process:
|
||||
The design and development of LobeHub would not have been possible without the excellent projects in the community and ecosystem. We have used or referred to some outstanding resources and guides in the design and development process. Here are some key reference resources for developers to refer to during the development and learning process:
|
||||
|
||||
1. **OpenAI API Guide**: We use OpenAI's API to access and process AI conversation data. You can check out the [OpenAI API Guide](https://platform.openai.com/docs/api-reference/introduction) for more details.
|
||||
2. **OpenAI SDK**: We use OpenAI's Node.js SDK to interact with OpenAI's API. You can view the source code and documentation on the [OpenAI SDK](https://github.com/openai/openai-node) GitHub repository.
|
||||
3. **AI SDK**: We use Vercel's AI SDK to access and process AI conversation data. You can refer to the documentation of [AI SDK](https://sdk.vercel.ai/docs) for more details.
|
||||
4. **LangChain**: Our early conversation feature was implemented based on LangChain. You can visit [LangChain](https://langchain.com) to learn more about it.
|
||||
5. **Chat-Next-Web**: Chat Next Web is an excellent project, and some of LobeChat's features and workflows are referenced from its implementation. You can view the source code and documentation on the [Chat-Next-Web](https://github.com/Yidadaa/ChatGPT-Next-Web) GitHub repository.
|
||||
5. **Chat-Next-Web**: Chat Next Web is an excellent project, and some of LobeHub's features and workflows are referenced from its implementation. You can view the source code and documentation on the [Chat-Next-Web](https://github.com/Yidadaa/ChatGPT-Next-Web) GitHub repository.
|
||||
6. **Next.js Documentation**: Our project is built on Next.js, and you can refer to the [Next.js Documentation](https://nextjs.org/docs) for more information about Next.js.
|
||||
7. **FlowGPT**: FlowGPT is currently the world's largest Prompt community, and some of the agents in LobeChat come from active authors in FlowGPT. You can visit [FlowGPT](https://flowgpt.com/) to learn more about it.
|
||||
7. **FlowGPT**: FlowGPT is currently the world's largest Prompt community, and some of the agents in LobeHub come from active authors in FlowGPT. You can visit [FlowGPT](https://flowgpt.com/) to learn more about it.
|
||||
|
||||
We will continue to update and supplement this list to provide developers with more reference resources.
|
||||
|
|
|
|||
|
|
@ -1,17 +1,24 @@
|
|||
---
|
||||
title: 资源与参考
|
||||
description: 探索 LobeHub 的设计与开发参考资源，助力开发者学习与成长。
|
||||
tags:
|
||||
- LobeHub
|
||||
- 开发资源
|
||||
- OpenAI API
|
||||
- AI SDK
|
||||
- LangChain
|
||||
---
|
||||
|
||||
# 资源与参考
|
||||
|
||||
LobeChat 的设计和开发离不开社区和生态中的优秀项目。我们在设计和开发过程中使用或参考了一些优秀的资源和指南。以下是一些主要的参考资源，供开发者在开发和学习过程中参考：
|
||||
LobeHub 的设计和开发离不开社区和生态中的优秀项目。我们在设计和开发过程中使用或参考了一些优秀的资源和指南。以下是一些主要的参考资源，供开发者在开发和学习过程中参考：
|
||||
|
||||
1. **OpenAI API 指南**：我们使用 OpenAI 的 API 来获取和处理 AI 的会话数据。你可以查看 [OpenAI API 指南](https://platform.openai.com/docs/api-reference/introduction) 了解更多详情。
|
||||
2. **OpenAI SDK**：我们使用 OpenAI 的 Node.js SDK 来与 OpenAI 的 API 交互。你可以在 [OpenAI SDK](https://github.com/openai/openai-node) 的 GitHub 仓库中查看源码和文档。
|
||||
3. **AI SDK**：我们使用 Vercel 的 AI SDK 来获取和处理 AI 的会话数据。你可以查看 [AI SDK](https://sdk.vercel.ai/docs) 的文档来了解更多详情。
|
||||
4. **LangChain**：我们早期的会话功能是基于 LangChain 实现的。你可以访问 [LangChain](https://langchain.com) 来了解更多关于它的信息。
|
||||
5. **Chat-Next-Web**：Chat Next Web 是一个优秀的项目，LobeChat 的部分功能、Workflow 等参考了它的实现。你可以在 [Chat-Next-Web](https://github.com/Yidadaa/ChatGPT-Next-Web) 的 GitHub 仓库中查看源码和文档。
|
||||
5. **Chat-Next-Web**：Chat Next Web 是一个优秀的项目，LobeHub 的部分功能、Workflow 等参考了它的实现。你可以在 [Chat-Next-Web](https://github.com/Yidadaa/ChatGPT-Next-Web) 的 GitHub 仓库中查看源码和文档。
|
||||
6. **Next.js 文档**：我们的项目是基于 Next.js 构建的，你可以查看 [Next.js 文档](https://nextjs.org/docs) 来了解更多关于 Next.js 的信息。
|
||||
7. **FlowGPT**：FlowGPT 是目前全球最大的 Prompt 社区，LobeChat 中的一些 Agent 来自 FlowGPT 的活跃作者。你可以访问 [FlowGPT](https://flowgpt.com/) 来了解更多关于它的信息。
|
||||
7. **FlowGPT**：FlowGPT 是目前全球最大的 Prompt 社区，LobeHub 中的一些 Agent 来自 FlowGPT 的活跃作者。你可以访问 [FlowGPT](https://flowgpt.com/) 来了解更多关于它的信息。
|
||||
|
||||
我们会持续更新和补充这个列表，为开发者提供更多的参考资源。
|
||||
|
|
|
|||
|
|
@ -1,10 +1,21 @@
|
|||
---
|
||||
title: Environment Setup Guide
|
||||
description: >-
|
||||
Step-by-step guide to set up LobeHub development environment locally or
|
||||
online.
|
||||
tags:
|
||||
- LobeHub
|
||||
- Development Setup
|
||||
- Node.js
|
||||
- PNPM
|
||||
- Bun
|
||||
- Git
|
||||
- VSCode
|
||||
---
|
||||
|
||||
# Environment Setup Guide
|
||||
|
||||
Welcome to the LobeChat development environment setup guide.
|
||||
Welcome to the LobeHub development environment setup guide.
|
||||
|
||||
## Online Development
|
||||
|
||||
|
|
@ -14,13 +25,13 @@ If you have access to GitHub Codespaces, you can click the button below to enter
|
|||
|
||||
## Local Development
|
||||
|
||||
Before starting development on LobeChat, you need to install and configure some necessary software and tools in your local environment. This document will guide you through these steps.
|
||||
Before starting development on LobeHub, you need to install and configure some necessary software and tools in your local environment. This document will guide you through these steps.
|
||||
|
||||
### Development Environment Requirements
|
||||
|
||||
First, you need to install the following software:
|
||||
|
||||
- Node.js: LobeChat is built on Node.js, so you need to install Node.js. We recommend installing the latest stable version.
|
||||
- Node.js: LobeHub is built on Node.js, so you need to install Node.js. We recommend installing the latest stable version.
|
||||
- PNPM: We use PNPM as the preferred package manager. You can download and install it from the [PNPM official website](https://pnpm.io/installation).
|
||||
- Bun: We use Bun as the npm scripts runner. You can download and install it from the [Bun official website](https://bun.com/docs/installation).
|
||||
- Git: We use Git for version control. You can download and install it from the Git official website.
|
||||
|
|
@ -32,9 +43,9 @@ We recommend installing the extensions listed in [.vscode/extensions.json](https
|
|||
|
||||
### Project Setup
|
||||
|
||||
After installing the above software, you can start setting up the LobeChat project.
|
||||
After installing the above software, you can start setting up the LobeHub project.
|
||||
|
||||
1. **Get the code**: First, you need to clone the LobeChat codebase from GitHub. Run the following command in the terminal:
|
||||
1. **Get the code**: First, you need to clone the LobeHub codebase from GitHub. Run the following command in the terminal:
|
||||
|
||||
```bash
|
||||
git clone https://github.com/lobehub/lobe-chat.git
|
||||
|
|
@ -53,13 +64,13 @@ pnpm i
|
|||
bun run dev
|
||||
```
|
||||
|
||||
Now, you can open `http://localhost:3010` in your browser, and you should see the welcome page of LobeChat. This indicates that you have successfully set up the development environment.
|
||||
Now, you can open `http://localhost:3010` in your browser, and you should see the welcome page of LobeHub. This indicates that you have successfully set up the development environment.
|
||||
|
||||
|
||||
|
||||
## Working with Server-Side Features
|
||||
|
||||
The basic setup above uses LobeChat's client-side database mode. If you need to work with server-side features such as:
|
||||
The basic setup above uses LobeHub's client-side database mode. If you need to work with server-side features such as:
|
||||
|
||||
- Database persistence
|
||||
- File uploads and storage
|
||||
|
|
@ -69,7 +80,7 @@ The basic setup above uses LobeChat's client-side database mode. If you need to
|
|||
|
||||
Please refer to the [Work with Server-Side Database](/docs/development/basic/work-with-server-side-database) guide for complete setup instructions.
|
||||
|
||||
During the development process, if you encounter any issues with environment setup or have any questions about LobeChat development, feel free to ask us at any time. We look forward to seeing your contributions!
|
||||
During the development process, if you encounter any issues with environment setup or have any questions about LobeHub development, feel free to ask us at any time. We look forward to seeing your contributions!
|
||||
|
||||
[codespaces-link]: https://codespaces.new/lobehub/lobe-chat
|
||||
[codespaces-shield]: https://github.com/codespaces/badge.svg
|
||||
|
|
|
|||
|
|
@ -1,10 +1,17 @@
|
|||
---
|
||||
title: 环境设置指南
|
||||
description: 详细介绍 LobeHub 的开发环境设置，包括软件安装和项目配置。
|
||||
tags:
|
||||
- LobeHub
|
||||
- 开发环境
|
||||
- Node.js
|
||||
- PNPM
|
||||
- Git
|
||||
---
|
||||
|
||||
# 环境设置指南
|
||||
|
||||
欢迎阅读 LobeChat 的开发环境设置指南。
|
||||
欢迎阅读 LobeHub 的开发环境设置指南。
|
||||
|
||||
## 在线开发
|
||||
|
||||
|
|
@ -14,13 +21,13 @@ title: 环境设置指南
|
|||
|
||||
## 本地开发
|
||||
|
||||
在开始开发 LobeChat 之前，你需要在本地环境中安装和配置一些必要的软件和工具。本文档将指导你完成这些步骤。
|
||||
在开始开发 LobeHub 之前，你需要在本地环境中安装和配置一些必要的软件和工具。本文档将指导你完成这些步骤。
|
||||
|
||||
### 开发环境需求
|
||||
|
||||
首先，你需要安装以下软件：
|
||||
|
||||
- Node.js：LobeChat 是基于 Node.js 构建的，因此你需要安装 Node.js。我们建议安装最新的稳定版。
|
||||
- Node.js：LobeHub 是基于 Node.js 构建的，因此你需要安装 Node.js。我们建议安装最新的稳定版。
|
||||
- PNPM：我们使用 PNPM 作为管理器。你可以从 [pnpm 的官方网站](https://pnpm.io/installation) 上下载并安装。
|
||||
- Bun：我们使用 Bun 作为 npm scripts runner, 你可以从 [Bun 的官方网站](https://bun.com/docs/installation) 上下载并安装。
|
||||
- Git：我们使用 Git 进行版本控制。你可以从 Git 的官方网站上下载并安装。
|
||||
|
|
@ -32,9 +39,9 @@ title: 环境设置指南
|
|||
|
||||
### 项目设置
|
||||
|
||||
完成上述软件的安装后，你可以开始设置 LobeChat 项目了。
|
||||
完成上述软件的安装后，你可以开始设置 LobeHub 项目了。
|
||||
|
||||
1. **获取代码**：首先，你需要从 GitHub 上克隆 LobeChat 的代码库。在终端中运行以下命令：
|
||||
1. **获取代码**：首先，你需要从 GitHub 上克隆 LobeHub 的代码库。在终端中运行以下命令：
|
||||
|
||||
```bash
|
||||
git clone https://github.com/lobehub/lobe-chat.git
|
||||
|
|
@ -53,13 +60,13 @@ pnpm i
|
|||
bun run dev
|
||||
```
|
||||
|
||||
现在，你可以在浏览器中打开 `http://localhost:3010`，你应该能看到 LobeChat 的欢迎页面。这表明你已经成功地设置了开发环境。
|
||||
现在，你可以在浏览器中打开 `http://localhost:3010`，你应该能看到 LobeHub 的欢迎页面。这表明你已经成功地设置了开发环境。
|
||||
|
||||
|
||||
|
||||
## 使用服务端功能
|
||||
|
||||
上述基础设置使用 LobeChat 的客户端数据库模式。如果你需要开发服务端功能，如：
|
||||
上述基础设置使用 LobeHub 的客户端数据库模式。如果你需要开发服务端功能，如：
|
||||
|
||||
- 数据库持久化
|
||||
- 文件上传和存储
|
||||
|
|
@ -69,7 +76,7 @@ bun run dev
|
|||
|
||||
请参考[使用服务端数据库](/docs/development/basic/work-with-server-side-database)指南获得完整的设置说明。
|
||||
|
||||
在开发过程中，如果你在环境设置上遇到任何问题，或者有任何关于 LobeChat 开发的问题，欢迎随时向我们提问。我们期待看到你的贡献！
|
||||
在开发过程中，如果你在环境设置上遇到任何问题，或者有任何关于 LobeHub 开发的问题，欢迎随时向我们提问。我们期待看到你的贡献！
|
||||
|
||||
[codespaces-link]: https://codespaces.new/lobehub/lobe-chat
|
||||
[codespaces-shield]: https://github.com/codespaces/badge.svg
|
||||
|
|
|
|||
|
|
@ -1,10 +1,19 @@
|
|||
---
|
||||
title: Testing Guide
|
||||
description: >-
|
||||
Explore LobeHub's testing strategy, including unit and end-to-end testing
|
||||
methods.
|
||||
tags:
|
||||
- LobeHub
|
||||
- Testing
|
||||
- Unit Testing
|
||||
- End-to-End Testing
|
||||
- vitest
|
||||
---
|
||||
|
||||
# Testing Guide
|
||||
|
||||
LobeChat's testing strategy includes unit testing and end-to-end (E2E) testing. Below are detailed explanations of each type of testing:
|
||||
LobeHub's testing strategy includes unit testing and end-to-end (E2E) testing. Below are detailed explanations of each type of testing:
|
||||
|
||||
## Unit Testing
|
||||
|
||||
|
|
@ -24,13 +33,13 @@ We encourage developers to write corresponding unit tests while writing code to
|
|||
|
||||
End-to-end testing is used to test the functionality and performance of the application in a real environment. It simulates real user operations and verifies the application's performance in different scenarios.
|
||||
|
||||
Currently, there is no integrated end-to-end testing in LobeChat. We will gradually introduce end-to-end testing in subsequent iterations.
|
||||
Currently, there is no integrated end-to-end testing in LobeHub. We will gradually introduce end-to-end testing in subsequent iterations.
|
||||
|
||||
## Development Testing
|
||||
|
||||
### 1. Unit Testing
|
||||
|
||||
Unit testing is conducted on the smallest testable units in the application, usually functions, components, or modules. In LobeChat, we use [vitest][vitest-url] for unit testing.
|
||||
Unit testing is conducted on the smallest testable units in the application, usually functions, components, or modules. In LobeHub, we use [vitest][vitest-url] for unit testing.
|
||||
|
||||
#### Writing Test Cases
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,16 @@
|
|||
---
|
||||
title: 测试指南
|
||||
description: 了解 LobeHub 的单元测试和端到端测试策略，确保代码质量与稳定性。
|
||||
tags:
|
||||
- LobeHub
|
||||
- 单元测试
|
||||
- 端到端测试
|
||||
- 测试策略
|
||||
---
|
||||
|
||||
# 测试指南
|
||||
|
||||
LobeChat 的测试策略包括单元测试和端到端 (E2E) 测试。下面是每种测试的详细说明：
|
||||
LobeHub 的测试策略包括单元测试和端到端 (E2E) 测试。下面是每种测试的详细说明：
|
||||
|
||||
## 单元测试
|
||||
|
||||
|
|
@ -24,13 +30,13 @@ npm run test
|
|||
|
||||
端到端测试用于测试应用在真实环境中的功能和性能。它模拟用户的真实操作，并验证应用在不同场景下的表现。
|
||||
|
||||
在 LobeChat 中，目前暂时没有集成端到端测试，我们会在后续迭代中逐步引入端到端测试。
|
||||
在 LobeHub 中，目前暂时没有集成端到端测试，我们会在后续迭代中逐步引入端到端测试。
|
||||
|
||||
## 开发测试
|
||||
|
||||
### 1. 单元测试
|
||||
|
||||
单元测试是针对应用中的最小可测试单元进行的测试，通常是针对函数、组件或模块进行的测试。在 LobeChat 中，我们使用 [vitest][vitest-url] 进行单元测试。
|
||||
单元测试是针对应用中的最小可测试单元进行的测试，通常是针对函数、组件或模块进行的测试。在 LobeHub 中，我们使用 [vitest][vitest-url] 进行单元测试。
|
||||
|
||||
#### 编写测试用例
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,17 @@
|
|||
---
|
||||
title: Work with Server-Side Database
|
||||
description: Learn how to set up a server-side database for LobeHub with Docker.
|
||||
tags:
|
||||
- LobeHub
|
||||
- Server-Side Database
|
||||
- Docker
|
||||
- PostgreSQL
|
||||
- MinIO
|
||||
---
|
||||
|
||||
# Work with Server-Side Database
|
||||
|
||||
LobeChat provides a battery-included experience with its client-side database.
|
||||
LobeHub provides a battery-included experience with its client-side database.
|
||||
While some features you really care about is only available at a server-side development.
|
||||
|
||||
In order to work with the aspect of server-side database,
|
||||
|
|
@ -55,7 +62,7 @@ You should see: `✅ database migration pass.`
|
|||
|
||||
### Start Development Server
|
||||
|
||||
Launch the LobeChat development server:
|
||||
Launch the LobeHub development server:
|
||||
|
||||
```bash
|
||||
pnpm dev
|
||||
|
|
@ -144,7 +151,7 @@ await fetch(uploadUrl, {
|
|||
|
||||
When running with Docker Compose development setup:
|
||||
|
||||
- **PostgreSQL**: `postgres://postgres@localhost:5432/lobechat`
|
||||
- **PostgreSQL**: `postgres://postgres@localhost:5432/LobeHub`
|
||||
- **MinIO API**: `http://localhost:9000`
|
||||
- **MinIO Console**: `http://localhost:9001` (admin/CHANGE\_THIS\_PASSWORD\_IN\_PRODUCTION)
|
||||
- **Application**: `http://localhost:3010`
|
||||
|
|
|
|||
|
|
@ -1,10 +1,17 @@
|
|||
---
|
||||
title: 使用服务端数据库
|
||||
description: 快速设置 LobeHub 服务端数据库，支持 Docker 和图像生成。
|
||||
tags:
|
||||
- 服务端数据库
|
||||
- LobeHub
|
||||
- Docker
|
||||
- 图像生成
|
||||
- PostgreSQL
|
||||
---
|
||||
|
||||
# 使用服务端数据库
|
||||
|
||||
LobeChat 提供了内置的客户端数据库体验。
|
||||
LobeHub 提供了内置的客户端数据库体验。
|
||||
但某些重要功能仅在服务端开发中可用。
|
||||
|
||||
为了使用服务端数据库功能，
|
||||
|
|
@ -55,7 +62,7 @@ pnpm db:migrate
|
|||
|
||||
### 启动开发服务器
|
||||
|
||||
启动 LobeChat 开发服务器：
|
||||
启动 LobeHub 开发服务器：
|
||||
|
||||
```bash
|
||||
pnpm dev
|
||||
|
|
@ -144,7 +151,7 @@ await fetch(uploadUrl, {
|
|||
|
||||
运行 Docker Compose 开发环境时：
|
||||
|
||||
- **PostgreSQL**：`postgres://postgres@localhost:5432/lobechat`
|
||||
- **PostgreSQL**：`postgres://postgres@localhost:5432/LobeHub`
|
||||
- **MinIO API**：`http://localhost:9000`
|
||||
- **MinIO 控制台**：`http://localhost:9001` (admin/CHANGE\_THIS\_PASSWORD\_IN\_PRODUCTION)
|
||||
- **应用程序**：`http://localhost:3010`
|
||||
|
|
|
|||
|
|
@ -1,14 +1,21 @@
|
|||
---
|
||||
title: New Locale Guide
|
||||
description: Learn how to add Vietnamese language support in LobeHub using lobe-i18n.
|
||||
tags:
|
||||
- LobeHub
|
||||
- i18n
|
||||
- language support
|
||||
- Vietnamese
|
||||
- localization
|
||||
---
|
||||
|
||||
# New Locale Guide
|
||||
|
||||
LobeChat uses [lobe-i18n](https://github.com/lobehub/lobe-cli-toolbox/tree/master/packages/lobe-i18n) as the i18n solution, which allows for quick addition of new language support in the application.
|
||||
LobeHub uses [lobe-i18n](https://github.com/lobehub/lobe-cli-toolbox/tree/master/packages/lobe-i18n) as the i18n solution, which allows for quick addition of new language support in the application.
|
||||
|
||||
## Adding New Language Support
|
||||
|
||||
To add new language internationalization support in LobeChat (for example, adding Vietnamese `vi-VN`), please follow the steps below:
|
||||
To add new language internationalization support in LobeHub (for example, adding Vietnamese `vi-VN`), please follow the steps below:
|
||||
|
||||
### Step 1: Update the Internationalization Configuration File
|
||||
|
||||
|
|
@ -33,7 +40,7 @@ module.exports = {
|
|||
|
||||
### Step 2: Automatically Translate Language Files
|
||||
|
||||
LobeChat uses the `lobe-i18n` tool to automatically translate language files, so manual updating of i18n files is not required.
|
||||
LobeHub uses the `lobe-i18n` tool to automatically translate language files, so manual updating of i18n files is not required.
|
||||
|
||||
Run the following command to automatically translate and generate the Vietnamese language files:
|
||||
|
||||
|
|
@ -47,12 +54,12 @@ This will utilize the `lobe-i18n` tool to process the language files.
|
|||
|
||||
Once you have completed the above steps, you need to submit your changes and create a Pull Request.
|
||||
|
||||
Ensure that you follow LobeChat's contribution guidelines and provide a necessary description to explain your changes. For example, refer to a similar previous Pull Request [#759](https://github.com/lobehub/lobe-chat/pull/759).
|
||||
Ensure that you follow LobeHub's contribution guidelines and provide a necessary description to explain your changes. For example, refer to a similar previous Pull Request [#759](https://github.com/lobehub/lobe-chat/pull/759).
|
||||
|
||||
### Additional Information
|
||||
|
||||
- After submitting your Pull Request, please patiently wait for the project maintainers to review it.
|
||||
- If you encounter any issues, you can reach out to the LobeChat community for assistance.
|
||||
- If you encounter any issues, you can reach out to the LobeHub community for assistance.
|
||||
- For more accurate results, ensure that your Pull Request is based on the latest main branch and stays in sync with the main branch.
|
||||
|
||||
By following the above steps, you can successfully add new language support to LobeChat and ensure that the application provides a localized experience for more users.
|
||||
By following the above steps, you can successfully add new language support to LobeHub and ensure that the application provides a localized experience for more users.
|
||||
|
|
|
|||
|
|
@ -1,14 +1,21 @@
|
|||
---
|
||||
title: 新语种添加指南
|
||||
description: 学习如何在 LobeHub 中添加新的语言支持，提升用户体验。
|
||||
tags:
|
||||
- LobeHub
|
||||
- 国际化
|
||||
- 语言支持
|
||||
- lobe-i18n
|
||||
- 越南语
|
||||
---
|
||||
|
||||
# 新语种添加指南
|
||||
|
||||
LobeChat 使用 [lobe-i18n](https://github.com/lobehub/lobe-cli-toolbox/tree/master/packages/lobe-i18n) 作为 i18n 解决方案，可以在应用中快速添加新的语言支持。
|
||||
LobeHub 使用 [lobe-i18n](https://github.com/lobehub/lobe-cli-toolbox/tree/master/packages/lobe-i18n) 作为 i18n 解决方案，可以在应用中快速添加新的语言支持。
|
||||
|
||||
## 添加新的语言支持
|
||||
|
||||
为了在 LobeChat 中添加新的语言国际化支持，（例如添加越南语 `vi-VN`)，请按照以下步骤操作：
|
||||
为了在 LobeHub 中添加新的语言国际化支持，（例如添加越南语 `vi-VN`)，请按照以下步骤操作：
|
||||
|
||||
### 步骤 1: 更新国际化配置文件
|
||||
|
||||
|
|
@ -33,7 +40,7 @@ module.exports = {
|
|||
|
||||
### 步骤 2: 自动翻译语言文件
|
||||
|
||||
LobeChat 使用 `lobe-i18n` 工具来自动翻译语言文件，因此不需要手动更新 i18n 文件。
|
||||
LobeHub 使用 `lobe-i18n` 工具来自动翻译语言文件，因此不需要手动更新 i18n 文件。
|
||||
|
||||
运行以下命令来自动翻译并生成越南语的语言文件：
|
||||
|
||||
|
|
@ -47,12 +54,12 @@ npm run i18n
|
|||
|
||||
一旦你完成了上述步骤，你需要提交你的更改并创建一个 Pull Request。
|
||||
|
||||
请确保你遵循了 LobeChat 的贡献指南，并提供必要的描述来说明你的更改。例如，参考之前的类似 Pull Request [#759](https://github.com/lobehub/lobe-chat/pull/759)。
|
||||
请确保你遵循了 LobeHub 的贡献指南，并提供必要的描述来说明你的更改。例如，参考之前的类似 Pull Request [#759](https://github.com/lobehub/lobe-chat/pull/759)。
|
||||
|
||||
### 附加信息
|
||||
|
||||
- 提交你的 Pull Request 后，请耐心等待项目维护人员的审查。
|
||||
- 如果遇到任何问题，可以联系 LobeChat 社区寻求帮助。
|
||||
- 如果遇到任何问题，可以联系 LobeHub 社区寻求帮助。
|
||||
- 为了更精确的结果，确保你的 Pull Request 是基于最新的主分支，并且与主分支保持同步。
|
||||
|
||||
通过遵循上述步骤，你可以成功为 LobeChat 添加新的语言支持，并且确保应用能够为更多用户提供本地化的体验。
|
||||
通过遵循上述步骤，你可以成功为 LobeHub 添加新的语言支持，并且确保应用能够为更多用户提供本地化的体验。
|
||||
|
|
|
|||
|
|
@ -1,18 +1,27 @@
|
|||
---
|
||||
title: Internationalization Implementation Guide
|
||||
description: >-
|
||||
Learn how to implement internationalization in LobeHub for multilingual
|
||||
support.
|
||||
tags:
|
||||
- Internationalization
|
||||
- i18next
|
||||
- LobeHub
|
||||
- Multilingual Support
|
||||
- Localization
|
||||
---
|
||||
|
||||
# Internationalization Implementation Guide
|
||||
|
||||
Welcome to the LobeChat Internationalization Implementation Guide. This document will guide you through understanding the internationalization mechanism of LobeChat, including file structure and how to add new languages. LobeChat uses `i18next` and `lobe-i18n` as the internationalization solution, aiming to provide users with seamless multilingual support.
|
||||
Welcome to the LobeHub Internationalization Implementation Guide. This document will guide you through understanding the internationalization mechanism of LobeHub, including file structure and how to add new languages. LobeHub uses `i18next` and `lobe-i18n` as the internationalization solution, aiming to provide users with seamless multilingual support.
|
||||
|
||||
## Internationalization Overview
|
||||
|
||||
Internationalization (i18n for short) is the process of enabling an application to adapt to different languages and regions. In LobeChat, we support multiple languages and achieve dynamic language switching and content localization through the `i18next` library. Our goal is to provide a localized experience for global users.
|
||||
Internationalization (i18n for short) is the process of enabling an application to adapt to different languages and regions. In LobeHub, we support multiple languages and achieve dynamic language switching and content localization through the `i18next` library. Our goal is to provide a localized experience for global users.
|
||||
|
||||
## File Structure
|
||||
|
||||
In the LobeChat project, internationalization-related files are organized as follows:
|
||||
In the LobeHub project, internationalization-related files are organized as follows:
|
||||
|
||||
- `src/locales/default`: Contains translation files for the default development language (Chinese), which we use as Chinese.
|
||||
- `locales`: Contains folders for all supported languages, with each language folder containing the respective translation files generated by lobe-i18n.
|
||||
|
|
@ -58,14 +67,14 @@ locales
|
|||
|
||||
## Core Implementation Logic
|
||||
|
||||
The internationalization core implementation logic of LobeChat is as follows:
|
||||
The internationalization core implementation logic of LobeHub is as follows:
|
||||
|
||||
- Initialize and configure using the `i18next` library.
|
||||
- Automatically detect the user's language preference using `i18next-browser-languagedetector`.
|
||||
- Dynamically load translation resources using `i18next-resources-to-backend`.
|
||||
- Set the direction of the HTML document (LTR or RTL) based on the user's language preference.
|
||||
|
||||
Here is a simplified pseudo code example to illustrate the core implementation logic of internationalization in LobeChat:
|
||||
Here is a simplified pseudo code example to illustrate the core implementation logic of internationalization in LobeHub:
|
||||
|
||||
```ts
|
||||
import i18n from 'i18next';
|
||||
|
|
@ -99,7 +108,7 @@ const createI18nInstance = (lang) => {
|
|||
};
|
||||
```
|
||||
|
||||
In this example, we demonstrate how to use `i18next` and related plugins to initialize internationalization settings. We dynamically import translation resources and respond to language change events to adjust the text direction of the page. This process provides LobeChat with flexible multilingual support capabilities.
|
||||
In this example, we demonstrate how to use `i18next` and related plugins to initialize internationalization settings. We dynamically import translation resources and respond to language change events to adjust the text direction of the page. This process provides LobeHub with flexible multilingual support capabilities.
|
||||
|
||||
## Adding Support for New Languages
|
||||
|
||||
|
|
@ -118,4 +127,4 @@ To add support for new languages, please refer to the detailed steps in the [New
|
|||
- [i18next Official Documentation](https://www.i18next.com/)
|
||||
- [lobe-i18n Tool Description](https://github.com/lobehub/lobe-cli-toolbox/tree/master/packages/lobe-i18n)
|
||||
|
||||
By following this guide, you can better understand and participate in the internationalization work of LobeChat, providing a seamless multilingual experience for global users.
|
||||
By following this guide, you can better understand and participate in the internationalization work of LobeHub, providing a seamless multilingual experience for global users.
|
||||
|
|
|
|||
|
|
@ -1,18 +1,24 @@
|
|||
---
|
||||
title: 国际化实现指南
|
||||
description: 了解 LobeHub 的国际化机制，支持多语言体验。
|
||||
tags:
|
||||
- 国际化
|
||||
- LobeHub
|
||||
- i18next
|
||||
- 多语言支持
|
||||
---
|
||||
|
||||
# 国际化实现指南
|
||||
|
||||
欢迎阅读 LobeChat 国际化实现指南。本文档将指导你了解 LobeChat 的国际化机制，包括文件结构、如何添加新语种。LobeChat 采用 `i18next` 和 `lobe-i18n` 作为国际化解决方案，旨在为用户提供流畅的多语言支持。
|
||||
欢迎阅读 LobeHub 国际化实现指南。本文档将指导你了解 LobeHub 的国际化机制，包括文件结构、如何添加新语种。LobeHub 采用 `i18next` 和 `lobe-i18n` 作为国际化解决方案，旨在为用户提供流畅的多语言支持。
|
||||
|
||||
## 国际化概述
|
||||
|
||||
国际化（Internationalization，简称为 i18n）是一个让应用能够适应不同语言和地区的过程。在 LobeChat 中，我们支持多种语言，并通过 `i18next` 库来实现语言的动态切换和内容的本地化。我们的目标是让 LobeChat 能够为全球用户提供本地化的体验。
|
||||
国际化（Internationalization，简称为 i18n）是一个让应用能够适应不同语言和地区的过程。在 LobeHub 中，我们支持多种语言，并通过 `i18next` 库来实现语言的动态切换和内容的本地化。我们的目标是让 LobeHub 能够为全球用户提供本地化的体验。
|
||||
|
||||
## 文件结构
|
||||
|
||||
在 LobeChat 的项目中，国际化相关的文件被组织如下：
|
||||
在 LobeHub 的项目中，国际化相关的文件被组织如下：
|
||||
|
||||
- `src/locales/default`: 包含默认开发语言（中文）的翻译文件，我们作为中文。
|
||||
- `locales`: 包含所有支持的语言文件夹，每个语言文件夹中包含相应语言的翻译文件，这些翻译文件通过 lobe-i18n 自动生成。
|
||||
|
|
@ -58,14 +64,14 @@ locales
|
|||
|
||||
## 核心实现逻辑
|
||||
|
||||
LobeChat 的国际化核心实现逻辑如下：
|
||||
LobeHub 的国际化核心实现逻辑如下：
|
||||
|
||||
- 使用 `i18next` 库进行初始化和配置。
|
||||
- 使用 `i18next-browser-languagedetector` 自动检测用户的语言偏好。
|
||||
- 使用 `i18next-resources-to-backend` 动态加载翻译资源。
|
||||
- 根据用户的语言偏好，设置 HTML 文档的方向（LTR 或 RTL）。
|
||||
|
||||
以下是一个简化的伪代码示例，用以说明 LobeChat 国际化的核心实现逻辑：
|
||||
以下是一个简化的伪代码示例，用以说明 LobeHub 国际化的核心实现逻辑：
|
||||
|
||||
```ts
|
||||
import i18n from 'i18next';
|
||||
|
|
@ -99,7 +105,7 @@ const createI18nInstance = (lang) => {
|
|||
};
|
||||
```
|
||||
|
||||
在这个示例中，我们展示了如何使用 `i18next` 和相关插件来初始化国际化设置。我们动态导入了翻译资源，并响应语言变化事件来调整页面的文本方向。这个过程为 LobeChat 提供了灵活的多语言支持能力。
|
||||
在这个示例中，我们展示了如何使用 `i18next` 和相关插件来初始化国际化设置。我们动态导入了翻译资源，并响应语言变化事件来调整页面的文本方向。这个过程为 LobeHub 提供了灵活的多语言支持能力。
|
||||
|
||||
## 添加新的语言支持
|
||||
|
||||
|
|
@ -118,4 +124,4 @@ const createI18nInstance = (lang) => {
|
|||
- [i18next 官方文档](https://www.i18next.com/)
|
||||
- [lobe-i18n 工具说明](https://github.com/lobehub/lobe-cli-toolbox/tree/master/packages/lobe-i18n)
|
||||
|
||||
通过遵循本指南，你可以更好地理解和参与到 LobeChat 的国际化工作中，为全球用户提供无缝的多语言体验。
|
||||
通过遵循本指南，你可以更好地理解和参与到 LobeHub 的国际化工作中，为全球用户提供无缝的多语言体验。
|
||||
|
|
|
|||
|
|
@ -1,5 +1,10 @@
|
|||
---
|
||||
title: Lighthouse Reports
|
||||
description: Explore Lighthouse reports for chat and discover pages on LobeHub.
|
||||
tags:
|
||||
- Lighthouse Reports
|
||||
- Chat Page
|
||||
- Discover Page
|
||||
---
|
||||
|
||||
# Lighthouse Reports
|
||||
|
|
@ -7,7 +12,7 @@ title: Lighthouse Reports
|
|||
## Chat Page
|
||||
|
||||
> **Info**\
|
||||
> [https://lobechat.com/chat](https://lobechat.com/chat)
|
||||
> [https://LobeHub.com/chat](https://LobeHub.com/chat)
|
||||
|
||||
| Desktop | Mobile |
|
||||
| :-----------------------------------------: | :----------------------------------------: |
|
||||
|
|
@ -17,7 +22,7 @@ title: Lighthouse Reports
|
|||
## Discover Page
|
||||
|
||||
> **Info**\
|
||||
> [https://lobechat.com/discover](https://lobechat.com/discover)
|
||||
> [https://LobeHub.com/discover](https://LobeHub.com/discover)
|
||||
|
||||
| Desktop | Mobile |
|
||||
| :---------------------------------------------: | :--------------------------------------------: |
|
||||
|
|
@ -25,10 +30,10 @@ title: Lighthouse Reports
|
|||
| [⚡️ Lighthouse Report][discover-desktop-report] | [⚡️ Lighthouse Report][discover-mobile-report] |
|
||||
|
||||
[chat-desktop]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/desktop/pagespeed.svg
|
||||
[chat-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/desktop/lobechat_com_chat.html
|
||||
[chat-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/desktop/LobeHub_com_chat.html
|
||||
[chat-mobile]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/mobile/pagespeed.svg
|
||||
[chat-mobile-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/mobile/lobechat_com_chat.html
|
||||
[chat-mobile-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/mobile/LobeHub_com_chat.html
|
||||
[discover-desktop]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/discover/desktop/pagespeed.svg
|
||||
[discover-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/discover/desktop/lobechat_com_discover.html
|
||||
[discover-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/discover/desktop/LobeHub_com_discover.html
|
||||
[discover-mobile]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/discover/mobile/pagespeed.svg
|
||||
[discover-mobile-report]: https://lobehub.github.io/lobe-chat/lighthouse/discover/mobile/lobechat_com_discover.html
|
||||
[discover-mobile-report]: https://lobehub.github.io/lobe-chat/lighthouse/discover/mobile/LobeHub_com_discover.html
|
||||
|
|
|
|||
|
|
@ -1,5 +1,11 @@
|
|||
---
|
||||
title: Lighthouse 测试报告
|
||||
description: 查看Lighthouse测试报告，了解聊天和发现页面的性能表现。
|
||||
tags:
|
||||
- Lighthouse
|
||||
- 测试报告
|
||||
- 聊天页面
|
||||
- 发现页面
|
||||
---
|
||||
|
||||
# Lighthouse 测试报告
|
||||
|
|
@ -7,7 +13,7 @@ title: Lighthouse 测试报告
|
|||
## Chat 聊天页面
|
||||
|
||||
> **Info**\
|
||||
> [https://lobechat.com/chat](https://lobechat.com/chat)
|
||||
> [https://LobeHub.com/chat](https://LobeHub.com/chat)
|
||||
|
||||
| Desktop | Mobile |
|
||||
| :-----------------------------------------: | :----------------------------------------: |
|
||||
|
|
@ -17,7 +23,7 @@ title: Lighthouse 测试报告
|
|||
## Discover 发现页面
|
||||
|
||||
> **Info**\
|
||||
> [https://lobechat.com/discover](https://lobechat.com/discover)
|
||||
> [https://LobeHub.com/discover](https://LobeHub.com/discover)
|
||||
|
||||
| Desktop | Mobile |
|
||||
| :---------------------------------------------: | :--------------------------------------------: |
|
||||
|
|
@ -25,10 +31,10 @@ title: Lighthouse 测试报告
|
|||
| [⚡️ Lighthouse Report][discover-desktop-report] | [⚡️ Lighthouse Report][discover-mobile-report] |
|
||||
|
||||
[chat-desktop]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/desktop/pagespeed.svg
|
||||
[chat-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/desktop/lobechat_com_chat.html
|
||||
[chat-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/desktop/LobeHub_com_chat.html
|
||||
[chat-mobile]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/mobile/pagespeed.svg
|
||||
[chat-mobile-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/mobile/lobechat_com_chat.html
|
||||
[chat-mobile-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/mobile/LobeHub_com_chat.html
|
||||
[discover-desktop]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/discover/desktop/pagespeed.svg
|
||||
[discover-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/discover/desktop/lobechat_com_discover.html
|
||||
[discover-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/discover/desktop/LobeHub_com_discover.html
|
||||
[discover-mobile]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/discover/mobile/pagespeed.svg
|
||||
[discover-mobile-report]: https://lobehub.github.io/lobe-chat/lighthouse/discover/mobile/lobechat_com_discover.html
|
||||
[discover-mobile-report]: https://lobehub.github.io/lobe-chat/lighthouse/discover/mobile/LobeHub_com_discover.html
|
||||
|
|
|
|||
|
|
@ -1,14 +1,23 @@
|
|||
---
|
||||
title: Technical Development Getting Started Guide
|
||||
description: >-
|
||||
Explore the LobeHub development setup, technology stack, and contribution
|
||||
guidelines.
|
||||
tags:
|
||||
- LobeHub
|
||||
- Next.js
|
||||
- Development Guide
|
||||
- Internationalization
|
||||
- Open Source
|
||||
---
|
||||
|
||||
# Technical Development Getting Started Guide
|
||||
|
||||
Welcome to the LobeChat Technical Development Getting Started Guide. LobeChat is an AI conversation application built on the Next.js framework, incorporating a range of technology stacks to achieve diverse functionalities and features. This guide will detail the main technical components of LobeChat and how to configure and use these technologies in your development environment.
|
||||
Welcome to the LobeHub Technical Development Getting Started Guide. LobeHub is an AI conversation application built on the Next.js framework, incorporating a range of technology stacks to achieve diverse functionalities and features. This guide will detail the main technical components of LobeHub and how to configure and use these technologies in your development environment.
|
||||
|
||||
## Basic Technology Stack
|
||||
|
||||
The core technology stack of LobeChat is as follows:
|
||||
The core technology stack of LobeHub is as follows:
|
||||
|
||||
- **Framework**: We chose [Next.js](https://nextjs.org/), a powerful React framework that provides key features such as server-side rendering, routing framework, and Router Handler.
|
||||
- **Component Library**: We use [Ant Design (antd)](https://ant.design/) as the basic component library, along with [lobe-ui](https://github.com/lobehub/lobe-ui) as our business component library.
|
||||
|
|
@ -21,7 +30,7 @@ The core technology stack of LobeChat is as follows:
|
|||
|
||||
## Folder Directory Structure
|
||||
|
||||
The folder directory structure of LobeChat is as follows:
|
||||
The folder directory structure of LobeHub is as follows:
|
||||
|
||||
```bash
|
||||
src
|
||||
|
|
@ -47,7 +56,7 @@ This section outlines setting up the development environment and local developme
|
|||
|
||||
We recommend using WebStorm as your integrated development environment (IDE).
|
||||
|
||||
1. **Get the code**: Clone the LobeChat code repository locally:
|
||||
1. **Get the code**: Clone the LobeHub code repository locally:
|
||||
|
||||
```bash
|
||||
git clone https://github.com/lobehub/lobe-chat.git
|
||||
|
|
@ -74,11 +83,11 @@ bun run dev
|
|||
> \[!IMPORTANT]\
|
||||
> If you encounter the error "Could not find 'stylelint-config-recommended'" when installing dependencies with `npm`, please reinstall the dependencies using `pnpm` or `bun`.
|
||||
|
||||
Now, you should be able to see the welcome page of LobeChat in your browser. For a detailed environment setup guide, please refer to [Development Environment Setup Guide](/docs/development/basic/setup-development).
|
||||
Now, you should be able to see the welcome page of LobeHub in your browser. For a detailed environment setup guide, please refer to [Development Environment Setup Guide](/docs/development/basic/setup-development).
|
||||
|
||||
## Code Style and Contribution Guide
|
||||
|
||||
In the LobeChat project, we place great emphasis on the quality and consistency of the code. For this reason, we have established a series of code style standards and contribution processes to ensure that every developer can smoothly participate in the project. Here are the code style and contribution guidelines you need to follow as a developer.
|
||||
In the LobeHub project, we place great emphasis on the quality and consistency of the code. For this reason, we have established a series of code style standards and contribution processes to ensure that every developer can smoothly participate in the project. Here are the code style and contribution guidelines you need to follow as a developer.
|
||||
|
||||
- **Code Style**: We use `@lobehub/lint` to unify the code style, including ESLint, Prettier, remarklint, and stylelint configurations. Please adhere to our code standards to maintain code consistency and readability.
|
||||
- **Contribution Process**: We use gitmoji and semantic release for code submission and release processes. Please use gitmoji to annotate your commit messages and ensure compliance with the semantic release standards so that our automation systems can correctly handle version control and releases.
|
||||
|
|
@ -89,7 +98,7 @@ For detailed code style and contribution guidelines, please refer to [Code Style
|
|||
|
||||
## Internationalization Implementation Guide
|
||||
|
||||
LobeChat uses `i18next` and `lobe-i18n` to implement multilingual support, ensuring a global user experience.
|
||||
LobeHub uses `i18next` and `lobe-i18n` to implement multilingual support, ensuring a global user experience.
|
||||
|
||||
Internationalization files are located in `src/locales`, containing the default language (Chinese). We generate other language JSON files automatically through `lobe-i18n`.
|
||||
|
||||
|
|
@ -99,8 +108,8 @@ For a detailed guide on internationalization implementation, please refer to [In
|
|||
|
||||
## Appendix: Resources and References
|
||||
|
||||
To support developers in better understanding and using the technology stack of LobeChat, we provide a comprehensive list of resources and references — [LobeChat Resources and References](/docs/development/basic/resources) - Visit our maintained list of resources, including tutorials, articles, and other useful links.
|
||||
To support developers in better understanding and using the technology stack of LobeHub, we provide a comprehensive list of resources and references — [LobeHub Resources and References](/docs/development/basic/resources) - Visit our maintained list of resources, including tutorials, articles, and other useful links.
|
||||
|
||||
We encourage developers to utilize these resources to deepen their learning and enhance their skills, join community discussions through [LobeChat GitHub Discussions](https://github.com/lobehub/lobe-chat/discussions) or [Discord](https://discord.com/invite/AYFPHvv2jT), ask questions, or share your experiences.
|
||||
We encourage developers to utilize these resources to deepen their learning and enhance their skills, join community discussions through [LobeHub GitHub Discussions](https://github.com/lobehub/lobe-chat/discussions) or [Discord](https://discord.com/invite/AYFPHvv2jT), ask questions, or share your experiences.
|
||||
|
||||
If you have any questions or need further assistance, please do not hesitate to contact us through the above channels.
|
||||
|
|
|
|||
|
|
@ -1,14 +1,21 @@
|
|||
---
|
||||
title: 技术开发上手指南
|
||||
description: 了解 LobeHub 的技术栈和开发环境设置，快速上手开发。
|
||||
tags:
|
||||
- LobeHub
|
||||
- 技术开发
|
||||
- Next.js
|
||||
- 国际化
|
||||
- 状态管理
|
||||
---
|
||||
|
||||
# 技术开发上手指南
|
||||
|
||||
欢迎来到 LobeChat 技术开发上手指南。LobeChat 是一款基于 Next.js 框架构建的 AI 会话应用，它汇集了一系列的技术栈，以实现多样化的功能和特性。本指南将详细介绍 LobeChat 的主要技术组成，以及如何在你的开发环境中配置和使用这些技术。
|
||||
欢迎来到 LobeHub 技术开发上手指南。LobeHub 是一款基于 Next.js 框架构建的 AI 会话应用，它汇集了一系列的技术栈，以实现多样化的功能和特性。本指南将详细介绍 LobeHub 的主要技术组成，以及如何在你的开发环境中配置和使用这些技术。
|
||||
|
||||
## 基础技术栈
|
||||
|
||||
LobeChat 的核心技术栈如下：
|
||||
LobeHub 的核心技术栈如下：
|
||||
|
||||
- **框架**：我们选择了 [Next.js](https://nextjs.org/)，这是一款强大的 React 框架，为我们的项目提供了服务端渲染、路由框架、Router Handler 等关键功能。
|
||||
- **组件库**：我们使用了 [Ant Design (antd)](https://ant.design/) 作为基础组件库，同时引入了 [lobe-ui](https://github.com/lobehub/lobe-ui) 作为我们的业务组件库。
|
||||
|
|
@ -21,7 +28,7 @@ LobeChat 的核心技术栈如下：
|
|||
|
||||
## 文件夹目录架构
|
||||
|
||||
LobeChat 的文件夹目录架构如下：
|
||||
LobeHub 的文件夹目录架构如下：
|
||||
|
||||
```bash
|
||||
src
|
||||
|
|
@ -47,7 +54,7 @@ src
|
|||
|
||||
我们推荐使用 WebStorm 作为你的集成开发环境（IDE）。
|
||||
|
||||
1. **获取代码**：克隆 LobeChat 的代码库到本地：
|
||||
1. **获取代码**：克隆 LobeHub 的代码库到本地：
|
||||
|
||||
```bash
|
||||
git clone https://github.com/lobehub/lobe-chat.git
|
||||
|
|
@ -74,11 +81,11 @@ bun run dev
|
|||
> \[!IMPORTANT]\
|
||||
> 如果使用`npm`安装依赖出现`Could not find "stylelint-config-recommended"`错误，请使用 `pnpm` 或者 `bun` 重新安装依赖。
|
||||
|
||||
现在，你应该可以在浏览器中看到 LobeChat 的欢迎页面。详细的环境配置指南，请参考 [开发环境设置指南](/zh/docs/development/basic/setup-development)。
|
||||
现在，你应该可以在浏览器中看到 LobeHub 的欢迎页面。详细的环境配置指南，请参考 [开发环境设置指南](/zh/docs/development/basic/setup-development)。
|
||||
|
||||
## 代码风格与贡献指南
|
||||
|
||||
在 LobeChat 项目中，我们十分重视代码的质量和一致性。为此，我们制定了一系列的代码风格规范和贡献流程，以确保每位开发者都能顺利地参与到项目中。以下是你作为开发者需要遵守的代码风格和贡献准则。
|
||||
在 LobeHub 项目中，我们十分重视代码的质量和一致性。为此，我们制定了一系列的代码风格规范和贡献流程，以确保每位开发者都能顺利地参与到项目中。以下是你作为开发者需要遵守的代码风格和贡献准则。
|
||||
|
||||
- **代码风格**：我们使用 `@lobehub/lint` 统一代码风格，包括 ESLint、Prettier、remarklint 和 stylelint 配置。请遵守我们的代码规范，以保持代码的一致性和可读性。
|
||||
- **贡献流程**：我们采用 gitmoji 和 semantic release 作为代码提交和发布流程。请使用 gitmoji 标注您的提交信息，并确保遵循 semantic release 的规范，以便我们的自动化系统能够正确处理版本控制和发布。
|
||||
|
|
@ -89,7 +96,7 @@ bun run dev
|
|||
|
||||
## 国际化实现指南
|
||||
|
||||
LobeChat 采用 `i18next` 和 `lobe-i18n` 实现多语言支持，确保用户全球化体验。
|
||||
LobeHub 采用 `i18next` 和 `lobe-i18n` 实现多语言支持，确保用户全球化体验。
|
||||
|
||||
国际化文件位于 `src/locales`，包含默认语言（中文）。 我们会通过 `lobe-i18n` 自动生成其他的语言 JSON 文件。
|
||||
|
||||
|
|
@ -99,8 +106,8 @@ LobeChat 采用 `i18next` 和 `lobe-i18n` 实现多语言支持，确保用户
|
|||
|
||||
## 附录：资源与参考
|
||||
|
||||
为了支持开发者更好地理解和使用 LobeChat 的技术栈，我们提供了一份详尽的资源与参考列表 —— [LobeChat 资源与参考](/zh/docs/development/basic/resources) - 访问我们维护的资源列表，包括教程、文章和其他有用的链接。
|
||||
为了支持开发者更好地理解和使用 LobeHub 的技术栈，我们提供了一份详尽的资源与参考列表 —— [LobeHub 资源与参考](/zh/docs/development/basic/resources) - 访问我们维护的资源列表，包括教程、文章和其他有用的链接。
|
||||
|
||||
我们鼓励开发者利用这些资源深入学习和提升技能，通过 [LobeChat GitHub Discussions](https://github.com/lobehub/lobe-chat/discussions) 或者 [Discord](https://discord.com/invite/AYFPHvv2jT) 加入社区讨论，提出问题或分享你的经验。
|
||||
我们鼓励开发者利用这些资源深入学习和提升技能，通过 [LobeHub GitHub Discussions](https://github.com/lobehub/lobe-chat/discussions) 或者 [Discord](https://discord.com/invite/AYFPHvv2jT) 加入社区讨论，提出问题或分享你的经验。
|
||||
|
||||
如果你有任何疑问，或者需要进一步的帮助，请不要犹豫，请通过上述渠道与我们联系。
|
||||
|
|
|
|||
|
|
@ -1,10 +1,18 @@
|
|||
---
|
||||
title: Best Practices for State Management
|
||||
description: >-
|
||||
Explore effective state management practices for LobeHub's complex data flow
|
||||
architecture.
|
||||
tags:
|
||||
- State Management
|
||||
- LobeHub
|
||||
- Data Flow
|
||||
- Best Practices
|
||||
---
|
||||
|
||||
# Best Practices for State Management
|
||||
|
||||
LobeChat differs from traditional CRUD web applications in that it involves a large amount of rich interactive capabilities. Therefore, it is crucial to design a data flow architecture that is easy to develop and maintain. This document will introduce the best practices for data flow management in LobeChat.
|
||||
LobeHub differs from traditional CRUD web applications in that it involves a large amount of rich interactive capabilities. Therefore, it is crucial to design a data flow architecture that is easy to develop and maintain. This document will introduce the best practices for data flow management in LobeHub.
|
||||
|
||||
## Key Concepts
|
||||
|
||||
|
|
@ -64,10 +72,10 @@ SortableTree/store
|
|||
|
||||
- **High Complexity**: Involves over 30 states and 20 actions, requiring modular cohesion using slices. Each slice declares its own initState, actions, reducers, and selectors.
|
||||
|
||||
The directory structure of the previous version of SessionStore for LobeChat, with high complexity, implements a large amount of business logic. However, with the modularization of slices and the fractal architecture, it is easy to find the corresponding modules, making it easy to maintain and iterate on new features.
|
||||
The directory structure of the previous version of SessionStore for LobeHub, with high complexity, implements a large amount of business logic. However, with the modularization of slices and the fractal architecture, it is easy to find the corresponding modules, making it easy to maintain and iterate on new features.
|
||||
|
||||
```bash
|
||||
LobeChat SessionStore
|
||||
LobeHub SessionStore
|
||||
├── index.ts
|
||||
├── initialState.ts
|
||||
├── selectors.ts
|
||||
|
|
@ -107,11 +115,11 @@ LobeChat SessionStore
|
|||
└── store.ts
|
||||
```
|
||||
|
||||
Based on the provided directory structure of LobeChat SessionStore, we can update the previous document and convert the examples to the implementation of LobeChat's SessionStore. The following is a portion of the updated document:
|
||||
Based on the provided directory structure of LobeHub SessionStore, we can update the previous document and convert the examples to the implementation of LobeHub's SessionStore. The following is a portion of the updated document:
|
||||
|
||||
### Best Practices for LobeChat SessionStore Directory Structure
|
||||
### Best Practices for LobeHub SessionStore Directory Structure
|
||||
|
||||
In the LobeChat application, session management is a complex functional module, so we use the Slice pattern to organize the data flow. Below is the directory structure of LobeChat SessionStore, where each directory and file has its specific purpose:
|
||||
In the LobeHub application, session management is a complex functional module, so we use the Slice pattern to organize the data flow. Below is the directory structure of LobeHub SessionStore, where each directory and file has its specific purpose:
|
||||
|
||||
{/* eslint-disable no-irregular-whitespace */}
|
||||
|
||||
|
|
@ -148,7 +156,7 @@ src/store/session
|
|||
|
||||
## Implementation of SessionStore
|
||||
|
||||
In LobeChat, the SessionStore is designed as the core module for managing session state and logic. It consists of multiple Slices, with each Slice managing a relevant portion of state and logic. Below is a simplified example of the SessionStore implementation:
|
||||
In LobeHub, the SessionStore is designed as the core module for managing session state and logic. It consists of multiple Slices, with each Slice managing a relevant portion of state and logic. Below is a simplified example of the SessionStore implementation:
|
||||
|
||||
### store.ts
|
||||
|
||||
|
|
@ -177,7 +185,7 @@ export const useSessionStore = createWithEqualityFn<SessionStore>()(
|
|||
persist(
|
||||
subscribeWithSelector(
|
||||
devtools(createStore, {
|
||||
name: 'LobeChat_Session' + (isDev ? '_DEV' : ''),
|
||||
name: 'LobeHub_Session' + (isDev ? '_DEV' : ''),
|
||||
}),
|
||||
),
|
||||
persistOptions,
|
||||
|
|
@ -218,4 +226,4 @@ export const createSessionSlice: StateCreator<
|
|||
|
||||
In the `action.ts` file, we define a `SessionActions` interface to describe session-related actions and implement a `useFetchSessions` function to create these actions. Then, we merge these actions with the initial state to form the session-related Slice.
|
||||
|
||||
Through this layered and modular approach, we can ensure that LobeChat's SessionStore is clear, maintainable, and easy to extend and test.
|
||||
Through this layered and modular approach, we can ensure that LobeHub's SessionStore is clear, maintainable, and easy to extend and test.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,16 @@
|
|||
---
|
||||
title: 状态管理最佳实践
|
||||
description: 探索 LobeHub 中的状态管理最佳实践，提升数据流架构的易用性与维护性。
|
||||
tags:
|
||||
- 状态管理
|
||||
- LobeHub
|
||||
- 数据流
|
||||
- 最佳实践
|
||||
---
|
||||
|
||||
# 状态管理最佳实践
|
||||
|
||||
LobeChat 不同于传统 CRUD 的网页，存在大量的富交互能力，如何设计一个易于开发与易于维护的数据流架构非常重要。本篇文档将介绍 LobeChat 中的数据流管理最佳实践。
|
||||
LobeHub 不同于传统 CRUD 的网页，存在大量的富交互能力，如何设计一个易于开发与易于维护的数据流架构非常重要。本篇文档将介绍 LobeHub 中的数据流管理最佳实践。
|
||||
|
||||
## 概念要素
|
||||
|
||||
|
|
@ -69,7 +75,7 @@ SortableTree/store
|
|||
下述这个数据流的目录结构是之前一版 SessionStore，具有很高的复杂度，实现了大量的业务逻辑。但借助于 slice 的模块化和分形架构的心智，我们可以很容易地找到对应的模块，新增功能与迭代都很易于维护。
|
||||
|
||||
```bash
|
||||
LobeChat SessionStore
|
||||
LobeHub SessionStore
|
||||
├── index.ts
|
||||
├── initialState.ts
|
||||
├── selectors.ts
|
||||
|
|
@ -109,9 +115,9 @@ LobeChat SessionStore
|
|||
└── store.ts
|
||||
```
|
||||
|
||||
### LobeChat SessionStore 目录结构最佳实践
|
||||
### LobeHub SessionStore 目录结构最佳实践
|
||||
|
||||
在 LobeChat 应用中，由于会话管理是一个复杂的功能模块，因此我们采用了 [slice 模式](https://github.com/pmndrs/zustand/blob/main/docs/guides/slices-pattern.md) 来组织数据流。下面是 LobeChat SessionStore 的目录结构，其中每个目录和文件都有其特定的用途：
|
||||
在 LobeHub 应用中，由于会话管理是一个复杂的功能模块，因此我们采用了 [slice 模式](https://github.com/pmndrs/zustand/blob/main/docs/guides/slices-pattern.md) 来组织数据流。下面是 LobeHub SessionStore 的目录结构，其中每个目录和文件都有其特定的用途：
|
||||
|
||||
{/* eslint-disable no-irregular-whitespace */}
|
||||
|
||||
|
|
@ -140,7 +146,7 @@ src/store/session
|
|||
|
||||
## SessionStore 的实现
|
||||
|
||||
在 LobeChat 中，SessionStore 被设计为管理会话状态和逻辑的核心模块。它由多个 Slices 组成，每个 Slice 管理一部分相关的状态和逻辑。下面是一个简化的 SessionStore 的实现示例：
|
||||
在 LobeHub 中，SessionStore 被设计为管理会话状态和逻辑的核心模块。它由多个 Slices 组成，每个 Slice 管理一部分相关的状态和逻辑。下面是一个简化的 SessionStore 的实现示例：
|
||||
|
||||
### store.ts
|
||||
|
||||
|
|
@ -169,7 +175,7 @@ export const useSessionStore = createWithEqualityFn<SessionStore>()(
|
|||
persist(
|
||||
subscribeWithSelector(
|
||||
devtools(createStore, {
|
||||
name: 'LobeChat_Session' + (isDev ? '_DEV' : ''),
|
||||
name: 'LobeHub_Session' + (isDev ? '_DEV' : ''),
|
||||
}),
|
||||
),
|
||||
persistOptions,
|
||||
|
|
@ -210,4 +216,4 @@ export const createSessionSlice: StateCreator<
|
|||
|
||||
在 `action.ts` 文件中，我们定义了一个 `SessionActions` 接口来描述会话相关的动作，并且实现了一个 `useFetchSessions` 函数来创建这些动作。然后，我们将这些动作与初始状态合并，以形成会话相关的 Slice。
|
||||
|
||||
通过这种结构分层和模块化的方法，我们可以确保 LobeChat 的 SessionStore 是清晰、可维护的，同时也便于扩展和测试。
|
||||
通过这种结构分层和模块化的方法，我们可以确保 LobeHub 的 SessionStore 是清晰、可维护的，同时也便于扩展和测试。
|
||||
|
|
|
|||
|
|
@ -1,10 +1,19 @@
|
|||
---
|
||||
title: Data Store Selector
|
||||
description: >-
|
||||
Explore the role of selectors in LobeHub for efficient data retrieval and
|
||||
management.
|
||||
tags:
|
||||
- Data Store
|
||||
- Selectors
|
||||
- LobeHub
|
||||
- TypeScript
|
||||
- State Management
|
||||
---
|
||||
|
||||
# Data Store Selector
|
||||
|
||||
Selectors are data retrieval modules under the LobeChat data flow development framework. Their role is to extract data from the store using specific business logic for consumption by components.
|
||||
Selectors are data retrieval modules under the LobeHub data flow development framework. Their role is to extract data from the store using specific business logic for consumption by components.
|
||||
|
||||
Taking `src/store/plugin/selectors.ts` as an example:
|
||||
|
||||
|
|
@ -65,9 +74,9 @@ The benefits of implementing this approach are:
|
|||
1. **Decoupling and reusability**: By separating selectors from components, we can reuse these selectors across multiple components without rewriting data retrieval logic. This reduces duplicate code, improves development efficiency, and makes the codebase cleaner and easier to maintain.
|
||||
2. **Performance optimization**: Selectors can be used to compute derived data, avoiding redundant calculations in each component. When the state changes, only the selectors dependent on that part of the state will recalculate, reducing unnecessary rendering and computation.
|
||||
3. **Ease of testing**: Selectors are pure functions, relying only on the passed parameters. This means they can be tested in an isolated environment without the need to simulate the entire store or component tree.
|
||||
4. **Type safety**: As LobeChat uses TypeScript, each selector has explicit input and output type definitions. This provides developers with the advantage of auto-completion and compile-time checks, reducing runtime errors.
|
||||
4. **Type safety**: As LobeHub uses TypeScript, each selector has explicit input and output type definitions. This provides developers with the advantage of auto-completion and compile-time checks, reducing runtime errors.
|
||||
5. **Maintainability**: Selectors centralize the logic for reading state, making it more intuitive to track state changes and management. If the state structure changes, only the relevant selectors need to be updated, rather than searching and replacing in multiple places throughout the codebase.
|
||||
6. **Composability**: Selectors can be composed with other selectors to create more complex selection logic. This pattern allows developers to build a hierarchy of selectors, making state selection more flexible and powerful.
|
||||
7. **Simplified component logic**: Components do not need to know the structure of the state or how to retrieve and compute the required data. Components only need to call selectors to obtain the data needed for rendering, simplifying and clarifying component logic.
|
||||
|
||||
With this design, LobeChat developers can focus more on building the user interface and business logic without worrying about the details of data retrieval and processing. This pattern also provides better adaptability and scalability for potential future changes in state structure.
|
||||
With this design, LobeHub developers can focus more on building the user interface and business logic without worrying about the details of data retrieval and processing. This pattern also provides better adaptability and scalability for potential future changes in state structure.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,17 @@
|
|||
---
|
||||
title: 数据存储取数模块
|
||||
description: 了解 LobeHub 数据存储取数模块及其选择器的使用和优势。
|
||||
tags:
|
||||
- LobeHub
|
||||
- 数据存储
|
||||
- 选择器
|
||||
- TypeScript
|
||||
- 前端开发
|
||||
---
|
||||
|
||||
# 数据存储取数模块
|
||||
|
||||
selectors 是 LobeChat 数据流研发框架下的取数模块，它的作用是从 store 中以特定特务逻辑取出数据，供组件消费使用。
|
||||
selectors 是 LobeHub 数据流研发框架下的取数模块，它的作用是从 store 中以特定特务逻辑取出数据，供组件消费使用。
|
||||
|
||||
以 `src/store/tool/slices/plugin/selectors.ts` 为例：
|
||||
|
||||
|
|
@ -46,9 +53,9 @@ const Render = () => {
|
|||
1. **解耦和重用**：通过将选择器独立于组件，我们可以在多个组件之间复用这些选择器而不需要重写取数逻辑。这减少了重复代码，提高了开发效率，并且使得代码库更加干净和易于维护。
|
||||
2. **性能优化**：选择器可以用来计算派生数据，这样可以避免在每个组件中重复计算相同的数据。当状态发生变化时，只有依赖于这部分状态的选择器才会重新计算，从而减少不必要的渲染和计算。
|
||||
3. **易于测试**：选择器是纯函数，它们仅依赖于传入的参数。这意味着它们可以在隔离的环境中进行测试，无需模拟整个 store 或组件树。
|
||||
4. **类型安全**：由于 LobeChat 使用 TypeScript，每个选择器都有明确的输入和输出类型定义。这为开发者提供了自动完成和编译时检查的优势，减少了运行时错误。
|
||||
4. **类型安全**：由于 LobeHub 使用 TypeScript，每个选择器都有明确的输入和输出类型定义。这为开发者提供了自动完成和编译时检查的优势，减少了运行时错误。
|
||||
5. **可维护性**：选择器集中了状态的读取逻辑，使得跟踪状态的变化和管理更加直观。如果状态结构发生变化，我们只需要更新相应的选择器，而不是搜索和替换整个代码库中的多个位置。
|
||||
6. **可组合性**：选择器可以组合其他选择器，以创建更复杂的选择逻辑。这种模式允许开发者构建一个选择器层次结构，使得状态选择更加灵活和强大。
|
||||
7. **简化组件逻辑**：组件不需要知道状态的结构或如何获取和计算需要的数据。组件只需调用选择器即可获取渲染所需的数据，这使得组件逻辑变得更简单和清晰。
|
||||
|
||||
通过这样的设计，LobeChat 的开发者可以更专注于构建用户界面和业务逻辑，而不必担心数据的获取和处理细节。这种模式也为未来可能的状态结构变更提供了更好的适应性和扩展性。
|
||||
通过这样的设计，LobeHub 的开发者可以更专注于构建用户界面和业务逻辑，而不必担心数据的获取和处理细节。这种模式也为未来可能的状态结构变更提供了更好的适应性和扩展性。
|
||||
|
|
|
|||
410
docs/development/tests/integration-testing.mdx
Normal file
410
docs/development/tests/integration-testing.mdx
Normal file
|
|
@ -0,0 +1,410 @@
|
|||
---
|
||||
title: Integration Testing Guide
|
||||
description: >-
|
||||
Learn how to effectively conduct integration testing to verify module
|
||||
interactions and data integrity.
|
||||
tags:
|
||||
- Integration Testing
|
||||
- Software Testing
|
||||
- Test Automation
|
||||
---
|
||||
|
||||
# Integration Testing Guide
|
||||
|
||||
## Overview
|
||||
|
||||
Integration testing verifies the correctness of multiple modules working together, ensuring that the complete call chain (Router → Service → Model → Database) functions as expected.
|
||||
|
||||
## Why Do We Need Integration Tests?
|
||||
|
||||
Even with high unit test coverage (80%+), integration issues can still occur:
|
||||
|
||||
### Common Issue Example
|
||||
|
||||
```typescript
|
||||
// ❌ Issue: Parameter lost in the call chain
|
||||
// Router layer
|
||||
const messageId = await messageModel.create({
|
||||
content: 'test',
|
||||
sessionId: 'xxx',
|
||||
topicId: 'yyy', // ← topicId is passed in
|
||||
});
|
||||
|
||||
// Model layer (assume there's a bug)
|
||||
async create(data) {
|
||||
return this.db.insert(messages).values({
|
||||
content: data.content,
|
||||
sessionId: data.sessionId,
|
||||
// ❌ Forgot to pass topicId
|
||||
});
|
||||
}
|
||||
|
||||
// Result: Unit test passes (because Model is mocked), but topicId is lost in actual execution
|
||||
```
|
||||
|
||||
### Issues Caught by Integration Tests
|
||||
|
||||
1. **Missing parameter propagation**: containerId, threadId, topicId, etc., lost in the call chain
|
||||
2. **Database constraints**: foreign keys, cascading deletes, etc., cannot be verified with mocks
|
||||
3. **Transaction integrity**: atomicity of cross-table operations
|
||||
4. **Permission checks**: cross-user access control
|
||||
5. **Real-world scenarios**: simulate complete user workflows
|
||||
|
||||
## Running Integration Tests
|
||||
|
||||
```bash
|
||||
# Run all integration tests
|
||||
pnpm test:integration
|
||||
|
||||
# Run a specific test file
|
||||
pnpm vitest tests/integration/routers/message.integration.test.ts
|
||||
|
||||
# Watch mode
|
||||
pnpm vitest tests/integration --watch
|
||||
|
||||
# Generate coverage report
|
||||
pnpm test:integration --coverage
|
||||
```
|
||||
|
||||
## Directory Structure
|
||||
|
||||
```
|
||||
tests/integration/
|
||||
├── README.md # Integration test documentation
|
||||
├── setup.ts # Common setup and utility functions
|
||||
└── routers/ # Router layer integration tests
|
||||
├── message.integration.test.ts # Message Router tests
|
||||
├── session.integration.test.ts # Session Router tests
|
||||
├── topic.integration.test.ts # Topic Router tests
|
||||
└── chat-flow.integration.test.ts # Full chat flow tests
|
||||
```
|
||||
|
||||
## Writing Integration Tests
|
||||
|
||||
### Basic Template
|
||||
|
||||
```typescript
|
||||
// @vitest-environment node
|
||||
import { eq } from 'drizzle-orm';
|
||||
import { afterEach, beforeEach, describe, expect, it } from 'vitest';
|
||||
|
||||
import { getTestDB } from '@/database/models/__tests__/_util';
|
||||
import { messages, sessions, users } from '@/database/schemas';
|
||||
import { LobeHubDatabase } from '@/database/type';
|
||||
import { messageRouter } from '@/server/routers/lambda/message';
|
||||
|
||||
import { cleanupTestUser, createTestContext, createTestUser } from '../setup';
|
||||
|
||||
describe('Your Feature Integration Tests', () => {
|
||||
let serverDB: LobeHubDatabase;
|
||||
let userId: string;
|
||||
|
||||
beforeEach(async () => {
|
||||
// 1. Get test database
|
||||
serverDB = await getTestDB();
|
||||
|
||||
// 2. Create test user
|
||||
userId = await createTestUser(serverDB);
|
||||
|
||||
// 3. Prepare other test data
|
||||
// ...
|
||||
});
|
||||
|
||||
afterEach(async () => {
|
||||
// Clean up test data
|
||||
await cleanupTestUser(serverDB, userId);
|
||||
});
|
||||
|
||||
it('should do something', async () => {
|
||||
// 1. Create tRPC caller
|
||||
const caller = messageRouter.createCaller(createTestContext(userId));
|
||||
|
||||
// 2. Perform operation
|
||||
const result = await caller.someMethod({
|
||||
/* params */
|
||||
});
|
||||
|
||||
// 3. Assert result
|
||||
expect(result).toBeDefined();
|
||||
|
||||
// 4. 🔥 Key: Verify from database
|
||||
const [dbRecord] = await serverDB.select().from(messages).where(eq(messages.id, result));
|
||||
|
||||
expect(dbRecord).toMatchObject({
|
||||
// Verify all critical fields
|
||||
});
|
||||
});
|
||||
});
|
||||
```
|
||||
|
||||
### Best Practices
|
||||
|
||||
#### 1. Test the Full Call Chain
|
||||
|
||||
```typescript
|
||||
it('should create message with correct associations', async () => {
|
||||
const caller = messageRouter.createCaller(createTestContext(userId));
|
||||
|
||||
// Perform operation
|
||||
const messageId = await caller.createMessage({
|
||||
content: 'Test',
|
||||
sessionId: testSessionId,
|
||||
topicId: testTopicId,
|
||||
});
|
||||
|
||||
// ✅ Verify from database, not just return value
|
||||
const [message] = await serverDB.select().from(messages).where(eq(messages.id, messageId));
|
||||
|
||||
expect(message.sessionId).toBe(testSessionId);
|
||||
expect(message.topicId).toBe(testTopicId);
|
||||
expect(message.userId).toBe(userId);
|
||||
});
|
||||
```
|
||||
|
||||
#### 2. Test Cascading Operations
|
||||
|
||||
```typescript
|
||||
it('should cascade delete messages when session is deleted', async () => {
|
||||
const sessionCaller = sessionRouter.createCaller(createTestContext(userId));
|
||||
const messageCaller = messageRouter.createCaller(createTestContext(userId));
|
||||
|
||||
// Create session and messages
|
||||
const sessionId = await sessionCaller.createSession({
|
||||
/* ... */
|
||||
});
|
||||
await messageCaller.createMessage({ sessionId /* ... */ });
|
||||
|
||||
// Delete session
|
||||
await sessionCaller.removeSession({ id: sessionId });
|
||||
|
||||
// ✅ Verify related messages are also deleted
|
||||
const remainingMessages = await serverDB
|
||||
.select()
|
||||
.from(messages)
|
||||
.where(eq(messages.sessionId, sessionId));
|
||||
|
||||
expect(remainingMessages).toHaveLength(0);
|
||||
});
|
||||
```
|
||||
|
||||
#### 3. Test Cross-Router Collaboration
|
||||
|
||||
```typescript
|
||||
it('should handle complete chat flow', async () => {
|
||||
const sessionCaller = sessionRouter.createCaller(createTestContext(userId));
|
||||
const topicCaller = topicRouter.createCaller(createTestContext(userId));
|
||||
const messageCaller = messageRouter.createCaller(createTestContext(userId));
|
||||
|
||||
// 1. Create session
|
||||
const sessionId = await sessionCaller.createSession({
|
||||
/* ... */
|
||||
});
|
||||
|
||||
// 2. Create topic
|
||||
const topicId = await topicCaller.createTopic({ sessionId /* ... */ });
|
||||
|
||||
// 3. Create message
|
||||
const messageId = await messageCaller.createMessage({
|
||||
sessionId,
|
||||
topicId,
|
||||
/* ... */
|
||||
});
|
||||
|
||||
// ✅ Verify full associations
|
||||
const [message] = await serverDB.select().from(messages).where(eq(messages.id, messageId));
|
||||
|
||||
expect(message.sessionId).toBe(sessionId);
|
||||
expect(message.topicId).toBe(topicId);
|
||||
});
|
||||
```
|
||||
|
||||
#### 4. Test Error Scenarios
|
||||
|
||||
```typescript
|
||||
it('should prevent cross-user access', async () => {
|
||||
// User A creates session
|
||||
const sessionId = await sessionRouter.createCaller(createTestContext(userA)).createSession({
|
||||
/* ... */
|
||||
});
|
||||
|
||||
// User B tries to access
|
||||
const callerB = messageRouter.createCaller(createTestContext(userB));
|
||||
|
||||
// ✅ Should throw error
|
||||
await expect(
|
||||
callerB.createMessage({
|
||||
sessionId,
|
||||
content: 'Unauthorized',
|
||||
}),
|
||||
).rejects.toThrow();
|
||||
});
|
||||
```
|
||||
|
||||
#### 5. Test Concurrency
|
||||
|
||||
```typescript
|
||||
it('should handle concurrent operations', async () => {
|
||||
const caller = messageRouter.createCaller(createTestContext(userId));
|
||||
|
||||
// Concurrently create multiple messages
|
||||
const promises = Array.from({ length: 10 }, (_, i) =>
|
||||
caller.createMessage({
|
||||
content: `Message ${i}`,
|
||||
sessionId: testSessionId,
|
||||
}),
|
||||
);
|
||||
|
||||
const messageIds = await Promise.all(promises);
|
||||
|
||||
// ✅ Verify all messages created successfully and are unique
|
||||
expect(messageIds).toHaveLength(10);
|
||||
expect(new Set(messageIds).size).toBe(10);
|
||||
});
|
||||
```
|
||||
|
||||
### Data Isolation
|
||||
|
||||
Each test case should be independent and not rely on others:
|
||||
|
||||
```typescript
|
||||
beforeEach(async () => {
|
||||
// Create new data for each test
|
||||
userId = await createTestUser(serverDB);
|
||||
testSessionId = await createTestSession(serverDB, userId);
|
||||
});
|
||||
|
||||
afterEach(async () => {
|
||||
// Clean up test data
|
||||
await cleanupTestUser(serverDB, userId);
|
||||
});
|
||||
```
|
||||
|
||||
### Test Naming
|
||||
|
||||
Use clear names to describe the test's intent:
|
||||
|
||||
```typescript
|
||||
// ✅ Good naming
|
||||
it('should create message with correct sessionId and topicId');
|
||||
it('should cascade delete messages when session is deleted');
|
||||
it('should prevent cross-user access to messages');
|
||||
|
||||
// ❌ Poor naming
|
||||
it('test message creation');
|
||||
it('test delete');
|
||||
```
|
||||
|
||||
## Differences from Unit Tests
|
||||
|
||||
| Dimension | Unit Test | Integration Test |
|
||||
| ---------------- | --------------------------- | --------------------------------- |
|
||||
| **Scope** | Single function/class | Multiple modules working together |
|
||||
| **Dependencies** | Mocks external dependencies | Uses real dependencies |
|
||||
| **Database** | Mocked | Real test database |
|
||||
| **Speed** | Fast (ms level) | Slower (seconds) |
|
||||
| **Quantity** | Many (60%) | Fewer (30%) |
|
||||
| **Purpose** | Verify logic correctness | Verify integration correctness |
|
||||
|
||||
## Testing Pyramid
|
||||
|
||||
```
|
||||
/\
|
||||
/E2E\ ← 10% (Critical business flows)
|
||||
/------\
|
||||
/Integration\ ← 30% (API integration tests) ⭐ Focus of this guide
|
||||
/------------\
|
||||
/ Unit Tests \ ← 60% (Already 80%+ coverage)
|
||||
/----------------\
|
||||
```
|
||||
|
||||
## Coverage Goals
|
||||
|
||||
### Priority P0 (Must Cover)
|
||||
|
||||
- ✅ Cross-layer ID propagation (sessionId, topicId, containerId, threadId)
|
||||
- ✅ Permission checks (users can only access their own resources)
|
||||
- ✅ Cascading deletes (deleting a session also deletes related data)
|
||||
- ✅ Foreign key constraints (cannot create associations to non-existent records)
|
||||
|
||||
### Priority P1 (Should Cover)
|
||||
|
||||
- Concurrency (multiple requests at the same time)
|
||||
- Pagination (correct data slicing)
|
||||
- Search functionality (keyword search)
|
||||
- Batch operations (bulk create/delete)
|
||||
|
||||
### Priority P2 (Nice to Have)
|
||||
|
||||
- Analytics (counts, rankings)
|
||||
- Complex queries (multi-condition filters)
|
||||
- Performance testing (large data scenarios)
|
||||
|
||||
## Debugging Tips
|
||||
|
||||
### 1. Inspect Test Database State
|
||||
|
||||
```typescript
|
||||
it('debug test', async () => {
|
||||
// Perform operation
|
||||
await caller.createMessage({
|
||||
/* ... */
|
||||
});
|
||||
|
||||
// Print database state
|
||||
const allMessages = await serverDB.select().from(messages);
|
||||
console.log('All messages:', allMessages);
|
||||
});
|
||||
```
|
||||
|
||||
### 2. Use Drizzle Studio
|
||||
|
||||
```bash
|
||||
# Launch Drizzle Studio to inspect test database
|
||||
pnpm db:studio
|
||||
```
|
||||
|
||||
### 3. Retain Test Data
|
||||
|
||||
```typescript
|
||||
afterEach(async () => {
|
||||
// Temporarily comment out cleanup to retain data for debugging
|
||||
// await cleanupTestUser(serverDB, userId);
|
||||
});
|
||||
```
|
||||
|
||||
## FAQ
|
||||
|
||||
### Q: Integration tests are slow. What can I do?
|
||||
|
||||
A:
|
||||
|
||||
1. Focus on critical paths, avoid over-testing
|
||||
2. Use `test.concurrent` to run independent tests in parallel
|
||||
3. Optimize test data setup to avoid redundant creation
|
||||
|
||||
### Q: Tests interfere with each other. How to fix?
|
||||
|
||||
A:
|
||||
|
||||
1. Ensure each test uses a unique userId
|
||||
2. Thoroughly clean up data in `afterEach`
|
||||
3. Use transaction isolation (if supported by the database)
|
||||
|
||||
### Q: How to test APIs that require authentication?
|
||||
|
||||
A: Use `createTestContext(userId)` to create an authenticated context:
|
||||
|
||||
```typescript
|
||||
const caller = messageRouter.createCaller(createTestContext(userId));
|
||||
```
|
||||
|
||||
## References
|
||||
|
||||
- [Vitest Documentation](https://vitest.dev/)
|
||||
- [Drizzle ORM Documentation](https://orm.drizzle.team/)
|
||||
- [tRPC Testing Guide](https://trpc.io/docs/server/testing)
|
||||
- [Test Pyramid by Martin Fowler](https://martinfowler.com/articles/practical-test-pyramid.html)
|
||||
|
||||
## Contributing
|
||||
|
||||
You're welcome to contribute more integration test cases! Please follow the style of existing test files.
|
||||
|
|
@ -1,5 +1,11 @@
|
|||
---
|
||||
title: 集成测试指南
|
||||
description: 了解集成测试的重要性及最佳实践，确保系统模块协同工作。
|
||||
tags:
|
||||
- 集成测试
|
||||
- 测试指南
|
||||
- 软件测试
|
||||
- 模块协作
|
||||
---
|
||||
|
||||
# 集成测试指南
|
||||
|
|
@ -83,13 +89,13 @@ import { afterEach, beforeEach, describe, expect, it } from 'vitest';
|
|||
|
||||
import { getTestDB } from '@/database/models/__tests__/_util';
|
||||
import { messages, sessions, users } from '@/database/schemas';
|
||||
import { LobeChatDatabase } from '@/database/type';
|
||||
import { LobeHubDatabase } from '@/database/type';
|
||||
import { messageRouter } from '@/server/routers/lambda/message';
|
||||
|
||||
import { cleanupTestUser, createTestContext, createTestUser } from '../setup';
|
||||
|
||||
describe('Your Feature Integration Tests', () => {
|
||||
let serverDB: LobeChatDatabase;
|
||||
let serverDB: LobeHubDatabase;
|
||||
let userId: string;
|
||||
|
||||
beforeEach(async () => {
|
||||
|
|
|
|||
|
|
@ -2,10 +2,10 @@
|
|||
|
||||
以下是一些词汇的固定翻译：
|
||||
|
||||
| develop key | zh-CN(中文) | en-US(English) |
|
||||
|-------------| ----------- | -------------- |
|
||||
| agent | 助理 | Agent |
|
||||
| agentGroup | 群组 | Group |
|
||||
| page | 文稿 | Page |
|
||||
| topic | 话题 | Topic |
|
||||
| thread | 子话题 | Thread |
|
||||
| develop key | zh-CN (中文) | en-US(English) |
|
||||
| ----------- | ------------ | -------------- |
|
||||
| agent | 助理 | Agent |
|
||||
| agentGroup | 群组 | Group |
|
||||
| page | 文稿 | Page |
|
||||
| topic | 话题 | Topic |
|
||||
| thread | 子话题 | Thread |
|
||||
|
|
|
|||
13
docs/glossary.zh-CN.md
Normal file
13
docs/glossary.zh-CN.md
Normal file
|
|
@ -0,0 +1,13 @@
|
|||
```markdown
|
||||
# 术语表
|
||||
|
||||
以下是一些词汇的固定翻译：
|
||||
|
||||
| 开发键 | zh-CN（中文） | en-US（英文） |
|
||||
| ---------- | ------------- | ------------- |
|
||||
| agent | 助理 | Agent |
|
||||
| agentGroup | 群组 | Group |
|
||||
| page | 文稿 | Page |
|
||||
| topic | 话题 | Topic |
|
||||
| thread | 子话题 | Thread |
|
||||
```
|
||||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: Integrating Data Analytics Services in LobeChat for User Usage Analysis
|
||||
title: Integrating Data Analytics Services in LobeHub for User Usage Analysis
|
||||
description: >-
|
||||
Learn how to integrate free/open-source data analytics services in LobeChat to
|
||||
Learn how to integrate free/open-source data analytics services in LobeHub to
|
||||
collect user usage data efficiently.
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- data analytics
|
||||
- user usage analysis
|
||||
- Vercel Analytics
|
||||
|
|
@ -13,7 +13,7 @@ tags:
|
|||
|
||||
# Data Analysis
|
||||
|
||||
To better help analyze the usage of LobeChat users, we have integrated several free/open-source data analytics services in LobeChat for collecting user usage data, which you can enable as needed.
|
||||
To better help analyze the usage of LobeHub users, we have integrated several free/open-source data analytics services in LobeHub for collecting user usage data, which you can enable as needed.
|
||||
|
||||
<Callout type={'warning'}>
|
||||
Currently, the integrated data analytics platforms only support deployment and usage on
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: LobeChat 数据分析集成服务介绍
|
||||
description: 了解如何在 LobeChat 中集成免费/开源的数据统计服务，帮助分析用户使用情况。包括 Vercel Analytics 的设置和使用教程。
|
||||
title: LobeHub 数据分析集成服务介绍
|
||||
description: 了解如何在 LobeHub 中集成免费/开源的数据统计服务，帮助分析用户使用情况。包括 Vercel Analytics 的设置和使用教程。
|
||||
tags:
|
||||
- LobeChat
|
||||
- LobeHub
|
||||
- 数据分析
|
||||
- Vercel Analytics
|
||||
- 数据统计服务
|
||||
|
|
@ -11,7 +11,7 @@ tags:
|
|||
|
||||
# 数据分析
|
||||
|
||||
为更好地帮助分析 LobeChat 的用户使用情况，我们在 LobeChat 中集成了若干免费 / 开源的数据统计服务，用于收集用户的使用情况，你可以按需开启。
|
||||
为更好地帮助分析 LobeHub 的用户使用情况，我们在 LobeHub 中集成了若干免费 / 开源的数据统计服务，用于收集用户的使用情况，你可以按需开启。
|
||||
|
||||
<Callout type={'warning'}>
|
||||
目前集成的数据分析平台，均只支持 Vercel / Zeabur 平台部署使用，不支持 Docker/Docker Compose 部署
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
---
|
||||
title: LobeChat Authentication Service Configuration
|
||||
title: LobeHub Authentication Service Configuration
|
||||
description: >-
|
||||
Learn how to configure Better Auth for centralized user authorization
|
||||
management. Supported SSO providers include Google, GitHub, Microsoft, and
|
||||
more.
|
||||
Learn how to configure external authentication services using Better Auth,
|
||||
Clerk, or Next Auth for centralized user authorization management. Supported
|
||||
authentication services include Auth0, Azure ID, etc.
|
||||
tags:
|
||||
- Authentication Service
|
||||
- Better Auth
|
||||
|
|
@ -12,13 +12,23 @@ tags:
|
|||
|
||||
# Authentication Service
|
||||
|
||||
LobeChat uses [Better Auth](https://www.better-auth.com) as its authentication solution, providing comprehensive, secure, and flexible identity verification for self-hosted deployments.
|
||||
LobeHub supports the configuration of external authentication services using Better Auth, Clerk, or Next Auth for internal use within enterprises/organizations to centrally manage user authorization.
|
||||
|
||||
<Callout type={'info'}>
|
||||
Looking for legacy authentication methods? See [Legacy Authentication](/docs/self-hosting/advanced/auth/legacy) for NextAuth and Clerk documentation.
|
||||
</Callout>
|
||||
|
||||
## Key Features
|
||||
Clerk is a comprehensive identity verification solution that has recently gained popularity. It provides a simple yet powerful API and services to handle user authentication and session management. Clerk's design philosophy is to offer a concise and modern authentication solution that enables developers to easily integrate and use it.
|
||||
|
||||
LobeHub has deeply integrated with Clerk to provide users with a more secure and convenient login and registration experience. It also relieves developers from the burden of managing authentication logic. Clerk's concise and modern design philosophy aligns perfectly with LobeHub's goals, making user management on the entire platform more efficient and reliable.
|
||||
|
||||
By setting the environment variables `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` and `CLERK_SECRET_KEY` in LobeHub's environment, you can enable and use Clerk.
|
||||
|
||||
## Better Auth
|
||||
|
||||
[Better Auth](https://www.better-auth.com) is a modern, framework-agnostic authentication library designed to provide comprehensive, secure, and flexible authentication solutions. It supports various authentication methods including email/password, magic links, and multiple OAuth/SSO providers.
|
||||
|
||||
### Key Features
|
||||
|
||||
- **Email/Password Authentication**: Built-in support for traditional email and password login with secure password hashing
|
||||
- **Email Verification**: Optional email verification flow with customizable email templates
|
||||
|
|
@ -28,12 +38,14 @@ LobeChat uses [Better Auth](https://www.better-auth.com) as its authentication s
|
|||
|
||||
## Getting Started
|
||||
|
||||
To enable Better Auth in LobeChat, set the following environment variables:
|
||||
To enable Better Auth in LobeHub, set the following environment variables:
|
||||
|
||||
| Environment Variable | Type | Description |
|
||||
| -------------------- | -------- | ------------------------------------------------------------------------------ |
|
||||
| `AUTH_SECRET` | Required | Key used to encrypt session tokens. Generate using: `openssl rand -base64 32` |
|
||||
| `AUTH_SSO_PROVIDERS` | Optional | Comma-separated list of enabled SSO providers, e.g., `google,github,microsoft` |
|
||||
| Environment Variable | Type | Description |
|
||||
| -------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `NEXT_PUBLIC_ENABLE_BETTER_AUTH` | Required | Set to `1` to enable Better Auth service |
|
||||
| `AUTH_SECRET` | Required | Key used to encrypt session tokens. Generate using: `openssl rand -base64 32` |
|
||||
| `NEXT_PUBLIC_AUTH_URL` | Required | The browser-accessible base URL for Better Auth (e.g., `http://localhost:3010`, `https://LobeHub.com`). Optional for Vercel deployments (auto-detected from `VERCEL_URL`) |
|
||||
| `AUTH_SSO_PROVIDERS` | Optional | Comma-separated list of enabled SSO providers, e.g., `google,github,microsoft` |
|
||||
|
||||
## Supported SSO Providers
|
||||
|
||||
|
|
@ -140,9 +152,7 @@ Send emails via SMTP protocol, suitable for users with existing email services.
|
|||
|
||||
### Common Configuration
|
||||
|
||||
| Environment Variable | Type | Description | Example |
|
||||
| ------------------------- | -------- | --------------------------------------------------------- | ------- |
|
||||
| `AUTH_EMAIL_VERIFICATION` | Optional | Set to `1` to require email verification (off by default) | `1` |
|
||||
Before using NextAuth, please set the following variables in LobeHub's environment variables:
|
||||
|
||||
## Magic Link (Passwordless) Login
|
||||
|
||||
|
|
@ -190,4 +200,16 @@ Set the `AUTH_ALLOWED_EMAILS` environment variable with a comma-separated list o
|
|||
- Allow only `example.com` domain: `AUTH_ALLOWED_EMAILS=example.com`
|
||||
- Allow multiple domains and specific emails: `AUTH_ALLOWED_EMAILS=example.com,company.org,admin@other.com`
|
||||
|
||||
Leave empty to allow all emails. This restriction applies to both email registration and SSO login.
|
||||
## Additional Features
|
||||
|
||||
### Webhook Support
|
||||
|
||||
Allow LobeHub to receive notifications when user information is updated in the identity provider. Supported providers include Casdoor and Logto. Please refer to the specific provider documentation for configuration details.
|
||||
|
||||
### Database Session
|
||||
|
||||
Allow the session store in database, see also the [Auth.js Session Documentation](https://authjs.dev/concepts/session-strategies#database-session).
|
||||
|
||||
## Other SSO Providers
|
||||
|
||||
Please refer to the [Auth.js](https://authjs.dev/getting-started/authentication/oauth) documentation and feel free to submit a Pull Request.
|
||||
|
|
|
|||
|
|
@ -1,21 +1,34 @@
|
|||
---
|
||||
title: LobeChat 身份验证服务配置
|
||||
description: 了解如何配置 Better Auth 以统一管理用户授权。支持的 SSO 提供商包括 Google、GitHub、Microsoft 等。
|
||||
title: LobeHub 身份验证服务配置
|
||||
description: >-
|
||||
了解如何使用 Better Auth、Clerk 或 Next Auth 配置外部身份验证服务，以统一管理用户授权。支持的身份验证服务包括 Auth0、
|
||||
Azure ID 等。
|
||||
tags:
|
||||
- 身份验证服务
|
||||
- Better Auth
|
||||
- LobeHub
|
||||
- SSO
|
||||
---
|
||||
|
||||
# 身份验证服务
|
||||
|
||||
LobeChat 使用 [Better Auth](https://www.better-auth.com) 作为身份验证解决方案，为自托管部署提供全面、安全、灵活的身份验证服务。
|
||||
LobeHub 支持使用 Better Auth、Clerk 或者 Next Auth 配置外部身份验证服务，供企业 / 组织内部使用，统一管理用户授权。
|
||||
|
||||
<Callout type={'info'}>
|
||||
需要使用旧版身份验证方案？请参阅 [旧版身份验证](/zh/docs/self-hosting/advanced/auth/legacy) 了解 NextAuth 和 Clerk 的文档。
|
||||
</Callout>
|
||||
|
||||
## 主要特性
|
||||
Clerk 是一个近期流行起来的全面的身份验证解决方案，它提供了简单而强大的 API 和服务来处理用户认证和会话管理。Clerk 的设计哲学是提供一套简洁、现代的认证解决方案，使得开发者可以轻松集成和使用。
|
||||
|
||||
LobeHub 与 Clerk 做了深度集成，能够为用户提供一个更加安全、便捷的登录和注册体验，同时也为开发者减轻了管理身份验证逻辑的负担。Clerk 的简洁和现代的设计理念与 LobeHub 的目标非常契合，使得整个平台的用户管理更加高效和可靠。
|
||||
|
||||
在 LobeHub 的环境变量中设置 `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` 和 `CLERK_SECRET_KEY`，即可开启和使用 Clerk。
|
||||
|
||||
## Better Auth
|
||||
|
||||
[Better Auth](https://www.better-auth.com) 是一个现代化、框架无关的身份验证库，旨在提供全面、安全、灵活的身份验证解决方案。它支持多种认证方式，包括邮箱 / 密码登录、魔法链接登录以及多种 OAuth/SSO 提供商。
|
||||
|
||||
### 主要特性
|
||||
|
||||
- **邮箱 / 密码认证**：内置支持传统的邮箱和密码登录，采用安全的密码哈希算法
|
||||
- **邮箱验证**：可选的邮箱验证流程，支持自定义邮件模板
|
||||
|
|
@ -25,12 +38,14 @@ LobeChat 使用 [Better Auth](https://www.better-auth.com) 作为身份验证解
|
|||
|
||||
## 快速开始
|
||||
|
||||
要在 LobeChat 中启用 Better Auth，请设置以下环境变量：
|
||||
要在 LobeHub 中启用 Better Auth，请设置以下环境变量：
|
||||
|
||||
| 环境变量 | 类型 | 描述 |
|
||||
| -------------------- | -- | ------------------------------------------------ |
|
||||
| `AUTH_SECRET` | 必选 | 用于加密会话令牌的密钥。使用以下命令生成：`openssl rand -base64 32` |
|
||||
| `AUTH_SSO_PROVIDERS` | 可选 | 启用的 SSO 提供商列表，以逗号分隔，例如 `google,github,microsoft` |
|
||||
| 环境变量 | 类型 | 描述 |
|
||||
| -------------------------------- | -- | --------------------------------------------------------------------------------------------------------------- |
|
||||
| `NEXT_PUBLIC_ENABLE_BETTER_AUTH` | 必选 | 设置为 `1` 以启用 Better Auth 服务 |
|
||||
| `AUTH_SECRET` | 必选 | 用于加密会话令牌的密钥。使用以下命令生成：`openssl rand -base64 32` |
|
||||
| `NEXT_PUBLIC_AUTH_URL` | 必选 | 浏览器可访问的 Better Auth 基础 URL（例如 `http://localhost:3010`、`https://LobeHub.com`）。Vercel 部署时可选（会自动从 `VERCEL_URL` 获取） |
|
||||
| `AUTH_SSO_PROVIDERS` | 可选 | 启用的 SSO 提供商列表，以逗号分隔，例如 `google,github,microsoft` |
|
||||
|
||||
## 支持的 SSO 提供商
|
||||
|
||||
|
|
@ -137,9 +152,7 @@ LobeChat 使用 [Better Auth](https://www.better-auth.com) 作为身份验证解
|
|||
|
||||
### 通用配置
|
||||
|
||||
| 环境变量 | 类型 | 描述 | 示例 |
|
||||
| ------------------------- | -- | --------------------------- | --- |
|
||||
| `AUTH_EMAIL_VERIFICATION` | 可选 | 设置为 `1` 以要求用户在登录前验证邮箱（默认关闭） | `1` |
|
||||
在使用 NextAuth 之前，请先在 LobeHub 的环境变量中设置以下变量：
|
||||
|
||||
## 魔法链接（免密）登录
|
||||
|
||||
|
|
@ -188,4 +201,14 @@ Better Auth 支持内置提供商（Google、GitHub、Microsoft、Apple、AWS Co
|
|||
- 只允许 `example.com` 域名：`AUTH_ALLOWED_EMAILS=example.com`
|
||||
- 允许多个域名和特定邮箱：`AUTH_ALLOWED_EMAILS=example.com,company.org,admin@other.com`
|
||||
|
||||
留空表示允许所有邮箱注册。此限制对邮箱注册和 SSO 登录均有效。
|
||||
### Webhook 支持
|
||||
|
||||
允许 LobeHub 在身份提供商中用户信息更新时接收通知。支持的提供商包括 Casdoor 和 Logto。请参考具体提供商文档进行配置。
|
||||
|
||||
### 数据库会话
|
||||
|
||||
允许会话存储在数据库中，详情请参阅 [Auth.js 会话文档](https://authjs.dev/concepts/session-strategies#database-session)。
|
||||
|
||||
## 其他 SSO 提供商
|
||||
|
||||
请参考 [NextAuth.js](https://next-auth.js.org/providers) 文档，欢迎提交 Pull Request。
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Reference in a new issue