@lobehub/lobehub 2.1.2 → 2.1.4

package/.env.example

@@ -1,6 +1,3 @@
-# add a access code to lock your lobe-chat application, you can set a long password to avoid leaking. If this value contains a comma, it is a password array.
-# ACCESS_CODE=lobe66
-
 # Specify your API Key selection method, currently supporting `random` and `turn`.
 # API_KEY_SELECT_MODE=random
 
@@ -265,9 +262,6 @@ OPENAI_API_KEY=sk-xxxxxxxxx
 # Bucket request endpoint
 # S3_ENDPOINT=https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxx.r2.cloudflarestorage.com
 
-# Public access domain for the bucket
-# S3_PUBLIC_DOMAIN=https://s3-for-lobechat.your-domain.com
-
 # Bucket region, such as us-west-1, generally not needed to add
 # but some service providers may require configuration
 # S3_REGION=us-west-1
@@ -295,6 +289,10 @@ OPENAI_API_KEY=sk-xxxxxxxxx
 # Leave empty to allow all emails
 # AUTH_ALLOWED_EMAILS=example.com,admin@other.com
 
+# Disable email/password authentication (SSO-only mode)
+# Set to '1' to disable email/password sign-in and registration, only allowing SSO login
+# AUTH_DISABLE_EMAIL_PASSWORD=0
+
 # Google OAuth Configuration (for Better-Auth)
 # Get credentials from: https://console.cloud.google.com/apis/credentials
 # Authorized redirect URIs:

package/.env.example.development

@@ -85,9 +85,6 @@ S3_ENDPOINT=http://localhost:${MINIO_PORT}
 # S3 bucket name for storing files
 S3_BUCKET=${MINIO_LOBE_BUCKET}
 
-# Public domain for S3 file access
-S3_PUBLIC_DOMAIN=http://localhost:${MINIO_PORT}
-
 # Enable path-style S3 requests (required for MinIO)
 S3_ENABLE_PATH_STYLE=1
 

package/.github/workflows/release-desktop-stable.yml

@@ -148,7 +148,7 @@ jobs:
           # 使用 GitHub Hosted Runner
           if [[ "${{ github.event_name }}" != "workflow_dispatch" ]] || [[ "${{ inputs.build_mac }}" == "true" ]]; then
             echo "Using GitHub-Hosted Runner for macOS ARM64"
-            arm_entry='{"os": "macos-14", "name": "macos-arm64"}'
+            arm_entry='{"os": "macos-15", "name": "macos-arm64"}'
             static_matrix=$(echo "$static_matrix" | jq -c --argjson entry "$arm_entry" '. + [$entry]')
           fi
 

package/CHANGELOG.md

@@ -2,6 +2,65 @@
 
 # Changelog
 
+### [Version 2.1.4](https://github.com/lobehub/lobe-chat/compare/v2.1.3...v2.1.4)
+
+<sup>Released on **2026-01-31**</sup>
+
+#### 🐛 Bug Fixes
+
+- **stream**: Update event handling to use 'text' instead of 'content_part' in gemini 2.5 models.
+
+#### 💄 Styles
+
+- **misc**: Update i18n, Update Kimi K2.5 & Qwen3 Max Thinking models.
+
+<br/>
+
+<details>
+<summary><kbd>Improvements and Fixes</kbd></summary>
+
+#### What's fixed
+
+- **stream**: Update event handling to use 'text' instead of 'content_part' in gemini 2.5 models, closes [#11235](https://github.com/lobehub/lobe-chat/issues/11235) ([a76a630](https://github.com/lobehub/lobe-chat/commit/a76a630))
+
+#### Styles
+
+- **misc**: Update i18n, closes [#11920](https://github.com/lobehub/lobe-chat/issues/11920) ([1a590a0](https://github.com/lobehub/lobe-chat/commit/1a590a0))
+- **misc**: Update Kimi K2.5 & Qwen3 Max Thinking models, closes [#11925](https://github.com/lobehub/lobe-chat/issues/11925) ([6f9e010](https://github.com/lobehub/lobe-chat/commit/6f9e010))
+
+</details>
+
+<div align="right">
+
+[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
+
+</div>
+
+### [Version 2.1.3](https://github.com/lobehub/lobe-chat/compare/v2.1.2...v2.1.3)
+
+<sup>Released on **2026-01-31**</sup>
+
+#### 🐛 Bug Fixes
+
+- **auth**: Add AUTH_DISABLE_EMAIL_PASSWORD env to enable SSO-only mode.
+
+<br/>
+
+<details>
+<summary><kbd>Improvements and Fixes</kbd></summary>
+
+#### What's fixed
+
+- **auth**: Add AUTH_DISABLE_EMAIL_PASSWORD env to enable SSO-only mode, closes [#12009](https://github.com/lobehub/lobe-chat/issues/12009) ([f3210a3](https://github.com/lobehub/lobe-chat/commit/f3210a3))
+
+</details>
+
+<div align="right">
+
+[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
+
+</div>
+
 ### [Version 2.1.2](https://github.com/lobehub/lobe-chat/compare/v2.1.1...v2.1.2)
 
 <sup>Released on **2026-01-30**</sup>

package/Dockerfile

@@ -158,14 +158,12 @@ ENV HOSTNAME="0.0.0.0" \
     PORT="3210"
 
 # General Variables
-ENV ACCESS_CODE="" \
-    APP_URL="" \
+ENV APP_URL="" \
     API_KEY_SELECT_MODE="" \
     DEFAULT_AGENT_CONFIG="" \
     SYSTEM_AGENT="" \
     FEATURE_FLAGS="" \
-    PROXY_URL="" \
-    ENABLE_AUTH_PROTECTION=""
+    PROXY_URL=""
 
 # Database
 ENV KEY_VAULTS_SECRET="" \
@@ -176,6 +174,10 @@ ENV KEY_VAULTS_SECRET="" \
 ENV AUTH_SECRET="" \
     AUTH_SSO_PROVIDERS="" \
     AUTH_ALLOWED_EMAILS="" \
+    AUTH_TRUSTED_ORIGINS="" \
+    AUTH_DISABLE_EMAIL_PASSWORD="" \
+    AUTH_EMAIL_VERIFICATION="" \
+    AUTH_ENABLE_MAGIC_LINK="" \
     # Google
     AUTH_GOOGLE_ID="" \
     AUTH_GOOGLE_SECRET="" \

package/README.md

@@ -581,7 +581,7 @@ LobeHub provides Self-Hosted Version with Vercel, Alibaba Cloud, and [Docker Ima
 "If you want to deploy this service yourself on Vercel, Zeabur or Alibaba Cloud, you can follow these steps:
 
 - Prepare your [OpenAI API Key](https://platform.openai.com/account/api-keys).
-- Click the button below to start deployment: Log in directly with your GitHub account, and remember to fill in the `OPENAI_API_KEY`(required) and `ACCESS_CODE` (recommended) on the environment variable section.
+- Click the button below to start deployment: Log in directly with your GitHub account, and remember to fill in the `OPENAI_API_KEY`(required) on the environment variable section.
 - After deployment, you can start using it.
 - Bind a custom domain (optional): The DNS of the domain assigned by Vercel is polluted in some areas; binding a custom domain can connect directly.
 
@@ -647,7 +647,6 @@ This project provides some additional configuration items set with environment v
 | -------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
 | `OPENAI_API_KEY`     | Yes      | This is the API key you apply on the OpenAI account page                                                                                                                  | `sk-xxxxxx...xxxxxx`                                                                                                 |
 | `OPENAI_PROXY_URL`   | No       | If you manually configure the OpenAI interface proxy, you can use this configuration item to override the default OpenAI API request base URL                             | `https://api.chatanywhere.cn` or `https://aihubmix.com/v1` <br/>The default value is<br/>`https://api.openai.com/v1` |
-| `ACCESS_CODE`        | No       | Add a password to access this service; you can set a long password to avoid leaking. If this value contains a comma, it is a password array.                              | `awCTe)re_r74` or `rtrt_ewee3@09!` or `code1,code2,code3`                                                            |
 | `OPENAI_MODEL_LIST`  | No       | Used to control the model list. Use `+` to add a model, `-` to hide a model, and `model_name=display_name` to customize the display name of a model, separated by commas. | `qwen-7b-chat,+glm-6b,-gpt-3.5-turbo`                                                                                |
 
 > \[!NOTE]
@@ -829,7 +828,7 @@ This project is [LobeHub Community License](./LICENSE) licensed.
 [codespaces-link]: https://codespaces.new/lobehub/lobe-chat
 [codespaces-shield]: https://github.com/codespaces/badge.svg
 [deploy-button-image]: https://vercel.com/button
-[deploy-link]: https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat&env=OPENAI_API_KEY,ACCESS_CODE&envDescription=Find%20your%20OpenAI%20API%20Key%20by%20click%20the%20right%20Learn%20More%20button.%20%7C%20Access%20Code%20can%20protect%20your%20website&envLink=https%3A%2F%2Fplatform.openai.com%2Faccount%2Fapi-keys&project-name=lobe-chat&repository-name=lobe-chat
+[deploy-link]: https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat&env=OPENAI_API_KEY&envDescription=Find%20your%20OpenAI%20API%20Key%20by%20click%20the%20right%20Learn%20More%20button.&envLink=https%3A%2F%2Fplatform.openai.com%2Faccount%2Fapi-keys&project-name=lobe-chat&repository-name=lobe-chat
 [deploy-on-alibaba-cloud-button-image]: https://service-info-public.oss-cn-hangzhou.aliyuncs.com/computenest-en.svg
 [deploy-on-alibaba-cloud-link]: https://computenest.console.aliyun.com/service/instance/create/default?type=user&ServiceName=LobeHub%E7%A4%BE%E5%8C%BA%E7%89%88
 [deploy-on-repocloud-button-image]: https://d16t0pc4846x52.cloudfront.net/deploylobe.svg

package/README.zh-CN.md

@@ -555,7 +555,7 @@ LobeHub 提供了 Vercel 的 自托管版本 和 [Docker 镜像][docker-release-
 如果想在 Vercel 、 Zeabur 或 阿里云 上部署该服务，可以按照以下步骤进行操作：
 
 - 准备好你的 [OpenAI API Key](https://platform.openai.com/account/api-keys) 。
-- 点击下方按钮开始部署： 直接使用 GitHub 账号登录即可，记得在环境变量页填入 `OPENAI_API_KEY` （必填） and `ACCESS_CODE`（推荐）；
+- 点击下方按钮开始部署： 直接使用 GitHub 账号登录即可，记得在环境变量页填入 `OPENAI_API_KEY` （必填）；
 - 部署完毕后，即可开始使用；
 - 绑定自定义域名（可选）：Vercel 分配的域名 DNS 在某些区域被污染了，绑定自定义域名即可直连。目前 Zeabur 提供的域名还未被污染，大多数地区都可以直连。
 
@@ -621,7 +621,6 @@ docker compose up -d
 | ------------------- | ---- | ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
 | `OPENAI_API_KEY`    | 必选 | 这是你在 OpenAI 账户页面申请的 API 密钥                                                                                       | `sk-xxxxxx...xxxxxx`                                                                                   |
 | `OPENAI_PROXY_URL`  | 可选 | 如果你手动配置了 OpenAI 接口代理，可以使用此配置项来覆盖默认的 OpenAI API 请求基础 URL                                        | `https://api.chatanywhere.cn` 或 `https://aihubmix.com/v1`<br/>默认值:<br/>`https://api.openai.com/v1` |
-| `ACCESS_CODE`       | 可选 | 添加访问此服务的密码，你可以设置一个长密码以防被爆破，该值用逗号分隔时为密码数组                                              | `awCTe)re_r74` or `rtrt_ewee3@09!` or `code1,code2,code3`                                              |
 | `OPENAI_MODEL_LIST` | 可选 | 用来控制模型列表，使用 `+` 增加一个模型，使用 `-` 来隐藏一个模型，使用 `模型名=展示名` 来自定义模型的展示名，用英文逗号隔开。 | `qwen-7b-chat,+glm-6b,-gpt-3.5-turbo`                                                                  |
 
 > \[!NOTE]
@@ -843,7 +842,7 @@ This project is [LobeHub Community License](./LICENSE) licensed.
 [codespaces-link]: https://codespaces.new/lobehub/lobe-chat
 [codespaces-shield]: https://github.com/codespaces/badge.svg
 [deploy-button-image]: https://vercel.com/button
-[deploy-link]: https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat&env=OPENAI_API_KEY,ACCESS_CODE&envDescription=Find%20your%20OpenAI%20API%20Key%20by%20click%20the%20right%20Learn%20More%20button.%20%7C%20Access%20Code%20can%20protect%20your%20website&envLink=https%3A%2F%2Fplatform.openai.com%2Faccount%2Fapi-keys&project-name=lobe-chat&repository-name=lobe-chat
+[deploy-link]: https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat&env=OPENAI_API_KEY&envDescription=Find%20your%20OpenAI%20API%20Key%20by%20click%20the%20right%20Learn%20More%20button.&envLink=https%3A%2F%2Fplatform.openai.com%2Faccount%2Fapi-keys&project-name=lobe-chat&repository-name=lobe-chat
 [deploy-on-alibaba-cloud-button-image]: https://service-info-public.oss-cn-hangzhou.aliyuncs.com/computenest-en.svg
 [deploy-on-alibaba-cloud-link]: https://computenest.console.aliyun.com/service/instance/create/default?type=user&ServiceName=LobeHub%E7%A4%BE%E5%8C%BA%E7%89%88
 [deploy-on-sealos-button-image]: https://raw.githubusercontent.com/labring-actions/templates/main/Deploy-on-Sealos.svg

package/changelog/v2.json

@@ -1,4 +1,18 @@
 [
+  {
+    "children": {
+      "improvements": [
+        "Update i18n, Update Kimi K2.5 & Qwen3 Max Thinking models."
+      ]
+    },
+    "date": "2026-01-31",
+    "version": "2.1.4"
+  },
+  {
+    "children": {},
+    "date": "2026-01-31",
+    "version": "2.1.3"
+  },
   {
     "children": {
       "fixes": [

package/docker-compose/deploy/.env.example

@@ -7,6 +7,9 @@
 # Leave empty to allow all users to register
 # AUTH_ALLOWED_EMAILS=user1@example.com,user2@example.com
 
+# Disable user registration (SSO-only mode)
+# When set to 1, users cannot register via email/password, only SSO login is allowed
+# AUTH_DISABLE_EMAIL_PASSWORD=1
 
 # ===========================
 # ====== Preset config ======
@@ -28,7 +31,6 @@ RUSTFS_ACCESS_KEY=admin
 RUSTFS_SECRET_KEY=YOUR_RUSTFS_PASSWORD
 
 # Configure the bucket information of RUSTFS
-S3_PUBLIC_DOMAIN=http://localhost:9000
 S3_ENDPOINT=http://localhost:9000
 RUSTFS_LOBE_BUCKET=lobe
 

package/docker-compose/deploy/.env.zh-CN.example

@@ -7,6 +7,10 @@
 # 留空则允许所有用户注册登录
 # AUTH_ALLOWED_EMAILS=user1@example.com,user2@example.com
 
+# 禁用用户注册（仅允许 SSO 登录）
+# 设置为 1 后，用户无法通过邮箱密码注册，只能通过 SSO 登录
+# AUTH_DISABLE_EMAIL_PASSWORD=1
+
 # ===================
 # ===== 预设配置 =====
 # ===================
@@ -24,7 +28,6 @@ RUSTFS_ACCESS_KEY=admin
 RUSTFS_SECRET_KEY=YOUR_RUSTFS_PASSWORD
 
 # 在下方配置 rustfs 中添加的桶
-S3_PUBLIC_DOMAIN=http://localhost:9000
 S3_ENDPOINT=http://localhost:9000
 RUSTFS_LOBE_BUCKET=lobe
 

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

@@ -37,7 +37,6 @@ RUSTFS_ACCESS_KEY=admin
 RUSTFS_SECRET_KEY=YOUR_RUSTFS_PASSWORD
 
 # Configure the bucket information of RUSTFS
-S3_PUBLIC_DOMAIN=http://localhost:9000
 S3_ENDPOINT=http://localhost:9000
 RUSTFS_LOBE_BUCKET=lobe
 

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

@@ -34,7 +34,6 @@ RUSTFS_ACCESS_KEY=admin
 RUSTFS_SECRET_KEY=YOUR_RUSTFS_PASSWORD
 
 # 在下方配置 rustfs 中添加的桶
-S3_PUBLIC_DOMAIN=http://localhost:9000
 S3_ENDPOINT=http://localhost:9000
 RUSTFS_LOBE_BUCKET=lobe
 

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

@@ -34,7 +34,6 @@ MINIO_ROOT_USER=admin
 MINIO_ROOT_PASSWORD=YOUR_MINIO_PASSWORD
 
 # Configure the bucket information of MinIO
-S3_PUBLIC_DOMAIN=http://localhost:9000
 S3_ENDPOINT=http://localhost:9000
 MINIO_LOBE_BUCKET=lobe
 

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

@@ -34,7 +34,6 @@ MINIO_ROOT_USER=admin
 MINIO_ROOT_PASSWORD=YOUR_MINIO_PASSWORD
 
 # 在下方配置 minio 中添加的桶
-S3_PUBLIC_DOMAIN=http://localhost:9000
 S3_ENDPOINT=http://localhost:9000
 MINIO_LOBE_BUCKET=lobe
 

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

@@ -103,7 +103,6 @@ services:
       - 'DATABASE_URL=postgresql://postgres:${POSTGRES_PASSWORD}@postgresql:5432/${LOBE_DB_NAME}'
       - 'S3_ENDPOINT=http://localhost:${MINIO_PORT}'
       - 'S3_BUCKET=${MINIO_LOBE_BUCKET}'
-      - 'S3_PUBLIC_DOMAIN=http://localhost:${MINIO_PORT}'
       - 'S3_ENABLE_PATH_STYLE=1'
       - 'REDIS_URL=redis://redis:6379'
       - 'REDIS_PREFIX=lobechat'

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

@@ -21,8 +21,7 @@ AUTH_ZITADEL_ISSUER=http://localhost:8080
 S3_ACCESS_KEY_ID=        
 S3_SECRET_ACCESS_KEY=
 S3_ENDPOINT=http://localhost:9000
-S3_BUCKET=lobe 
-S3_PUBLIC_DOMAIN=http://localhost:9000
+S3_BUCKET=lobe
 S3_ENABLE_PATH_STYLE=1
 LLM_VISION_IMAGE_USE_BASE64=1
 

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

@@ -20,8 +20,7 @@ AUTH_ZITADEL_ISSUER=http://localhost:8080
 S3_ACCESS_KEY_ID=        
 S3_SECRET_ACCESS_KEY=
 S3_ENDPOINT=http://localhost:9000
-S3_BUCKET=lobe 
-S3_PUBLIC_DOMAIN=http://localhost:9000
+S3_BUCKET=lobe
 S3_ENABLE_PATH_STYLE=1
 LLM_VISION_IMAGE_USE_BASE64=1
 

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

@@ -34,7 +34,6 @@ MINIO_ROOT_USER=admin
 MINIO_ROOT_PASSWORD=YOUR_MINIO_PASSWORD
 
 # Configure the bucket information of MinIO
-S3_PUBLIC_DOMAIN=http://localhost:9000
 S3_ENDPOINT=http://localhost:9000
 MINIO_LOBE_BUCKET=lobe
 

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

@@ -34,7 +34,6 @@ MINIO_ROOT_USER=admin
 MINIO_ROOT_PASSWORD=YOUR_MINIO_PASSWORD
 
 # 在下方配置 minio 中添加的桶
-S3_PUBLIC_DOMAIN=http://localhost:9000
 S3_ENDPOINT=http://localhost:9000
 MINIO_LOBE_BUCKET=lobe
 

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

@@ -38,8 +38,6 @@ S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY
 S3_ENDPOINT=https://lobe-s3-api.example.com
 # Required: S3 Bucket (invalid until manually created in MinIO UI)
 S3_BUCKET=lobe
-# Required: S3 Public Domain for client access to unstructured data
-S3_PUBLIC_DOMAIN=https://lobe-s3-api.example.com
 # Optional: S3 Enable Path Style
 # Use 0 for mainstream S3 cloud providers; use 1 for self-hosted MinIO
 # See: https://lobehub.com/docs/self-hosting/advanced/s3#s-3-enable-path-style

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

@@ -38,8 +38,6 @@ S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY
 S3_ENDPOINT=https://lobe-s3-api.example.com
 # 必填，S3 的 Bucket，直到在 MinIO UI 中手动创建之前都是无效的
 S3_BUCKET=lobe
-# 必填，S3 的 Public Domain，用于客户端通过公开连接访问非结构化数据
-S3_PUBLIC_DOMAIN=https://lobe-s3-api.example.com
 # 选填，S3 的 Enable Path Style
 # 对于主流 S3 Cloud 服务商，一般填 0 即可；对于自部署的 MinIO，请填 1
 # 请参考：https://lobehub.com/zh/docs/self-hosting/advanced/s3#s-3-enable-path-style

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

@@ -35,8 +35,6 @@ S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY
 S3_ENDPOINT=https://lobe-s3-api.example.com
 # Required: S3 Bucket (invalid until manually created in MinIO UI)
 S3_BUCKET=lobe
-# Required: S3 Public Domain for client access to unstructured data
-S3_PUBLIC_DOMAIN=https://lobe-s3-api.example.com
 # Optional: S3 Enable Path Style
 # Use 0 for mainstream S3 cloud providers; use 1 for self-hosted MinIO
 # See: https://lobehub.com/docs/self-hosting/advanced/s3#s-3-enable-path-style

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

@@ -31,8 +31,6 @@ S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY
 S3_ENDPOINT=https://lobe-s3-api.example.com
 # 必填，S3 的 Bucket，直到在 MinIO UI 中手动创建之前都是无效的
 S3_BUCKET=lobe
-# 必填，S3 的 Public Domain，用于客户端通过公开连接访问非结构化数据
-S3_PUBLIC_DOMAIN=https://lobe-s3-api.example.com
 # 选填，S3 的 Enable Path Style
 # 对于主流 S3 Cloud 服务商，一般填 0 即可；对于自部署的 MinIO，请填 1
 # 请参考：https://lobehub.com/zh/docs/self-hosting/advanced/s3#s-3-enable-path-style

package/docker-compose/setup.sh

@@ -230,6 +230,20 @@ show_message() {
                 ;;
             esac
         ;;
+        tips_disable_registration)
+            case $LANGUAGE in
+                zh_CN)
+                    echo "如需限制用户注册，可在 .env 中配置："
+                    echo "  - 使用 SSO 登录时，设置 AUTH_DISABLE_EMAIL_PASSWORD=1 可禁用邮箱密码注册"
+                    echo "  - 使用邮箱密码登录时，设置 AUTH_ALLOWED_EMAILS=user1@example.com,user2@example.com 可限制允许登录的邮箱"
+                ;;
+                *)
+                    echo "To restrict user registration, configure in .env:"
+                    echo "  - For SSO login: set AUTH_DISABLE_EMAIL_PASSWORD=1 to disable email/password registration"
+                    echo "  - For email/password login: set AUTH_ALLOWED_EMAILS=user1@example.com,user2@example.com to allow specific emails"
+                ;;
+            esac
+        ;;
         tips_show_documentation)
             case $LANGUAGE in
                 zh_CN)
@@ -595,7 +609,6 @@ section_configurate_host() {
     # lobe host
     sed "${SED_INPLACE_ARGS[@]}" "s#^APP_URL=.*#APP_URL=$PROTOCOL://$LOBE_HOST#" .env
     # s3 related
-    sed "${SED_INPLACE_ARGS[@]}" "s#^S3_PUBLIC_DOMAIN=.*#S3_PUBLIC_DOMAIN=$PROTOCOL://$RUSTFS_HOST#" .env
     sed "${SED_INPLACE_ARGS[@]}" "s#^S3_ENDPOINT=.*#S3_ENDPOINT=$PROTOCOL://$RUSTFS_HOST#" .env
     
 
@@ -726,7 +739,8 @@ section_display_configurated_report() {
     printf "\n%s\n\n" "$(show_message "tips_run_command")"
     print_centered "docker compose up --no-attach searxng" "green"
     printf "\n%s\n" "$(show_message "tips_if_run_normally")"
-    printf "\n%s\n\n" "$(show_message "tips_regen_jwks")"
+    printf "\n%s\n" "$(show_message "tips_regen_jwks")"
+    printf "\n%s\n\n" "$(show_message "tips_disable_registration")"
     print_centered "docker compose up -d --no-attach searxng" "green"
     printf "\n%s\n" "$(show_message "tips_if_want_searxng_logs")"
     print_centered "docker compose logs -f searxng" "white"

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

@@ -17,20 +17,29 @@ The directory structure of LobeHub is as follows:
 
 ```bash
 src
-├── app        # Next.js App Router implementation with route groups and API routes
-├── components # Reusable UI components
-├── config     # Application configuration files, including client-side and server-side environment variables
-├── features   # Function modules related to business functions, such as agent settings, plugin development pop-ups, etc.
-├── hooks      # Custom utility hooks reused throughout the application
-├── layout     # Application layout components, such as navigation bars, sidebars, etc.
-├── libs       # Third-party integrations (analytics, OIDC, etc.)
-├── locales    # Internationalization language files
-├── server     # Server-side modules and services
-├── services   # Encapsulated backend service interfaces, such as HTTP requests
-├── store      # Zustand store for state management
-├── styles     # Global styles and CSS-in-JS configurations
-├── types      # TypeScript type definition files
-└── utils      # Common utility functions
+├── app            # Next.js App Router implementation with route groups and API routes
+├── business       # Business logic modules (client and server)
+├── components     # Reusable UI components
+├── config         # Application configuration files, including client-side and server-side environment variables
+├── const          # Application constants and enums
+├── envs           # Environment variable definitions and validation (analytics, auth, llm, etc.)
+├── features       # Function modules related to business functions, such as agent settings, plugin development pop-ups, etc.
+├── helpers        # Utility helpers for tool engineering, placeholder parsing, etc.
+├── hooks          # Custom utility hooks reused throughout the application
+├── layout         # Application layout components, such as navigation bars, sidebars, etc.
+├── libs           # Third-party integrations (analytics, OIDC, etc.)
+├── locales        # Internationalization language files
+├── server         # Server-side modules and services
+├── services       # Encapsulated backend service interfaces, such as HTTP requests
+├── store          # Zustand store for state management
+├── styles         # Global styles and CSS-in-JS configurations
+├── tools          # Built-in tools (artifacts, inspectors, interventions, etc.)
+├── types          # TypeScript type definition files
+├── utils          # Common utility functions
+├── auth.ts        # Authentication configuration (Better Auth)
+├── instrumentation.ts      # Application monitoring and telemetry setup
+├── instrumentation.node.ts # Node.js-specific instrumentation
+└── proxy.ts       # Next.js middleware proxy configuration
 ```
 
 ## app

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

@@ -15,20 +15,29 @@ LobeHub 的文件夹目录架构如下：
 
 ```bash
 src
-├── app        # Next.js App Router 实现，包含路由组和 API 路由
-├── components # 可复用的 UI 组件
-├── config     # 应用的配置文件，包含客户端环境变量与服务端环境变量
-├── features   # 与业务功能相关的功能模块，如 Agent 设置、插件开发弹窗等
-├── hooks      # 全应用复用自定义的工具 Hooks
-├── layout     # 应用的布局组件，如导航栏、侧边栏等
-├── libs       # 第三方集成（分析、OIDC 等）
-├── locales    # 国际化的语言文件
-├── server     # 服务端模块和服务
-├── services   # 封装的后端服务接口，如 HTTP 请求
-├── store      # 用于状态管理的 zustand store
-├── styles     # 全局样式和 CSS-in-JS 配置
-├── types      # TypeScript 的类型定义文件
-└── utils      # 通用的工具函数
+├── app            # Next.js App Router 实现，包含路由组和 API 路由
+├── business       # 业务逻辑模块（客户端和服务端）
+├── components     # 可复用的 UI 组件
+├── config         # 应用的配置文件，包含客户端环境变量与服务端环境变量
+├── const          # 应用常量和枚举
+├── envs           # 环境变量定义和校验（分析、认证、LLM 等）
+├── features       # 与业务功能相关的功能模块，如 Agent 设置、插件开发弹窗等
+├── helpers        # 工具辅助函数，用于工具工程、占位符解析等
+├── hooks          # 全应用复用自定义的工具 Hooks
+├── layout         # 应用的布局组件，如导航栏、侧边栏等
+├── libs           # 第三方集成（分析、OIDC 等）
+├── locales        # 国际化的语言文件
+├── server         # 服务端模块和服务
+├── services       # 封装的后端服务接口，如 HTTP 请求
+├── store          # 用于状态管理的 zustand store
+├── styles         # 全局样式和 CSS-in-JS 配置
+├── tools          # 内置工具（artifacts、inspectors、interventions 等）
+├── types          # TypeScript 的类型定义文件
+├── utils          # 通用的工具函数
+├── auth.ts        # 认证配置（Better Auth）
+├── instrumentation.ts      # 应用监控和遥测设置
+├── instrumentation.node.ts # Node.js 专用的 instrumentation
+└── proxy.ts       # Next.js 中间件代理配置
 ```
 
 ## app

package/docs/development/basic/work-with-server-side-database.mdx

@@ -101,7 +101,6 @@ S3_ACCESS_KEY_ID=${MINIO_ROOT_USER}
 S3_SECRET_ACCESS_KEY=${MINIO_ROOT_PASSWORD}
 S3_ENDPOINT=http://localhost:${MINIO_PORT}
 S3_BUCKET=${MINIO_LOBE_BUCKET}
-S3_PUBLIC_DOMAIN=http://localhost:${MINIO_PORT}
 S3_ENABLE_PATH_STYLE=1  # Required for MinIO
 S3_SET_ACL=0  # MinIO compatibility
 ```

package/docs/development/basic/work-with-server-side-database.zh-CN.mdx

@@ -101,7 +101,6 @@ S3_ACCESS_KEY_ID=${MINIO_ROOT_USER}
 S3_SECRET_ACCESS_KEY=${MINIO_ROOT_PASSWORD}
 S3_ENDPOINT=http://localhost:${MINIO_PORT}
 S3_BUCKET=${MINIO_LOBE_BUCKET}
-S3_PUBLIC_DOMAIN=http://localhost:${MINIO_PORT}
 S3_ENABLE_PATH_STYLE=1  # MinIO 必需
 S3_SET_ACL=0  # MinIO 兼容性
 ```

package/docs/development/start.mdx

@@ -34,18 +34,25 @@ The folder directory structure of LobeHub is as follows:
 
 ```bash
 src
-├── app        # Code related to the main logic and state management of the application
-├── components # Reusable UI components
-├── config     # Application configuration files, including client and server environment variables
-├── const      # Used to define constants, such as action types, route names, etc.
-├── features   # Business-related feature modules, such as Agent settings, plugin development pop-ups, etc.
-├── hooks      # Custom utility Hooks reusable across the application
-├── layout     # Application layout components, such as navigation bars, sidebars, etc.
-├── locales    # Language files for internationalization
-├── services   # Encapsulated backend service interfaces, such as HTTP requests
-├── store      # Zustand store for state management
-├── types      # TypeScript type definition files
-└── utils      # General utility functions
+├── app            # Next.js App Router implementation with route groups and API routes
+├── business       # Business logic modules (client and server)
+├── components     # Reusable UI components
+├── config         # Application configuration files, including client and server environment variables
+├── const          # Application constants and enums
+├── envs           # Environment variable definitions and validation (analytics, auth, llm, etc.)
+├── features       # Business-related feature modules, such as Agent settings, plugin development pop-ups, etc.
+├── helpers        # Utility helpers for tool engineering, placeholder parsing, etc.
+├── hooks          # Custom utility Hooks reusable across the application
+├── layout         # Application layout components, such as navigation bars, sidebars, etc.
+├── libs           # Third-party integrations (analytics, OIDC, etc.)
+├── locales        # Language files for internationalization
+├── server         # Server-side modules and services
+├── services       # Encapsulated backend service interfaces, such as HTTP requests
+├── store          # Zustand store for state management
+├── styles         # Global styles and CSS-in-JS configurations
+├── tools          # Built-in tools (artifacts, inspectors, interventions, etc.)
+├── types          # TypeScript type definition files
+└── utils          # General utility functions
 ```
 
 For a detailed introduction to the directory structure, see: [Folder Directory Structure](/docs/development/basic/folder-structure)

package/docs/development/start.zh-CN.mdx

@@ -32,18 +32,25 @@ LobeHub 的文件夹目录架构如下：
 
 ```bash
 src
-├── app        # 应用主要逻辑和状态管理相关的代码
-├── components # 可复用的 UI 组件
-├── config     # 应用的配置文件，包含客户端环境变量与服务端环境变量
-├── const      # 用于定义常量，如 action 类型、路由名等
-├── features   # 与业务功能相关的功能模块，如 Agent 设置、插件开发弹窗等
-├── hooks      # 全应用复用自定义的工具 Hooks
-├── layout     # 应用的布局组件，如导航栏、侧边栏等
-├── locales    # 国际化的语言文件
-├── services   # 封装的后端服务接口，如 HTTP 请求
-├── store      # 用于状态管理的 zustand store
-├── types      # TypeScript 的类型定义文件
-└── utils      # 通用的工具函数
+├── app            # Next.js App Router 实现，包含路由组和 API 路由
+├── business       # 业务逻辑模块（客户端和服务端）
+├── components     # 可复用的 UI 组件
+├── config         # 应用的配置文件，包含客户端环境变量与服务端环境变量
+├── const          # 应用常量和枚举
+├── envs           # 环境变量定义和校验（分析、认证、LLM 等）
+├── features       # 与业务功能相关的功能模块，如 Agent 设置、插件开发弹窗等
+├── helpers        # 工具辅助函数，用于工具工程、占位符解析等
+├── hooks          # 全应用复用自定义的工具 Hooks
+├── layout         # 应用的布局组件，如导航栏、侧边栏等
+├── libs           # 第三方集成（分析、OIDC 等）
+├── locales        # 国际化的语言文件
+├── server         # 服务端模块和服务
+├── services       # 封装的后端服务接口，如 HTTP 请求
+├── store          # 用于状态管理的 zustand store
+├── styles         # 全局样式和 CSS-in-JS 配置
+├── tools          # 内置工具（artifacts、inspectors、interventions 等）
+├── types          # TypeScript 的类型定义文件
+└── utils          # 通用的工具函数
 ```
 
 有关目录架构的详细介绍，详见： [文件夹目录架构](/zh/docs/development/basic/folder-structure)