@lobehub/lobehub 2.1.0 → 2.1.2

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` 镜像。