@lobehub/lobehub 2.0.3 → 2.0.4

package/.github/ISSUE_TEMPLATE/1_bug_report.yml

@@ -47,17 +47,6 @@ body:
     validations:
       required: false
 
-  - type: dropdown
-    attributes:
-      label: '🔧 Deployment Mode'
-      multiple: true
-      options:
-        - 'client db (lobe-chat image)'
-        - 'client pgelite db (lobe-chat-pglite image)'
-        - 'server db (lobe-chat-database image)'
-    validations:
-      required: true
-
   - type: input
     attributes:
       label: '📌 Version'

package/CHANGELOG.md

@@ -2,6 +2,31 @@
 
 # Changelog
 
+### [Version 2.0.4](https://github.com/lobehub/lobe-chat/compare/v2.0.3...v2.0.4)
+
+<sup>Released on **2026-01-27**</sup>
+
+#### 🐛 Bug Fixes
+
+- **misc**: Rename docker image and update docs for v2.
+
+<br/>
+
+<details>
+<summary><kbd>Improvements and Fixes</kbd></summary>
+
+#### What's fixed
+
+- **misc**: Rename docker image and update docs for v2, closes [#11911](https://github.com/lobehub/lobe-chat/issues/11911) ([e6cb6cb](https://github.com/lobehub/lobe-chat/commit/e6cb6cb))
+
+</details>
+
+<div align="right">
+
+[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
+
+</div>
+
 ### [Version 2.0.3](https://github.com/lobehub/lobe-chat/compare/v2.0.2...v2.0.3)
 
 <sup>Released on **2026-01-27**</sup>

package/README.md

@@ -479,13 +479,9 @@ Regardless of which database you choose, LobeHub can provide you with an excelle
 
 ### [Support Multi-User Management][docs-feat-auth]
 
-LobeHub supports multi-user management and provides two main user authentication and management solutions to meet different needs:
+LobeHub supports multi-user management and provides flexible user authentication solutions:
 
-- **next-auth**: LobeHub 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.
-
-- [**Clerk**](https://go.clerk.com/exgqLG0): For users who need more advanced user management features, LobeHub 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, LobeHub can provide you with an excellent user experience and powerful functional support.
+- **Better Auth**: LobeHub integrates `Better Auth`, a modern and flexible authentication library that supports multiple authentication methods, including OAuth, email login, credential login, magic links, 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.
 
 <div align="right">
 
@@ -845,12 +841,12 @@ This project is [LobeHub Community License](./LICENSE) licensed.
 [discord-link]: https://discord.gg/AYFPHvv2jT
 [discord-shield]: https://img.shields.io/discord/1127171173982154893?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=flat-square
 [discord-shield-badge]: https://img.shields.io/discord/1127171173982154893?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=for-the-badge
-[docker-pulls-link]: https://hub.docker.com/r/lobehub/lobe-chat-database
-[docker-pulls-shield]: https://img.shields.io/docker/pulls/lobehub/lobe-chat?color=45cc11&labelColor=black&style=flat-square&sort=semver
-[docker-release-link]: https://hub.docker.com/r/lobehub/lobe-chat-database
-[docker-release-shield]: https://img.shields.io/docker/v/lobehub/lobe-chat-database?color=369eff&label=docker&labelColor=black&logo=docker&logoColor=white&style=flat-square&sort=semver
-[docker-size-link]: https://hub.docker.com/r/lobehub/lobe-chat-database
-[docker-size-shield]: https://img.shields.io/docker/image-size/lobehub/lobe-chat-database?color=369eff&labelColor=black&style=flat-square&sort=semver
+[docker-pulls-link]: https://hub.docker.com/r/lobehub/lobehub
+[docker-pulls-shield]: https://img.shields.io/docker/pulls/lobehub/lobehub?color=45cc11&labelColor=black&style=flat-square&sort=semver
+[docker-release-link]: https://hub.docker.com/r/lobehub/lobehub
+[docker-release-shield]: https://img.shields.io/docker/v/lobehub/lobehub?color=369eff&label=docker&labelColor=black&logo=docker&logoColor=white&style=flat-square&sort=semver
+[docker-size-link]: https://hub.docker.com/r/lobehub/lobehub
+[docker-size-shield]: https://img.shields.io/docker/image-size/lobehub/lobehub?color=369eff&labelColor=black&style=flat-square&sort=semver
 [docs]: https://lobehub.com/docs/usage/start
 [docs-dev-guide]: https://lobehub.com/docs/development/start
 [docs-docker]: https://lobehub.com/docs/self-hosting/server-database/docker-compose
@@ -964,5 +960,5 @@ This project is [LobeHub Community License](./LICENSE) licensed.
 [submit-agents-shield]: https://img.shields.io/badge/🤖/🏪_submit_agent-%E2%86%92-c4f042?labelColor=black&style=for-the-badge
 [submit-plugin-link]: https://github.com/lobehub/lobe-chat-plugins
 [submit-plugin-shield]: https://img.shields.io/badge/🧩/🏪_submit_plugin-%E2%86%92-95f3d9?labelColor=black&style=for-the-badge
-[vercel-link]: https://chat-preview.lobehub.com
+[vercel-link]: https://app.lobehub.com
 [vercel-shield]: https://img.shields.io/badge/vercel-online-55b467?labelColor=black&logo=vercel&style=flat-square

package/README.zh-CN.md

@@ -461,8 +461,6 @@ LobeHub 支持多用户管理，提供了灵活的用户认证方案：
 
 - **Better Auth**：LobeHub 集成了 `Better Auth`，一个现代化且灵活的身份验证库，支持多种身份验证方式，包括 OAuth、邮件登录、凭证登录、魔法链接等。通过 `Better Auth`，您可以轻松实现用户的注册、登录、会话管理、社交登录、多因素认证 (MFA) 等功能，确保用户数据的安全性和隐私性。
 
-- **next-auth**：LobeHub 还支持 `next-auth`，一个广泛使用的身份验证库，具有丰富的 OAuth 提供商支持和灵活的会话管理选项。
-
 <div align="right">
 
 [![][back-to-top]](#readme-top)
@@ -855,12 +853,12 @@ This project is [LobeHub Community License](./LICENSE) licensed.
 [discord-link]: https://discord.gg/AYFPHvv2jT
 [discord-shield]: https://img.shields.io/discord/1127171173982154893?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=flat-square
 [discord-shield-badge]: https://img.shields.io/discord/1127171173982154893?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=for-the-badge
-[docker-pulls-link]: https://hub.docker.com/r/lobehub/lobe-chat-database
-[docker-pulls-shield]: https://img.shields.io/docker/pulls/lobehub/lobe-chat?color=45cc11&labelColor=black&style=flat-square&sort=semver
-[docker-release-link]: https://hub.docker.com/r/lobehub/lobe-chat-database
-[docker-release-shield]: https://img.shields.io/docker/v/lobehub/lobe-chat-database?color=369eff&label=docker&labelColor=black&logo=docker&logoColor=white&style=flat-square&sort=semver
-[docker-size-link]: https://hub.docker.com/r/lobehub/lobe-chat-database
-[docker-size-shield]: https://img.shields.io/docker/image-size/lobehub/lobe-chat-database?color=369eff&labelColor=black&style=flat-square&sort=semver
+[docker-pulls-link]: https://hub.docker.com/r/lobehub/lobehub
+[docker-pulls-shield]: https://img.shields.io/docker/pulls/lobehub/lobehub?color=45cc11&labelColor=black&style=flat-square&sort=semver
+[docker-release-link]: https://hub.docker.com/r/lobehub/lobehub
+[docker-release-shield]: https://img.shields.io/docker/v/lobehub/lobehub?color=369eff&label=docker&labelColor=black&logo=docker&logoColor=white&style=flat-square&sort=semver
+[docker-size-link]: https://hub.docker.com/r/lobehub/lobehub
+[docker-size-shield]: https://img.shields.io/docker/image-size/lobehub/lobehub?color=369eff&labelColor=black&style=flat-square&sort=semver
 [docs]: https://lobehub.com/zh/docs/usage/start
 [docs-dev-guide]: https://lobehub.com/docs/development/start
 [docs-docker]: https://lobehub.com/zh/docs/self-hosting/server-database/docker-compose

package/apps/desktop/Development.md

@@ -181,7 +181,7 @@ export default class AuthCtr extends ControllerModule {
 
 2. **桌面端特定认证**：
    - 在桌面应用中使用固定的用户 ID
-   - 支持与 Clerk 和 NextAuth 等认证系统集成
+   - 支持与 Better Auth 认证系统集成
 
 ### 存储模块 (Store)
 

package/changelog/v2.json

@@ -1,4 +1,13 @@
 [
+  {
+    "children": {
+      "fixes": [
+        "Rename docker image and update docs for v2."
+      ]
+    },
+    "date": "2026-01-27",
+    "version": "2.0.4"
+  },
   {
     "children": {
       "fixes": [

package/docker-compose/local/docker-compose.yml

@@ -1,4 +1,4 @@
-name: lobe-chat-database
+name: lobehub
 services:
   network-service:
     image: alpine
@@ -128,7 +128,7 @@ services:
 
   lobe:
     image: lobehub/lobehub
-    container_name: lobe-chat
+    container_name: lobehub
     network_mode: 'service:network-service'
     depends_on:
       postgresql:

package/docker-compose/local/grafana/docker-compose.yml

@@ -1,4 +1,4 @@
-name: lobe-chat-database
+name: lobehub
 services:
   network-service:
     image: alpine
@@ -159,8 +159,8 @@ services:
       - ENDPOINT=127.0.0.1:4317
 
   lobe:
-    image: lobehub/lobe-chat-database
-    container_name: lobe-chat
+    image: lobehub/lobehub
+    container_name: lobehub
     network_mode: 'service:network-service'
     depends_on:
       postgresql:

package/docker-compose/local/logto/docker-compose.yml

@@ -1,4 +1,4 @@
-name: lobe-chat-database
+name: lobehub
 services:
   network-service:
     image: alpine
@@ -79,8 +79,8 @@ services:
     entrypoint: ['sh', '-c', 'npm run cli db seed -- --swe && npm start']
 
   lobe:
-    image: lobehub/lobe-chat-database
-    container_name: lobe-chat
+    image: lobehub/lobehub
+    container_name: lobehub
     network_mode: 'service:network-service'
     depends_on:
       postgresql:
@@ -99,7 +99,6 @@ services:
       - 'AUTH_SSO_PROVIDERS=logto'
       - 'KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ='
       - 'AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg'
-      - 'NEXTAUTH_URL=http://localhost:${LOBE_PORT}/api/auth'
       - 'AUTH_LOGTO_ISSUER=http://localhost:${LOGTO_PORT}/oidc'
       - 'DATABASE_URL=postgresql://postgres:${POSTGRES_PASSWORD}@postgresql:5432/${LOBE_DB_NAME}'
       - 'S3_ENDPOINT=http://localhost:${MINIO_PORT}'

package/docker-compose/local/zitadel/.env.example

@@ -1,5 +1,5 @@
 # Required: LobeChat domain for tRPC calls
-# Ensure this domain is whitelisted in your NextAuth providers and S3 service CORS settings
+# Ensure this domain is whitelisted in your SSO providers and S3 service CORS settings
 APP_URL=http://localhost:3210
 
 # Postgres related environment variables
@@ -8,12 +8,11 @@ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
 # Required: Postgres database connection string
 DATABASE_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/lobechat
 
-# NEXT_AUTH related environment variables
-NEXTAUTH_URL=http://localhost:3210/api/auth
+# Authentication related environment variables
 AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg
 AUTH_SSO_PROVIDERS=zitadel
 # ZiTADEL provider configuration
-# Please refer to：https://lobehub.com/zh/docs/self-hosting/advanced/auth/next-auth/zitadel
+# Please refer to：https://lobehub.com/zh/docs/self-hosting/advanced/auth/providers/zitadel
 AUTH_ZITADEL_ID=285945938244075523
 AUTH_ZITADEL_SECRET=hkbtzHLaCEIeHeFThym14UcydpmQiEB5JtAX08HSqSoJxhAlVVkyovTuNUZ5TNrT
 AUTH_ZITADEL_ISSUER=http://localhost:8080

package/docker-compose/local/zitadel/.env.zh-CN.example

@@ -7,8 +7,7 @@ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
 # Postgres 数据库连接字符串
 DATABASE_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/lobechat
 
-# NEXT_AUTH 相关
-NEXTAUTH_URL=http://localhost:3210/api/auth
+# 鉴权相关
 AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg
 AUTH_SSO_PROVIDERS=zitadel
 # ZiTADEL 鉴权服务提供商部分

package/docker-compose/local/zitadel/docker-compose.yml

@@ -1,4 +1,4 @@
-name: lobe-chat-database
+name: lobehub
 services:
   network-service:
     image: alpine
@@ -60,8 +60,8 @@ services:
         condition: service_healthy
 
   lobe:
-    image: lobehub/lobe-chat-database
-    container_name: lobe-chat
+    image: lobehub/lobehub
+    container_name: lobehub
     network_mode: 'service:network-service'
     depends_on:
       postgresql:

package/docker-compose/production/grafana/docker-compose.yml

@@ -1,4 +1,4 @@
-name: lobe-chat-database
+name: lobehub
 services:
   network-service:
     image: alpine
@@ -157,8 +157,8 @@ services:
       - ENDPOINT=127.0.0.1:4317
 
   lobe:
-    image: lobehub/lobe-chat-database
-    container_name: lobe-chat
+    image: lobehub/lobehub
+    container_name: lobehub
     network_mode: 'service:network-service'
     depends_on:
       postgresql:

package/docker-compose/production/logto/.env.example

@@ -1,5 +1,5 @@
 # Required: LobeChat domain for tRPC calls
-# Ensure this domain is whitelisted in your NextAuth providers and S3 service CORS settings
+# Ensure this domain is whitelisted in your SSO providers and S3 service CORS settings
 APP_URL=https://lobe.example.com/
 
 # Postgres related environment variables
@@ -10,18 +10,16 @@ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
 # If using Docker, you can use the container name as the host
 DATABASE_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/lobe
 
-# NEXT_AUTH related environment variables
-# Supports auth0, Azure AD, GitHub, Authentik, Zitadel, Logto, etc.
-# For supported providers, see: https://lobehub.com/docs/self-hosting/advanced/auth#next-auth
-# If you have ACCESS_CODE, please remove it. We use NEXT_AUTH as the sole authentication source
-# Required: NextAuth secret key. Generate with: openssl rand -base64 32
+# Authentication related environment variables
+# Supports Auth0, Azure AD, GitHub, Authentik, Zitadel, Logto, etc.
+# For supported providers, see: https://lobehub.com/docs/self-hosting/advanced/auth
+# If you have ACCESS_CODE, please remove it. We use Better Auth as the sole authentication source
+# Required: Auth secret key. Generate with: openssl rand -base64 32
 AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg
 # Required: Specify the authentication provider (e.g., Logto)
 AUTH_SSO_PROVIDERS=logto
-# Required: NextAuth URL for callbacks
-NEXTAUTH_URL=https://lobe.example.com/api/auth
 
-# NextAuth providers configuration (example using Logto)
+# SSO providers configuration (example using Logto)
 # For other providers, see: https://lobehub.com/docs/self-hosting/environment-variables/auth
 AUTH_LOGTO_ID=YOUR_LOGTO_ID
 AUTH_LOGTO_SECRET=YOUR_LOGTO_SECRET

package/docker-compose/production/logto/.env.zh-CN.example

@@ -1,5 +1,5 @@
 # 必填，LobeChat 域名，用于 tRPC 调用
-# 请保证此域名在你的 NextAuth 鉴权服务提供商、S3 服务商的 CORS 白名单中
+# 请保证此域名在你的 SSO 鉴权服务提供商、S3 服务商的 CORS 白名单中
 APP_URL=https://lobe.example.com/
 
 # Postgres 相关，也即 DB 必需的环境变量
@@ -9,18 +9,16 @@ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
 # 格式：postgresql://username:password@host:port/dbname，如果你的 pg 实例为 Docker 容器且位于同一 docker-compose 文件中，亦可使用容器名作为 host
 DATABASE_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/lobe
 
-# NEXT_AUTH 相关，也即鉴权服务必需的环境变量
-# 可以使用 auth0、Azure AD、GitHub、Authentik、Zitadel、Logto 等，如有其他接入诉求欢迎提 PR
-# 目前支持的鉴权服务提供商请参考：https://lobehub.com/zh/docs/self-hosting/advanced/auth#next-auth
-# 如果你有 ACCESS_CODE，请务必清空，我们以 NEXT_AUTH 作为唯一鉴权来源
-# 必填，用于 NextAuth 的密钥，可以使用 openssl rand -base64 32 生成
+# 鉴权服务必需的环境变量
+# 可以使用 Auth0、Azure AD、GitHub、Authentik、Zitadel、Logto 等，如有其他接入诉求欢迎提 PR
+# 目前支持的鉴权服务提供商请参考：https://lobehub.com/zh/docs/self-hosting/advanced/auth
+# 如果你有 ACCESS_CODE，请务必清空，我们以 Better Auth 作为唯一鉴权来源
+# 必填，用于鉴权的密钥，可以使用 openssl rand -base64 32 生成
 AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg
 # 必填，指定鉴权服务提供商，这里以 Logto 为例
 AUTH_SSO_PROVIDERS=logto
-# 必填，NextAuth 的 URL，用于 NextAuth 的回调
-NEXTAUTH_URL=https://lobe.example.com/api/auth
 
-# NextAuth 鉴权服务提供商部分，以 Logto 为例
+# SSO 鉴权服务提供商部分，以 Logto 为例
 # 其他鉴权服务提供商所需的环境变量，请参考：https://lobehub.com/zh/docs/self-hosting/environment-variables/auth
 AUTH_LOGTO_ID=YOUR_LOGTO_ID
 AUTH_LOGTO_SECRET=YOUR_LOGTO_SECRET

package/docker-compose/production/logto/docker-compose.yml

@@ -1,4 +1,4 @@
-name: lobe-chat-database
+name: lobehub
 services:
   postgresql:
     image: pgvector/pgvector:pg16
@@ -52,8 +52,8 @@ services:
     entrypoint: ['sh', '-c', 'npm run cli db seed -- --swe && npm start']
 
   lobe:
-    image: lobehub/lobe-chat-database
-    container_name: lobe-chat
+    image: lobehub/lobehub
+    container_name: lobehub
     ports:
       - '3210:3210'
     depends_on:

package/docker-compose/production/zitadel/.env.example

@@ -1,5 +1,5 @@
 # Required: LobeChat domain for tRPC calls
-# Ensure this domain is whitelisted in your NextAuth providers and S3 service CORS settings
+# Ensure this domain is whitelisted in your SSO providers and S3 service CORS settings
 APP_URL=https://lobe.example.com/
 
 # Postgres related environment variables
@@ -10,16 +10,14 @@ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
 # If using Docker, you can use the container name as the host
 DATABASE_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/lobe
 
-# NEXT_AUTH related environment variables
-# Required: NextAuth URL for callbacks
-NEXTAUTH_URL=https://lobe.example.com/api/auth
-# Required: NextAuth secret key. Generate with: openssl rand -base64 32
+# Authentication related environment variables
+# Required: Auth secret key. Generate with: openssl rand -base64 32
 AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg
 # Required: Specify the authentication provider
 AUTH_SSO_PROVIDERS=zitadel
 
 # ZiTADEL provider configuration
-# Please refer to：https://lobehub.com/zh/docs/self-hosting/advanced/auth/next-auth/zitadel
+# Please refer to：https://lobehub.com/zh/docs/self-hosting/advanced/auth/providers/zitadel
 AUTH_ZITADEL_ID=285934220675723622
 AUTH_ZITADEL_SECRET=pe7Nh3lopXkZkfqh5YEDYI2xsbIz08eZKqInOUZxssd3refRia518Apbv3DZ
 AUTH_ZITADEL_ISSUER=https://zitadel.example.com

package/docker-compose/production/zitadel/.env.zh-CN.example

@@ -1,5 +1,5 @@
 # 必填，LobeChat 域名，用于 tRPC 调用
-# 请保证此域名在你的 NextAuth 鉴权服务提供商、S3 服务商的 CORS 白名单中
+# 请保证此域名在你的 SSO 鉴权服务提供商、S3 服务商的 CORS 白名单中
 APP_URL=https://lobe.example.com/
 
 # Postgres 相关，也即 DB 必需的环境变量
@@ -9,10 +9,8 @@ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
 # 格式：postgresql://username:password@host:port/dbname，如果你的 pg 实例为 Docker 容器且位于同一 docker-compose 文件中，亦可使用容器名作为 host
 DATABASE_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/lobe
 
-# NEXT_AUTH 相关，也即鉴权服务必需的环境变量
-# 必填，NextAuth 的 URL，用于 NextAuth 的回调
-NEXTAUTH_URL=https://lobe.example.com/api/auth
-# 必填，用于 NextAuth 的密钥，可以使用 openssl rand -base64 32 生成
+# 鉴权服务必需的环境变量
+# 必填，用于鉴权的密钥，可以使用 openssl rand -base64 32 生成
 AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg
 # 必填，指定鉴权服务提供商
 AUTH_SSO_PROVIDERS=zitadel

package/docker-compose/production/zitadel/docker-compose.yml

@@ -1,4 +1,4 @@
-name: lobe-chat-database
+name: lobehub
 services:
   postgresql:
     image: pgvector/pgvector:pg16
@@ -50,8 +50,8 @@ services:
         condition: service_healthy
 
   lobe:
-    image: lobehub/lobe-chat-database
-    container_name: lobe-chat
+    image: lobehub/lobehub
+    container_name: lobehub
     ports:
       - '3210:3210'
     depends_on:

package/docs/development/basic/folder-structure.mdx

@@ -59,8 +59,7 @@ app
 ├── [variants]/                   # Platform and device variants
 │   ├── (auth)/                   # Authentication pages
 │   │   ├── login/
-│   │   ├── signup/
-│   │   └── next-auth/
+│   │   └── signup/
 │   ├── (main)/                   # Main application routes
 │   │   ├── (mobile)/             # Mobile-specific routes
 │   │   │   └── me/               # Mobile profile pages

package/docs/development/basic/folder-structure.zh-CN.mdx

@@ -57,8 +57,7 @@ app
 ├── [variants]/                   # 平台和设备变体
 │   ├── (auth)/                   # 身份验证页面
 │   │   ├── login/
-│   │   ├── signup/
-│   │   └── next-auth/
+│   │   └── signup/
 │   ├── (main)/                   # 主应用路由
 │   │   ├── (mobile)/             # 移动端专用路由
 │   │   │   └── me/               # 移动端个人资料页面

package/docs/self-hosting/advanced/auth/legacy.mdx

@@ -44,7 +44,7 @@ Before using NextAuth, please set the following variables in LobeChat's environm
 
 | Environment Variable             | Type     | Description                                                                                                                                                                                                                                |
 | -------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `NEXT_PUBLIC_ENABLE_NEXT_AUTH`   | Required | This is used to enable the NextAuth service. Set it to `1` to enable it; changing this setting requires recompiling the application. Users deploying with the `lobehub/lobe-chat-database` image have this configuration added by default. |
+| `NEXT_PUBLIC_ENABLE_NEXT_AUTH`   | Required | This is used to enable the NextAuth service. Set it to `1` to enable it; changing this setting requires recompiling the application. Users deploying with the `lobehub/lobehub` image have this configuration added by default. |
 | `AUTH_SECRET`                    | Required | The key used to encrypt Auth.js session tokens. You can use the following command: `openssl rand -base64 32`, or visit `https://generate-secret.vercel.app/32` to generate the key.                                                        |
 | `AUTH_URL`                       | Required | This URL specifies the callback address for Auth.js when performing OAuth verification. Set this only if the default generated redirect address is incorrect. `https://example.com/api/auth`                                               |
 | `NEXT_AUTH_SSO_PROVIDERS`        | Optional | This environment variable is used to enable multiple identity verification sources simultaneously, separated by commas, for example, `auth0,microsoft-entra-id,authentik`.                                                                 |

package/docs/self-hosting/advanced/auth/legacy.zh-CN.mdx

@@ -42,7 +42,7 @@ LobeChat 与 Clerk 做了深度集成，能够为用户提供安全、便捷的
 
 | 环境变量                             | 类型 | 描述                                                                                                           |
 | -------------------------------- | -- | ------------------------------------------------------------------------------------------------------------ |
-| `NEXT_PUBLIC_ENABLE_NEXT_AUTH`   | 必选 | 用于启用 NextAuth 服务，设置为 `1` 以启用，更改此项需要重新编译应用。使用 `lobehub/lobe-chat-database` 镜像部署的用户已经默认添加了该项配置。                |
+| `NEXT_PUBLIC_ENABLE_NEXT_AUTH`   | 必选 | 用于启用 NextAuth 服务，设置为 `1` 以启用，更改此项需要重新编译应用。使用 `lobehub/lobehub` 镜像部署的用户已经默认添加了该项配置。                |
 | `NEXT_AUTH_SECRET`               | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令： `openssl rand -base64 32`，或者访问 `https://generate-secret.vercel.app/32` 生成秘钥。 |
 | `AUTH_URL`                       | 必选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth`                  |
 | `NEXT_AUTH_SSO_PROVIDERS`        | 可选 | 该环境变量用于同时启用多个身份验证源，以逗号 `,` 分割，例如 `auth0,microsoft-entra-id,authentik`。                                       |

package/docs/self-hosting/advanced/auth/nextauth-to-betterauth.mdx

@@ -351,6 +351,10 @@ When configuring SSO connections (e.g., GitHub in Auth0), make sure to enable **
 
 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.
+</Callout>
+
 Solution:
 
 1. First configure the Webhook in LobeChat to sync user data from the identity provider:

package/docs/self-hosting/advanced/auth/nextauth-to-betterauth.zh-CN.mdx

@@ -345,6 +345,10 @@ npx tsx scripts/nextauth-to-betterauth/verify.ts
 
 对于 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) 版本。后续官方计划提供用户端自助迁移功能，届时没有邮箱的用户登录时会被重定向到绑定邮箱页面。
+</Callout>
+
 解决方案：
 
 1. 先在 LobeChat 中配置身份提供商的 Webhook 以同步用户数据：

package/docs/self-hosting/advanced/auth/providers/casdoor.mdx

@@ -58,6 +58,14 @@ tags:
 
   Configure Casdoor [Webhook](https://www.casdoor.org/docs/webhooks/overview#setting-up-a-webhook) to sync user data updates to LobeChat.
 
+  **Synced data fields**:
+
+  - Avatar (`avatar`)
+  - Email (`email`)
+  - Display name (`displayName`)
+
+  **Configuration steps**:
+
   1. Go to **Admin Tools** -> **Webhooks** and create a Webhook
   2. Fill in the following fields:
      - URL: `https://your-domain.com/api/webhooks/casdoor`

package/docs/self-hosting/advanced/auth/providers/casdoor.zh-CN.mdx

@@ -56,6 +56,14 @@ tags:
 
   配置 Casdoor 的 [Webhook](https://www.casdoor.org/docs/webhooks/overview#setting-up-a-webhook) 以便在用户信息更新时同步到 LobeChat。
 
+  **同步的数据字段**：
+
+  - 头像 (`avatar`)
+  - 邮箱 (`email`)
+  - 显示名称 (`displayName`)
+
+  **配置步骤**：
+
   1. 前往 `管理工具` -> `Webhooks`，创建一个 Webhook
   2. 填写以下字段：
      - 链接：`https://your-domain.com/api/webhooks/casdoor`

package/docs/self-hosting/advanced/auth.mdx

@@ -152,7 +152,19 @@ Send emails via SMTP protocol, suitable for users with existing email services.
 
 ### Common Configuration
 
-Before using NextAuth, please set the following variables in LobeHub's environment variables:
+Before using Better Auth, please set the following variables in LobeHub's environment variables:
+
+## Email Verification
+
+Enable email verification to ensure users own the email addresses they register with (off by default):
+
+| Environment Variable      | Type     | Description                                                 |
+| ------------------------- | -------- | ----------------------------------------------------------- |
+| `AUTH_EMAIL_VERIFICATION` | Optional | Set to `1` to require email verification after registration |
+
+<Callout type={'info'}>
+  Email verification requires a working email service (SMTP or Resend) configured above. When enabled, users must verify their email address before they can sign in.
+</Callout>
 
 ## Magic Link (Passwordless) Login
 
@@ -193,6 +205,17 @@ Set the `AUTH_SSO_PROVIDERS` environment variable with a comma-separated list, e
 
 The current authentication system requires email. Please configure a valid email address for users in Casdoor. Using a real, valid email is strongly recommended, otherwise features like password reset and magic link login will not work.
 
+### Can I use fake or random email addresses?
+
+**Strongly not recommended.** You should always use valid, real email addresses. Using fake emails will cause the following issues:
+
+- Password reset functionality will not work
+- Magic link login will not work
+- Email verification will fail
+- You may lose access to your account if you forget your password
+
+This applies to all authentication methods, including SSO providers like Casdoor. Always ensure users have valid email addresses configured.
+
 ### How do I restrict registration to specific emails or domains?
 
 Set the `AUTH_ALLOWED_EMAILS` environment variable with a comma-separated list of allowed emails or domains. For example:
@@ -200,6 +223,10 @@ 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`
 
+<Callout type={'info'}>
+  Note: `AUTH_ALLOWED_EMAILS` only restricts which email addresses can register, but does not verify email ownership. If you need to ensure users actually own the email address they register with, set `AUTH_EMAIL_VERIFICATION=1` to require email verification. This requires configuring an email service (SMTP).
+</Callout>
+
 ## Additional Features
 
 ### Webhook Support

package/docs/self-hosting/advanced/auth.zh-CN.mdx

@@ -152,7 +152,19 @@ LobeHub 与 Clerk 做了深度集成，能够为用户提供一个更加安全
 
 ### 通用配置
 
-在使用 NextAuth 之前，请先在 LobeHub 的环境变量中设置以下变量：
+在使用 Better Auth 之前，请先在 LobeHub 的环境变量中设置以下变量：
+
+## 邮箱验证
+
+启用邮箱验证以确保用户拥有其注册的邮箱地址（默认关闭）：
+
+| 环境变量                      | 类型 | 描述                   |
+| ------------------------- | -- | -------------------- |
+| `AUTH_EMAIL_VERIFICATION` | 可选 | 设置为 `1` 以要求注册后进行邮箱验证 |
+
+<Callout type={'info'}>
+  邮箱验证需要上方已配置好的邮件服务（SMTP 或 Resend）。启用后，用户必须验证其邮箱地址才能登录。
+</Callout>
 
 ## 魔法链接（免密）登录
 
@@ -194,6 +206,17 @@ Better Auth 支持内置提供商（Google、GitHub、Microsoft、Apple、AWS Co
 当前身份验证方案强依赖 email。请在 Casdoor 中为用户配置有效的 email 地址。
 强烈建议使用真实有效的邮箱，否则密码重置、魔法链接登录等功能将无法使用。
 
+### 邮箱可以随便乱填吗？
+
+**强烈不建议**。请务必填写真实有效的邮箱地址。使用虚假邮箱会导致以下问题：
+
+- 密码重置功能无法使用
+- 魔法链接登录无法使用
+- 邮箱验证无法通过
+- 忘记密码时可能无法找回账户
+
+这适用于所有身份验证方式，包括 Casdoor 等 SSO 提供商。请确保用户配置了有效的邮箱地址。
+
 ### 如何限制只允许特定邮箱或域名注册？
 
 设置 `AUTH_ALLOWED_EMAILS` 环境变量，支持完整邮箱地址或域名，以逗号分隔。例如：
@@ -201,6 +224,10 @@ 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`
 
+<Callout type={'info'}>
+  注意：`AUTH_ALLOWED_EMAILS` 仅限制哪些邮箱地址可以注册，但不会验证邮箱所有权。如果需要确保用户确实拥有其注册的邮箱地址，请设置 `AUTH_EMAIL_VERIFICATION=1` 以启用邮箱验证。这需要配置邮件服务（SMTP）。
+</Callout>
+
 ### Webhook 支持
 
 允许 LobeHub 在身份提供商中用户信息更新时接收通知。支持的提供商包括 Casdoor 和 Logto。请参考具体提供商文档进行配置。
@@ -211,4 +238,4 @@ Better Auth 支持内置提供商（Google、GitHub、Microsoft、Apple、AWS Co
 
 ## 其他 SSO 提供商
 
-请参考 [NextAuth.js](https://next-auth.js.org/providers) 文档，欢迎提交 Pull Request。
+请参考 [Auth.js](https://authjs.dev/getting-started/authentication/oauth) 文档，欢迎提交 Pull Request。