@lobehub/lobehub 2.1.1 → 2.1.3

package/docs/self-hosting/environment-variables/basic.mdx

@@ -190,13 +190,6 @@ SSRF_ALLOW_IP_ADDRESS_LIST=192.168.1.100,10.0.0.50
 - Allow access to internal API gateway: `10.0.0.50`
 - Allow access to internal documentation server: `172.16.0.10`
 
-### `ENABLE_AUTH_PROTECTION`
-
-- Type: Optional
-- Description: Controls whether to enable route protection. When set to `1`, all routes except public routes (like `/api/auth`, `/login`, `/signup`) will require authentication. When set to `0` or not set, only specific protected routes (like `/settings`, `/files`) will require authentication.
-- Default: `0`
-- Example: `1` or `0`
-
 ### `NEXT_PUBLIC_ASSET_PREFIX`
 
 - Type: Optional

package/docs/self-hosting/environment-variables/basic.zh-CN.mdx

@@ -185,13 +185,6 @@ SSRF_ALLOW_IP_ADDRESS_LIST=192.168.1.100,10.0.0.50
 - 允许访问内网 API 网关：`10.0.0.50`
 - 允许访问内网文档服务器：`172.16.0.10`
 
-### `ENABLE_AUTH_PROTECTION`
-
-- 类型：可选
-- 说明：控制是否启用路由保护。当设置为 `1` 时，除了公共路由（如 `/api/auth`、`/login`、`/signup`）外，所有路由都需要认证。当设置为 `0` 或未设置时，只有特定的受保护路由（如 `/settings`、`/files` 等）需要认证。
-- 默认值：`0`
-- 示例：`1` 或 `0`
-
 ### `NEXT_PUBLIC_ASSET_PREFIX`
 
 - 类型：可选

package/docs/self-hosting/environment-variables/redis.mdx

@@ -10,7 +10,7 @@ tags:
 
 # Configure Redis Cache Service
 
-LobeChat uses Redis as a high-performance cache and session storage service. Configuring Redis can optimize authentication session management, file proxy caching, and more.
+LobeHub uses Redis as a high-performance cache and session storage service. Configuring Redis can optimize authentication session management, file proxy caching, and more.
 
 ## Core Environment Variables
 

package/docs/self-hosting/environment-variables/redis.zh-CN.mdx

@@ -10,7 +10,7 @@ tags:
 
 # 配置 Redis 缓存服务
 
-LobeChat 使用 Redis 作为高性能缓存和会话存储服务。配置 Redis 可以优化认证会话管理、文件代理缓存等功能。
+LobeHub 使用 Redis 作为高性能缓存和会话存储服务。配置 Redis 可以优化认证会话管理、文件代理缓存等功能。
 
 ## 核心环境变量
 

package/docs/self-hosting/environment-variables.mdx

@@ -57,7 +57,7 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v3
         with:
-          repository: lobehub/lobe-chat
+          repository: lobehub/lobehub
 
       - name: Log in to the Container registry
         uses: docker/login-action@v2

package/docs/self-hosting/examples/azure-openai.mdx

@@ -40,4 +40,3 @@ If you want the deployed version to be pre-configured with Azure OpenAI for end
 | `AZURE_ENDPOINT`     | Required | Azure API address, can be found in the "Keys and Endpoints" section when checking resources in the Azure portal                                                                                                                                                      | -                  | `https://docs-test-001.openai.azure.com`                                                                         |
 | `AZURE_API_VERSION`  | Required | Azure API version, following the format YYYY-MM-DD                                                                                                                                                                                                                   | 2023-08-01-preview | `-`, see [latest version](https://learn.microsoft.com/en-us/azure/ai-services/openai/reference#chat-completions) |
 | `AZURE_MODEL_LIST`   | Required | Used to control the model list, use `+` to add a model, use `-` to hide a model, use `id->deplymentName=displayName` to customize the display name of a model, separated by commas. Definition syntax rules see [Model List](/docs/self-hosting/advanced/model-list) | -                  | `gpt-35-turbo->my-deploy=GPT 3.5 Turbo` or `gpt-4-turbo->my-gpt4=GPT 4 Turbo<128000:vision:fc>`                  |
-| `ACCESS_CODE`        | Optional | Add a password to access LobeHub. You can set a long password to prevent brute force attacks. When this value is separated by commas, it becomes an array of passwords                                                                                               | -                  | `awCT74` or `e3@09!` or `code1,code2,code3`                                                                      |

package/docs/self-hosting/examples/azure-openai.zh-CN.mdx

@@ -42,4 +42,3 @@ LobeHub 支持使用 [Azure OpenAI](https://learn.microsoft.com/zh-cn/azure/ai-s
 | `AZURE_ENDPOINT`    | 必选 | Azure API 地址，从 Azure 门户检查资源时，可在 “密钥和终结点” 部分中找到此值                                                                | -                  | `https://docs-test-001.openai.azure.com`                                                            |
 | `AZURE_API_VERSION` | 必选 | Azure 的 API 版本，遵循 YYYY-MM-DD 格式                                                                                 | 2023-08-01-preview | `-`，查阅[最新版本](https://learn.microsoft.com/zh-cn/azure/ai-services/openai/reference#chat-completions) |
 | `AZURE_MODEL_LIST`  | 必选 | 用来控制模型列表，使用 `模型名->部署名=展示名` 来自定义模型的展示名，用英文逗号隔开。支持扩展能力，其余语法规则详见 [模型列表](/zh/docs/self-hosting/advanced/model-list) | -                  | `gpt-35-turbo->my-deploy=GPT 3.5 Turbo` 或 `gpt-4-turbo->my-gpt4=GPT 4 Turbo<128000:vision:fc>`      |
-| `ACCESS_CODE`       | 可选 | 添加访问 LobeHub 的密码，你可以设置一个长密码以防被爆破，该值用逗号分隔时为密码数组                                                                  | -                  | `awCT74` 或 `e3@09!` or `code1,code2,code3`                                                          |

package/docs/self-hosting/faq/no-v1-suffix.mdx

@@ -21,8 +21,8 @@ Recheck and confirm whether `OPENAI_PROXY_URL` is set correctly, including wheth
 
 ### Related Discussion Links
 
-- [Why is the return value blank after configuring environment variables in Docker?](https://github.com/lobehub/lobe-chat/discussions/623)
-- [Reasons for errors when using third-party interfaces](https://github.com/lobehub/lobe-chat/discussions/734)
-- [No response when the proxy server address is filled in for chat](https://github.com/lobehub/lobe-chat/discussions/1065)
+- [Why is the return value blank after configuring environment variables in Docker?](https://github.com/lobehub/lobehub/discussions/623)
+- [Reasons for errors when using third-party interfaces](https://github.com/lobehub/lobehub/discussions/734)
+- [No response when the proxy server address is filled in for chat](https://github.com/lobehub/lobehub/discussions/1065)
 
 If the problem still cannot be resolved, it is recommended to raise the issue in the community, providing relevant logs and configuration information for other developers or maintainers to offer assistance.

package/docs/self-hosting/faq/no-v1-suffix.zh-CN.mdx

@@ -20,8 +20,8 @@ tags:
 
 ### 相关讨论链接
 
-- [Docker 安装，配置好环境变量后，为何返回值是空白？](https://github.com/lobehub/lobe-chat/discussions/623)
-- [使用第三方接口报错的原因](https://github.com/lobehub/lobe-chat/discussions/734)
-- [代理服务器地址填了聊天没任何反应](https://github.com/lobehub/lobe-chat/discussions/1065)
+- [Docker 安装，配置好环境变量后，为何返回值是空白？](https://github.com/lobehub/lobehub/discussions/623)
+- [使用第三方接口报错的原因](https://github.com/lobehub/lobehub/discussions/734)
+- [代理服务器地址填了聊天没任何反应](https://github.com/lobehub/lobehub/discussions/1065)
 
 如果问题依旧无法解决，建议在社区中提出问题，附上相关日志和配置信息，以便其他开发者或维护者提供帮助。

package/docs/self-hosting/{advanced → migration/v2}/auth/clerk-to-betterauth.mdx

@@ -1,7 +1,7 @@
 ---
 title: Migrating from Clerk to Better Auth
 description: >-
-  Guide for migrating your LobeChat deployment from Clerk authentication to
+  Guide for migrating your LobeHub deployment from Clerk authentication to
   Better Auth, including simple and full migration options.
 tags:
   - Authentication Service
@@ -12,17 +12,17 @@ tags:
 
 # Migrating from Clerk to Better Auth
 
-This guide helps you migrate your existing Clerk-based LobeChat deployment to Better Auth.
+This guide helps you migrate your existing Clerk-based LobeHub deployment to Better Auth.
 
 <Callout type={'info'}>
-  Better Auth is the recommended authentication solution for LobeChat. It offers simpler configuration, more SSO providers, and better self-hosting support.
+  Better Auth is the recommended authentication solution for LobeHub. It offers simpler configuration, more SSO providers, and better self-hosting support.
 </Callout>
 
 <Callout type={'error'}>
   **Important Notice**:
 
   - **Always backup your database first!** For Neon users, create a backup via [Fork Branch](https://neon.tech/docs/manage/branches#create-a-branch)
-  - LobeChat is not responsible for any data loss or issues that may occur during the migration process
+  - LobeHub is not responsible for any data loss or issues that may occur during the migration process
   - This guide is intended for users with development experience; not recommended for users without technical background
   - If you have any questions, feel free to ask in our [Discord](https://discord.com/invite/AYFPHvv2jT) community or [GitHub Issue](https://github.com/lobehub/lobe-chat/issues/11707)
 </Callout>
@@ -83,7 +83,7 @@ For small self-hosted deployments, the simplest approach is to let users reset t
      See [Authentication Service Configuration](/docs/self-hosting/advanced/auth) for complete environment variables and SSO provider setup.
    </Callout>
 
-3. **Redeploy LobeChat**
+3. **Redeploy LobeHub**
 
    Deploy the new version with Better Auth enabled.
 
@@ -102,7 +102,7 @@ For small self-hosted deployments, the simplest approach is to let users reset t
    - Log in using their previously linked social account (e.g., Google, GitHub)
    - Click "Set Password" to receive an email and set a new password
 
-   ![LobeChat Login Page - Social Login Hint](https://hub-apac-1.lobeobjects.space/docs/8d0563701fcd17ad7252a72b1746dd42.png)
+   ![LobeHub Login Page - Social Login Hint](https://hub-apac-1.lobeobjects.space/docs/8d0563701fcd17ad7252a72b1746dd42.png)
 
    3. (Optional) After logging in, users can manage their account in the Profile page:
       - Linked Accounts: Link additional social accounts
@@ -139,7 +139,7 @@ For larger deployments or when you need to preserve user passwords and SSO conne
 
 **Preparation:**
 
-1. Clone the LobeChat repository and install dependencies:
+1. Clone the LobeHub repository and install dependencies:
 
    ```bash
    git clone https://github.com/lobehub/lobe-chat.git

package/docs/self-hosting/{advanced → migration/v2}/auth/clerk-to-betterauth.zh-CN.mdx

@@ -1,6 +1,6 @@
 ---
 title: 从 Clerk 迁移到 Better Auth
-description: 将 LobeChat 部署从 Clerk 身份验证迁移到 Better Auth 的指南，包括简单迁移和完整迁移选项。
+description: 将 LobeHub 部署从 Clerk 身份验证迁移到 Better Auth 的指南，包括简单迁移和完整迁移选项。
 tags:
   - 身份验证服务
   - Better Auth
@@ -10,17 +10,17 @@ tags:
 
 # 从 Clerk 迁移到 Better Auth
 
-本指南帮助您将现有的基于 Clerk 的 LobeChat 部署迁移到 Better Auth。
+本指南帮助您将现有的基于 Clerk 的 LobeHub 部署迁移到 Better Auth。
 
 <Callout type={'info'}>
-  Better Auth 是 LobeChat 推荐的身份验证解决方案。它提供更简单的配置、更多的 SSO 提供商支持，以及更好的自托管体验。
+  Better Auth 是 LobeHub 推荐的身份验证解决方案。它提供更简单的配置、更多的 SSO 提供商支持，以及更好的自托管体验。
 </Callout>
 
 <Callout type={'error'}>
   **重要提醒**：
 
   - **务必先备份数据库**！如使用 Neon，可通过 [Fork 分支](https://neon.tech/docs/manage/branches#create-a-branch) 创建备份
-  - 迁移过程中可能出现的任何数据丢失或问题，LobeChat 概不负责
+  - 迁移过程中可能出现的任何数据丢失或问题，LobeHub 概不负责
   - 本指南适合有一定开发背景的用户，不建议无技术经验的用户自行操作
   - 如有任何疑问，欢迎到 [Discord](https://discord.com/invite/AYFPHvv2jT) 社区或 [GitHub Issue](https://github.com/lobehub/lobe-chat/issues/11707) 提问
 </Callout>
@@ -81,7 +81,7 @@ tags:
      查阅 [身份验证服务配置](/zh/docs/self-hosting/advanced/auth) 了解完整的环境变量和 SSO 提供商配置。
    </Callout>
 
-3. **重新部署 LobeChat**
+3. **重新部署 LobeHub**
 
    部署启用 Better Auth 的新版本。
 
@@ -99,7 +99,7 @@ tags:
    - 使用之前关联的社交账号（如 Google、GitHub）登录
    - 点击「设置密码」链接，通过邮件设置新密码后登录
 
-   ![LobeChat 登录页面 - 社交账号登录提示](https://hub-apac-1.lobeobjects.space/docs/8d0563701fcd17ad7252a72b1746dd42.png)
+   ![LobeHub 登录页面 - 社交账号登录提示](https://hub-apac-1.lobeobjects.space/docs/8d0563701fcd17ad7252a72b1746dd42.png)
 
    3. （可选）登录后可在个人资料页进行以下操作：
       - 已关联账号：手动关联其他社交账号
@@ -134,7 +134,7 @@ tags:
 
 **准备工作：**
 
-1. Clone LobeChat 仓库并安装依赖：
+1. Clone LobeHub 仓库并安装依赖：
 
    ```bash
    git clone https://github.com/lobehub/lobe-chat.git

package/docs/self-hosting/{advanced → migration/v2}/auth/migration-internals.mdx

@@ -1,7 +1,7 @@
 ---
 title: Understanding Auth Migration - Technical Deep Dive
 description: >-
-  Technical explanation of how authentication migration works in LobeChat,
+  Technical explanation of how authentication migration works in LobeHub,
   including database schema, migration principles, and troubleshooting guide.
 tags:
   - Authentication
@@ -12,7 +12,7 @@ tags:
 
 # Understanding Auth Migration
 
-This document explains the technical principles behind authentication migration in LobeChat. It's intended for users with database and development experience who want to understand how migration works under the hood.
+This document explains the technical principles behind authentication migration in LobeHub. It's intended for users with database and development experience who want to understand how migration works under the hood.
 
 <Callout type={'info'}>
   For step-by-step migration instructions, see [NextAuth Migration](/docs/self-hosting/advanced/auth/nextauth-to-betterauth) or [Clerk Migration](/docs/self-hosting/advanced/auth/clerk-to-betterauth).

package/docs/self-hosting/{advanced → migration/v2}/auth/migration-internals.zh-CN.mdx

@@ -1,7 +1,7 @@
 ---
 title: 认证迁移原理 - 技术深入解析
 description: >-
-  LobeChat 认证迁移的技术原理解析，包括数据库 Schema、迁移原理和问题排查指南。
+  LobeHub 认证迁移的技术原理解析，包括数据库 Schema、迁移原理和问题排查指南。
 tags:
   - 认证
   - 迁移
@@ -11,7 +11,7 @@ tags:
 
 # 认证迁移原理
 
-本文档解释 LobeChat 认证迁移的技术原理，适合有数据库和开发经验的用户，帮助理解迁移的底层逻辑。
+本文档解释 LobeHub 认证迁移的技术原理，适合有数据库和开发经验的用户，帮助理解迁移的底层逻辑。
 
 <Callout type={'info'}>
   如需分步迁移指南，请参阅 [NextAuth 迁移](/docs/self-hosting/advanced/auth/nextauth-to-betterauth) 或 [Clerk 迁移](/docs/self-hosting/advanced/auth/clerk-to-betterauth)。

package/docs/self-hosting/{advanced → migration/v2}/auth/nextauth-to-betterauth.mdx

@@ -1,7 +1,7 @@
 ---
 title: Migrating from NextAuth to Better Auth
 description: >-
-  Guide for migrating your LobeChat deployment from NextAuth authentication to
+  Guide for migrating your LobeHub deployment from NextAuth authentication to
   Better Auth, including simple and full migration options.
 tags:
   - Authentication Service
@@ -12,17 +12,17 @@ tags:
 
 # Migrating from NextAuth to Better Auth
 
-This guide helps you migrate your existing NextAuth-based LobeChat deployment to Better Auth.
+This guide helps you migrate your existing NextAuth-based LobeHub deployment to Better Auth.
 
 <Callout type={'info'}>
-  Better Auth is the recommended authentication solution for LobeChat. It offers simpler configuration, more SSO providers, and better self-hosting support.
+  Better Auth is the recommended authentication solution for LobeHub. It offers simpler configuration, more SSO providers, and better self-hosting support.
 </Callout>
 
 <Callout type={'error'}>
   **Important Notice**:
 
   - **Always backup your database first!** For Neon users, create a backup via [Fork Branch](https://neon.tech/docs/manage/branches#create-a-branch)
-  - LobeChat is not responsible for any data loss or issues that may occur during the migration process
+  - LobeHub is not responsible for any data loss or issues that may occur during the migration process
   - This guide is intended for users with development experience; not recommended for users without technical background
   - If you have any questions, feel free to ask in our [Discord](https://discord.com/invite/AYFPHvv2jT) community or [GitHub Issue](https://github.com/lobehub/lobe-chat/issues)
 </Callout>
@@ -136,7 +136,7 @@ For small self-hosted deployments, the simplest approach is to let users re-logi
      See [Authentication Service Configuration](/docs/self-hosting/advanced/auth) for complete environment variables and SSO provider setup.
    </Callout>
 
-2. **Redeploy LobeChat**
+2. **Redeploy LobeHub**
 
    Deploy the new version with Better Auth enabled.
 
@@ -172,7 +172,7 @@ For larger deployments or when you need to preserve SSO connections, use the mig
 
 **Preparation:**
 
-1. Clone the LobeChat repository and install dependencies:
+1. Clone the LobeHub repository and install dependencies:
 
    ```bash
    git clone https://github.com/lobehub/lobe-chat.git
@@ -337,7 +337,7 @@ This error occurs because the database schema is outdated. Run `pnpm db:migrate`
 
 ### email\_not\_found error
 
-If you see a redirect to `signin?callbackUrl=...&error=email_not_found`, it means LobeChat cannot get the user's email.
+If you see a redirect to `signin?callbackUrl=...&error=email_not_found`, it means LobeHub cannot get the user's email.
 
 <Callout type={'warning'}>
   **Important**: Better Auth currently **requires user email** for authentication. All SSO providers must be configured to return email information, otherwise users cannot log in.
@@ -347,23 +347,23 @@ Common causes:
 
 **Cause 1: SSO connection not requesting email permission**
 
-When configuring SSO connections (e.g., GitHub in Auth0), make sure to enable **Email Address** permission in the Attributes section. LobeChat requires user email for authentication.
+When configuring SSO connections (e.g., GitHub in Auth0), make sure to enable **Email Address** permission in the Attributes section. LobeHub requires user email for authentication.
 
 **Cause 2: User email not configured in identity provider**
 
 For identity providers like Casdoor or Logto, users may not have an email configured.
 
 <Callout type={'warning'}>
-  **Note for Casdoor Users**: Casdoor does not require users to have an email configured, but LobeChat strongly depends on email for authentication. If you find migration difficult due to many users without email addresses, we recommend staying on [v2.0.0-next.344](https://github.com/lobehub/lobe-chat/releases/tag/v2.0.0-next.344) for now. We plan to provide a self-service migration feature in the future, where users without email will be redirected to a bind-email page when they log in.
+  **Note for Casdoor Users**: Casdoor does not require users to have an email configured, but LobeHub strongly depends on email for authentication. If you find migration difficult due to many users without email addresses, we recommend staying on [v2.0.0-next.344](https://github.com/lobehub/lobe-chat/releases/tag/v2.0.0-next.344) for now. We plan to provide a self-service migration feature in the future, where users without email will be redirected to a bind-email page when they log in.
 </Callout>
 
 Solution:
 
-1. First configure the Webhook in LobeChat to sync user data from the identity provider:
+1. First configure the Webhook in LobeHub to sync user data from the identity provider:
    - [Casdoor Webhook Configuration](/docs/self-hosting/advanced/auth/providers/casdoor)
    - [Logto Webhook Configuration](/docs/self-hosting/advanced/auth/providers/logto)
 2. Then configure the user's email in the identity provider's admin console
-3. The user data will be synced to LobeChat via Webhook, and the user can then log in
+3. The user data will be synced to LobeHub via Webhook, and the user can then log in
 
 ## Related Reading
 

package/docs/self-hosting/{advanced → migration/v2}/auth/nextauth-to-betterauth.zh-CN.mdx

@@ -1,6 +1,6 @@
 ---
 title: 从 NextAuth 迁移到 Better Auth
-description: 将 LobeChat 部署从 NextAuth 身份验证迁移到 Better Auth 的指南，包括简单迁移和完整迁移选项。
+description: 将 LobeHub 部署从 NextAuth 身份验证迁移到 Better Auth 的指南，包括简单迁移和完整迁移选项。
 tags:
   - 身份验证服务
   - Better Auth
@@ -10,17 +10,17 @@ tags:
 
 # 从 NextAuth 迁移到 Better Auth
 
-本指南帮助您将现有的基于 NextAuth 的 LobeChat 部署迁移到 Better Auth。
+本指南帮助您将现有的基于 NextAuth 的 LobeHub 部署迁移到 Better Auth。
 
 <Callout type={'info'}>
-  Better Auth 是 LobeChat 推荐的身份验证解决方案。它提供更简单的配置、更多的 SSO 提供商支持，以及更好的自托管体验。
+  Better Auth 是 LobeHub 推荐的身份验证解决方案。它提供更简单的配置、更多的 SSO 提供商支持，以及更好的自托管体验。
 </Callout>
 
 <Callout type={'error'}>
   **重要提醒**：
 
   - **务必先备份数据库**！如使用 Neon，可通过 [Fork 分支](https://neon.tech/docs/manage/branches#create-a-branch) 创建备份
-  - 迁移过程中可能出现的任何数据丢失或问题，LobeChat 概不负责
+  - 迁移过程中可能出现的任何数据丢失或问题，LobeHub 概不负责
   - 本指南适合有一定开发背景的用户，不建议无技术经验的用户自行操作
   - 如有任何疑问，欢迎到 [Discord](https://discord.com/invite/AYFPHvv2jT) 社区或 [GitHub Issue](https://github.com/lobehub/lobe-chat/issues) 提问
 </Callout>
@@ -131,7 +131,7 @@ Better Auth 支持更多功能，以下是新增的环境变量：
      查阅 [身份验证服务配置](/zh/docs/self-hosting/advanced/auth) 了解完整的环境变量和 SSO 提供商配置。
    </Callout>
 
-2. **重新部署 LobeChat**
+2. **重新部署 LobeHub**
 
    部署启用 Better Auth 的新版本。
 
@@ -167,7 +167,7 @@ Better Auth 支持更多功能，以下是新增的环境变量：
 
 **准备工作：**
 
-1. Clone LobeChat 仓库并安装依赖：
+1. Clone LobeHub 仓库并安装依赖：
 
    ```bash
    git clone https://github.com/lobehub/lobe-chat.git
@@ -331,7 +331,7 @@ npx tsx scripts/nextauth-to-betterauth/verify.ts
 
 ### email\_not\_found 错误
 
-如果登录时跳转到 `signin?callbackUrl=...&error=email_not_found`，说明 LobeChat 无法获取用户邮箱。
+如果登录时跳转到 `signin?callbackUrl=...&error=email_not_found`，说明 LobeHub 无法获取用户邮箱。
 
 <Callout type={'warning'}>
   **重要提示**：Better Auth 目前**强依赖用户邮箱**进行身份认证。所有 SSO 提供商必须配置为返回邮箱信息，否则用户无法登录。
@@ -341,23 +341,23 @@ npx tsx scripts/nextauth-to-betterauth/verify.ts
 
 **原因 1：SSO 连接未请求邮箱权限**
 
-配置 SSO 连接时（如 Auth0 中的 GitHub 连接），务必在 **Attributes** 部分勾选 **Email Address** 权限。LobeChat 需要用户邮箱进行身份认证。
+配置 SSO 连接时（如 Auth0 中的 GitHub 连接），务必在 **Attributes** 部分勾选 **Email Address** 权限。LobeHub 需要用户邮箱进行身份认证。
 
 **原因 2：用户在身份提供商中未配置邮箱**
 
 对于 Casdoor、Logto 等身份提供商，用户可能没有配置邮箱。
 
 <Callout type={'warning'}>
-  **Casdoor 用户注意**：Casdoor 不要求用户必须配置邮箱，但 LobeChat 强依赖邮箱进行身份认证。如果因为大量用户没有邮箱而感觉迁移困难，建议暂时停留在 [v2.0.0-next.344](https://github.com/lobehub/lobe-chat/releases/tag/v2.0.0-next.344) 版本。后续官方计划提供用户端自助迁移功能，届时没有邮箱的用户登录时会被重定向到绑定邮箱页面。
+  **Casdoor 用户注意**：Casdoor 不要求用户必须配置邮箱，但 LobeHub 强依赖邮箱进行身份认证。如果因为大量用户没有邮箱而感觉迁移困难，建议暂时停留在 [v2.0.0-next.344](https://github.com/lobehub/lobe-chat/releases/tag/v2.0.0-next.344) 版本。后续官方计划提供用户端自助迁移功能，届时没有邮箱的用户登录时会被重定向到绑定邮箱页面。
 </Callout>
 
 解决方案：
 
-1. 先在 LobeChat 中配置身份提供商的 Webhook 以同步用户数据：
+1. 先在 LobeHub 中配置身份提供商的 Webhook 以同步用户数据：
    - [Casdoor Webhook 配置](/zh/docs/self-hosting/advanced/auth/providers/casdoor)
    - [Logto Webhook 配置](/zh/docs/self-hosting/advanced/auth/providers/logto)
 2. 然后在身份提供商的管理后台为用户配置邮箱
-3. 用户数据通过 Webhook 同步到 LobeChat 后即可正常登录
+3. 用户数据通过 Webhook 同步到 LobeHub 后即可正常登录
 
 ## 相关阅读
 

package/docs/self-hosting/migration/v2/breaking-changes.mdx

@@ -78,4 +78,4 @@ LobeHub 2.0 recommends using **PostgreSQL 17** or higher.
 
 This is because LobeHub 2.0 uses the [pg\_search](https://github.com/paradedb/paradedb/tree/main/pg_search) extension for full-text search capabilities. If you use Serverless Postgres services like Neon, the pg\_search extension is only available on PostgreSQL 17.
 
-If you self-host your database with Docker, we recommend using the `pgvector/pgvector:pg17` image.
+If you self-host your database with Docker, we recommend using the `paradedb/paradedb:latest-pg17` image.

package/docs/self-hosting/migration/v2/breaking-changes.zh-CN.mdx

@@ -76,4 +76,4 @@ LobeHub 2.0 推荐使用 **PostgreSQL 17** 及以上版本。
 
 这是因为 LobeHub 2.0 使用了 [pg\_search](https://github.com/paradedb/paradedb/tree/main/pg_search) 插件来提供全文搜索能力。如果您使用 Neon 等 Serverless Postgres 服务，pg\_search 插件仅在 PostgreSQL 17 上可用。
 
-如果您使用 Docker 自建数据库，推荐使用 `pgvector/pgvector:pg17` 镜像。
+如果您使用 Docker 自建数据库，推荐使用 `paradedb/paradedb:latest-pg17` 镜像。

package/docs/self-hosting/platform/docker-compose.zh-CN.mdx

@@ -8,7 +8,7 @@ tags:
   - 部署指引
 ---
 
-# 使用 Docker Compose 部署 LobeHub 服务端数据库版本
+# 使用 Docker Compose 部署 LobeHub
 
 <div style={{display:"flex", gap: 4}}>
   [![][docker-release-shield]][docker-release-link]
@@ -254,13 +254,13 @@ mv .env.zh-CN.example .env
 
 ### 预备知识
 
-一般来讲，想要完整的运行 LobeHub 数据库版本，你需要至少拥有如下三个服务：
+一般来讲，想要完整的运行 LobeHub，你需要至少拥有如下三个服务：
 
-- LobeHub 数据库版本自身
+- LobeHub 自身
 - 带有 PGVector 插件的 PostgreSQL 数据库
 - 支持 S3 协议的对象存储服务
 
-这些服务可以通过自建或者在线云服务组合搭配，以满足不同层次的部署需求。本文中，我们提供了完全基于开源自建服务的 Docker Compose 配置，你可以直接使用这份配置文件来启动 LobeHub 数据库版本，也可以对之进行修改以适应你的需求。
+这些服务可以通过自建或者在线云服务组合搭配，以满足不同层次的部署需求。本文中，我们提供了完全基于开源自建服务的 Docker Compose 配置，你可以直接使用这份配置文件来启动 LobeHub，也可以对之进行修改以适应你的需求。
 
 我们默认使用 [RustFS](https://github.com/rustfs/rustfs) 作为本地 S3 对象存储服务。如需配置 SSO 登录鉴权服务，请参考 [身份验证服务](/zh/docs/self-hosting/advanced/auth) 文档。
 

package/docs/self-hosting/platform/docker.mdx

@@ -35,19 +35,19 @@ Here is the process for deploying the LobeHub server database version on a Linux
 <Steps>
   ### Create a Postgres Database Instance
 
-  Please create a Postgres database instance with the PGVector plugin according to your needs, for example:
+  Please create a Postgres database instance according to your needs, for example:
 
   ```sh
   docker network create pg
 
-  docker run --name my-postgres --network pg -e POSTGRES_PASSWORD=mysecretpassword -p 5432:5432 -d pgvector/pgvector:pg17
+  docker run --name my-postgres --network pg -e POSTGRES_PASSWORD=mysecretpassword -p 5432:5432 -d paradedb/paradedb:latest-pg17
   ```
 
-  The above command will create a PG instance named `my-postgres` on the network `pg`, where `pgvector/pgvector:pg17` is a Postgres 17 image with the pgvector plugin installed by default.
+  The above command will create a PG instance named `my-postgres` on the network `pg`, where `paradedb/paradedb:latest-pg17` is a Postgres 17 image with pgvector and pg\_search plugins installed by default.
 
   <Callout type="info">
-    The pgvector plugin provides vector search capabilities for Postgres, which is an important
-    component for LobeHub to implement RAG.
+    The ParadeDB image includes pgvector (vector search) and pg\_search (full-text search) plugins, which are important
+    components for LobeHub to implement RAG and knowledge base search.
   </Callout>
 
   <Callout type="warning">

package/docs/self-hosting/platform/docker.zh-CN.mdx

@@ -8,7 +8,7 @@ tags:
   - Postgres
 ---
 
-# 使用 Docker 部署服务端数据库版
+# 使用 Docker 部署 LobeHub
 
 <div style={{display:"flex", gap: 4}}>
   [![][docker-release-shield]][docker-release-link]
@@ -19,32 +19,32 @@ tags:
 </div>
 
 <Callout type="info">
-  本文已经假定你了解了 LobeHub 服务端数据库版本（下简称 DB
-  版）的部署基本原理和流程，因此只包含核心环境变量配置的内容。如果你还不了解 LobeHub DB
-  版的部署原理，请先查阅 [使用服务端数据库部署](/zh/docs/self-hosting/server-database) 。
+  本文已经假定你了解了 LobeHub
+  的部署基本原理和流程，因此只包含核心环境变量配置的内容。如果你还不了解 LobeHub
+  的部署原理，请先查阅 [使用服务端数据库部署](/zh/docs/self-hosting/server-database) 。
   此外，针对国内的腾讯云储存桶用户，可查询[配置腾讯云 COS
   存储服务](/zh/docs/self-hosting/advanced/s3/tencent-cloud)。
 </Callout>
 
 ## 在 Linux 服务器上部署
 
-以下是在 Linux 服务器上部署 LobeHub DB 版的流程：
+以下是在 Linux 服务器上部署 LobeHub 的流程：
 
 <Steps>
   ### 创建 Postgres 数据库实例
 
-  请按照你自己的诉求创建一个带有 PGVector 插件的 Postgres 数据库实例，例如：
+  请按照你自己的诉求创建一个 Postgres 数据库实例，例如：
 
   ```sh
   docker network create pg
 
-  docker run --name my-postgres --network pg -e POSTGRES_PASSWORD=mysecretpassword -p 5432:5432 -d pgvector/pgvector:pg17
+  docker run --name my-postgres --network pg -e POSTGRES_PASSWORD=mysecretpassword -p 5432:5432 -d paradedb/paradedb:latest-pg17
   ```
 
-  上述指令会创建一个名为 `my-postgres`，并且网络为 `pg` 的 PG 实例，其中 `pgvector/pgvector:pg17` 是一个 Postgres 17 的镜像，且默认安装了 pgvector 插件。
+  上述指令会创建一个名为 `my-postgres`，并且网络为 `pg` 的 PG 实例，其中 `paradedb/paradedb:latest-pg17` 是一个 Postgres 17 的镜像，且默认安装了 pgvector 和 pg\_search 插件。
 
   <Callout type="info">
-    pgvector 插件为 Postgres 提供了向量搜索的能力，是 LobeHub 实现 RAG 的重要构件之一。
+    ParadeDB 镜像包含了 pgvector（向量搜索）和 pg\_search（全文搜索）插件，是 LobeHub 实现 RAG 和知识库搜索的重要构件。
   </Callout>
 
   <Callout type="warning">
@@ -125,7 +125,7 @@ tags:
 
 ## 在本地（Mac / Windows） 上使用
 
-LobeHub 的 DB 版也支持直接在本地的 Mac/Windows 本地使用。
+LobeHub 也支持直接在本地的 Mac/Windows 本地使用。
 
 在此我们已假设你的本地有一个 5432 端口可用，账号为 `postgres` ，密码是 `mysecretpassword` 的 pg 实例，它在 `localhost:5432` 可用。
 

package/docs/self-hosting/platform/dokploy.mdx

@@ -67,7 +67,7 @@ You also need to configure the `JWKS_KEY` environment variable for signing and v
 
 ## 2. Deploying the database on Dokploy
 
-Enter the previously created Project, click on Create Service, and select Database. In the Database interface, choose PostgreSQL, then set the database name, user, and password. In the Docker image field, enter `pgvector/pgvector:pg17`, and finally click Create to create the database.
+Enter the previously created Project, click on Create Service, and select Database. In the Database interface, choose PostgreSQL, then set the database name, user, and password. In the Docker image field, enter `paradedb/paradedb:latest-pg17`, and finally click Create to create the database.
 
 ![](/blog/assets7006b60baaf62aa0d95cd40456e24afe.webp)
 

package/docs/self-hosting/platform/dokploy.zh-CN.mdx

@@ -1,6 +1,6 @@
 ---
-title: 在 Dokploy 上部署 LobeHub 的服务端数据库版本
-description: 本文详细介绍如何在 Dokploy 中部署服务端数据库版 LobeHub，包括数据库配置、身份验证服务配置的设置步骤。
+title: 在 Dokploy 上部署 LobeHub
+description: 本文详细介绍如何在 Dokploy 中部署 LobeHub，包括数据库配置、身份验证服务配置的设置步骤。
 tags:
   - 服务端数据库
   - Postgres
@@ -11,9 +11,9 @@ tags:
   - 环境变量配置
 ---
 
-# 在 Dokploy 上部署服务端数据库版
+# 在 Dokploy 上部署 LobeHub
 
-本文将详细介绍如何在 Dokploy 中部署服务端数据库版 LobeHub。
+本文将详细介绍如何在 Dokploy 中部署 LobeHub。
 
 ## 一、准备工作
 
@@ -68,7 +68,7 @@ S3_ENABLE_PATH_STYLE=
 
 ## 二、在 Dokploy 上部署数据库
 
-进入前面创建的 Project，点击 Create Service 选择 Database，在 Database 界面选择 PostgreSQL ，然后设置数据库名、用户、密码，在 Docker image 中填入 `pgvector/pgvector:pg17` 最后点击 Create 创建数据库。
+进入前面创建的 Project，点击 Create Service 选择 Database，在 Database 界面选择 PostgreSQL ，然后设置数据库名、用户、密码，在 Docker image 中填入 `paradedb/paradedb:latest-pg17` 最后点击 Create 创建数据库。
 
 ![](/blog/assets7006b60baaf62aa0d95cd40456e24afe.webp)