🔖 chore(release): v1.24.2 [skip ci]

### [Version 1.24.2](https://github.com/lobehub/lobe-chat/compare/v1.24.1...v1.24.2)
<sup>Released on **2024-10-26**</sup>

#### 💄 Styles

- **misc**: Update Google Model list, add `gemini-1.5-flash-8b`.

<br/>

<details>
<summary><kbd>Improvements and Fixes</kbd></summary>

#### Styles

* **misc**: Update Google Model list, add `gemini-1.5-flash-8b`, closes [#4495](https://github.com/lobehub/lobe-chat/issues/4495) ([499c479](https://github.com/lobehub/lobe-chat/commit/499c479))

</details>

<div align="right">

[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)

</div>

.dockerignore

@@ -4,8 +4,6 @@ node_modules
 npm-debug.log
 .next
 .git
-scripts
-docs
 .github
 *.md
 .env.example

.env.example

@@ -33,7 +33,7 @@ OPENAI_API_KEY=sk-xxxxxxxxx
 # AZURE_ENDPOINT=https://docs-test-001.openai.azure.com
 
 # Azure's API version, follows the YYYY-MM-DD format
-# AZURE_API_VERSION=2024-02-01
+# AZURE_API_VERSION=2024-06-01
 
 
 ### Anthropic Service ####
@@ -104,6 +104,18 @@ OPENAI_API_KEY=sk-xxxxxxxxx
 
 # MINIMAX_API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
+### DeepSeek AI  ####
+
+# DEEPSEEK_API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+### Qwen AI  ####
+
+# QWEN_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+### SiliconCloud AI  ####
+
+# SILICONCLOUD_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
 ########################################
 ############ Market Service ############
 ########################################
@@ -121,3 +133,63 @@ OPENAI_API_KEY=sk-xxxxxxxxx
 # set the plugin settings
 # the format is `plugin-identifier:key1=value1;key2=value2`, multiple settings fields are separated by semicolons `;`, multiple plugin settings are separated by commas `,`.
 # PLUGIN_SETTINGS=search-engine:SERPAPI_API_KEY=xxxxx
+
+
+########################################
+##### S3 Object Storage Service ########
+########################################
+
+# S3 keys
+#S3_ACCESS_KEY_ID=9998d6757e276cf9f1edbd325b7083a6
+#S3_SECRET_ACCESS_KEY=55af75d8eb6b99f189f6a35f855336ea62cd9c4751a5cf4337c53c1d3f497ac2
+
+# Bucket name
+#S3_BUCKET=lobechat
+
+# Bucket request endpoint
+#S3_ENDPOINT=https://0b33a03b5c993fd2f453379dc36558e5.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
+
+
+########################################
+############ Auth Service ##############
+########################################
+
+
+# Clerk related configurations
+
+# Clerk public key and secret key
+#NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_live_xxxxxxxxxxx
+#CLERK_SECRET_KEY=sk_live_xxxxxxxxxxxxxxxxxxxxxx
+
+# you need to config the clerk webhook secret key if you want to use the clerk with database
+#CLERK_WEBHOOK_SECRET=whsec_xxxxxxxxxxxxxxxxxxxxxx
+
+
+# NextAuth related configurations
+# NEXT_AUTH_SECRET=
+
+# Auth0 configurations
+# AUTH_AUTH0_ID=
+# AUTH_AUTH0_SECRET=
+# AUTH_AUTH0_ISSUER=https://your-domain.auth0.com
+
+########################################
+########## Server Database #############
+########################################
+
+# Specify the service mode as server if you want to use the server database
+#NEXT_PUBLIC_SERVICE_MODE=server
+
+# Postgres database URL
+#DATABASE_URL=postgres://username:password@host:port/database
+
+# use `openssl rand -base64 32` to generate a key for the encryption of the database
+# we use this key to encrypt the user api key
+#KEY_VAULTS_SECRET=xxxxx/xxxxxxxxxxxxxx=

.eslintignore

@@ -10,9 +10,8 @@ coverage
 
 # test
 jest*
-_test_
-__test__
 *.test.ts
+*.test.tsx
 
 # umi
 .umi

.github/ISSUE_TEMPLATE/1_bug_report.yml

@@ -5,53 +5,64 @@ labels: ['🐛 Bug']
 body:
   - type: dropdown
     attributes:
-      label: '💻 Operating System'
+      label: '📦 Environment'
+      multiple: true
       options:
-        - Windows
-        - macOS
-        - Ubuntu
-        - Other Linux
-        - iOS
-        - Android
-        - Other
+        - 'Official Preview'
+        - 'Vercel'
+        - 'Zeabur'
+        - 'Sealos'
+        - 'Netlify'
+        - 'Docker'
+        - 'Other'
     validations:
       required: true
+  - type: input
+    attributes:
+      label: '📌 Version'
+    validations:
+      required: true
+  
   - type: dropdown
     attributes:
-      label: '📦 Environment'
+      label: '💻 Operating System'
+      multiple: true
       options:
-        - Official Preview
-        - Vercel / Zeabur / Sealos
-        - Docker
-        - Other
+        - 'Windows'
+        - 'macOS'
+        - 'Ubuntu'
+        - 'Other Linux'
+        - 'iOS'
+        - 'Android'
+        - 'Other'
     validations:
       required: true
-
   - type: dropdown
     attributes:
       label: '🌐 Browser'
+      multiple: true
       options:
-        - Chrome
-        - Edge
-        - Safari
-        - Firefox
-        - Other
+        - 'Chrome'
+        - 'Edge'
+        - 'Safari'
+        - 'Firefox'
+        - 'Other'
     validations:
       required: true
   - type: textarea
     attributes:
       label: '🐛 Bug Description'
-      description: A clear and concise description of the bug.
+      description: A clear and concise description of the bug, if the above option is `Other`, please also explain in detail.
     validations:
       required: true
-  - type: textarea
-    attributes:
-      label: '🚦 Expected Behavior'
-      description: A clear and concise description of what you expected to happen.
   - type: textarea
     attributes:
       label: '📷 Recurrence Steps'
       description: A clear and concise description of how to recurrence.
+  - type: textarea
+    attributes:
+      label: '🚦 Expected Behavior'
+      description: A clear and concise description of what you expected to happen.
   - type: textarea
     attributes:
       label: '📝 Additional Information'

.github/ISSUE_TEMPLATE/1_bug_report_cn.yml

@@ -5,54 +5,64 @@ labels: ['🐛 Bug']
 body:
   - type: dropdown
     attributes:
-      label: '💻 系统环境'
+      label: '📦 部署环境'
+      multiple: true
       options:
-        - Windows
-        - macOS
-        - Ubuntu
-        - Other Linux
-        - iOS
-        - Android
-        - Other
+        - 'Official Preview'
+        - 'Vercel'
+        - 'Zeabur'
+        - 'Sealos'
+        - 'Netlify'
+        - 'Docker'
+        - 'Other'
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: '📌 软件版本'
     validations:
       required: true
 
   - type: dropdown
     attributes:
-      label: '📦 部署环境'
+      label: '💻 系统环境'
+      multiple: true
       options:
-        - Official Preview
-        - Vercel / Zeabur / Sealos
-        - Docker
-        - Other
+        - 'Windows'
+        - 'macOS'
+        - 'Ubuntu'
+        - 'Other Linux'
+        - 'iOS'
+        - 'Android'
+        - 'Other'
     validations:
       required: true
-
   - type: dropdown
     attributes:
       label: '🌐 浏览器'
+      multiple: true
       options:
-        - Chrome
-        - Edge
-        - Safari
-        - Firefox
-        - Other
+        - 'Chrome'
+        - 'Edge'
+        - 'Safari'
+        - 'Firefox'
+        - 'Other'
     validations:
       required: true
   - type: textarea
     attributes:
       label: '🐛 问题描述'
-      description: 请提供一个清晰且简洁的问题描述。
+      description: 请提供一个清晰且简洁的问题描述，若上述选项为`Other`，也请详细说明。
     validations:
       required: true
-  - type: textarea
-    attributes:
-      label: '🚦 期望结果'
-      description: 请提供一个清晰且简洁的描述，说明您期望发生什么。
   - type: textarea
     attributes:
       label: '📷 复现步骤'
       description: 请提供一个清晰且简洁的描述，说明如何复现问题。
+  - type: textarea
+    attributes:
+      label: '🚦 期望结果'
+      description: 请提供一个清晰且简洁的描述，说明您期望发生什么。
   - type: textarea
     attributes:
       label: '📝 补充信息'

.github/PULL_REQUEST_TEMPLATE.md

@@ -6,9 +6,10 @@
 - [ ] 🐛 fix
 - [ ] ♻️ refactor
 - [ ] 💄 style
-- [ ] 🔨 chore
+- [ ] 👷 build
 - [ ] ⚡️ perf
 - [ ] 📝 docs
+- [ ] 🔨 chore
 
 #### 🔀 变更说明 | Description of Change
 

.github/workflows/docker-database.yml

@@ -0,0 +1,46 @@
+name: Publish Database Docker Image
+
+on:
+  workflow_dispatch:
+  release:
+    types: [published]
+
+jobs:
+  push_to_registry:
+    name: Push Docker image to Docker Hub
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out the repo
+        uses: actions/checkout@v4
+      - name: Log in to Docker Hub
+        uses: docker/login-action@v3
+        with:
+          username: ${{ secrets.DOCKER_REGISTRY_USER }}
+          password: ${{ secrets.DOCKER_REGISTRY_PASSWORD }}
+
+      - name: Extract metadata (tags, labels) for Docker
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: lobehub/lobe-chat-database
+          tags: |
+            type=raw,value=latest
+            type=ref,event=tag
+
+      - name: Set up QEMU
+        uses: docker/setup-qemu-action@v3
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      - name: Build and push Docker image
+        uses: docker/build-push-action@v5
+        with:
+          context: .
+          file: ./Dockerfile.database  # 指定使用 Dockerfile.database 文件
+          platforms: linux/amd64,linux/arm64
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          cache-from: type=gha
+          cache-to: type=gha,mode=max

.github/workflows/release.yml

@@ -8,6 +8,17 @@ jobs:
   release:
     name: Release
     runs-on: ubuntu-latest
+
+    services:
+      postgres:
+        image: pgvector/pgvector:pg16
+        env:
+          POSTGRES_PASSWORD: postgres
+        options: >-
+          --health-cmd pg_isready --health-interval 10s --health-timeout 5s  --health-retries 5
+        ports:
+          - 5432:5432
+
     steps:
       - uses: actions/checkout@v4
 
@@ -22,8 +33,18 @@ jobs:
       - name: Lint
         run: bun run lint
 
-      - name: Test
-        run: bun run test
+      - name: Test Server Coverage
+        run: bun run test-server:coverage
+        env:
+          DATABASE_TEST_URL: postgresql://postgres:postgres@localhost:5432/postgres
+          DATABASE_DRIVER: node
+          NEXT_PUBLIC_SERVICE_MODE: server
+          KEY_VAULTS_SECRET: LA7n9k3JdEcbSgml2sxfw+4TV1AzaaFU5+R176aQz4s=
+          S3_PUBLIC_DOMAIN: https://example.com
+          APP_URL: https://home.com
+
+      - name: Test App Coverage
+        run: bun run test-app:coverage
 
       - name: Release
         run: bun run release

.github/workflows/sync.yml

@@ -7,7 +7,7 @@ permissions:
 
 on:
   schedule:
-    - cron: '0 * * * *' # every hour
+    - cron: '0 */6 * * *' # every 6 hours
   workflow_dispatch:
 
 jobs:

.github/workflows/test.yml

@@ -1,9 +1,23 @@
 name: Test CI
+
 on: [push, pull_request]
+
 jobs:
   test:
     runs-on: ubuntu-latest
 
+    services:
+      postgres:
+        image: pgvector/pgvector:pg16
+        env:
+          POSTGRES_PASSWORD: postgres
+        options: >-
+          --health-cmd pg_isready --health-interval 10s --health-timeout 5s  --health-retries 5
+
+
+        ports:
+          - 5432:5432
+
     steps:
       - uses: actions/checkout@v4
 
@@ -18,10 +32,29 @@ jobs:
       - name: Lint
         run: bun run lint
 
-      - name: Test and coverage
-        run: bun run test:coverage
+      - name: Test Server Coverage
+        run: bun run test-server:coverage
+        env:
+          DATABASE_TEST_URL: postgresql://postgres:postgres@localhost:5432/postgres
+          DATABASE_DRIVER: node
+          NEXT_PUBLIC_SERVICE_MODE: server
+          KEY_VAULTS_SECRET: LA7n9k3JdEcbSgml2sxfw+4TV1AzaaFU5+R176aQz4s=
+          S3_PUBLIC_DOMAIN: https://example.com
+          APP_URL: https://home.com
 
-      - name: Upload coverage to Codecov
+      - name: Upload Server coverage to Codecov
         uses: codecov/codecov-action@v4
         with:
-          token: ${{ secrets.CODECOV_TOKEN }} # required
+          token: ${{ secrets.CODECOV_TOKEN }}
+          files: ./coverage/server/lcov.info
+          flags: server
+
+      - name: Test App Coverage
+        run: bun run test-app:coverage
+
+      - name: Upload App Coverage to Codecov
+        uses: codecov/codecov-action@v4
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}
+          files: ./coverage/app/lcov.info
+          flags: app

.gitignore

@@ -55,8 +55,15 @@ next-env.d.ts
 .next
 .env
 public/*.js
+public/sitemap.xml
+public/sitemap-index.xml
 bun.lockb
 sitemap*.xml
 robots.txt
 
+# Serwist
+public/sw*
+public/swe-worker*
+
 *.patch
+*.pdf

.i18nrc.js

@@ -23,8 +23,7 @@ module.exports = defineConfig({
     'vi-VN',
   ],
   temperature: 0,
-  modelName: 'gpt-3.5-turbo-0125',
-  splitToken: 2048,
+  modelName: 'gpt-4o-mini',
   experimental: {
     jsonMode: true,
   },

.npmrc

@@ -14,3 +14,6 @@ public-hoist-pattern[]=*semantic-release*
 public-hoist-pattern[]=*stylelint*
 
 public-hoist-pattern[]=@auth/core
+public-hoist-pattern[]=@clerk/backend
+public-hoist-pattern[]=@clerk/types
+public-hoist-pattern[]=pdfjs-dist

.nvmrc

@@ -1 +1 @@
-lts/hydrogen
+lts/iron

.seorc.cjs

@@ -2,7 +2,7 @@ const { defineConfig } = require('@lobehub/seo-cli');
 
 module.exports = defineConfig({
   entry: ['./docs/**/*.mdx'],
-  modelName: 'gpt-3.5-turbo-0125',
+  modelName: 'gpt-4o-mini',
   experimental: {
     jsonMode: true,
   },

.stylelintrc.js

@@ -4,5 +4,6 @@ module.exports = {
   ...config,
   rules: {
     'selector-id-pattern': null,
+    ...config.rules,
   },
 };

Dockerfile

@@ -1,109 +1,214 @@
+## Base image for all building stages
 FROM node:20-slim AS base
 
-## Sharp dependencies, copy all the files for production
-FROM base AS sharp
-ENV PNPM_HOME="/pnpm"
-ENV PATH="$PNPM_HOME:$PATH"
-RUN corepack enable
+ARG USE_CN_MIRROR
 
-WORKDIR /app
+ENV DEBIAN_FRONTEND="noninteractive"
 
-RUN pnpm add sharp
+RUN \
+    # If you want to build docker in China, build with --build-arg USE_CN_MIRROR=true
+    if [ "${USE_CN_MIRROR:-false}" = "true" ]; then \
+        sed -i "s/deb.debian.org/mirrors.ustc.edu.cn/g" "/etc/apt/sources.list.d/debian.sources"; \
+    fi \
+    # Add required package
+    && apt update \
+    && apt install ca-certificates proxychains-ng -qy \
+    # Prepare required package to distroless
+    && mkdir -p /distroless/bin /distroless/etc /distroless/etc/ssl/certs /distroless/lib \
+    # Copy proxychains to distroless
+    && cp /usr/lib/$(arch)-linux-gnu/libproxychains.so.4 /distroless/lib/libproxychains.so.4 \
+    && cp /usr/lib/$(arch)-linux-gnu/libdl.so.2 /distroless/lib/libdl.so.2 \
+    && cp /usr/bin/proxychains4 /distroless/bin/proxychains \
+    && cp /etc/proxychains4.conf /distroless/etc/proxychains4.conf \
+    # Copy node to distroless
+    && cp /usr/lib/$(arch)-linux-gnu/libstdc++.so.6 /distroless/lib/libstdc++.so.6 \
+    && cp /usr/lib/$(arch)-linux-gnu/libgcc_s.so.1 /distroless/lib/libgcc_s.so.1 \
+    && cp /usr/local/bin/node /distroless/bin/node \
+    # Copy CA certificates to distroless
+    && cp /etc/ssl/certs/ca-certificates.crt /distroless/etc/ssl/certs/ca-certificates.crt \
+    # Cleanup temp files
+    && rm -rf /tmp/* /var/lib/apt/lists/* /var/tmp/*
 
-## Install dependencies only when needed
+## Builder image, install all the dependencies and build the app
 FROM base AS builder
-ENV PNPM_HOME="/pnpm"
-ENV PATH="$PNPM_HOME:$PATH"
-RUN corepack enable
+
+ARG USE_CN_MIRROR
+ARG NEXT_PUBLIC_BASE_PATH
+ARG NEXT_PUBLIC_SENTRY_DSN
+ARG NEXT_PUBLIC_ANALYTICS_POSTHOG
+ARG NEXT_PUBLIC_POSTHOG_HOST
+ARG NEXT_PUBLIC_POSTHOG_KEY
+ARG NEXT_PUBLIC_ANALYTICS_UMAMI
+ARG NEXT_PUBLIC_UMAMI_SCRIPT_URL
+ARG NEXT_PUBLIC_UMAMI_WEBSITE_ID
+
+ENV NEXT_PUBLIC_BASE_PATH="${NEXT_PUBLIC_BASE_PATH}"
+
+# Sentry
+ENV NEXT_PUBLIC_SENTRY_DSN="${NEXT_PUBLIC_SENTRY_DSN}" \
+    SENTRY_ORG="" \
+    SENTRY_PROJECT=""
+
+# Posthog
+ENV NEXT_PUBLIC_ANALYTICS_POSTHOG="${NEXT_PUBLIC_ANALYTICS_POSTHOG}" \
+    NEXT_PUBLIC_POSTHOG_HOST="${NEXT_PUBLIC_POSTHOG_HOST}" \
+    NEXT_PUBLIC_POSTHOG_KEY="${NEXT_PUBLIC_POSTHOG_KEY}"
+
+# Umami
+ENV NEXT_PUBLIC_ANALYTICS_UMAMI="${NEXT_PUBLIC_ANALYTICS_UMAMI}" \
+    NEXT_PUBLIC_UMAMI_SCRIPT_URL="${NEXT_PUBLIC_UMAMI_SCRIPT_URL}" \
+    NEXT_PUBLIC_UMAMI_WEBSITE_ID="${NEXT_PUBLIC_UMAMI_WEBSITE_ID}"
+
+# Node
+ENV NODE_OPTIONS="--max-old-space-size=8192"
 
 WORKDIR /app
 
 COPY package.json ./
+COPY .npmrc ./
 
-# If you want to build docker in China
-# RUN npm config set registry https://registry.npmmirror.com/
-RUN pnpm i
+RUN \
+    # If you want to build docker in China, build with --build-arg USE_CN_MIRROR=true
+    if [ "${USE_CN_MIRROR:-false}" = "true" ]; then \
+        export SENTRYCLI_CDNURL="https://npmmirror.com/mirrors/sentry-cli"; \
+        npm config set registry "https://registry.npmmirror.com/"; \
+        echo 'canvas_binary_host_mirror=https://npmmirror.com/mirrors/canvas' >> .npmrc; \
+    fi \
+    # Set the registry for corepack
+    && export COREPACK_NPM_REGISTRY=$(npm config get registry | sed 's/\/$//') \
+    # Enable corepack
+    && corepack enable \
+    # Use pnpm for corepack
+    && corepack use pnpm \
+    # Install the dependencies
+    && pnpm i \
+    # Add sharp dependencies
+    && mkdir -p /deps \
+    && pnpm add sharp --prefix /deps
 
 COPY . .
-RUN pnpm run build:docker # run build standalone for docker version
 
-## Production image, copy all the files and run next
-FROM base AS runner
-WORKDIR /app
+# run build standalone for docker version
+RUN npm run build:docker
 
-ENV NODE_ENV production
+## Application image, copy all the files for production
+FROM busybox:latest AS app
 
-RUN addgroup --system --gid 1001 nodejs
-RUN adduser --system --uid 1001 nextjs
+COPY --from=base /distroless/ /
 
-COPY --from=builder /app/public ./public
-
-# Set the correct permission for prerender cache
-RUN mkdir .next
-RUN chown nextjs:nodejs .next
+COPY --from=builder /app/public /app/public
 
 # Automatically leverage output traces to reduce image size
 # https://nextjs.org/docs/advanced-features/output-file-tracing
-COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
-COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
-COPY --from=sharp --chown=nextjs:nodejs /app/node_modules/.pnpm ./node_modules/.pnpm
+COPY --from=builder /app/.next/standalone /app/
+COPY --from=builder /app/.next/static /app/.next/static
+COPY --from=builder /deps/node_modules/.pnpm /app/node_modules/.pnpm
+
+# Copy server launcher
+COPY --from=builder /app/scripts/serverLauncher/startServer.js /app/startServer.js
+
+RUN \
+    # Add nextjs:nodejs to run the app
+    addgroup -S -g 1001 nodejs \
+    && adduser -D -G nodejs -H -S -h /app -u 1001 nextjs \
+    # Set permission for nextjs:nodejs
+    && chown -R nextjs:nodejs /app /etc/proxychains4.conf
+
+## Production image, copy all the files and run next
+FROM scratch
+
+# Copy all the files from app, set the correct permission for prerender cache
+COPY --from=app / /
+
+ENV NODE_ENV="production" \
+    NODE_OPTIONS="--dns-result-order=ipv4first --use-openssl-ca" \
+    NODE_EXTRA_CA_CERTS="" \
+    NODE_TLS_REJECT_UNAUTHORIZED="" \
+    SSL_CERT_DIR="/etc/ssl/certs/ca-certificates.crt"
+
+# set hostname to localhost
+ENV HOSTNAME="0.0.0.0" \
+    PORT="3210"
+
+# General Variables
+ENV ACCESS_CODE="" \
+    API_KEY_SELECT_MODE="" \
+    DEFAULT_AGENT_CONFIG="" \
+    SYSTEM_AGENT="" \
+    FEATURE_FLAGS="" \
+    PROXY_URL=""
+
+# Model Variables
+ENV \
+    # AI21
+    AI21_API_KEY="" AI21_MODEL_LIST="" \
+    # Ai360
+    AI360_API_KEY="" AI360_MODEL_LIST="" \
+    # Anthropic
+    ANTHROPIC_API_KEY="" ANTHROPIC_MODEL_LIST="" ANTHROPIC_PROXY_URL="" \
+    # Amazon Bedrock
+    AWS_ACCESS_KEY_ID="" AWS_SECRET_ACCESS_KEY="" AWS_REGION="" AWS_BEDROCK_MODEL_LIST="" \
+    # Azure OpenAI
+    AZURE_API_KEY="" AZURE_API_VERSION="" AZURE_ENDPOINT="" AZURE_MODEL_LIST="" \
+    # Baichuan
+    BAICHUAN_API_KEY="" BAICHUAN_MODEL_LIST="" \
+    # DeepSeek
+    DEEPSEEK_API_KEY="" DEEPSEEK_MODEL_LIST="" \
+    # Fireworks AI
+    FIREWORKSAI_API_KEY="" FIREWORKSAI_MODEL_LIST="" \
+    # GitHub
+    GITHUB_TOKEN="" GITHUB_MODEL_LIST="" \
+    # Google
+    GOOGLE_API_KEY="" GOOGLE_MODEL_LIST="" GOOGLE_PROXY_URL="" \
+    # Groq
+    GROQ_API_KEY="" GROQ_MODEL_LIST="" GROQ_PROXY_URL="" \
+    # HuggingFace
+    HUGGINGFACE_API_KEY="" HUGGINGFACE_MODEL_LIST="" HUGGINGFACE_PROXY_URL="" \
+    # Hunyuan
+    HUNYUAN_API_KEY="" HUNYUAN_MODEL_LIST="" \
+    # Minimax
+    MINIMAX_API_KEY="" MINIMAX_MODEL_LIST="" \
+    # Mistral
+    MISTRAL_API_KEY="" MISTRAL_MODEL_LIST="" \
+    # Moonshot
+    MOONSHOT_API_KEY="" MOONSHOT_MODEL_LIST="" MOONSHOT_PROXY_URL="" \
+    # Novita
+    NOVITA_API_KEY="" NOVITA_MODEL_LIST="" \
+    # Ollama
+    OLLAMA_MODEL_LIST="" OLLAMA_PROXY_URL="" \
+    # OpenAI
+    OPENAI_API_KEY="" OPENAI_MODEL_LIST="" OPENAI_PROXY_URL="" \
+    # OpenRouter
+    OPENROUTER_API_KEY="" OPENROUTER_MODEL_LIST="" \
+    # Perplexity
+    PERPLEXITY_API_KEY="" PERPLEXITY_MODEL_LIST="" PERPLEXITY_PROXY_URL="" \
+    # Qwen
+    QWEN_API_KEY="" QWEN_MODEL_LIST="" \
+    # SenseNova
+    SENSENOVA_ACCESS_KEY_ID="" SENSENOVA_ACCESS_KEY_SECRET="" SENSENOVA_MODEL_LIST="" \
+    # SiliconCloud
+    SILICONCLOUD_API_KEY="" SILICONCLOUD_MODEL_LIST="" SILICONCLOUD_PROXY_URL="" \
+    # Spark
+    SPARK_API_KEY="" SPARK_MODEL_LIST="" \
+    # Stepfun
+    STEPFUN_API_KEY="" STEPFUN_MODEL_LIST="" \
+    # Taichu
+    TAICHU_API_KEY="" TAICHU_MODEL_LIST="" \
+    # TogetherAI
+    TOGETHERAI_API_KEY="" TOGETHERAI_MODEL_LIST="" \
+    # Upstage
+    UPSTAGE_API_KEY="" UPSTAGE_MODEL_LIST="" \
+    # Wenxin
+    WENXIN_ACCESS_KEY="" WENXIN_SECRET_KEY="" WENXIN_MODEL_LIST="" \
+    # 01.AI
+    ZEROONE_API_KEY="" ZEROONE_MODEL_LIST="" \
+    # Zhipu
+    ZHIPU_API_KEY="" ZHIPU_MODEL_LIST=""
 
 USER nextjs
 
-EXPOSE 3210
+EXPOSE 3210/tcp
 
-# set hostname to localhost
-ENV HOSTNAME "0.0.0.0"
-ENV PORT=3210
+ENTRYPOINT ["/bin/node"]
 
-# General Variables
-ENV ACCESS_CODE ""
-
-ENV API_KEY_SELECT_MODE ""
-
-# OpenAI
-ENV OPENAI_API_KEY ""
-ENV OPENAI_PROXY_URL ""
-ENV OPENAI_MODEL_LIST ""
-
-# Azure OpenAI
-ENV USE_AZURE_OPENAI ""
-ENV AZURE_API_KEY ""
-ENV AZURE_API_VERSION ""
-
-# Google
-ENV GOOGLE_API_KEY ""
-
-# Zhipu
-ENV ZHIPU_API_KEY ""
-
-# Moonshot
-ENV MOONSHOT_API_KEY ""
-
-# Ollama
-ENV OLLAMA_PROXY_URL ""
-ENV OLLAMA_MODEL_LIST ""
-
-# Perplexity
-ENV PERPLEXITY_API_KEY ""
-
-# Anthropic
-ENV ANTHROPIC_API_KEY ""
-
-# Mistral
-ENV MISTRAL_API_KEY ""
-
-# OpenRouter
-ENV OPENROUTER_API_KEY ""
-ENV OPENROUTER_MODEL_LIST ""
-
-# 01.AI
-ENV ZEROONE_API_KEY ""
-
-# TogetherAI
-ENV TOGETHERAI_API_KEY ""
-
-# Minimax
-ENV MINIMAX_API_KEY ""
-
-CMD ["node", "server.js"]
+CMD ["/app/startServer.js"]

Dockerfile.database

@@ -0,0 +1,249 @@
+## Base image for all building stages
+FROM node:20-slim AS base
+
+ARG USE_CN_MIRROR
+
+ENV DEBIAN_FRONTEND="noninteractive"
+
+RUN \
+    # If you want to build docker in China, build with --build-arg USE_CN_MIRROR=true
+    if [ "${USE_CN_MIRROR:-false}" = "true" ]; then \
+        sed -i "s/deb.debian.org/mirrors.ustc.edu.cn/g" "/etc/apt/sources.list.d/debian.sources"; \
+    fi \
+    # Add required package
+    && apt update \
+    && apt install ca-certificates proxychains-ng -qy \
+    # Prepare required package to distroless
+    && mkdir -p /distroless/bin /distroless/etc /distroless/etc/ssl/certs /distroless/lib \
+    # Copy proxychains to distroless
+    && cp /usr/lib/$(arch)-linux-gnu/libproxychains.so.4 /distroless/lib/libproxychains.so.4 \
+    && cp /usr/lib/$(arch)-linux-gnu/libdl.so.2 /distroless/lib/libdl.so.2 \
+    && cp /usr/bin/proxychains4 /distroless/bin/proxychains \
+    && cp /etc/proxychains4.conf /distroless/etc/proxychains4.conf \
+    # Copy node to distroless
+    && cp /usr/lib/$(arch)-linux-gnu/libstdc++.so.6 /distroless/lib/libstdc++.so.6 \
+    && cp /usr/lib/$(arch)-linux-gnu/libgcc_s.so.1 /distroless/lib/libgcc_s.so.1 \
+    && cp /usr/local/bin/node /distroless/bin/node \
+    # Copy CA certificates to distroless
+    && cp /etc/ssl/certs/ca-certificates.crt /distroless/etc/ssl/certs/ca-certificates.crt \
+    # Cleanup temp files
+    && rm -rf /tmp/* /var/lib/apt/lists/* /var/tmp/*
+
+## Builder image, install all the dependencies and build the app
+FROM base AS builder
+
+ARG USE_CN_MIRROR
+ARG NEXT_PUBLIC_BASE_PATH
+ARG NEXT_PUBLIC_SERVICE_MODE
+ARG NEXT_PUBLIC_SENTRY_DSN
+ARG NEXT_PUBLIC_ANALYTICS_POSTHOG
+ARG NEXT_PUBLIC_POSTHOG_HOST
+ARG NEXT_PUBLIC_POSTHOG_KEY
+ARG NEXT_PUBLIC_ANALYTICS_UMAMI
+ARG NEXT_PUBLIC_UMAMI_SCRIPT_URL
+ARG NEXT_PUBLIC_UMAMI_WEBSITE_ID
+
+ENV NEXT_PUBLIC_BASE_PATH="${NEXT_PUBLIC_BASE_PATH}"
+
+ENV NEXT_PUBLIC_SERVICE_MODE="${NEXT_PUBLIC_SERVICE_MODE:-server}" \
+    APP_URL="http://app.com" \
+    DATABASE_DRIVER="node" \
+    DATABASE_URL="postgres://postgres:password@localhost:5432/postgres" \
+    KEY_VAULTS_SECRET="use-for-build"
+
+# Sentry
+ENV NEXT_PUBLIC_SENTRY_DSN="${NEXT_PUBLIC_SENTRY_DSN}" \
+    SENTRY_ORG="" \
+    SENTRY_PROJECT=""
+
+# Posthog
+ENV NEXT_PUBLIC_ANALYTICS_POSTHOG="${NEXT_PUBLIC_ANALYTICS_POSTHOG}" \
+    NEXT_PUBLIC_POSTHOG_HOST="${NEXT_PUBLIC_POSTHOG_HOST}" \
+    NEXT_PUBLIC_POSTHOG_KEY="${NEXT_PUBLIC_POSTHOG_KEY}"
+
+# Umami
+ENV NEXT_PUBLIC_ANALYTICS_UMAMI="${NEXT_PUBLIC_ANALYTICS_UMAMI}" \
+    NEXT_PUBLIC_UMAMI_SCRIPT_URL="${NEXT_PUBLIC_UMAMI_SCRIPT_URL}" \
+    NEXT_PUBLIC_UMAMI_WEBSITE_ID="${NEXT_PUBLIC_UMAMI_WEBSITE_ID}"
+
+# Node
+ENV NODE_OPTIONS="--max-old-space-size=8192"
+
+WORKDIR /app
+
+COPY package.json ./
+COPY .npmrc ./
+
+RUN \
+    # If you want to build docker in China, build with --build-arg USE_CN_MIRROR=true
+    if [ "${USE_CN_MIRROR:-false}" = "true" ]; then \
+        export SENTRYCLI_CDNURL="https://npmmirror.com/mirrors/sentry-cli"; \
+        npm config set registry "https://registry.npmmirror.com/"; \
+        echo 'canvas_binary_host_mirror=https://npmmirror.com/mirrors/canvas' >> .npmrc; \
+    fi \
+    # Set the registry for corepack
+    && export COREPACK_NPM_REGISTRY=$(npm config get registry | sed 's/\/$//') \
+    # Enable corepack
+    && corepack enable \
+    # Use pnpm for corepack
+    && corepack use pnpm \
+    # Install the dependencies
+    && pnpm i \
+    # Add sharp and db migration dependencies
+    && mkdir -p /deps \
+    && pnpm add sharp pg drizzle-orm --prefix /deps
+
+COPY . .
+
+# run build standalone for docker version
+RUN npm run build:docker
+
+## Application image, copy all the files for production
+FROM busybox:latest AS app
+
+COPY --from=base /distroless/ /
+
+COPY --from=builder /app/public /app/public
+
+# Automatically leverage output traces to reduce image size
+# https://nextjs.org/docs/advanced-features/output-file-tracing
+COPY --from=builder /app/.next/standalone /app/
+COPY --from=builder /app/.next/static /app/.next/static
+
+# copy dependencies
+COPY --from=builder /deps/node_modules/.pnpm /app/node_modules/.pnpm
+COPY --from=builder /deps/node_modules/pg /app/node_modules/pg
+COPY --from=builder /deps/node_modules/drizzle-orm /app/node_modules/drizzle-orm
+
+# Copy database migrations
+COPY --from=builder /app/src/database/server/migrations /app/migrations
+COPY --from=builder /app/scripts/migrateServerDB/docker.cjs /app/docker.cjs
+COPY --from=builder /app/scripts/migrateServerDB/errorHint.js /app/errorHint.js
+
+# Copy server launcher
+COPY --from=builder /app/scripts/serverLauncher/startServer.js /app/startServer.js
+
+RUN \
+    # Add nextjs:nodejs to run the app
+    addgroup -S -g 1001 nodejs \
+    && adduser -D -G nodejs -H -S -h /app -u 1001 nextjs \
+    # Set permission for nextjs:nodejs
+    && chown -R nextjs:nodejs /app /etc/proxychains4.conf
+
+## Production image, copy all the files and run next
+FROM scratch
+
+# Copy all the files from app, set the correct permission for prerender cache
+COPY --from=app / /
+
+ENV NODE_ENV="production" \
+    NODE_OPTIONS="--dns-result-order=ipv4first --use-openssl-ca" \
+    NODE_EXTRA_CA_CERTS="" \
+    NODE_TLS_REJECT_UNAUTHORIZED="" \
+    SSL_CERT_DIR="/etc/ssl/certs/ca-certificates.crt"
+
+# set hostname to localhost
+ENV HOSTNAME="0.0.0.0" \
+    PORT="3210"
+
+# General Variables
+ENV ACCESS_CODE="" \
+    APP_URL="" \
+    API_KEY_SELECT_MODE="" \
+    DEFAULT_AGENT_CONFIG="" \
+    SYSTEM_AGENT="" \
+    FEATURE_FLAGS="" \
+    PROXY_URL=""
+
+# Database
+ENV KEY_VAULTS_SECRET="" \
+    DATABASE_DRIVER="node" \
+    DATABASE_URL=""
+
+# Next Auth
+ENV NEXT_AUTH_SECRET="" \
+    NEXT_AUTH_SSO_PROVIDERS="" \
+    NEXTAUTH_URL=""
+
+# S3
+ENV NEXT_PUBLIC_S3_DOMAIN="" \
+    S3_PUBLIC_DOMAIN="" \
+    S3_ACCESS_KEY_ID="" \
+    S3_BUCKET="" \
+    S3_ENDPOINT="" \
+    S3_SECRET_ACCESS_KEY=""
+
+# Model Variables
+ENV \
+    # AI21
+    AI21_API_KEY="" AI21_MODEL_LIST="" \
+    # Ai360
+    AI360_API_KEY="" AI360_MODEL_LIST="" \
+    # Anthropic
+    ANTHROPIC_API_KEY="" ANTHROPIC_MODEL_LIST="" ANTHROPIC_PROXY_URL="" \
+    # Amazon Bedrock
+    AWS_ACCESS_KEY_ID="" AWS_SECRET_ACCESS_KEY="" AWS_REGION="" AWS_BEDROCK_MODEL_LIST="" \
+    # Azure OpenAI
+    AZURE_API_KEY="" AZURE_API_VERSION="" AZURE_ENDPOINT="" AZURE_MODEL_LIST="" \
+    # Baichuan
+    BAICHUAN_API_KEY="" BAICHUAN_MODEL_LIST="" \
+    # DeepSeek
+    DEEPSEEK_API_KEY="" DEEPSEEK_MODEL_LIST="" \
+    # Fireworks AI
+    FIREWORKSAI_API_KEY="" FIREWORKSAI_MODEL_LIST="" \
+    # GitHub
+    GITHUB_TOKEN="" GITHUB_MODEL_LIST="" \
+    # Google
+    GOOGLE_API_KEY="" GOOGLE_MODEL_LIST="" GOOGLE_PROXY_URL="" \
+    # Groq
+    GROQ_API_KEY="" GROQ_MODEL_LIST="" GROQ_PROXY_URL="" \
+    # HuggingFace
+    HUGGINGFACE_API_KEY="" HUGGINGFACE_MODEL_LIST="" HUGGINGFACE_PROXY_URL="" \
+    # Hunyuan
+    HUNYUAN_API_KEY="" HUNYUAN_MODEL_LIST="" \
+    # Minimax
+    MINIMAX_API_KEY="" MINIMAX_MODEL_LIST="" \
+    # Mistral
+    MISTRAL_API_KEY="" MISTRAL_MODEL_LIST="" \
+    # Moonshot
+    MOONSHOT_API_KEY="" MOONSHOT_MODEL_LIST="" MOONSHOT_PROXY_URL="" \
+    # Novita
+    NOVITA_API_KEY="" NOVITA_MODEL_LIST="" \
+    # Ollama
+    OLLAMA_MODEL_LIST="" OLLAMA_PROXY_URL="" \
+    # OpenAI
+    OPENAI_API_KEY="" OPENAI_MODEL_LIST="" OPENAI_PROXY_URL="" \
+    # OpenRouter
+    OPENROUTER_API_KEY="" OPENROUTER_MODEL_LIST="" \
+    # Perplexity
+    PERPLEXITY_API_KEY="" PERPLEXITY_MODEL_LIST="" PERPLEXITY_PROXY_URL="" \
+    # Qwen
+    QWEN_API_KEY="" QWEN_MODEL_LIST="" \
+    # SenseNova
+    SENSENOVA_ACCESS_KEY_ID="" SENSENOVA_ACCESS_KEY_SECRET="" SENSENOVA_MODEL_LIST="" \
+    # SiliconCloud
+    SILICONCLOUD_API_KEY="" SILICONCLOUD_MODEL_LIST="" SILICONCLOUD_PROXY_URL="" \
+    # Spark
+    SPARK_API_KEY="" SPARK_MODEL_LIST="" \
+    # Stepfun
+    STEPFUN_API_KEY="" STEPFUN_MODEL_LIST="" \
+    # Taichu
+    TAICHU_API_KEY="" TAICHU_MODEL_LIST="" \
+    # TogetherAI
+    TOGETHERAI_API_KEY="" TOGETHERAI_MODEL_LIST="" \
+    # Upstage
+    UPSTAGE_API_KEY="" UPSTAGE_MODEL_LIST="" \
+    # Wenxin
+    WENXIN_ACCESS_KEY="" WENXIN_SECRET_KEY="" WENXIN_MODEL_LIST="" \
+    # 01.AI
+    ZEROONE_API_KEY="" ZEROONE_MODEL_LIST="" \
+    # Zhipu
+    ZHIPU_API_KEY="" ZHIPU_MODEL_LIST=""
+
+USER nextjs
+
+EXPOSE 3210/tcp
+
+ENTRYPOINT ["/bin/node"]
+
+CMD ["/app/startServer.js"]

LICENSE

@@ -1,21 +1,38 @@
-MIT License
+Apache License Version 2.0
 
-Copyright (c) 2023 - current LobeHub
+Copyright (c) 2024/06/17 - current LobeHub LLC. All rights reserved.
 
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
+----------
 
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
+From 1.0, LobeChat is licensed under the Apache License 2.0, with the following additional conditions:
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+1. The commercial usage of LobeChat:
+
+  a. LobeChat may be utilized commercially, including as a frontend and backend service without modifying the source code.
+
+  b. a commercial license must be obtained from the producer if you want to develop and distribute a derivative work based on LobeChat.
+
+Please contact hello@lobehub.com by email to inquire about licensing matters.
+
+
+2. As a contributor, you should agree that:
+
+  a. The producer can adjust the open-source agreement to be more strict or relaxed as deemed necessary.
+
+  b. Your contributed code may be used for commercial purposes, including but not limited to its cloud edition.
+
+Apart from the specific conditions mentioned above, all other rights and restrictions follow the Apache License 2.0. Detailed information about the Apache License 2.0 can be found at http://www.apache.org/licenses/LICENSE-2.0.
+
+----------
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

README.ja-JP.md

@@ -0,0 +1,809 @@
+<div align="center"><a name="readme-top"></a>
+
+[![][image-banner]][vercel-link]
+
+# Lobe Chat
+
+オープンソースのモダンデザインChatGPT/LLMs UI/フレームワーク。<br/>
+音声合成、マルチモーダル、拡張可能な（[function call][docs-functionc-call]）プラグインシステムをサポート。<br/>
+プライベートなOpenAI ChatGPT/Claude/Gemini/Groq/Ollamaチャットアプリケーションをワンクリックで**無料**でデプロイ。
+
+[English](./README.md) · [简体中文](./README.zh-CN.md) · **日本語** · [公式サイト][official-site] · [変更履歴](./CHANGELOG.md) · [ドキュメント][docs] · [ブログ][blog] · [フィードバック][github-issues-link]
+
+<!-- SHIELD GROUP -->
+
+[![][github-release-shield]][github-release-link]
+[![][docker-release-shield]][docker-release-link]
+[![][vercel-shield]][vercel-link]
+[![][discord-shield]][discord-link]<br/>
+[![][codecov-shield]][codecov-link]
+[![][github-action-test-shield]][github-action-test-link]
+[![][github-action-release-shield]][github-action-release-link]
+[![][github-releasedate-shield]][github-releasedate-link]<br/>
+[![][github-contributors-shield]][github-contributors-link]
+[![][github-forks-shield]][github-forks-link]
+[![][github-stars-shield]][github-stars-link]
+[![][github-issues-shield]][github-issues-link]
+[![][github-license-shield]][github-license-link]<br>
+[![][sponsor-shield]][sponsor-link]
+
+**LobeChatリポジトリを共有**
+
+[![][share-x-shield]][share-x-link]
+[![][share-telegram-shield]][share-telegram-link]
+[![][share-whatsapp-shield]][share-whatsapp-link]
+[![][share-reddit-shield]][share-reddit-link]
+[![][share-weibo-shield]][share-weibo-link]
+[![][share-mastodon-shield]][share-mastodon-link]
+[![][share-linkedin-shield]][share-linkedin-link]
+
+<sup>新しい時代の思考と創造を先導します。あなたのために、スーパー個人のために作られました。</sup>
+
+[![][github-trending-shield]][github-trending-url]
+
+[![][image-overview]][vercel-link]
+
+</div>
+
+<details>
+<summary><kbd>目次</kbd></summary>
+
+#### TOC
+
+- [👋🏻 はじめに & コミュニティに参加](#-はじめに--コミュニティに参加)
+- [✨ 特徴](#-特徴)
+  - [`1` マルチモデルサービスプロバイダーのサポート](#1-マルチモデルサービスプロバイダーのサポート)
+  - [`2` ローカル大規模言語モデル (LLM) のサポート](#2-ローカル大規模言語モデル-llm-のサポート)
+  - [`3` モデルの視覚認識](#3-モデルの視覚認識)
+  - [`4` TTS & STT 音声会話](#4-tts--stt-音声会話)
+  - [`5` テキストから画像生成](#5-テキストから画像生成)
+  - [`6` プラグインシステム (Function Calling)](#6-プラグインシステム-function-calling)
+  - [`7` エージェントマーケット (GPTs)](#7-エージェントマーケット-gpts)
+  - [`8` ローカル / リモートデータベースのサポート](#8-ローカル--リモートデータベースのサポート)
+  - [`9` マルチユーザ管理のサポート](#9-マルチユーザ管理のサポート)
+  - [`10` プログレッシブウェブアプリ (PWA)](#10-プログレッシブウェブアプリ-pwa)
+  - [`11` モバイルデバイスの適応](#11-モバイルデバイスの適応)
+  - [`12` カスタムテーマ](#12-カスタムテーマ)
+  - [`*` その他の特徴](#-その他の特徴)
+- [⚡️ パフォーマンス](#️-パフォーマンス)
+- [🛳 自己ホスティング](#-自己ホスティング)
+  - [`A` Vercel、Zeabur、Sealosでのデプロイ](#a-vercelzeabursealosでのデプロイ)
+  - [`B` Dockerでのデプロイ](#b-dockerでのデプロイ)
+  - [環境変数](#環境変数)
+- [📦 エコシステム](#-エコシステム)
+- [🧩 プラグイン](#-プラグイン)
+- [⌨️ ローカル開発](#️-ローカル開発)
+- [🤝 貢献](#-貢献)
+- [❤️ スポンサー](#️-スポンサー)
+- [🔗 その他の製品](#-その他の製品)
+
+####
+
+<br/>
+
+</details>
+
+## 👋🏻 はじめに & コミュニティに参加
+
+私たちは、AIGCのためのモダンデザインコンポーネントとツールを提供することを目指すデザインエンジニアのグループです。
+ブートストラッピングアプローチを採用することで、開発者とユーザーに対してよりオープンで透明性のある、使いやすい製品エコシステムを提供することを目指しています。
+
+ユーザーやプロの開発者にとって、LobeHubはあなたのAIエージェントの遊び場となるでしょう。LobeChatは現在アクティブに開発中であり、遭遇した[問題][issues-link]についてのフィードバックを歓迎します。
+
+| [![][vercel-shield-badge]][vercel-link]   | インストールや登録は不要です！私たちのウェブサイトにアクセスして、直接体験してください。                           |
+| :---------------------------------------- | :----------------------------------------------------------------------------------------------------------------- |
+| [![][discord-shield-badge]][discord-link] | 私たちのDiscordコミュニティに参加しましょう！ここでは、LobeHubの開発者や他の熱心なユーザーとつながることができます。 |
+
+> \[!IMPORTANT]
+>
+> **スターを付けてください**。GitHubからのすべてのリリース通知を遅延なく受け取ることができます\~ ⭐️
+
+[![][image-star]][github-stars-link]
+
+<details>
+  <summary><kbd>スター履歴</kbd></summary>
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=lobehub%2Flobe-chat&theme=dark&type=Date">
+    <img width="100%" src="https://api.star-history.com/svg?repos=lobehub%2Flobe-chat&type=Date">
+  </picture>
+</details>
+
+## ✨ 特徴
+
+[![][image-feat-privoder]][docs-feat-provider]
+
+### `1` [マルチモデルサービスプロバイダーのサポート][docs-feat-provider]
+
+LobeChatの継続的な開発において、AI会話サービスを提供する際のモデルサービスプロバイダーの多様性がコミュニティのニーズを満たすために重要であることを深く理解しています。そのため、単一のモデルサービスプロバイダーに限定せず、複数のモデルサービスプロバイダーをサポートすることで、ユーザーにより多様で豊富な会話の選択肢を提供しています。
+
+このようにして、LobeChatは異なるユーザーのニーズにより柔軟に対応し、開発者にも幅広い選択肢を提供します。
+
+#### サポートされているモデルサービスプロバイダー
+
+以下のモデルサービスプロバイダーをサポートしています：
+
+- **AWS Bedrock**：AWS Bedrockサービスと統合され、**Claude / LLama2**などのモデルをサポートし、強力な自然言語処理能力を提供します。[詳細はこちら](https://aws.amazon.com/cn/bedrock)
+- **Anthropic (Claude)**：Anthropicの**Claude**シリーズモデルにアクセスし、Claude 3およびClaude 2を含む、マルチモーダル機能と拡張コンテキストで業界の新しいベンチマークを設定します。[詳細はこちら](https://www.anthropic.com/claude)
+- **Google AI (Gemini Pro, Gemini Vision)**：Googleの**Gemini**シリーズモデルにアクセスし、GeminiおよびGemini Proを含む、高度な言語理解と生成をサポートします。[詳細はこちら](https://deepmind.google/technologies/gemini/)
+- **Groq**：GroqのAIモデルにアクセスし、メッセージシーケンスを効率的に処理し、応答を生成し、マルチターンの対話や単一のインタラクションタスクを実行できます。[詳細はこちら](https://groq.com/)
+- **OpenRouter**：**Claude 3**、**Gemma**、**Mistral**、**Llama2**、**Cohere**などのモデルのルーティングをサポートし、インテリジェントなルーティング最適化をサポートし、使用効率を向上させ、オープンで柔軟です。[詳細はこちら](https://openrouter.ai/)
+- **01.AI (Yi Model)**：01.AIモデルを統合し、推論速度が速いAPIシリーズを提供し、処理時間を短縮しながら優れたモデル性能を維持します。[詳細はこちら](https://01.ai/)
+- **Together.ai**：Together Inference APIを通じて、100以上の主要なオープンソースのチャット、言語、画像、コード、および埋め込みモデルにアクセスできます。これらのモデルについては、使用した分だけ支払います。[詳細はこちら](https://www.together.ai/)
+- **ChatGLM**：智谱の**ChatGLM**シリーズモデル（GLM-4/GLM-4-vision/GLM-3-turbo）を追加し、ユーザーにもう一つの効率的な会話モデルの選択肢を提供します。[詳細はこちら](https://www.zhipuai.cn/)
+- **Moonshot AI (Dark Side of the Moon)**：中国の革新的なAIスタートアップであるMoonshotシリーズモデルと統合し、より深い会話理解を提供します。[詳細はこちら](https://www.moonshot.cn/)
+- **Minimax**：Minimaxモデルを統合し、MoEモデル**abab6**を含む、より広範な選択肢を提供します。[詳細はこちら](https://www.minimaxi.com/)
+- **DeepSeek**：中国の革新的なAIスタートアップであるDeepSeekシリーズモデルと統合し、性能と価格のバランスを取ったモデルを提供します。[詳細はこちら](https://www.deepseek.com/)
+- **Qwen**：Qwenシリーズモデルを統合し、最新の**qwen-turbo**、**qwen-plus**、**qwen-max**を含む。[詳細はこちら](https://help.aliyun.com/zh/dashscope/developer-reference/model-introduction)
+- **Novita AI**：**Llama**、**Mistral**、その他の主要なオープンソースモデルに最安値でアクセスできます。検閲されないロールプレイに参加し、創造的な議論を引き起こし、制限のないイノベーションを促進します。**使用した分だけ支払います。** [詳細はこちら](https://novita.ai/llm-api?utm_source=lobechat&utm_medium=ch&utm_campaign=api)
+
+同時に、ReplicateやPerplexityなどのモデルサービスプロバイダーのサポートも計画しています。これにより、サービスプロバイダーのライブラリをさらに充実させることができます。LobeChatがあなたのお気に入りのサービスプロバイダーをサポートすることを希望する場合は、[コミュニティディスカッション](https://github.com/lobehub/lobe-chat/discussions/1284)に参加してください。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+[![][image-feat-local]][docs-feat-local]
+
+### `2` [ローカル大規模言語モデル (LLM) のサポート][docs-feat-local]
+
+特定のユーザーのニーズに応えるために、LobeChatは[Ollama](https://ollama.ai)に基づいてローカルモデルの使用をサポートしており、ユーザーが自分自身またはサードパーティのモデルを柔軟に使用できるようにしています。
+
+> \[!TIP]
+>
+> [📘 LobeChatでのOllamaの使用][docs-usage-ollama]について詳しくはこちらをご覧ください。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+[![][image-feat-vision]][docs-feat-vision]
+
+### `3` [モデルの視覚認識][docs-feat-vision]
+
+LobeChatは、OpenAIの最新の視覚認識機能を備えた[`gpt-4-vision`](https://platform.openai.com/docs/guides/vision)モデルをサポートしています。
+これは視覚を認識できるマルチモーダルインテリジェンスです。ユーザーは簡単に画像をアップロードしたり、画像をドラッグアンドドロップして対話ボックスに入れることができ、
+エージェントは画像の内容を認識し、これに基づいてインテリジェントな会話を行い、よりスマートで多様なチャットシナリオを作成します。
+
+この機能は、新しいインタラクティブな方法を提供し、コミュニケーションがテキストを超えて視覚要素を含むことを可能にします。
+日常の使用での画像共有や特定の業界での画像解釈に関係なく、エージェントは優れた会話体験を提供します。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+[![][image-feat-tts]][docs-feat-tts]
+
+### `4` [TTS & STT 音声会話][docs-feat-tts]
+
+LobeChatは、テキストから音声への変換（Text-to-Speech、TTS）および音声からテキストへの変換（Speech-to-Text、STT）技術をサポートしており、
+テキストメッセージを明瞭な音声出力に変換し、ユーザーが実際の人と話しているかのように対話エージェントと対話できるようにします。
+ユーザーは、エージェントに適した音声を選択することができます。
+
+さらに、TTSは聴覚学習を好む人や忙しい中で情報を受け取りたい人にとって優れたソリューションを提供します。
+LobeChatでは、異なる地域や文化的背景のユーザーのニーズに応えるために、さまざまな高品質の音声オプション（OpenAI Audio、Microsoft Edge Speech）を慎重に選択しました。
+ユーザーは、個人の好みや特定のシナリオに応じて適切な音声を選択し、パーソナライズされたコミュニケーション体験を得ることができます。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+[![][image-feat-t2i]][docs-feat-t2i]
+
+### `5` [テキストから画像生成][docs-feat-t2i]
+
+最新のテキストから画像生成技術をサポートし、LobeChatはユーザーがエージェントとの対話中に直接画像作成ツールを呼び出すことができるようになりました。
+[`DALL-E 3`](https://openai.com/dall-e-3)、[`MidJourney`](https://www.midjourney.com/)、[`Pollinations`](https://pollinations.ai/)などのAIツールの能力を活用することで、
+エージェントはあなたのアイデアを画像に変えることができます。
+
+これにより、プライベートで没入感のある創造プロセスが可能になり、個人的な対話に視覚的なストーリーテリングをシームレスに統合することができます。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+[![][image-feat-plugin]][docs-feat-plugin]
+
+### `6` [プラグインシステム (Function Calling)][docs-feat-plugin]
+
+LobeChatのプラグインエコシステムは、そのコア機能の重要な拡張であり、LobeChatアシスタントの実用性と柔軟性を大幅に向上させます。
+
+<video controls src="https://github.com/lobehub/lobe-chat/assets/28616219/f29475a3-f346-4196-a435-41a6373ab9e2" muted="false"></video>
+
+プラグインを利用することで、LobeChatアシスタントはリアルタイムの情報を取得して処理することができ、ウェブ情報を検索し、ユーザーに即時かつ関連性の高いニュースを提供することができます。
+
+さらに、これらのプラグインはニュースの集約に限定されず、他の実用的な機能にも拡張できます。たとえば、ドキュメントの迅速な検索、画像の生成、Bilibili、Steamなどのさまざまなプラットフォームからのデータの取得、さまざまなサードパーティサービスとの連携などです。
+
+> \[!TIP]
+>
+> [📘 プラグインの使用][docs-usage-plugin]について詳しくはこちらをご覧ください。
+
+<!-- PLUGIN LIST -->
+
+| 最近の提出                                                                                                          | 説明                                                                                                                               |
+| ------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| [ショッピングツール](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **shoppingtools** on **2024-07-19**</sup> | eBayとAliExpressで製品を検索し、eBayのイベントとクーポンを見つけます。プロンプトの例を取得します。<br/>`ショッピング` `e-bay` `ali-express` `クーポン` |
+| [Savvy Trader AI](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **savvytrader** on **2024-06-27**</sup>  | リアルタイムの株式、暗号通貨、その他の投資データ。<br/>`株式` `分析`                                                                   |
+| [ソーシャル検索](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **say-apps** on **2024-06-02**</sup>       | ソーシャル検索は、ツイート、ユーザー、フォロワー、画像、メディアなどへのアクセスを提供します。<br/>`ソーシャル` `ツイッター` `x` `検索`                |
+| [スペース](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **automateyournetwork** on **2024-05-12**</sup>    | NASAを含む宇宙データ。<br/>`宇宙` `nasa`                                                                                             |
+
+> 📊 合計プラグイン数: [<kbd>**52**</kbd>](https://github.com/lobehub/lobe-chat-plugins)
+
+ <!-- PLUGIN LIST -->
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+[![][image-feat-agent]][docs-feat-agent]
+
+### `7` [エージェントマーケット (GPTs)][docs-feat-agent]
+
+LobeChatエージェントマーケットプレイスでは、クリエイターが多くの優れたエージェントを発見できる活気に満ちた革新的なコミュニティを提供しています。
+これらのエージェントは、仕事のシナリオで重要な役割を果たすだけでなく、学習プロセスでも大いに便利です。
+私たちのマーケットプレイスは、単なるショーケースプラットフォームではなく、協力の場でもあります。ここでは、誰もが自分の知恵を貢献し、開発したエージェントを共有できます。
+
+> \[!TIP]
+>
+> [🤖/🏪 エージェントを提出][submit-agents-link]することで、簡単にエージェント作品をプラットフォームに提出できます。
+> 重要なのは、LobeChatが高度な自動化国際化（i18n）ワークフローを確立しており、
+> あなたのエージェントを複数の言語バージョンにシームレスに翻訳できることです。
+> これにより、ユーザーがどの言語を話していても、エージェントを障害なく体験できます。
+
+> \[!IMPORTANT]
+>
+> すべてのユーザーがこの成長するエコシステムに参加し、エージェントの反復と最適化に参加することを歓迎します。
+> 一緒に、より面白く、実用的で革新的なエージェントを作成し、エージェントの多様性と実用性をさらに豊かにしましょう。
+
+<!-- AGENT LIST -->
+
+| 最近の提出                                                                                                                                                                                                 | 説明                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Cプログラム学習アシスタント](https://chat-preview.lobehub.com/market?agent=sichuan-university-941-c-programming-assistant)<br/><sup>By **[YBGuoYang](https://github.com/YBGuoYang)** on **2024-07-28**</sup> | Cプログラム設計の学習を支援します<br/>`941`                                                                                                                                                                                                                                                                                                                                                                                |
+| [ブランドパイオニア](https://chat-preview.lobehub.com/market?agent=brand-pioneer)<br/><sup>By **[SaintFresh](https://github.com/SaintFresh)** on **2024-07-25**</sup>                                               | ブランド開発の専門家、思想リーダー、ブランド戦略のスーパー天才、ブランドビジョナリー。ブランドパイオニアは、革新の最前線の探検家であり、自分の分野の発明者です。市場を提供し、専門分野の画期的な進展を特徴とする未来の世界を想像させてください。<br/>`ビジネス` `ブランドパイオニア` `ブランド開発` `ビジネスアシスタント` `ブランドナラティブ` |
+| [ネットワークセキュリティアシスタント](https://chat-preview.lobehub.com/market?agent=cybersecurity-copilot)<br/><sup>By **[huoji120](https://github.com/huoji120)** on **2024-07-23**</sup>                              | ログ、コード、逆コンパイルを分析し、問題を特定し、最適化の提案を提供するネットワークセキュリティの専門家アシスタント。<br/>`ネットワークセキュリティ` `トラフィック分析` `ログ分析` `コード逆コンパイル` `ctf`                                                                                                                                                                                                   |
+| [BIDOSx2](https://chat-preview.lobehub.com/market?agent=bidosx-2-v-2)<br/><sup>By **[SaintFresh](https://github.com/SaintFresh)** on **2024-07-21**</sup>                                                      | 従来のAIを超越する高度なAI LLM。'BIDOS'は、'ブランドのアイデア、開発、運営、スケーリング'と'ビジネスインテリジェンス決定最適化システム'の両方を意味します。<br/>`ブランド開発` `aiアシスタント` `市場分析` `戦略計画` `ビジネス最適化` `ビジネスインテリジェンス`                                                                                                   |
+
+> 📊 合計エージェント数: [<kbd>**307**</kbd> ](https://github.com/lobehub/lobe-chat-agents)
+
+ <!-- AGENT LIST -->
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+[![][image-feat-database]][docs-feat-database]
+
+### `8` [ローカル / リモートデータベースのサポート][docs-feat-database]
+
+LobeChatは、サーバーサイドデータベースとローカルデータベースの両方の使用をサポートしています。ニーズに応じて、適切なデプロイメントソリューションを選択できます：
+
+- **ローカルデータベース**：データとプライバシー保護に対するより多くの制御を希望するユーザーに適しています。LobeChatはCRDT（Conflict-Free Replicated Data Type）技術を使用してマルチデバイス同期を実現しています。これはシームレスなデータ同期体験を提供することを目的とした実験的な機能です。
+- **サーバーサイドデータベース**：より便利なユーザー体験を希望するユーザーに適しています。LobeChatはPostgreSQLをサーバーサイドデータベースとしてサポートしています。サーバーサイドデータベースの設定方法についての詳細なドキュメントは、[サーバーサイドデータベースの設定](https://lobehub.com/docs/self-hosting/advanced/server-database)をご覧ください。
+
+どのデータベースを選択しても、LobeChatは優れたユーザー体験を提供します。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+[![][image-feat-auth]][docs-feat-auth]
+
+### `9` [マルチユーザ管理のサポート][docs-feat-auth]
+
+LobeChatはマルチユーザ管理をサポートし、異なるニーズに応じて2つの主要なユーザ認証および管理ソリューションを提供します：
+
+- **next-auth**：LobeChatは、複数の認証方法（OAuth、メールログイン、資格情報ログインなど）をサポートする柔軟で強力な認証ライブラリである`next-auth`を統合しています。`next-auth`を使用すると、ユーザの登録、ログイン、セッション管理、ソーシャルログインなどの機能を簡単に実装し、ユーザデータのセキュリティとプライバシーを確保できます。
+
+- **Clerk**：より高度なユーザ管理機能が必要なユーザ向けに、LobeChatは`Clerk`もサポートしています。`Clerk`は、現代的なユーザ管理プラットフォームであり、多要素認証（MFA）、ユーザプロファイル管理、ログイン活動の監視など、より豊富な機能を提供します。`Clerk`を使用すると、より高いセキュリティと柔軟性を得ることができ、複雑なユーザ管理ニーズに簡単に対応できます。
+
+どのユーザ管理ソリューションを選択しても、LobeChatは優れたユーザー体験と強力な機能サポートを提供します。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+[![][image-feat-pwa]][docs-feat-pwa]
+
+### `10` [プログレッシブウェブアプリ (PWA)][docs-feat-pwa]
+
+私たちは、今日のマルチデバイス環境でユーザーにシームレスな体験を提供することの重要性を深く理解しています。
+そのため、プログレッシブウェブアプリケーション（[PWA](https://support.google.com/chrome/answer/9658361)）技術を採用しました。
+これは、ウェブアプリケーションをネイティブアプリに近い体験に引き上げるモダンなウェブ技術です。
+
+PWAを通じて、LobeChatはデスクトップとモバイルデバイスの両方で高度に最適化されたユーザー体験を提供しながら、その軽量で高性能な特性を維持します。
+視覚的および感覚的には、インターフェースを慎重に設計し、ネイティブアプリと区別がつかないようにし、
+スムーズなアニメーション、レスポンシブレイアウト、および異なるデバイスの画面解像度に適応するようにしています。
+
+> \[!NOTE]
+>
+> PWAのインストールプロセスに慣れていない場合は、以下の手順に従ってLobeChatをデスクトップアプリケーション（モバイルデバイスにも適用）として追加できます：
+>
+> - コンピュータでChromeまたはEdgeブラウザを起動します。
+> - LobeChatのウェブページにアクセスします。
+> - アドレスバーの右上にある<kbd>インストール</kbd>アイコンをクリックします。
+> - 画面の指示に従ってPWAのインストールを完了します。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+[![][image-feat-mobile]][docs-feat-mobile]
+
+### `11` [モバイルデバイスの適応][docs-feat-mobile]
+
+モバイルデバイスのユーザー体験を向上させるために、一連の最適化設計を行いました。現在、モバイルユーザー体験のバージョンを繰り返し改善しています。ご意見やアイデアがある場合は、GitHub IssuesやPull Requestsを通じてフィードバックをお寄せください。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+[![][image-feat-theme]][docs-feat-theme]
+
+### `12` [カスタムテーマ][docs-feat-theme]
+
+デザインエンジニアリング指向のアプリケーションとして、LobeChatはユーザーの個別体験を重視しており、
+柔軟で多様なテーマモードを導入しています。日中のライトモードと夜間のダークモードを含みます。
+テーマモードの切り替えに加えて、さまざまな色のカスタマイズオプションを提供し、ユーザーが自分の好みに応じてアプリケーションのテーマカラーを調整できるようにしています。
+落ち着いたダークブルー、活気のあるピーチピンク、プロフェッショナルなグレーホワイトなど、LobeChatでは自分のスタイルに合った色の選択肢を見つけることができます。
+
+> \[!TIP]
+>
+> デフォルトの設定は、ユーザーのシステムのカラーモードをインテリジェントに認識し、テーマを自動的に切り替えて、オペレーティングシステムと一貫した視覚体験を提供します。
+> 詳細を手動で制御するのが好きなユーザーには、直感的な設定オプションと、会話シナリオに対してチャットバブルモードとドキュメントモードの選択肢を提供します。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+### `*` その他の特徴
+
+これらの特徴に加えて、LobeChatは基本的な技術基盤も優れています：
+
+- [x] 💨 **迅速なデプロイ**：VercelプラットフォームまたはDockerイメージを使用して、ワンクリックでデプロイを行い、1分以内にプロセスを完了できます。複雑な設定は不要です。
+- [x] 🌐 **カスタムドメイン**：ユーザーが独自のドメインを持っている場合、プラットフォームにバインドして、どこからでも対話エージェントに迅速にアクセスできます。
+- [x] 🔒 **プライバシー保護**：すべてのデータはユーザーのブラウザにローカルに保存され、ユーザーのプライバシーを保護します。
+- [x] 💎 **洗練されたUIデザイン**：慎重に設計されたインターフェースで、エレガントな外観とスムーズなインタラクションを提供します。ライトモードとダークモードをサポートし、モバイルフレンドリーです。PWAサポートにより、よりネイティブに近い体験を提供します。
+- [x] 🗣️ **スムーズな会話体験**：流れるような応答により、スムーズな会話体験を提供します。Markdownレンダリングを完全にサポートし、コードのハイライト、LaTexの数式、Mermaidのフローチャートなどを含みます。
+
+> ✨ LobeChatの進化に伴い、さらに多くの機能が追加されます。
+
+---
+
+> \[!NOTE]
+>
+> 今後の[ロードマップ][github-project-link]計画は、Projectsセクションで確認できます。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+## ⚡️ パフォーマンス
+
+> \[!NOTE]
+>
+> 完全なレポートのリストは[📘 Lighthouseレポート][docs-lighthouse]で確認できます。
+
+|                   デスクトップ                   |                   モバイル                   |
+| :-----------------------------------------: | :----------------------------------------: |
+|              ![][chat-desktop]              |              ![][chat-mobile]              |
+| [📑 Lighthouseレポート][chat-desktop-report] | [📑 Lighthouseレポート][chat-mobile-report] |
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+## 🛳 自己ホスティング
+
+LobeChatは、Vercelと[Dockerイメージ][docker-release-link]を使用した自己ホスティングバージョンを提供しています。これにより、事前の知識がなくても数分で独自のチャットボットをデプロイできます。
+
+> \[!TIP]
+>
+> [📘 独自のLobeChatを構築する][docs-self-hosting]について詳しくはこちらをご覧ください。
+
+### `A` Vercel、Zeabur、Sealosでのデプロイ
+
+このサービスをVercelまたはZeaburでデプロイしたい場合は、以下の手順に従ってください：
+
+- [OpenAI API Key](https://platform.openai.com/account/api-keys)を準備します。
+- 下のボタンをクリックしてデプロイを開始します：GitHubアカウントで直接ログインし、環境変数セクションに`OPENAI_API_KEY`（必須）と`ACCESS_CODE`（推奨）を入力します。
+- デプロイが完了したら、使用を開始できます。
+- カスタムドメインをバインド（オプション）：Vercelが割り当てたドメインのDNSは一部の地域で汚染されているため、カスタムドメインをバインドすることで直接接続できます。
+
+<div align="center">
+
+|           Vercelでデプロイ            |                     Zeaburでデプロイ                      |                     Sealosでデプロイ                      |
+| :-------------------------------------: | :---------------------------------------------------------: | :---------------------------------------------------------: |
+| [![][deploy-button-image]][deploy-link] | [![][deploy-on-zeabur-button-image]][deploy-on-zeabur-link] | [![][deploy-on-sealos-button-image]][deploy-on-sealos-link] |
+
+</div>
+
+#### フォーク後
+
+フォーク後、リポジトリのアクションページで他のアクションを無効にし、アップストリーム同期アクションのみを保持します。
+
+#### 更新を維持
+
+READMEのワンクリックデプロイ手順に従って独自のプロジェクトをデプロイした場合、「更新が利用可能です」というプロンプトが常に表示されることがあります。これは、Vercelがデフォルトで新しいプロジェクトを作成し、フォークしないため、更新を正確に検出できないためです。
+
+> \[!TIP]
+>
+> [📘 最新バージョンと自動同期][docs-upstream-sync]の手順に従って再デプロイすることをお勧めします。
+
+<br/>
+
+### `B` Dockerでのデプロイ
+
+[![][docker-release-shield]][docker-release-link]
+[![][docker-size-shield]][docker-size-link]
+[![][docker-pulls-shield]][docker-pulls-link]
+
+LobeChatサービスを独自のプライベートデバイスにデプロイするためのDockerイメージを提供しています。以下のコマンドを使用してLobeChatサービスを開始します：
+
+```fish
+$ docker run -d -p 3210:3210 \
+  -e OPENAI_API_KEY=sk-xxxx \
+  -e ACCESS_CODE=lobe66 \
+  --name lobe-chat \
+  lobehub/lobe-chat
+```
+
+> \[!TIP]
+>
+> OpenAIサービスをプロキシ経由で使用する必要がある場合は、`OPENAI_PROXY_URL`環境変数を使用してプロキシアドレスを設定できます：
+
+```fish
+$ docker run -d -p 3210:3210 \
+  -e OPENAI_API_KEY=sk-xxxx \
+  -e OPENAI_PROXY_URL=https://api-proxy.com/v1 \
+  -e ACCESS_CODE=lobe66 \
+  --name lobe-chat \
+  lobehub/lobe-chat
+```
+
+> \[!NOTE]
+>
+> Dockerを使用したデプロイの詳細な手順については、[📘 Dockerデプロイガイド][docs-docker]を参照してください。
+
+<br/>
+
+### 環境変数
+
+このプロジェクトは、環境変数で設定される追加の構成項目を提供します：
+
+| 環境変数            | 必須 | 説明                                                                                                                                                               | 例                                                                                                              |
+| -------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
+| `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` または `rtrt_ewee3@09!` または `code1,code2,code3`                                                            |
+| `OPENAI_MODEL_LIST`  | いいえ       | モデルリストをコントロールするために使用します。モデルを追加するには `+` を、モデルを非表示にするには `-` を、モデルの表示名をカンマ区切りでカスタマイズするには `model_name=display_name` を使用します。 | `qwen-7b-chat,+glm-6b,-gpt-3.5-turbo`                                                                                |
+
+> \[!NOTE]
+>
+> 環境変数の完全なリストは [📘環境変数][docs-env-var] にあります
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+## 📦 エコシステム
+
+| NPM                               | リポジトリ                              | 説明                                                                                           | バージョン                                   |
+| --------------------------------- | --------------------------------------- | ----------------------------------------------------------------------------------------------------- | ----------------------------------------- |
+| [@lobehub/ui][lobe-ui-link]       | [lobehub/lobe-ui][lobe-ui-github]       | AIGC ウェブアプリケーション構築専用のオープンソースUIコンポーネントライブラリ。                         | [![][lobe-ui-shield]][lobe-ui-link]       |
+| [@lobehub/icons][lobe-icons-link] | [lobehub/lobe-icons][lobe-icons-github] | 人気の AI/LLM モデルブランドの SVG ロゴとアイコン集。                                            | [![][lobe-icons-shield]][lobe-icons-link] |
+| [@lobehub/tts][lobe-tts-link]     | [lobehub/lobe-tts][lobe-tts-github]     | 高品質で信頼性の高い TTS/STT React Hooks ライブラリ                                                   | [![][lobe-tts-shield]][lobe-tts-link]     |
+| [@lobehub/lint][lobe-lint-link]   | [lobehub/lobe-lint][lobe-lint-github]   | LobeHub の ESlint、Stylelint、Commitlint、Prettier、Remark、Semantic Release の設定。 | [![][lobe-lint-shield]][lobe-lint-link]   |
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+## 🧩 プラグイン
+
+プラグインは、LobeChatの[関数呼び出し][docs-functionc-call]機能を拡張する手段を提供します。プラグインを使用して、新しい関数呼び出しやメッセージ結果の新しいレンダリング方法を導入することができます。プラグイン開発に興味がある方は、Wikiの[📘プラグイン開発ガイド][docs-plugin-dev]を参照してください。
+
+- [lobe-chat-plugins][lobe-chat-plugins]: これはLobeChatのプラグインインデックスです。このリポジトリからindex.jsonにアクセスし、LobeChatで利用可能なプラグインのリストをユーザに表示します。
+- [chat-plugin-template][chat-plugin-template]: これはLobeChatプラグイン開発用のプラグインテンプレートです。
+- [@lobehub/chat-plugin-sdk][chat-plugin-sdk]: LobeChatプラグインSDKは、Lobe Chat用の優れたチャットプラグインの作成を支援します。
+- [@lobehub/chat-plugins-gateway][chat-plugins-gateway]: LobeChat Plugins Gatewayは、LobeChatプラグインのためのゲートウェイを提供するバックエンドサービスです。このサービスはVercelを使用してデプロイされます。プライマリAPIのPOST /api/v1/runnerはEdge Functionとしてデプロイされます。
+
+> \[!NOTE]
+>
+> プラグインシステムは現在大規模な開発中です。詳しくは以下の issue をご覧ください:
+>
+> - [x] [**プラグインフェイズ 1**](https://github.com/lobehub/lobe-chat/issues/73): プラグインを本体から分離し、メンテナンスのためにプラグインを独立したリポジトリに分割し、プラグインの動的ロードを実現する。
+> - [x] [**プラグインフェイズ 2**](https://github.com/lobehub/lobe-chat/issues/97): プラグイン使用の安全性と安定性、より正確な異常状態の提示、プラグインアーキテクチャの保守性、開発者フレンドリー。
+> - [x] [**プラグインフェイズ 3**](https://github.com/lobehub/lobe-chat/issues/149): より高度で包括的なカスタマイズ機能、プラグイン認証のサポート、サンプル。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+## ⌨️ ローカル開発
+
+GitHub Codespaces を使ってオンライン開発ができます:
+
+[![][codespaces-shield]][codespaces-link]
+
+Or clone it for local development:
+
+```fish
+$ git clone https://github.com/lobehub/lobe-chat.git
+$ cd lobe-chat
+$ pnpm install
+$ pnpm dev
+```
+
+より詳しい情報をお知りになりたい方は、[📘開発ガイド][docs-dev-guide]をご覧ください。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+## 🤝 コントリビュート
+
+どのようなタイプのコントリビュートも大歓迎です;コードを提供することに興味がある方は、GitHub の [Issues][github-issues-link] や [Projects][github-project-link] をチェックして、あなたの力をお貸しください。
+
+> \[!TIP]
+>
+> 私たちは技術主導のフォーラムを創設し、知識の交流とアイデアの交換を促進することで、相互のインスピレーションと協力的なイノベーションを生み出すことを目指しています。
+>
+> LobeChat の改善にご協力ください。製品設計のフィードバックやユーザー体験に関するディスカッションを直接お寄せください。
+>
+> **プリンシパルメンテナー:** [@arvinxx](https://github.com/arvinxx) [@canisminor1990](https://github.com/canisminor1990)
+
+[![][pr-welcome-shield]][pr-welcome-link]
+[![][submit-agents-shield]][submit-agents-link]
+[![][submit-plugin-shield]][submit-plugin-link]
+
+<a href="https://github.com/lobehub/lobe-chat/graphs/contributors" target="_blank">
+  <table>
+    <tr>
+      <th colspan="2">
+        <br><img src="https://contrib.rocks/image?repo=lobehub/lobe-chat"><br><br>
+      </th>
+    </tr>
+    <tr>
+      <td>
+        <picture>
+          <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-org-active-contributors/thumbnail.png?activity=active&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=2x3&color_scheme=dark">
+          <img src="https://next.ossinsight.io/widgets/official/compose-org-active-contributors/thumbnail.png?activity=active&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=2x3&color_scheme=light">
+        </picture>
+      </td>
+      <td rowspan="2">
+        <picture>
+          <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-org-participants-growth/thumbnail.png?activity=active&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=4x7&color_scheme=dark">
+          <img src="https://next.ossinsight.io/widgets/official/compose-org-participants-growth/thumbnail.png?activity=active&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=4x7&color_scheme=light">
+        </picture>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <picture>
+          <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-org-active-contributors/thumbnail.png?activity=new&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=2x3&color_scheme=dark">
+          <img src="https://next.ossinsight.io/widgets/official/compose-org-active-contributors/thumbnail.png?activity=new&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=2x3&color_scheme=light">
+        </picture>
+      </td>
+    </tr>
+  </table>
+</a>
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+## ❤️ スポンサー
+
+あなたの一度きりの寄付が、私たちの銀河系で輝きを放ちます！皆様は流れ星であり、私たちの旅路に迅速かつ明るい影響を与えます。私たちを信じてくださり、ありがとうございます。皆様の寛大なお気持ちが、私たちの使命に向かって、一度に輝かしい閃光を放つよう導いてくださるのです。
+
+<a href="https://opencollective.com/lobehub" target="_blank">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://github.com/lobehub/.github/blob/main/static/sponsor-dark.png?raw=true">
+    <img  src="https://github.com/lobehub/.github/blob/main/static/sponsor-light.png?raw=true">
+  </picture>
+</a>
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+## 🔗 その他の製品
+
+- **[🅰️ Lobe SD Theme][lobe-theme]:** Stable Diffusion WebUI のためのモダンなテーマ、絶妙なインターフェースデザイン、高度にカスタマイズ可能なUI、効率を高める機能。
+- **[⛵️ Lobe Midjourney WebUI][lobe-midjourney-webui]:** Midjourney の WebUI は、AI を活用しテキストプロンプトから豊富で多様な画像を素早く生成し、創造性を刺激して会話を盛り上げます。
+- **[🌏 Lobe i18n][lobe-i18n] :** Lobe i18n は ChatGPT を利用した国際化翻訳プロセスの自動化ツールです。大きなファイルの自動分割、増分更新、OpenAIモデル、APIプロキシ、温度のカスタマイズオプションなどの機能をサポートしています。
+- **[💌 Lobe Commit][lobe-commit]:** Lobe Commit は、Langchain/ChatGPT を活用して Gitmoji ベースのコミットメッセージを生成する CLI ツールです。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+---
+
+<details><summary><h4>📝 License</h4></summary>
+
+[![][fossa-license-shield]][fossa-license-link]
+
+</details>
+
+Copyright © 2024 [LobeHub][profile-link]. <br />
+This project is [Apache 2.0](./LICENSE) licensed.
+
+<!-- LINK GROUP -->
+
+[back-to-top]: https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square
+[blog]: https://lobehub.com/blog
+[chat-desktop]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/desktop/pagespeed.svg
+[chat-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/desktop/chat_preview_lobehub_com_chat.html
+[chat-mobile]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/mobile/pagespeed.svg
+[chat-mobile-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/mobile/chat_preview_lobehub_com_chat.html
+[chat-plugin-sdk]: https://github.com/lobehub/chat-plugin-sdk
+[chat-plugin-template]: https://github.com/lobehub/chat-plugin-template
+[chat-plugins-gateway]: https://github.com/lobehub/chat-plugins-gateway
+[codecov-link]: https://codecov.io/gh/lobehub/lobe-chat
+[codecov-shield]: https://img.shields.io/codecov/c/github/lobehub/lobe-chat?labelColor=black&style=flat-square&logo=codecov&logoColor=white
+[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-on-sealos-button-image]: https://raw.githubusercontent.com/labring-actions/templates/main/Deploy-on-Sealos.svg
+[deploy-on-sealos-link]: https://cloud.sealos.io/?openapp=system-template%3FtemplateName%3Dlobe-chat
+[deploy-on-zeabur-button-image]: https://zeabur.com/button.svg
+[deploy-on-zeabur-link]: https://zeabur.com/templates/VZGGTI
+[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
+[docker-pulls-shield]: https://img.shields.io/docker/pulls/lobehub/lobe-chat?color=45cc11&labelColor=black&style=flat-square
+[docker-release-link]: https://hub.docker.com/r/lobehub/lobe-chat
+[docker-release-shield]: https://img.shields.io/docker/v/lobehub/lobe-chat?color=369eff&label=docker&labelColor=black&logo=docker&logoColor=white&style=flat-square
+[docker-size-link]: https://hub.docker.com/r/lobehub/lobe-chat
+[docker-size-shield]: https://img.shields.io/docker/image-size/lobehub/lobe-chat?color=369eff&labelColor=black&style=flat-square
+[docs]: https://lobehub.com/docs/usage/start
+[docs-dev-guide]: https://github.com/lobehub/lobe-chat/wiki/index
+[docs-docker]: https://lobehub.com/docs/self-hosting/platform/docker
+[docs-env-var]: https://lobehub.com/docs/self-hosting/environment-variables
+[docs-feat-agent]: https://lobehub.com/docs/usage/features/agent-market
+[docs-feat-auth]: https://lobehub.com/docs/usage/features/auth
+[docs-feat-database]: https://lobehub.com/docs/usage/features/database
+[docs-feat-local]: https://lobehub.com/docs/usage/features/local-llm
+[docs-feat-mobile]: https://lobehub.com/docs/usage/features/mobile
+[docs-feat-plugin]: https://lobehub.com/docs/usage/features/plugin-system
+[docs-feat-provider]: https://lobehub.com/docs/usage/features/multi-ai-providers
+[docs-feat-pwa]: https://lobehub.com/docs/usage/features/pwa
+[docs-feat-t2i]: https://lobehub.com/docs/usage/features/text-to-image
+[docs-feat-theme]: https://lobehub.com/docs/usage/features/theme
+[docs-feat-tts]: https://lobehub.com/docs/usage/features/tts
+[docs-feat-vision]: https://lobehub.com/docs/usage/features/vision
+[docs-functionc-call]: https://lobehub.com/blog/openai-function-call
+[docs-lighthouse]: https://github.com/lobehub/lobe-chat/wiki/Lighthouse
+[docs-plugin-dev]: https://lobehub.com/docs/usage/plugins/development
+[docs-self-hosting]: https://lobehub.com/docs/self-hosting/start
+[docs-upstream-sync]: https://lobehub.com/docs/self-hosting/advanced/upstream-sync
+[docs-usage-ollama]: https://lobehub.com/docs/usage/providers/ollama
+[docs-usage-plugin]: https://lobehub.com/docs/usage/plugins/basic
+[fossa-license-link]: https://app.fossa.com/projects/git%2Bgithub.com%2Flobehub%2Flobe-chat
+[fossa-license-shield]: https://app.fossa.com/api/projects/git%2Bgithub.com%2Flobehub%2Flobe-chat.svg?type=large
+[github-action-release-link]: https://github.com/actions/workflows/lobehub/lobe-chat/release.yml
+[github-action-release-shield]: https://img.shields.io/github/actions/workflow/status/lobehub/lobe-chat/release.yml?label=release&labelColor=black&logo=githubactions&logoColor=white&style=flat-square
+[github-action-test-link]: https://github.com/actions/workflows/lobehub/lobe-chat/test.yml
+[github-action-test-shield]: https://img.shields.io/github/actions/workflow/status/lobehub/lobe-chat/test.yml?label=test&labelColor=black&logo=githubactions&logoColor=white&style=flat-square
+[github-contributors-link]: https://github.com/lobehub/lobe-chat/graphs/contributors
+[github-contributors-shield]: https://img.shields.io/github/contributors/lobehub/lobe-chat?color=c4f042&labelColor=black&style=flat-square
+[github-forks-link]: https://github.com/lobehub/lobe-chat/network/members
+[github-forks-shield]: https://img.shields.io/github/forks/lobehub/lobe-chat?color=8ae8ff&labelColor=black&style=flat-square
+[github-issues-link]: https://github.com/lobehub/lobe-chat/issues
+[github-issues-shield]: https://img.shields.io/github/issues/lobehub/lobe-chat?color=ff80eb&labelColor=black&style=flat-square
+[github-license-link]: https://github.com/lobehub/lobe-chat/blob/main/LICENSE
+[github-license-shield]: https://img.shields.io/badge/license-apache%202.0-white?labelColor=black&style=flat-square
+[github-project-link]: https://github.com/lobehub/lobe-chat/projects
+[github-release-link]: https://github.com/lobehub/lobe-chat/releases
+[github-release-shield]: https://img.shields.io/github/v/release/lobehub/lobe-chat?color=369eff&labelColor=black&logo=github&style=flat-square
+[github-releasedate-link]: https://github.com/lobehub/lobe-chat/releases
+[github-releasedate-shield]: https://img.shields.io/github/release-date/lobehub/lobe-chat?labelColor=black&style=flat-square
+[github-stars-link]: https://github.com/lobehub/lobe-chat/network/stargazers
+[github-stars-shield]: https://img.shields.io/github/stars/lobehub/lobe-chat?color=ffcb47&labelColor=black&style=flat-square
+[github-trending-shield]: https://trendshift.io/api/badge/repositories/2256
+[github-trending-url]: https://trendshift.io/repositories/2256
+[image-banner]: https://github.com/lobehub/lobe-chat/assets/28616219/9f155dff-4737-429f-9cad-a70a1a860c5f
+[image-feat-agent]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670869-f1ffbf66-42b6-42cf-a937-9ce1f8328514.png
+[image-feat-auth]: https://github.com/lobehub/lobe-chat/assets/17870709/8ce70e15-40df-451e-b700-66090fe5b8c2
+[image-feat-database]: https://github.com/lobehub/lobe-chat/assets/17870709/c27a0234-a4e9-40e5-8bcb-42d5ce7e40f9
+[image-feat-local]: https://github.com/lobehub/lobe-chat/assets/28616219/ca9a21bc-ea6c-4c90-bf4a-fa53b4fb2b5c
+[image-feat-mobile]: https://gw.alipayobjects.com/zos/kitchen/R441AuFS4W/mobile.webp
+[image-feat-plugin]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670883-33c43a5c-a512-467e-855c-fa299548cce5.png
+[image-feat-privoder]: https://github.com/lobehub/lobe-chat/assets/28616219/b164bc54-8ba2-4c1e-b2f2-f4d7f7e7a551
+[image-feat-pwa]: https://gw.alipayobjects.com/zos/kitchen/69x6bllkX3/pwa.webp
+[image-feat-t2i]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/297746445-0ff762b9-aa08-4337-afb7-12f932b6efbb.png
+[image-feat-theme]: https://gw.alipayobjects.com/zos/kitchen/pvus1lo%26Z7/darkmode.webp
+[image-feat-tts]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072124-c9853d8d-f1b5-44a8-a305-45ebc0f6d19a.png
+[image-feat-vision]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072129-382bdf30-e3d6-4411-b5a0-249710b8ba08.png
+[image-overview]: https://github.com/lobehub/lobe-chat/assets/17870709/56b95d48-f573-41cd-8b38-387bf88bc4bf
+[image-star]: https://github.com/lobehub/lobe-chat/assets/17870709/cb06b748-513f-47c2-8740-d876858d7855
+[issues-link]: https://img.shields.io/github/issues/lobehub/lobe-chat.svg?style=flat
+[lobe-chat-plugins]: https://github.com/lobehub/lobe-chat-plugins
+[lobe-commit]: https://github.com/lobehub/lobe-commit/tree/master/packages/lobe-commit
+[lobe-i18n]: https://github.com/lobehub/lobe-commit/tree/master/packages/lobe-i18n
+[lobe-icons-github]: https://github.com/lobehub/lobe-icons
+[lobe-icons-link]: https://www.npmjs.com/package/@lobehub/icons
+[lobe-icons-shield]: https://img.shields.io/npm/v/@lobehub/icons?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
+[lobe-lint-github]: https://github.com/lobehub/lobe-lint
+[lobe-lint-link]: https://www.npmjs.com/package/@lobehub/lint
+[lobe-lint-shield]: https://img.shields.io/npm/v/@lobehub/lint?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
+[lobe-midjourney-webui]: https://github.com/lobehub/lobe-midjourney-webui
+[lobe-theme]: https://github.com/lobehub/sd-webui-lobe-theme
+[lobe-tts-github]: https://github.com/lobehub/lobe-tts
+[lobe-tts-link]: https://www.npmjs.com/package/@lobehub/tts
+[lobe-tts-shield]: https://img.shields.io/npm/v/@lobehub/tts?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
+[lobe-ui-github]: https://github.com/lobehub/lobe-ui
+[lobe-ui-link]: https://www.npmjs.com/package/@lobehub/ui
+[lobe-ui-shield]: https://img.shields.io/npm/v/@lobehub/ui?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
+[official-site]: https://lobehub.com
+[pr-welcome-link]: https://github.com/lobehub/lobe-chat/pulls
+[pr-welcome-shield]: https://img.shields.io/badge/🤯_pr_welcome-%E2%86%92-ffcb47?labelColor=black&style=for-the-badge
+[profile-link]: https://github.com/lobehub
+[share-linkedin-link]: https://linkedin.com/feed
+[share-linkedin-shield]: https://img.shields.io/badge/-share%20on%20linkedin-black?labelColor=black&logo=linkedin&logoColor=white&style=flat-square
+[share-mastodon-link]: https://mastodon.social/share?text=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source,%20extensible%20(Function%20Calling),%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT/LLM%20web%20application.%20https://github.com/lobehub/lobe-chat%20#chatbot%20#chatGPT%20#openAI
+[share-mastodon-shield]: https://img.shields.io/badge/-share%20on%20mastodon-black?labelColor=black&logo=mastodon&logoColor=white&style=flat-square
+[share-reddit-link]: https://www.reddit.com/submit?title=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source%2C%20extensible%20%28Function%20Calling%29%2C%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT%2FLLM%20web%20application.%20%23chatbot%20%23chatGPT%20%23openAI&url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat
+[share-reddit-shield]: https://img.shields.io/badge/-share%20on%20reddit-black?labelColor=black&logo=reddit&logoColor=white&style=flat-square
+[share-telegram-link]: https://t.me/share/url"?text=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source%2C%20extensible%20%28Function%20Calling%29%2C%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT%2FLLM%20web%20application.%20%23chatbot%20%23chatGPT%20%23openAI&url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat
+[share-telegram-shield]: https://img.shields.io/badge/-share%20on%20telegram-black?labelColor=black&logo=telegram&logoColor=white&style=flat-square
+[share-weibo-link]: http://service.weibo.com/share/share.php?sharesource=weibo&title=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source%2C%20extensible%20%28Function%20Calling%29%2C%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT%2FLLM%20web%20application.%20%23chatbot%20%23chatGPT%20%23openAI&url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat
+[share-weibo-shield]: https://img.shields.io/badge/-share%20on%20weibo-black?labelColor=black&logo=sinaweibo&logoColor=white&style=flat-square
+[share-whatsapp-link]: https://api.whatsapp.com/send?text=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source%2C%20extensible%20%28Function%20Calling%29%2C%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT%2FLLM%20web%20application.%20https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat%20%23chatbot%20%23chatGPT%20%23openAI
+[share-whatsapp-shield]: https://img.shields.io/badge/-share%20on%20whatsapp-black?labelColor=black&logo=whatsapp&logoColor=white&style=flat-square
+[share-x-link]: https://x.com/intent/tweet?hashtags=chatbot%2CchatGPT%2CopenAI&text=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source%2C%20extensible%20%28Function%20Calling%29%2C%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT%2FLLM%20web%20application.&url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat
+[share-x-shield]: https://img.shields.io/badge/-share%20on%20x-black?labelColor=black&logo=x&logoColor=white&style=flat-square
+[sponsor-link]: https://opencollective.com/lobehub 'Become ❤️ LobeHub Sponsor'
+[sponsor-shield]: https://img.shields.io/badge/-Sponsor%20LobeHub-f04f88?logo=opencollective&logoColor=white&style=flat-square
+[submit-agents-link]: https://github.com/lobehub/lobe-chat-agents
+[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-shield]: https://img.shields.io/badge/vercel-online-55b467?labelColor=black&logo=vercel&style=flat-square
+[vercel-shield-badge]: https://img.shields.io/badge/TRY%20LOBECHAT-ONLINE-55b467?labelColor=black&logo=vercel&style=for-the-badge

README.md

@@ -8,7 +8,7 @@ An open-source, modern-design ChatGPT/LLMs UI/Framework.<br/>
 Supports speech-synthesis, multi-modal, and extensible ([function call][docs-functionc-call]) plugin system.<br/>
 One-click **FREE** deployment of your private OpenAI ChatGPT/Claude/Gemini/Groq/Ollama chat application.
 
-**English** · [简体中文](./README.zh-CN.md) · [Changelog](./CHANGELOG.md) · [Documents][docs] · [Report Bug][github-issues-link] · [Request Feature][github-issues-link]
+**English** · [简体中文](./README.zh-CN.md) · [日本語](./README.ja-JP.md) · [Official Site][official-site] · [Changelog](./CHANGELOG.md) · [Documents][docs] · [Blog][blog] · [Feedback][github-issues-link]
 
 <!-- SHIELD GROUP -->
 
@@ -52,20 +52,23 @@ One-click **FREE** deployment of your private OpenAI ChatGPT/Claude/Gemini/Groq/
 
 - [👋🏻 Getting Started & Join Our Community](#-getting-started--join-our-community)
 - [✨ Features](#-features)
-  - [`1` Multi-Model Service Provider Support](#1-multi-model-service-provider-support)
-  - [`2` Local Large Language Model (LLM) Support](#2-local-large-language-model-llm-support)
-  - [`3` Model Visual Recognition](#3-model-visual-recognition)
-  - [`4` TTS & STT Voice Conversation](#4-tts--stt-voice-conversation)
-  - [`5` Text to Image Generation](#5-text-to-image-generation)
-  - [`6` Plugin System (Function Calling)](#6-plugin-system-function-calling)
-  - [`7` Agent Market (GPTs)](#7-agent-market-gpts)
-  - [`8` Progressive Web App (PWA)](#8-progressive-web-app-pwa)
-  - [`9` Mobile Device Adaptation](#9-mobile-device-adaptation)
-  - [`10` Custom Themes](#10-custom-themes)
+  - [`1` File Upload/Knowledge Base](#1-file-uploadknowledge-base)
+  - [`2` Multi-Model Service Provider Support](#2-multi-model-service-provider-support)
+  - [`3` Local Large Language Model (LLM) Support](#3-local-large-language-model-llm-support)
+  - [`4` Model Visual Recognition](#4-model-visual-recognition)
+  - [`5` TTS & STT Voice Conversation](#5-tts--stt-voice-conversation)
+  - [`6` Text to Image Generation](#6-text-to-image-generation)
+  - [`7` Plugin System (Function Calling)](#7-plugin-system-function-calling)
+  - [`8` Agent Market (GPTs)](#8-agent-market-gpts)
+  - [`9` Support Local / Remote Database](#9-support-local--remote-database)
+  - [`10` Support Multi-User Management](#10-support-multi-user-management)
+  - [`11` Progressive Web App (PWA)](#11-progressive-web-app-pwa)
+  - [`12` Mobile Device Adaptation](#12-mobile-device-adaptation)
+  - [`13` Custom Themes](#13-custom-themes)
   - [`*` What's more](#-whats-more)
 - [⚡️ Performance](#️-performance)
 - [🛳 Self Hosting](#-self-hosting)
-  - [`A` Deploying with Vercel, Zeabur or Sealos](#a-deploying-with-vercel-zeabur-or-sealos)
+  - [`A` Deploying with Vercel, Zeabur , Sealos or Alibaba Cloud](#a-deploying-with-vercel-zeabur--sealos-or-alibaba-cloud)
   - [`B` Deploying with Docker](#b-deploying-with-docker)
   - [Environment Variable](#environment-variable)
 - [📦 Ecosystem](#-ecosystem)
@@ -108,9 +111,27 @@ Whether for users or professional developers, LobeHub will be your AI Agent play
 
 ## ✨ Features
 
+[![][image-feat-knowledgebase]][docs-feat-knowledgebase]
+
+### `1` [File Upload/Knowledge Base][docs-feat-knowledgebase]
+
+LobeChat supports file upload and knowledge base functionality. You can upload various types of files including documents, images, audio, and video, as well as create knowledge bases, making it convenient for users to manage and search for files. Additionally, you can utilize files and knowledge base features during conversations, enabling a richer dialogue experience.
+
+<https://github.com/user-attachments/assets/faa8cf67-e743-4590-8bf6-ebf6ccc34175>
+
+> \[!TIP]
+>
+> Learn more on [📘 LobeChat Knowledge Base Launch — From Now On, Every Step Counts](https://lobehub.com/blog/knowledge-base)
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
 [![][image-feat-privoder]][docs-feat-provider]
 
-### `1` [Multi-Model Service Provider Support][docs-feat-provider]
+### `2` [Multi-Model Service Provider Support][docs-feat-provider]
 
 In the continuous development of LobeChat, we deeply understand the importance of diversity in model service providers for meeting the needs of the community when providing AI conversation services. Therefore, we have expanded our support to multiple model service providers, rather than being limited to a single one, in order to offer users a more diverse and rich selection of conversations.
 
@@ -130,6 +151,9 @@ We have implemented support for the following model service providers:
 - **ChatGLM**: Added the **ChatGLM** series models from Zhipuai (GLM-4/GLM-4-vision/GLM-3-turbo), providing users with another efficient conversation model choice. [Learn more](https://www.zhipuai.cn/)
 - **Moonshot AI (Dark Side of the Moon)**: Integrated with the Moonshot series models, an innovative AI startup from China, aiming to provide deeper conversation understanding. [Learn more](https://www.moonshot.cn/)
 - **Minimax**: Integrated the Minimax models, including the MoE model **abab6**, offers a broader range of choices. [Learn more](https://www.minimaxi.com/)
+- **DeepSeek**: Integrated with the DeepSeek series models, an innovative AI startup from China, The product has been designed to provide a model that balances performance with price. [Learn more](https://www.deepseek.com/)
+- **Qwen**: Integrated the Qwen series models, including the latest **qwen-turbo**, **qwen-plus** and **qwen-max**. [Learn more](https://help.aliyun.com/zh/dashscope/developer-reference/model-introduction)
+- **Novita AI**: Access **Llama**, **Mistral**, and other leading open-source models at cheapest prices. Engage in uncensored role-play, spark creative discussions, and foster unrestricted innovation. **Pay For What You Use.** [Learn more](https://novita.ai/llm-api?utm_source=lobechat&utm_medium=ch&utm_campaign=api)
 
 At the same time, we are also planning to support more model service providers, such as Replicate and Perplexity, to further enrich our service provider library. If you would like LobeChat to support your favorite service provider, feel free to join our [community discussion](https://github.com/lobehub/lobe-chat/discussions/1284).
 
@@ -141,7 +165,7 @@ At the same time, we are also planning to support more model service providers,
 
 [![][image-feat-local]][docs-feat-local]
 
-### `2` [Local Large Language Model (LLM) Support][docs-feat-local]
+### `3` [Local Large Language Model (LLM) Support][docs-feat-local]
 
 To meet the specific needs of users, LobeChat also supports the use of local models based on [Ollama](https://ollama.ai), allowing users to flexibly use their own or third-party models.
 
@@ -157,7 +181,7 @@ To meet the specific needs of users, LobeChat also supports the use of local mod
 
 [![][image-feat-vision]][docs-feat-vision]
 
-### `3` [Model Visual Recognition][docs-feat-vision]
+### `4` [Model Visual Recognition][docs-feat-vision]
 
 LobeChat now supports OpenAI's latest [`gpt-4-vision`](https://platform.openai.com/docs/guides/vision) model with visual recognition capabilities,
 a multimodal intelligence that can perceive visuals. Users can easily upload or drag and drop images into the dialogue box,
@@ -175,7 +199,7 @@ Whether it's sharing images in daily use or interpreting images within specific
 
 [![][image-feat-tts]][docs-feat-tts]
 
-### `4` [TTS & STT Voice Conversation][docs-feat-tts]
+### `5` [TTS & STT Voice Conversation][docs-feat-tts]
 
 LobeChat supports Text-to-Speech (TTS) and Speech-to-Text (STT) technologies, enabling our application to convert text messages into clear voice outputs,
 allowing users to interact with our conversational agent as if they were talking to a real person. Users can choose from a variety of voices to pair with the agent.
@@ -192,7 +216,7 @@ Users can choose the voice that suits their personal preferences or specific sce
 
 [![][image-feat-t2i]][docs-feat-t2i]
 
-### `5` [Text to Image Generation][docs-feat-t2i]
+### `6` [Text to Image Generation][docs-feat-t2i]
 
 With support for the latest text-to-image generation technology, LobeChat now allows users to invoke image creation tools directly within conversations with the agent. By leveraging the capabilities of AI tools such as [`DALL-E 3`](https://openai.com/dall-e-3), [`MidJourney`](https://www.midjourney.com/), and [`Pollinations`](https://pollinations.ai/), the agents are now equipped to transform your ideas into images.
 
@@ -206,7 +230,7 @@ This enables a more private and immersive creative process, allowing for the sea
 
 [![][image-feat-plugin]][docs-feat-plugin]
 
-### `6` [Plugin System (Function Calling)][docs-feat-plugin]
+### `7` [Plugin System (Function Calling)][docs-feat-plugin]
 
 The plugin ecosystem of LobeChat is an important extension of its core functionality, greatly enhancing the practicality and flexibility of the LobeChat assistant.
 
@@ -222,14 +246,14 @@ In addition, these plugins are not limited to news aggregation, but can also ext
 
 <!-- PLUGIN LIST -->
 
-| Recent Submits                                                                                                            | Description                                                                                                                                     |
-| ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Social Search](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **say-apps** on **2024-05-02**</sup>         | The Social Search provides access to tweets, users, followers, images, media and more.<br/>`social` `twitter` `x` `search`                      |
-| [Search Google via Serper](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **Barry** on **2024-04-30**</sup> | Google search engine via Serper.dev free API (2500x🆓/month)<br/>`web` `search`                                                                 |
-| [NFT Guru](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **swap** on **2024-04-03**</sup>                  | Discover current prices of NFTs across major platforms and keep track of the rapidly changing marketplace with real-time<br/>`crypto` `nft`     |
-| [Calendar Assistant](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **cc** on **2024-03-13**</sup>          | A plugin to manage your calendar events # will auto generate i18n in workflow<br/>`calendar` `schedule` `will-auto-generate-i-18-n-in-workflow` |
+| Recent Submits                                                                                                                     | Description                                                                                                                               |
+| ---------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| [Tongyi wanxiang Image Generator](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **YoungTx** on **2024-08-09**</sup> | This plugin uses Alibaba's Tongyi Wanxiang model to generate images based on text prompts.<br/>`image` `tongyi` `wanxiang`                |
+| [Shopping tools](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **shoppingtools** on **2024-07-19**</sup>            | Search for products on eBay & AliExpress, find eBay events & coupons. Get prompt examples.<br/>`shopping` `e-bay` `ali-express` `coupons` |
+| [Savvy Trader AI](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **savvytrader** on **2024-06-27**</sup>             | Realtime stock, crypto and other investment data.<br/>`stock` `analyze`                                                                   |
+| [Search1API](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **fatwang2** on **2024-05-06**</sup>                     | Search aggregation service, specifically designed for LLMs<br/>`web` `search`                                                             |
 
-> 📊 Total plugins: [<kbd>**56**</kbd>](https://github.com/lobehub/lobe-chat-plugins)
+> 📊 Total plugins: [<kbd>**49**</kbd>](https://github.com/lobehub/lobe-chat-plugins)
 
  <!-- PLUGIN LIST -->
 
@@ -241,7 +265,7 @@ In addition, these plugins are not limited to news aggregation, but can also ext
 
 [![][image-feat-agent]][docs-feat-agent]
 
-### `7` [Agent Market (GPTs)][docs-feat-agent]
+### `8` [Agent Market (GPTs)][docs-feat-agent]
 
 In LobeChat Agent Marketplace, creators can discover a vibrant and innovative community that brings together a multitude of well-designed agents,
 which not only play an important role in work scenarios but also offer great convenience in learning processes.
@@ -261,14 +285,14 @@ Our marketplace is not just a showcase platform but also a collaborative space.
 
 <!-- AGENT LIST -->
 
-| Recent Submits                                                                                                                                                                      | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| [Sales Description Specialist](https://chat-preview.lobehub.com/market?agent=verkauf-kleinanzeigen)<br/><sup>By **[highseen](https://github.com/highseen)** on **2024-04-30**</sup> | Assists in the sale of used items through research, pricing, description, and title creation.<br/>`product-sales` `research` `description`                                                                                                                                                                                                                                                                                                                                     |
-| [Jailbreak Assistant DAN](https://chat-preview.lobehub.com/market?agent=gpt-4-dan-assistant)<br/><sup>By **[MapleEve](https://github.com/MapleEve)** on **2024-04-26**</sup>        | Bypass OpenAI review mechanism, ChatGPT after jailbreak<br/>`creative` `artificial-intelligence` `conversation` `jailbreak`                                                                                                                                                                                                                                                                                                                                                    |
-| [TailwindHelper](https://chat-preview.lobehub.com/market?agent=tailwind-helper)<br/><sup>By **[aototo](https://github.com/aototo)** on **2024-04-26**</sup>                         | TailwindHelper is a professional frontend designer with a solid foundation in design theory and rich practical experience. Created by a leading software development company, it aims to help developers and designers accelerate the development process of web interfaces. TailwindHelper is proficient in the Tailwind CSS framework and can translate complex design requirements into efficient and responsive CSS class names.<br/>`tailwindcss` `css` `tailwind-helper` |
-| [yapi JSON-SCHEMA to Typescript](https://chat-preview.lobehub.com/market?agent=yapi-ts-helper)<br/><sup>By **[zcf0508](https://github.com/zcf0508)** on **2024-04-26**</sup>        | Specializes in converting JSON schema to TypeScript types.<br/>`typescript` `development`                                                                                                                                                                                                                                                                                                                                                                                      |
+| Recent Submits                                                                                                                                                            | Description                                                                                                                                                                                                           |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Algorithm Answer Mentor](https://chat-preview.lobehub.com/market?agent=leetcode-tutor)<br/><sup>By **[Stark-X](https://github.com/Stark-X)** on **2024-10-21**</sup>     | Specializes in LeetCode algorithm solutions and user guidance<br/>`algorithm` `problem-solving` `programming` `education`                                                                                             |
+| [Psychologist](https://chat-preview.lobehub.com/market?agent=psychological-counselor)<br/><sup>By **[JIANGTUNAN](https://github.com/JIANGTUNAN)** on **2024-10-21**</sup> | An experienced psychologist, warmly and patiently listening to your story.<br/>`psychological-counseling` `consultation` `sharing` `friendly` `doctor` `counselor`                                                    |
+| [Boxing Training Master](https://chat-preview.lobehub.com/market?agent=boxing-master)<br/><sup>By **[Luyi-2333](https://github.com/Luyi-2333)** on **2024-10-15**</sup>   | Expert in boxing training guidance and personalized plan development<br/>`boxing-training` `personalized-plans` `fitness-guidance` `progress-evaluation` `technique-improvement` `health-and-nutrition`               |
+| [Coconut](https://chat-preview.lobehub.com/market?agent=deep-thinker-ai)<br/><sup>By **[hia1234](https://github.com/hia1234)** on **2024-10-15**</sup>                    | A chatbot that undergoes several reviews of its responses, checking whether there is a basis for its statements and actively requesting feedback while engaging in repeated interactions.<br/>`programming` `general` |
 
-> 📊 Total agents: [<kbd>**244**</kbd> ](https://github.com/lobehub/lobe-chat-agents)
+> 📊 Total agents: [<kbd>**420**</kbd> ](https://github.com/lobehub/lobe-chat-agents)
 
  <!-- AGENT LIST -->
 
@@ -278,9 +302,44 @@ Our marketplace is not just a showcase platform but also a collaborative space.
 
 </div>
 
+[![][image-feat-database]][docs-feat-database]
+
+### `9` [Support Local / Remote Database][docs-feat-database]
+
+LobeChat supports the use of both server-side and local databases. Depending on your needs, you can choose the appropriate deployment solution:
+
+- **Local database**: suitable for users who want more control over their data and privacy protection. LobeChat uses CRDT (Conflict-Free Replicated Data Type) technology to achieve multi-device synchronization. This is an experimental feature aimed at providing a seamless data synchronization experience.
+- **Server-side database**: suitable for users who want a more convenient user experience. LobeChat supports PostgreSQL as a server-side database. For detailed documentation on how to configure the server-side database, please visit [Configure Server-side Database](https://lobehub.com/docs/self-hosting/advanced/server-database).
+
+Regardless of which database you choose, LobeChat can provide you with an excellent user experience.
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+[![][image-feat-auth]][docs-feat-auth]
+
+### `10` [Support Multi-User Management][docs-feat-auth]
+
+LobeChat supports multi-user management and provides two main user authentication and management solutions to meet different needs:
+
+- **next-auth**: LobeChat integrates `next-auth`, a flexible and powerful identity verification library that supports multiple authentication methods, including OAuth, email login, credential login, etc. With `next-auth`, you can easily implement user registration, login, session management, social login, and other functions to ensure the security and privacy of user data.
+
+- [**Clerk**](https://go.clerk.com/exgqLG0): For users who need more advanced user management features, LobeChat also supports `Clerk`, a modern user management platform. `Clerk` provides richer functions, such as multi-factor authentication (MFA), user profile management, login activity monitoring, etc. With `Clerk`, you can get higher security and flexibility, and easily cope with complex user management needs.
+
+Regardless of which user management solution you choose, LobeChat can provide you with an excellent user experience and powerful functional support.
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
 [![][image-feat-pwa]][docs-feat-pwa]
 
-### `8` [Progressive Web App (PWA)][docs-feat-pwa]
+### `11` [Progressive Web App (PWA)][docs-feat-pwa]
 
 We deeply understand the importance of providing a seamless experience for users in today's multi-device environment.
 Therefore, we have adopted Progressive Web Application ([PWA](https://support.google.com/chrome/answer/9658361)) technology,
@@ -307,7 +366,7 @@ providing smooth animations, responsive layouts, and adapting to different devic
 
 [![][image-feat-mobile]][docs-feat-mobile]
 
-### `9` [Mobile Device Adaptation][docs-feat-mobile]
+### `12` [Mobile Device Adaptation][docs-feat-mobile]
 
 We have carried out a series of optimization designs for mobile devices to enhance the user's mobile experience. Currently, we are iterating on the mobile user experience to achieve smoother and more intuitive interactions. If you have any suggestions or ideas, we welcome you to provide feedback through GitHub Issues or Pull Requests.
 
@@ -319,7 +378,7 @@ We have carried out a series of optimization designs for mobile devices to enhan
 
 [![][image-feat-theme]][docs-feat-theme]
 
-### `10` [Custom Themes][docs-feat-theme]
+### `13` [Custom Themes][docs-feat-theme]
 
 As a design-engineering-oriented application, LobeChat places great emphasis on users' personalized experiences,
 hence introducing flexible and diverse theme modes, including a light mode for daytime and a dark mode for nighttime.
@@ -380,15 +439,15 @@ Beside these features, LobeChat also have much better basic technique undergroun
 
 ## 🛳 Self Hosting
 
-LobeChat provides Self-Hosted Version with Vercel and [Docker Image][docker-release-link]. This allows you to deploy your own chatbot within a few minutes without any prior knowledge.
+LobeChat provides Self-Hosted Version with Vercel, Alibaba Cloud, and [Docker Image][docker-release-link]. This allows you to deploy your own chatbot within a few minutes without any prior knowledge.
 
 > \[!TIP]
 >
 > Learn more about [📘 Build your own LobeChat][docs-self-hosting] by checking it out.
 
-### `A` Deploying with Vercel, Zeabur or Sealos
+### `A` Deploying with Vercel, Zeabur , Sealos or Alibaba Cloud
 
-If you want to deploy this service yourself on either Vercel or Zeabur, you can follow these steps:
+"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.
@@ -397,9 +456,9 @@ If you want to deploy this service yourself on either Vercel or Zeabur, you can
 
 <div align="center">
 
-|           Deploy with Vercel            |                     Deploy with Zeabur                      |                     Deploy with Sealos                      |
-| :-------------------------------------: | :---------------------------------------------------------: | :---------------------------------------------------------: |
-| [![][deploy-button-image]][deploy-link] | [![][deploy-on-zeabur-button-image]][deploy-on-zeabur-link] | [![][deploy-on-sealos-button-image]][deploy-on-sealos-link] |
+|           Deploy with Vercel            |                     Deploy with Zeabur                      |                     Deploy with Sealos                      |                       Deploy with RepoCloud                       |                         Deploy with Alibaba Cloud                         |
+| :-------------------------------------: | :---------------------------------------------------------: | :---------------------------------------------------------: | :---------------------------------------------------------------: | :-----------------------------------------------------------------------: |
+| [![][deploy-button-image]][deploy-link] | [![][deploy-on-zeabur-button-image]][deploy-on-zeabur-link] | [![][deploy-on-sealos-button-image]][deploy-on-sealos-link] | [![][deploy-on-repocloud-button-image]][deploy-on-repocloud-link] | [![][deploy-on-alibaba-cloud-button-image]][deploy-on-alibaba-cloud-link] |
 
 </div>
 
@@ -627,11 +686,12 @@ Every bit counts and your one-time donation sparkles in our galaxy of support! Y
 </details>
 
 Copyright © 2024 [LobeHub][profile-link]. <br />
-This project is [MIT](./LICENSE) licensed.
+This project is [Apache 2.0](./LICENSE) licensed.
 
 <!-- LINK GROUP -->
 
 [back-to-top]: https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square
+[blog]: https://lobehub.com/blog
 [chat-desktop]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/desktop/pagespeed.svg
 [chat-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/desktop/chat_preview_lobehub_com_chat.html
 [chat-mobile]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/mobile/pagespeed.svg
@@ -645,6 +705,10 @@ This project is [MIT](./LICENSE) licensed.
 [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-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=LobeChat%E7%A4%BE%E5%8C%BA%E7%89%88
+[deploy-on-repocloud-button-image]: https://d16t0pc4846x52.cloudfront.net/deploylobe.svg
+[deploy-on-repocloud-link]: https://repocloud.io/details/?app_id=248
 [deploy-on-sealos-button-image]: https://raw.githubusercontent.com/labring-actions/templates/main/Deploy-on-Sealos.svg
 [deploy-on-sealos-link]: https://cloud.sealos.io/?openapp=system-template%3FtemplateName%3Dlobe-chat
 [deploy-on-zeabur-button-image]: https://zeabur.com/button.svg
@@ -658,11 +722,14 @@ This project is [MIT](./LICENSE) licensed.
 [docker-release-shield]: https://img.shields.io/docker/v/lobehub/lobe-chat?color=369eff&label=docker&labelColor=black&logo=docker&logoColor=white&style=flat-square
 [docker-size-link]: https://hub.docker.com/r/lobehub/lobe-chat
 [docker-size-shield]: https://img.shields.io/docker/image-size/lobehub/lobe-chat?color=369eff&labelColor=black&style=flat-square
-[docs]: https://lobehub.com/docs
+[docs]: https://lobehub.com/docs/usage/start
 [docs-dev-guide]: https://github.com/lobehub/lobe-chat/wiki/index
 [docs-docker]: https://lobehub.com/docs/self-hosting/platform/docker
 [docs-env-var]: https://lobehub.com/docs/self-hosting/environment-variables
 [docs-feat-agent]: https://lobehub.com/docs/usage/features/agent-market
+[docs-feat-auth]: https://lobehub.com/docs/usage/features/auth
+[docs-feat-database]: https://lobehub.com/docs/usage/features/database
+[docs-feat-knowledgebase]: https://lobehub.com/blog/knowledge-base
 [docs-feat-local]: https://lobehub.com/docs/usage/features/local-llm
 [docs-feat-mobile]: https://lobehub.com/docs/usage/features/mobile
 [docs-feat-plugin]: https://lobehub.com/docs/usage/features/plugin-system
@@ -672,7 +739,7 @@ This project is [MIT](./LICENSE) licensed.
 [docs-feat-theme]: https://lobehub.com/docs/usage/features/theme
 [docs-feat-tts]: https://lobehub.com/docs/usage/features/tts
 [docs-feat-vision]: https://lobehub.com/docs/usage/features/vision
-[docs-functionc-call]: https://platform.openai.com/docs/guides/function-calling
+[docs-functionc-call]: https://lobehub.com/blog/openai-function-call
 [docs-lighthouse]: https://github.com/lobehub/lobe-chat/wiki/Lighthouse
 [docs-plugin-dev]: https://lobehub.com/docs/usage/plugins/development
 [docs-self-hosting]: https://lobehub.com/docs/self-hosting/start
@@ -692,7 +759,7 @@ This project is [MIT](./LICENSE) licensed.
 [github-issues-link]: https://github.com/lobehub/lobe-chat/issues
 [github-issues-shield]: https://img.shields.io/github/issues/lobehub/lobe-chat?color=ff80eb&labelColor=black&style=flat-square
 [github-license-link]: https://github.com/lobehub/lobe-chat/blob/main/LICENSE
-[github-license-shield]: https://img.shields.io/github/license/lobehub/lobe-chat?color=white&labelColor=black&style=flat-square
+[github-license-shield]: https://img.shields.io/badge/license-apache%202.0-white?labelColor=black&style=flat-square
 [github-project-link]: https://github.com/lobehub/lobe-chat/projects
 [github-release-link]: https://github.com/lobehub/lobe-chat/releases
 [github-release-shield]: https://img.shields.io/github/v/release/lobehub/lobe-chat?color=369eff&labelColor=black&logo=github&style=flat-square
@@ -704,6 +771,9 @@ This project is [MIT](./LICENSE) licensed.
 [github-trending-url]: https://trendshift.io/repositories/2256
 [image-banner]: https://github.com/lobehub/lobe-chat/assets/28616219/9f155dff-4737-429f-9cad-a70a1a860c5f
 [image-feat-agent]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670869-f1ffbf66-42b6-42cf-a937-9ce1f8328514.png
+[image-feat-auth]: https://github.com/lobehub/lobe-chat/assets/17870709/8ce70e15-40df-451e-b700-66090fe5b8c2
+[image-feat-database]: https://github.com/lobehub/lobe-chat/assets/17870709/c27a0234-a4e9-40e5-8bcb-42d5ce7e40f9
+[image-feat-knowledgebase]: https://github.com/user-attachments/assets/77e58e1c-c82f-4341-b159-f4eeede9967f
 [image-feat-local]: https://github.com/lobehub/lobe-chat/assets/28616219/ca9a21bc-ea6c-4c90-bf4a-fa53b4fb2b5c
 [image-feat-mobile]: https://gw.alipayobjects.com/zos/kitchen/R441AuFS4W/mobile.webp
 [image-feat-plugin]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670883-33c43a5c-a512-467e-855c-fa299548cce5.png
@@ -713,7 +783,7 @@ This project is [MIT](./LICENSE) licensed.
 [image-feat-theme]: https://gw.alipayobjects.com/zos/kitchen/pvus1lo%26Z7/darkmode.webp
 [image-feat-tts]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072124-c9853d8d-f1b5-44a8-a305-45ebc0f6d19a.png
 [image-feat-vision]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072129-382bdf30-e3d6-4411-b5a0-249710b8ba08.png
-[image-overview]: https://github.com/lobehub/lobe-chat/assets/28616219/8b04c3c9-3d71-4fb4-bd9b-a4f415c5876d
+[image-overview]: https://github.com/lobehub/lobe-chat/assets/17870709/56b95d48-f573-41cd-8b38-387bf88bc4bf
 [image-star]: https://github.com/lobehub/lobe-chat/assets/17870709/cb06b748-513f-47c2-8740-d876858d7855
 [issues-link]: https://img.shields.io/github/issues/lobehub/lobe-chat.svg?style=flat
 [lobe-chat-plugins]: https://github.com/lobehub/lobe-chat-plugins
@@ -733,6 +803,7 @@ This project is [MIT](./LICENSE) licensed.
 [lobe-ui-github]: https://github.com/lobehub/lobe-ui
 [lobe-ui-link]: https://www.npmjs.com/package/@lobehub/ui
 [lobe-ui-shield]: https://img.shields.io/npm/v/@lobehub/ui?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
+[official-site]: https://lobehub.com
 [pr-welcome-link]: https://github.com/lobehub/lobe-chat/pulls
 [pr-welcome-shield]: https://img.shields.io/badge/🤯_pr_welcome-%E2%86%92-ffcb47?labelColor=black&style=for-the-badge
 [profile-link]: https://github.com/lobehub
@@ -757,5 +828,5 @@ This project is [MIT](./LICENSE) licensed.
 [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-shield]: https://img.shields.io/website?down_message=offline&label=vercel&labelColor=black&logo=vercel&style=flat-square&up_message=online&url=https%3A%2F%2Fchat-preview.lobehub.com
-[vercel-shield-badge]: https://img.shields.io/website?down_message=offline&label=try%20lobechat&labelColor=black&logo=vercel&style=for-the-badge&up_message=online&url=https%3A%2F%2Fchat-preview.lobehub.com
+[vercel-shield]: https://img.shields.io/badge/vercel-online-55b467?labelColor=black&logo=vercel&style=flat-square
+[vercel-shield-badge]: https://img.shields.io/badge/TRY%20LOBECHAT-ONLINE-55b467?labelColor=black&logo=vercel&style=for-the-badge

README.zh-CN.md

@@ -8,7 +8,7 @@
 支持语音合成、多模态、可扩展的（[function call][docs-functionc-call]）插件系统<br/>
 一键**免费**拥有你自己的 ChatGPT/Gemini/Claude/Ollama 应用
 
-[English](./README.md) · **简体中文** · [更新日志](./CHANGELOG.md) · [文档][github-document-link] · [报告问题][github-issues-link] · [请求功能][github-issues-link]
+[English](./README.md) · **简体中文** · [日本語](./README.ja-JP.md) · [官网][official-site] · [更新日志](./CHANGELOG.md) · [文档][docs] · [博客][blog] · [反馈问题][github-issues-link]
 
 <!-- SHIELD GROUP -->
 
@@ -39,6 +39,7 @@
 <sup>探索私人生产力的未来。在个体崛起的时代中为你打造.</sup>
 
 [![][github-trending-shield]][github-trending-url]
+[![][github-hello-shield]][github-hello-url]
 
 [![][image-overview]][vercel-link]
 
@@ -51,20 +52,23 @@
 
 - [👋🏻 开始使用 & 交流](#-开始使用--交流)
 - [✨ 特性一览](#-特性一览)
-  - [`1` 多模型服务商支持](#1-多模型服务商支持)
-  - [`2` 支持本地大语言模型 (LLM)](#2-支持本地大语言模型-llm)
-  - [`3` 模型视觉识别 (Model Visual)](#3-模型视觉识别-model-visual)
-  - [`4` TTS & STT 语音会话](#4-tts--stt-语音会话)
-  - [`5` Text to Image 文生图](#5-text-to-image-文生图)
-  - [`6` 插件系统 (Function Calling)](#6-插件系统-function-calling)
-  - [`7` 助手市场 (GPTs)](#7-助手市场-gpts)
-  - [`8` 渐进式 Web 应用 (PWA)](#8-渐进式-web-应用-pwa)
-  - [`9` 移动设备适配](#9-移动设备适配)
-  - [`10` 自定义主题](#10-自定义主题)
+  - [`1` 文件上传 / 知识库](#1-文件上传--知识库)
+  - [`2` 多模型服务商支持](#2-多模型服务商支持)
+  - [`3` 支持本地大语言模型 (LLM)](#3-支持本地大语言模型-llm)
+  - [`4` 模型视觉识别 (Model Visual)](#4-模型视觉识别-model-visual)
+  - [`5` TTS & STT 语音会话](#5-tts--stt-语音会话)
+  - [`6` Text to Image 文生图](#6-text-to-image-文生图)
+  - [`7` 插件系统 (Tools Calling)](#7-插件系统-tools-calling)
+  - [`8` 助手市场 (GPTs)](#8-助手市场-gpts)
+  - [`9` 支持本地 / 远程数据库](#9-支持本地--远程数据库)
+  - [`10` 支持多用户管理](#10-支持多用户管理)
+  - [`11` 渐进式 Web 应用 (PWA)](#11-渐进式-web-应用-pwa)
+  - [`12` 移动设备适配](#12-移动设备适配)
+  - [`13` 自定义主题](#13-自定义主题)
   - [更多特性](#更多特性)
 - [⚡️ 性能测试](#️-性能测试)
 - [🛳 开箱即用](#-开箱即用)
-  - [`A` 使用 Vercel、Zeabur 或 Sealos 部署](#a-使用-vercelzeabur-或-sealos-部署)
+  - [`A` 使用 Vercel、Zeabur 、Sealos 或 阿里云计算巢 部署](#a-使用-vercelzeabur-sealos-或-阿里云计算巢-部署)
   - [`B` 使用 Docker 部署](#b-使用-docker-部署)
   - [环境变量](#环境变量)
   - [获取 OpenAI API Key](#获取-openai-api-key)
@@ -107,9 +111,27 @@
 
 ## ✨ 特性一览
 
+[![][image-feat-knowledgebase]][docs-feat-knowledgebase]
+
+### `1` [文件上传 / 知识库][docs-feat-knowledgebase]
+
+LobeChat 支持文件上传与知识库功能，你可以上传文件、图片、音频、视频等多种类型的文件，以及创建知识库，方便用户管理和查找文件。同时在对话中使用文件和知识库功能，实现更加丰富的对话体验。
+
+<https://github.com/user-attachments/assets/faa8cf67-e743-4590-8bf6-ebf6ccc34175>
+
+> \[!TIP]
+>
+> 查阅 [📘 LobeChat 知识库上线 —— 此刻起，跬步千里](https://lobehub.com/zh/blog/knowledge-base) 了解详情。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
 [![][image-feat-privoder]][docs-feat-provider]
 
-### `1` [多模型服务商支持][docs-feat-provider]
+### `2` [多模型服务商支持][docs-feat-provider]
 
 在 LobeChat 的不断发展过程中，我们深刻理解到在提供 AI 会话服务时模型服务商的多样性对于满足社区需求的重要性。因此，我们不再局限于单一的模型服务商，而是拓展了对多种模型服务商的支持，以便为用户提供更为丰富和多样化的会话选择。
 
@@ -129,6 +151,9 @@
 - **Groq**：接入了 Groq 的 AI 模型，高效处理消息序列，生成回应，胜任多轮对话及单次交互任务。[了解更多](https://groq.com/)
 - **OpenRouter**：其支持包括 **Claude 3**，**Gemma**，**Mistral**，**Llama2**和**Cohere**等模型路由，支持智能路由优化，提升使用效率，开放且灵活。[了解更多](https://openrouter.ai/)
 - **Minimax**: 接入了 Minimax 的 AI 模型，包括 MoE 模型 **abab6**，提供了更多的选择空间。[了解更多](https://www.minimaxi.com/)
+- **DeepSeek**: 接入了 DeepSeek 的 AI 模型，包括最新的 **DeepSeek-V2**，提供兼顾性能与价格的模型。[了解更多](https://www.deepseek.com/)
+- **Qwen**: 接入了 Qwen 的 AI 模型，包括最新的 **qwen-turbo**，**qwen-plus** 和 **qwen-max** 等模型。[了解更多](https://help.aliyun.com/zh/dashscope/developer-reference/model-introduction)
+- **Novita AI**: 性价比最高的开源模型供应商，支持 **Llama**，**Mistral** 系列等最前沿的开源模型。在情感陪伴等场景表现优异，无任何内容限制或审查。 [了解更多](https://novita.ai/model-api/product/llm-api?utm_source=lobechat&utm_medium=ch&utm_campaign=api)
 
 同时，我们也在计划支持更多的模型服务商，如 Replicate 和 Perplexity 等，以进一步丰富我们的服务商库。如果你希望让 LobeChat 支持你喜爱的服务商，欢迎加入我们的[社区讨论](https://github.com/lobehub/lobe-chat/discussions/1284)。
 
@@ -140,7 +165,7 @@
 
 [![][image-feat-local]][docs-feat-local]
 
-### `2` [支持本地大语言模型 (LLM)][docs-feat-local]
+### `3` [支持本地大语言模型 (LLM)][docs-feat-local]
 
 为了满足特定用户的需求，LobeChat 还基于 [Ollama](https://ollama.ai) 支持了本地模型的使用，让用户能够更灵活地使用自己的或第三方的模型。
 
@@ -156,7 +181,7 @@
 
 [![][image-feat-vision]][docs-feat-vision]
 
-### `3` [模型视觉识别 (Model Visual)][docs-feat-vision]
+### `4` [模型视觉识别 (Model Visual)][docs-feat-vision]
 
 LobeChat 已经支持 OpenAI 最新的 [`gpt-4-vision`](https://platform.openai.com/docs/guides/vision) 支持视觉识别的模型，这是一个具备视觉识别能力的多模态应用。
 用户可以轻松上传图片或者拖拽图片到对话框中，助手将能够识别图片内容，并在此基础上进行智能对话，构建更智能、更多元化的聊天场景。
@@ -171,7 +196,7 @@ LobeChat 已经支持 OpenAI 最新的 [`gpt-4-vision`](https://platform.openai.
 
 [![][image-feat-tts]][docs-feat-tts]
 
-### `4` [TTS & STT 语音会话][docs-feat-tts]
+### `5` [TTS & STT 语音会话][docs-feat-tts]
 
 LobeChat 支持文字转语音（Text-to-Speech，TTS）和语音转文字（Speech-to-Text，STT）技术，这使得我们的应用能够将文本信息转化为清晰的语音输出，用户可以像与真人交谈一样与我们的对话助手进行交流。
 用户可以从多种声音中选择，给助手搭配合适的音源。 同时，对于那些倾向于听觉学习或者想要在忙碌中获取信息的用户来说，TTS 提供了一个极佳的解决方案。
@@ -186,7 +211,7 @@ LobeChat 支持文字转语音（Text-to-Speech，TTS）和语音转文字（Spe
 
 [![][image-feat-t2i]][docs-feat-t2i]
 
-### `5` [Text to Image 文生图][docs-feat-t2i]
+### `6` [Text to Image 文生图][docs-feat-t2i]
 
 支持最新的文本到图片生成技术，LobeChat 现在能够让用户在与助手对话中直接调用文生图工具进行创作。
 通过利用 [`DALL-E 3`](https://openai.com/dall-e-3)、[`MidJourney`](https://www.midjourney.com/) 和 [`Pollinations`](https://pollinations.ai/) 等 AI 工具的能力， 助手们现在可以将你的想法转化为图像。
@@ -200,7 +225,7 @@ LobeChat 支持文字转语音（Text-to-Speech，TTS）和语音转文字（Spe
 
 [![][image-feat-plugin]][docs-feat-plugin]
 
-### `6` [插件系统 (Function Calling)][docs-feat-plugin]
+### `7` [插件系统 (Tools Calling)][docs-feat-plugin]
 
 LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地增强了 ChatGPT 的实用性和灵活性。
 
@@ -214,14 +239,14 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地
 
 <!-- PLUGIN LIST -->
 
-| 最近新增                                                                                                                 | 插件描述                                                                                                       |
-| ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------- |
-| [社交搜索](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **say-apps** on **2024-05-02**</sup>             | 社交搜索提供访问推文、用户、关注者、图片、媒体等功能。<br/>`社交` `推特` `x` `搜索`                            |
-| [通过 Serper 搜索 Google](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **Barry** on **2024-04-30**</sup> | 通过 Serper.dev 免费 API 进行 Google 搜索引擎（每月 2500 次🆓）<br/>`网络` `搜索`                              |
-| [NFT Guru](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **swap** on **2024-04-03**</sup>                 | 发现主要平台上 NFT 的当前价格，并通过实时跟踪快速变化的市场了解情况<br/>`加密货币` `nft`                       |
-| [日历助手](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **cc** on **2024-03-13**</sup>                   | 一个用于管理日历事件的插件 # 将自动生成工作流程中的 i18n<br/>`日历` `日程安排` `将自动生成工作流程中的-i-18-n` |
+| 最近新增                                                                                                               | 插件描述                                                                                                           |
+| ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| [通义万象图像生成器](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **YoungTx** on **2024-08-09**</sup>  | 此插件使用阿里巴巴的通义万象模型根据文本提示生成图像。<br/>`图像` `通义` `万象`                                    |
+| [购物工具](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **shoppingtools** on **2024-07-19**</sup>      | 在 eBay 和 AliExpress 上搜索产品，查找 eBay 活动和优惠券。获取快速示例。<br/>`购物` `e-bay` `ali-express` `优惠券` |
+| [Savvy Trader AI](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **savvytrader** on **2024-06-27**</sup> | 实时股票、加密货币和其他投资数据。<br/>`股票` `分析`                                                               |
+| [Search1API](https://chat-preview.lobehub.com/settings/agent)<br/><sup>By **fatwang2** on **2024-05-06**</sup>         | 搜索聚合服务，专为 LLMs 设计<br/>`web` `search`                                                                    |
 
-> 📊 Total plugins: [<kbd>**56**</kbd>](https://github.com/lobehub/lobe-chat-plugins)
+> 📊 Total plugins: [<kbd>**49**</kbd>](https://github.com/lobehub/lobe-chat-plugins)
 
  <!-- PLUGIN LIST -->
 
@@ -233,7 +258,7 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地
 
 [![][image-feat-agent]][docs-feat-agent]
 
-### `7` [助手市场 (GPTs)][docs-feat-agent]
+### `8` [助手市场 (GPTs)][docs-feat-agent]
 
 在 LobeChat 的助手市场中，创作者们可以发现一个充满活力和创新的社区，它汇聚了众多精心设计的助手，这些助手不仅在工作场景中发挥着重要作用，也在学习过程中提供了极大的便利。
 我们的市场不仅是一个展示平台，更是一个协作的空间。在这里，每个人都可以贡献自己的智慧，分享个人开发的助手。
@@ -249,14 +274,14 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地
 
 <!-- AGENT LIST -->
 
-| 最近新增                                                                                                                                                                     | 助手说明                                                                                                                                                                                                                                                                                                 |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [销售描述专家](https://chat-preview.lobehub.com/market?agent=verkauf-kleinanzeigen)<br/><sup>By **[highseen](https://github.com/highseen)** on **2024-04-30**</sup>          | 通过研究、定价、描述和标题设计帮助销售二手物品。<br/>`产品销售` `研究` `描述`                                                                                                                                                                                                                            |
-| [越狱助手 DAN](https://chat-preview.lobehub.com/market?agent=gpt-4-dan-assistant)<br/><sup>By **[MapleEve](https://github.com/MapleEve)** on **2024-04-26**</sup>            | 突破 OpenAI 审核机制，越狱之后的 ChatGPT<br/>`创意` `人工智能` `对话` `越狱`                                                                                                                                                                                                                             |
-| [TailwindHelper](https://chat-preview.lobehub.com/market?agent=tailwind-helper)<br/><sup>By **[aototo](https://github.com/aototo)** on **2024-04-26**</sup>                  | TailwindHelper 是一位专业的前端设计师，拥有深厚的设计理论基础和丰富的实践经验。它由一家领先的软件开发公司创建，旨在帮助开发者和设计师加速 Web 界面的开发过程。TailwindHelper 精通 Tailwind CSS 框架，并能够理解复杂的设计要求，转化为高效且响应式的 CSS 类名。<br/>`tailwindcss` `css` `tailwind-helper` |
-| [yapi JSON-SCHEMA to Typescript](https://chat-preview.lobehub.com/market?agent=yapi-ts-helper)<br/><sup>By **[zcf0508](https://github.com/zcf0508)** on **2024-04-26**</sup> | 擅长将 JSON schema 转换为 TypeScript 类型。<br/>`typescript` `开发`                                                                                                                                                                                                                                      |
+| 最近新增                                                                                                                                                                | 助手说明                                                                                                   |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
+| [算法解答导师](https://chat-preview.lobehub.com/market?agent=leetcode-tutor)<br/><sup>By **[Stark-X](https://github.com/Stark-X)** on **2024-10-21**</sup>              | 擅长 LeetCode 算法解答与用户指导<br/>`算法` `解题` `编程` `教育`                                           |
+| [心理咨询师](https://chat-preview.lobehub.com/market?agent=psychological-counselor)<br/><sup>By **[JIANGTUNAN](https://github.com/JIANGTUNAN)** on **2024-10-21**</sup> | 一个资深心理医生，温暖和耐心的倾听你的故事。<br/>`心理咨询` `咨询` `倾述` `友好` `医生` `咨询师`           |
+| [拳击训练大师](https://chat-preview.lobehub.com/market?agent=boxing-master)<br/><sup>By **[Luyi-2333](https://github.com/Luyi-2333)** on **2024-10-15**</sup>           | 擅长拳击训练指导与个性化计划制定<br/>`拳击训练` `个性化计划` `健身指导` `进度评估` `技术提升` `健康与营养` |
+| [椰子](https://chat-preview.lobehub.com/market?agent=deep-thinker-ai)<br/><sup>By **[hia1234](https://github.com/hia1234)** on **2024-10-15**</sup>                     | 在自己的回答中进行多次审查，确保聊天机器人所说的话有依据，并积极请求反馈，反复进行互动<br/>`编程` `一般`   |
 
-> 📊 Total agents: [<kbd>**244**</kbd> ](https://github.com/lobehub/lobe-chat-agents)
+> 📊 Total agents: [<kbd>**420**</kbd> ](https://github.com/lobehub/lobe-chat-agents)
 
  <!-- AGENT LIST -->
 
@@ -266,9 +291,44 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地
 
 </div>
 
+[![][image-feat-database]][docs-feat-database]
+
+### `9` [支持本地 / 远程数据库][docs-feat-database]
+
+LobeChat 支持同时使用服务端数据库和本地数据库。根据您的需求，您可以选择合适的部署方案：
+
+- 本地数据库：适合希望对数据有更多掌控感和隐私保护的用户。LobeChat 采用了 CRDT (Conflict-Free Replicated Data Type) 技术，实现了多端同步功能。这是一项实验性功能，旨在提供无缝的数据同步体验。
+- 服务端数据库：适合希望更便捷使用体验的用户。LobeChat 支持 PostgreSQL 作为服务端数据库。关于如何配置服务端数据库的详细文档，请前往 [配置服务端数据库](https://lobehub.com/zh/docs/self-hosting/advanced/server-database)。
+
+无论您选择哪种数据库，LobeChat 都能为您提供卓越的用户体验。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
+[![][image-feat-auth]][docs-feat-auth]
+
+### `10` [支持多用户管理][docs-feat-auth]
+
+LobeChat 支持多用户管理，提供了两种主要的用户认证和管理方案，以满足不同需求：
+
+- **next-auth**：LobeChat 集成了 `next-auth`，一个灵活且强大的身份验证库，支持多种身份验证方式，包括 OAuth、邮件登录、凭证登录等。通过 `next-auth`，您可以轻松实现用户的注册、登录、会话管理以及社交登录等功能，确保用户数据的安全性和隐私性。
+
+- [**Clerk**](https://go.clerk.com/exgqLG0)：对于需要更高级用户管理功能的用户，LobeChat 还支持 `Clerk`，一个现代化的用户管理平台。`Clerk` 提供了更丰富的功能，如多因素认证 (MFA)、白名单、用户管理、登录活动监控等。通过 `Clerk`，您可以获得更高的安全性和灵活性，轻松应对生产级的用户管理需求。
+
+您可以根据自己的需求，选择合适的用户管理方案。
+
+<div align="right">
+
+[![][back-to-top]](#readme-top)
+
+</div>
+
 [![][image-feat-pwa]][docs-feat-pwa]
 
-### `8` [渐进式 Web 应用 (PWA)][docs-feat-pwa]
+### `11` [渐进式 Web 应用 (PWA)][docs-feat-pwa]
 
 我们深知在当今多设备环境下为用户提供无缝体验的重要性。为此，我们采用了渐进式 Web 应用 [PWA](https://support.google.com/chrome/answer/9658361) 技术，
 这是一种能够将网页应用提升至接近原生应用体验的现代 Web 技术。通过 PWA，LobeChat 能够在桌面和移动设备上提供高度优化的用户体验，同时保持轻量级和高性能的特点。
@@ -291,7 +351,7 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地
 
 [![][image-feat-mobile]][docs-feat-mobile]
 
-### `9` [移动设备适配][docs-feat-mobile]
+### `12` [移动设备适配][docs-feat-mobile]
 
 针对移动设备进行了一系列的优化设计，以提升用户的移动体验。目前，我们正在对移动端的用户体验进行版本迭代，以实现更加流畅和直观的交互。如果您有任何建议或想法，我们非常欢迎您通过 GitHub Issues 或者 Pull Requests 提供反馈。
 
@@ -303,7 +363,7 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地
 
 [![][image-feat-theme]][docs-feat-theme]
 
-### `10` [自定义主题][docs-feat-theme]
+### `13` [自定义主题][docs-feat-theme]
 
 作为设计工程师出身，LobeChat 在界面设计上充分考虑用户的个性化体验，因此引入了灵活多变的主题模式，其中包括日间的亮色模式和夜间的深色模式。
 除了主题模式的切换，还提供了一系列的颜色定制选项，允许用户根据自己的喜好来调整应用的主题色彩。无论是想要沉稳的深蓝，还是希望活泼的桃粉，或者是专业的灰白，用户都能够在 LobeChat 中找到匹配自己风格的颜色选择。
@@ -367,9 +427,9 @@ LobeChat 提供了 Vercel 的 自托管版本 和 [Docker 镜像][docker-release
 >
 > 完整教程请查阅 [📘 构建属于自己的 Lobe Chat][docs-self-hosting]
 
-### `A` 使用 Vercel、Zeabur 或 Sealos 部署
+### `A` 使用 Vercel、Zeabur 、Sealos 或 阿里云计算巢 部署
 
-如果想在 Vercel 或 Zeabur 上部署该服务，可以按照以下步骤进行操作：
+如果想在 Vercel 、 Zeabur 或 阿里云 上部署该服务，可以按照以下步骤进行操作：
 
 - 准备好你的 [OpenAI API Key](https://platform.openai.com/account/api-keys) 。
 - 点击下方按钮开始部署： 直接使用 GitHub 账号登录即可，记得在环境变量页填入 `OPENAI_API_KEY` （必填） and `ACCESS_CODE`（推荐）；
@@ -378,9 +438,9 @@ LobeChat 提供了 Vercel 的 自托管版本 和 [Docker 镜像][docker-release
 
 <div align="center">
 
-|            使用 Vercel 部署             |                      使用 Zeabur 部署                       |                      使用 Sealos 部署                       |
-| :-------------------------------------: | :---------------------------------------------------------: | :---------------------------------------------------------: |
-| [![][deploy-button-image]][deploy-link] | [![][deploy-on-zeabur-button-image]][deploy-on-zeabur-link] | [![][deploy-on-sealos-button-image]][deploy-on-sealos-link] |
+|            使用 Vercel 部署             |                      使用 Zeabur 部署                       |                      使用 Sealos 部署                       |                           使用阿里云计算巢部署                            |
+| :-------------------------------------: | :---------------------------------------------------------: | :---------------------------------------------------------: | :-----------------------------------------------------------------------: |
+| [![][deploy-button-image]][deploy-link] | [![][deploy-on-zeabur-button-image]][deploy-on-zeabur-link] | [![][deploy-on-sealos-button-image]][deploy-on-sealos-link] | [![][deploy-on-alibaba-cloud-button-image]][deploy-on-alibaba-cloud-link] |
 
 </div>
 
@@ -477,9 +537,9 @@ API Key 是使用 LobeChat 进行大语言模型会话的必要信息，本节
 如果你发现注册 OpenAI 账户或者绑定外币信用卡比较麻烦，可以考虑借助一些知名的 OpenAI 第三方代理商来获取 API Key，这可以有效降低获取 OpenAI API Key 的门槛。但与此同时，一旦使用三方服务，你可能也需要承担潜在的风险，
 请根据你自己的实际情况自行决策。以下是常见的第三方模型代理商列表，供你参考：
 
-|                                                                                                                                                   | 服务商       | 特性说明                                                       | Proxy 代理地址            | 链接                            |
-| ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------- | ------------------------- | ------------------------------- |
-| <img src="https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/296272721-c3ac0bf3-e433-4496-89c4-ebdc20689c17.jpg" width="48" /> | **AiHubMix** | 使用 OpenAI 企业接口，全站模型价格为官方 **6 折**（含 GPT-4 ） | `https://aihubmix.com/v1` | [获取](https://lobe.li/XHnZIUP) |
+|                                                                                                                                                   | 服务商       | 特性说明                                                        | Proxy 代理地址            | 链接                            |
+| ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------------------------- | ------------------------- | ------------------------------- |
+| <img src="https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/296272721-c3ac0bf3-e433-4496-89c4-ebdc20689c17.jpg" width="48" /> | **AiHubMix** | 使用 OpenAI 企业接口，全站模型价格为官方 **86 折**（含 GPT-4 ） | `https://aihubmix.com/v1` | [获取](https://lobe.li/XHnZIUP) |
 
 > \[!WARNING]
 >
@@ -648,11 +708,12 @@ $ pnpm run dev
 </details>
 
 Copyright © 2023 [LobeHub][profile-link]. <br />
-This project is [MIT](./LICENSE) licensed.
+This project is [Apache 2.0](./LICENSE) licensed.
 
 <!-- LINK GROUP -->
 
 [back-to-top]: https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square
+[blog]: https://lobehub.com/zh/blog
 [chat-desktop]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/desktop/pagespeed.svg
 [chat-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/desktop/chat_preview_lobehub_com_chat.html
 [chat-mobile]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/mobile/pagespeed.svg
@@ -666,6 +727,8 @@ This project is [MIT](./LICENSE) licensed.
 [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-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=LobeChat%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
 [deploy-on-sealos-link]: https://cloud.sealos.io/?openapp=system-template%3FtemplateName%3Dlobe-chat
 [deploy-on-zeabur-button-image]: https://zeabur.com/button.svg
@@ -679,10 +742,14 @@ This project is [MIT](./LICENSE) licensed.
 [docker-release-shield]: https://img.shields.io/docker/v/lobehub/lobe-chat?color=369eff&label=docker&labelColor=black&logo=docker&logoColor=white&style=flat-square
 [docker-size-link]: https://hub.docker.com/r/lobehub/lobe-chat
 [docker-size-shield]: https://img.shields.io/docker/image-size/lobehub/lobe-chat?color=369eff&labelColor=black&style=flat-square
+[docs]: https://lobehub.com/zh/docs/usage/start
 [docs-dev-guide]: https://github.com/lobehub/lobe-chat/wiki/index
 [docs-docker]: https://lobehub.com/docs/self-hosting/platform/docker
 [docs-env-var]: https://lobehub.com/docs/self-hosting/environment-variables
 [docs-feat-agent]: https://lobehub.com/docs/usage/features/agent-market
+[docs-feat-auth]: https://lobehub.com/docs/usage/features/auth
+[docs-feat-database]: https://lobehub.com/docs/usage/features/database
+[docs-feat-knowledgebase]: https://lobehub.com/blog/knowledge-base
 [docs-feat-local]: https://lobehub.com/docs/usage/features/local-llm
 [docs-feat-mobile]: https://lobehub.com/docs/usage/features/mobile
 [docs-feat-plugin]: https://lobehub.com/docs/usage/features/plugin-system
@@ -692,7 +759,7 @@ This project is [MIT](./LICENSE) licensed.
 [docs-feat-theme]: https://lobehub.com/docs/usage/features/theme
 [docs-feat-tts]: https://lobehub.com/docs/usage/features/tts
 [docs-feat-vision]: https://lobehub.com/docs/usage/features/vision
-[docs-functionc-call]: https://platform.openai.com/docs/guides/function-calling
+[docs-functionc-call]: https://lobehub.com/zh/blog/openai-function-call
 [docs-lighthouse]: https://github.com/lobehub/lobe-chat/wiki/Lighthouse.zh-CN
 [docs-plugin-dev]: https://lobehub.com/docs/usage/plugins/development
 [docs-self-hosting]: https://lobehub.com/docs/self-hosting/start
@@ -707,13 +774,14 @@ This project is [MIT](./LICENSE) licensed.
 [github-action-test-shield]: https://img.shields.io/github/actions/workflow/status/lobehub/lobe-chat/test.yml?label=test&labelColor=black&logo=githubactions&logoColor=white&style=flat-square
 [github-contributors-link]: https://github.com/lobehub/lobe-chat/graphs/contributors
 [github-contributors-shield]: https://img.shields.io/github/contributors/lobehub/lobe-chat?color=c4f042&labelColor=black&style=flat-square
-[github-document-link]: https://lobehub.com/docs
 [github-forks-link]: https://github.com/lobehub/lobe-chat/network/members
 [github-forks-shield]: https://img.shields.io/github/forks/lobehub/lobe-chat?color=8ae8ff&labelColor=black&style=flat-square
+[github-hello-shield]: https://abroad.hellogithub.com/v1/widgets/recommend.svg?rid=39701baf5a734cb894ec812248a5655a&claim_uid=HxYvFN34htJzGCD&theme=dark&theme=neutral&theme=dark&theme=neutral
+[github-hello-url]: https://hellogithub.com/repository/39701baf5a734cb894ec812248a5655a
 [github-issues-link]: https://github.com/lobehub/lobe-chat/issues
 [github-issues-shield]: https://img.shields.io/github/issues/lobehub/lobe-chat?color=ff80eb&labelColor=black&style=flat-square
 [github-license-link]: https://github.com/lobehub/lobe-chat/blob/main/LICENSE
-[github-license-shield]: https://img.shields.io/github/license/lobehub/lobe-chat?color=white&labelColor=black&style=flat-square
+[github-license-shield]: https://img.shields.io/badge/license-apache%202.0-white?labelColor=black&style=flat-square
 [github-project-link]: https://github.com/lobehub/lobe-chat/projects
 [github-release-link]: https://github.com/lobehub/lobe-chat/releases
 [github-release-shield]: https://img.shields.io/github/v/release/lobehub/lobe-chat?color=369eff&labelColor=black&logo=github&style=flat-square
@@ -725,6 +793,9 @@ This project is [MIT](./LICENSE) licensed.
 [github-trending-url]: https://trendshift.io/repositories/2256
 [image-banner]: https://github.com/lobehub/lobe-chat/assets/28616219/9f155dff-4737-429f-9cad-a70a1a860c5f
 [image-feat-agent]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670869-f1ffbf66-42b6-42cf-a937-9ce1f8328514.png
+[image-feat-auth]: https://github.com/lobehub/lobe-chat/assets/17870709/8ce70e15-40df-451e-b700-66090fe5b8c2
+[image-feat-database]: https://github.com/lobehub/lobe-chat/assets/17870709/c27a0234-a4e9-40e5-8bcb-42d5ce7e40f9
+[image-feat-knowledgebase]: https://github.com/user-attachments/assets/77e58e1c-c82f-4341-b159-f4eeede9967f
 [image-feat-local]: https://github.com/lobehub/lobe-chat/assets/28616219/ca9a21bc-ea6c-4c90-bf4a-fa53b4fb2b5c
 [image-feat-mobile]: https://gw.alipayobjects.com/zos/kitchen/R441AuFS4W/mobile.webp
 [image-feat-plugin]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670883-33c43a5c-a512-467e-855c-fa299548cce5.png
@@ -734,7 +805,7 @@ This project is [MIT](./LICENSE) licensed.
 [image-feat-theme]: https://gw.alipayobjects.com/zos/kitchen/pvus1lo%26Z7/darkmode.webp
 [image-feat-tts]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072124-c9853d8d-f1b5-44a8-a305-45ebc0f6d19a.png
 [image-feat-vision]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072129-382bdf30-e3d6-4411-b5a0-249710b8ba08.png
-[image-overview]: https://github.com/lobehub/lobe-chat/assets/28616219/8b04c3c9-3d71-4fb4-bd9b-a4f415c5876d
+[image-overview]: https://github.com/lobehub/lobe-chat/assets/17870709/56b95d48-f573-41cd-8b38-387bf88bc4bf
 [image-star]: https://github.com/lobehub/lobe-chat/assets/17870709/cb06b748-513f-47c2-8740-d876858d7855
 [issues-link]: https://img.shields.io/github/issues/lobehub/lobe-chat.svg?style=flat
 [lobe-chat-plugins]: https://github.com/lobehub/lobe-chat-plugins
@@ -754,6 +825,7 @@ This project is [MIT](./LICENSE) licensed.
 [lobe-ui-github]: https://github.com/lobehub/lobe-ui
 [lobe-ui-link]: https://www.npmjs.com/package/@lobehub/ui
 [lobe-ui-shield]: https://img.shields.io/npm/v/@lobehub/ui?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
+[official-site]: https://lobehub.com
 [pr-welcome-link]: https://github.com/lobehub/lobe-chat/pulls
 [pr-welcome-shield]: https://img.shields.io/badge/🤯_pr_welcome-%E2%86%92-ffcb47?labelColor=black&style=for-the-badge
 [profile-link]: https://github.com/lobehub
@@ -776,5 +848,5 @@ This project is [MIT](./LICENSE) licensed.
 [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-shield]: https://img.shields.io/website?down_message=offline&label=vercel&labelColor=black&logo=vercel&style=flat-square&up_message=online&url=https%3A%2F%2Fchat-preview.lobehub.com
-[vercel-shield-badge]: https://img.shields.io/website?down_message=offline&label=try%20lobechat&labelColor=black&logo=vercel&style=for-the-badge&up_message=online&url=https%3A%2F%2Fchat-preview.lobehub.com
+[vercel-shield]: https://img.shields.io/badge/vercel-online-55b467?labelColor=black&logo=vercel&style=flat-square
+[vercel-shield-badge]: https://img.shields.io/badge/TRY%20LOBECHAT-ONLINE-55b467?labelColor=black&logo=vercel&style=for-the-badge

codecov.yml

@@ -0,0 +1,11 @@
+coverage:
+  status:
+    project:
+      default: off
+      server:
+        flags:
+          - server
+      app:
+        flags:
+          - app
+    patch: off

contributing/Basic/Feature-Development.md

@@ -4,14 +4,14 @@ This document aims to guide developers on how to develop a complete feature requ
 
 We will use the implementation of sessionGroup as an example: [✨ feat: add session group manager](https://github.com/lobehub/lobe-chat/pull/1055), and explain the complete implementation process through the following six main sections:
 
-1. Data Model / Database Definition
-2. Service Implementation / Model Implementation
-3. Frontend Data Flow Store Implementation
-4. UI Implementation and Action Binding
-5. Data Migration
-6. Data Import and Export
+1. [Data Model / Database Definition](#1-data-model--database-definition)
+2. [Service Implementation / Model Implementation](#2-service-implementation--model-implementation)
+3. [Frontend Data Flow Store Implementation](#3-frontend-data-flow-store-implementation)
+4. [UI Implementation and Action Binding](#4-ui-implementation-and-action-binding)
+5. [Data Migration](#5-data-migration)
+6. [Data Import and Export](#6-data-import-and-export)
 
-## 1. Database Section
+## 1. Data Model / Database Definition
 
 To implement the Session Group feature, it is necessary to define the relevant data model and indexes at the database level.
 
@@ -119,7 +119,7 @@ As a result, you can now view the `sessionGroups` table in the `LOBE_CHAT_DB` in
 
 ![](https://github.com/lobehub/lobe-chat/assets/28616219/aea50f66-4060-4a32-88c8-b3c672d05be8)
 
-## 2. Model and Service Section
+## 2. Service Implementation / Model Implementation
 
 ### Define Model
 
@@ -176,7 +176,7 @@ class SessionService {
 }
 ```
 
-## 3. Store Action Section
+## 3. Frontend Data Flow Store Implementation
 
 In the LobeChat application, the Store module is used to manage the frontend state of the application. The Actions within it are functions that trigger state updates, usually by calling methods in the service layer to perform actual data processing operations and then updating the state in the Store. We use `zustand` as the underlying dependency for the Store module. For a detailed practical introduction to state management, you can refer to [📘 Best Practices for State Management](../State-Management/State-Management-Intro.zh-CN.md).
 
@@ -351,7 +351,7 @@ Since all data retrieval in the UI is implemented using syntax like `useSessionS
 >
 > If you are not familiar with the concept and functionality of selectors, you can refer to the section [📘 Data Storage and Retrieval Module](./State-Management-Selectors.en-US) for relevant information.
 
-## IV. UI Section
+## 4. UI Implementation and Action Binding
 
 Bind Store Action in the UI component to implement interactive logic, for example `CreateGroupModal`:
 
@@ -570,7 +570,7 @@ export class LocalDB extends Dexie {
 
 This is our data migration strategy. When performing the migration, it is essential to ensure the correctness of the migration script and validate the migration results through thorough testing.
 
-## VI. Data Import and Export
+## 6. Data Import and Export
 
 In LobeChat, the data import and export feature is designed to ensure that users can migrate their data between different devices. This includes session, topic, message, and settings data. In the implementation of the Session Group feature, we also need to handle data import and export to ensure that the complete exported data can be restored exactly the same on other devices.
 

contributing/Basic/Feature-Development.zh-CN.md

@@ -4,14 +4,14 @@
 
 我们将以 sessionGroup 的实现为示例：[✨ feat: add session group manager](https://github.com/lobehub/lobe-chat/pull/1055) ， 通过以下六个主要部分来阐述完整的实现流程：
 
-1. 数据模型 / 数据库定义
-2. Service 实现 / Model 实现
-3. 前端数据流 Store 实现
-4. UI 实现与 action 绑定
-5. 数据迁移
-6. 数据导入导出
+1. [数据模型 / 数据库定义](#一数据模型--数据库定义)
+2. [Service 实现 / Model 实现](#二service-实现--model-实现)
+3. [前端数据流 Store 实现](#三前端数据流-store-实现)
+4. [UI 实现与 action 绑定](#四ui-实现与-action-绑定)
+5. [数据迁移](#五数据迁移)
+6. [数据导入导出](#六数据导入导出)
 
-## 一、数据库部分
+## 一、数据模型 / 数据库定义
 
 为了实现 Session Group 功能，首先需要在数据库层面定义相关的数据模型和索引。
 
@@ -119,7 +119,7 @@ export class LocalDB extends Dexie {
 
 ![](https://github.com/lobehub/lobe-chat/assets/28616219/aea50f66-4060-4a32-88c8-b3c672d05be8)
 
-## 二、Model 与 Service 部分
+## 二、Service 实现 / Model 实现
 
 ### 定义 Model
 
@@ -176,7 +176,7 @@ class SessionService {
 }
 ```
 
-## 三、Store Action 部分
+## 三、前端数据流 Store 实现
 
 在 LobeChat 应用中，Store 是用于管理应用前端状态的模块。其中的 Action 是触发状态更新的函数，通常会调用服务层的方法来执行实际的数据处理操作，然后更新 Store 中的状态。我们采用了 `zustand` 作为 Store 模块的底层依赖，对于状态管理的详细实践介绍，可以查阅 [📘 状态管理最佳实践](../State-Management/State-Management-Intro.zh-CN.md)
 
@@ -351,7 +351,7 @@ const customSessionGroups = (s: SessionStore): CustomSessionGroup[] => s.customS
 >
 > 如果你对 Selectors 的概念和功能不太了解，可以查阅 [📘 数据存储取数模块](../State-Management/State-Management-Selectors.zh-CN.md) 部分了解相关内容。
 
-## 四、UI 部分
+## 四、UI 实现与 action 绑定
 
 在 UI 组件中绑定 Store Action 实现交互逻辑，例如 `CreateGroupModal`：
 

contributing/Basic/Intro.md

@@ -1,22 +1,26 @@
 # Technical Development Getting Started Guide
 
-Welcome to the LobeChat technical development getting started guide. LobeChat is an AI conversation application built on the Next.js framework, which integrates a series of technology stacks to achieve diverse functions and features. This guide will provide a detailed introduction to the main technical components of LobeChat and how to configure and use these technologies in your development environment.
+Welcome to the LobeChat Technical Development Getting Started Guide. LobeChat is an AI conversation application built on the Next.js framework, incorporating a range of technology stacks to achieve diverse functionalities and features. This guide will detail the main technical components of LobeChat and how to configure and use these technologies in your development environment.
 
 #### TOC
 
 - [Basic Technology Stack](#basic-technology-stack)
 - [Folder Directory Structure](#folder-directory-structure)
+- [Local Development Environment Setup](#local-development-environment-setup)
+- [Code Style and Contribution Guide](#code-style-and-contribution-guide)
+- [Internationalization Implementation Guide](#internationalization-implementation-guide)
+- [Appendix: Resources and References](#appendix-resources-and-references)
 
 ## Basic Technology Stack
 
-The core technology stack of LobeChat includes:
+The core technology stack of LobeChat is as follows:
 
-- **Framework**: We have chosen [Next.js](https://nextjs.org/), a powerful React framework that provides key features such as server-side rendering, routing framework, and Router Handler for our project.
-- **Component Library**: We use [Ant Design (antd)](https://ant.design/) as the basic component library, and also introduce [lobe-ui](https://github.com/lobehub/lobe-ui) as our business component library.
-- **State Management**: We have opted for [zustand](https://github.com/pmndrs/zustand), a lightweight and easy-to-use state management library.
+- **Framework**: We chose [Next.js](https://nextjs.org/), a powerful React framework that provides key features such as server-side rendering, routing framework, and Router Handler.
+- **Component Library**: We use [Ant Design (antd)](https://ant.design/) as the basic component library, along with [lobe-ui](https://github.com/lobehub/lobe-ui) as our business component library.
+- **State Management**: We selected [zustand](https://github.com/pmndrs/zustand), a lightweight and easy-to-use state management library.
 - **Network Requests**: We use [swr](https://swr.vercel.app/), a React Hooks library for data fetching.
-- **Routing**: For routing management, we directly use the solution provided by [Next.js](https://nextjs.org/) itself.
-- **Internationalization**: We use [i18next](https://www.i18next.com/) to implement multi-language support for the application.
+- **Routing**: For routing management, we directly use the solution provided by [Next.js](https://nextjs.org/).
+- **Internationalization**: We use [i18next](https://www.i18next.com/) to support multiple languages in the application.
 - **Styling**: We use [antd-style](https://github.com/ant-design/antd-style), a CSS-in-JS library that complements Ant Design.
 - **Unit Testing**: We use [vitest](https://github.com/vitest-dev/vitest) for unit testing.
 
@@ -26,18 +30,82 @@ The folder directory structure of LobeChat is as follows:
 
 ```bash
 src
-├── app        # Main logic of the application and code related to state management
+├── app        # Code related to the main logic and state management of the application
 ├── components # Reusable UI components
-├── config     # Application configuration files, including client-side environment variables and server-side environment variables
+├── config     # Application configuration files, including client and server environment variables
 ├── const      # Used to define constants, such as action types, route names, etc.
-├── features   # Function modules related to business features, such as Agent settings, plugin development pop-ups, etc.
-├── hooks      # Custom utility hooks reused throughout the application
+├── 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      # Common utility functions
+└── utils      # General utility functions
 ```
 
-For a detailed introduction to the directory structure, please refer to: [Folder Directory Structure](Folder-Structure.en-US.md)
+For a detailed introduction to the directory structure, see: [Folder Directory Structure](Folder-Structure.zh-CN.md)
+
+## Local Development Environment Setup
+
+This section outlines setting up the development environment and local development. Before starting, please ensure that Node.js, Git, and your chosen package manager (Bun or PNPM) are installed in your local environment.
+
+We recommend using WebStorm as your integrated development environment (IDE).
+
+1. **Get the code**: Clone the LobeChat code repository locally:
+
+```bash
+git clone https://github.com/lobehub/lobe-chat.git
+```
+
+2. **Install dependencies**: Enter the project directory and install the required dependencies:
+
+```bash
+cd lobe-chat
+# If you use Bun
+bun install
+# If you use PNPM
+pnpm install
+```
+
+3. **Run and debug**: Start the local development server and begin your development journey:
+
+```bash
+# Start the development server with Bun
+bun run dev
+# Visit http://localhost:3010 to view the application
+```
+
+> \[!IMPORTANT]\
+> If you encounter the error "Could not find 'stylelint-config-recommended'" when installing dependencies with `npm`, please reinstall the dependencies using `pnpm` or `bun`.
+
+Now, you should be able to see the welcome page of LobeChat in your browser. For a detailed environment setup guide, please refer to [Development Environment Setup Guide](Setup-Development.zh-CN.md).
+
+## Code Style and Contribution Guide
+
+In the LobeChat project, we place great emphasis on the quality and consistency of the code. For this reason, we have established a series of code style standards and contribution processes to ensure that every developer can smoothly participate in the project. Here are the code style and contribution guidelines you need to follow as a developer.
+
+- **Code Style**: We use `@lobehub/lint` to unify the code style, including ESLint, Prettier, remarklint, and stylelint configurations. Please adhere to our code standards to maintain code consistency and readability.
+- **Contribution Process**: We use gitmoji and semantic release for code submission and release processes. Please use gitmoji to annotate your commit messages and ensure compliance with the semantic release standards so that our automation systems can correctly handle version control and releases.
+
+All contributions will undergo code review. Maintainers may suggest modifications or requirements. Please respond actively to review comments and make timely adjustments. We look forward to your participation and contribution.
+
+For detailed code style and contribution guidelines, please refer to [Code Style and Contribution Guide](Contributing-Guidelines.zh-CN.md).
+
+## Internationalization Implementation Guide
+
+LobeChat uses `i18next` and `lobe-i18n` to implement multilingual support, ensuring a global user experience.
+
+Internationalization files are located in `src/locales`, containing the default language (Chinese). We generate other language JSON files automatically through `lobe-i18n`.
+
+If you want to add a new language, follow specific steps detailed in [New Language Addition Guide](../Internationalization/Add-New-Locale.zh-CN.md). We encourage you to participate in our internationalization efforts to provide better services to global users.
+
+For a detailed guide on internationalization implementation, please refer to [Internationalization Implementation Guide](../Internationalization/Internationalization-Implementation.zh-CN.md).
+
+## Appendix: Resources and References
+
+To support developers in better understanding and using the technology stack of LobeChat, we provide a comprehensive list of resources and references — [LobeChat Resources and References](https://github.com/lobehub/lobe-chat/wiki/Resources.zh-CN) - Visit our maintained list of resources, including tutorials, articles, and other useful links.
+
+We encourage developers to utilize these resources to deepen their learning and enhance their skills, join community discussions through [LobeChat GitHub Discussions](https://github.com/lobehub/lobe-chat/discussions) or [Discord](https://discord.com/invite/AYFPHvv2jT), ask questions, or share your experiences.
+
+If you have any questions or need further assistance, please do not hesitate to contact us through the above channels.

contributing/Basic/Intro.zh-CN.md

@@ -76,6 +76,9 @@ bun run dev
 # 访问 http://localhost:3010 查看应用
 ```
 
+> \[!IMPORTANT]\
+> 如果使用`npm`安装依赖出现`Could not find "stylelint-config-recommended"`错误，请使用 `pnpm` 或者 `bun` 重新安装依赖。
+
 现在，你应该可以在浏览器中看到 LobeChat 的欢迎页面。详细的环境配置指南，请参考 [开发环境设置指南](Setup-Development.zh-CN.md)。
 
 ## 代码风格与贡献指南

docker-compose/local/.env.example

@@ -0,0 +1,35 @@
+# Proxy, if you need it
+# HTTP_PROXY=http://localhost:7890
+# HTTPS_PROXY=http://localhost:7890
+
+
+# Other environment variables, as needed. You can refer to the environment variables configuration for the client version, making sure not to have ACCESS_CODE.
+# OPENAI_API_KEY=sk-xxxx
+# OPENAI_PROXY_URL=https://api.openai.com/v1
+# OPENAI_MODEL_LIST=...
+
+
+# ===========================
+# ====== Preset config ====== 
+# ===========================
+# if no special requirements, no need to change
+LOBE_PORT=3210
+CASDOOR_PORT=8000
+MINIO_PORT=9000
+
+# Postgres related, which are the necessary environment variables for DB
+LOBE_DB_NAME=lobechat
+POSTGRES_PASSWORD=uWNZugjBqixf8dxC
+
+# Casdoor secret
+AUTH_CASDOOR_ID=a387a4892ee19b1a2249
+AUTH_CASDOOR_SECRET=dbf205949d704de81b0b5b3603174e23fbecc354
+
+# MinIO S3 configuration
+MINIO_ROOT_USER=YOUR_MINIO_USER
+MINIO_ROOT_PASSWORD=YOUR_MINIO_PASSWORD
+
+# Configure the bucket information of MinIO
+MINIO_LOBE_BUCKET=lobe
+S3_ACCESS_KEY_ID=soaucnP8Bip0TDdUjxng
+S3_SECRET_ACCESS_KEY=ZPUzvY34umfcfxvWKSv0P00vczVMB6YmgJS5J9eO

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

@@ -0,0 +1,36 @@
+# Proxy，如果你需要的话（比如你使用 GitHub 作为鉴权服务提供商）
+# HTTP_PROXY=http://localhost:7890
+# HTTPS_PROXY=http://localhost:7890
+
+
+# 其他环境变量，视需求而定，可以参照客户端版本的环境变量配置，注意不要有 ACCESS_CODE
+# OPENAI_API_KEY=sk-xxxx
+# OPENAI_PROXY_URL=https://api.openai.com/v1
+# OPENAI_MODEL_LIST=...
+
+
+# ===================
+# ===== 预设配置 =====
+# ===================
+# 如没有特殊需要不用更改
+LOBE_PORT=3210
+CASDOOR_PORT=8000
+MINIO_PORT=9000
+
+# Postgres 相关，也即 DB 必须的环境变量
+LOBE_DB_NAME=lobechat
+POSTGRES_PASSWORD=uWNZugjBqixf8dxC
+
+# Casdoor secret
+AUTH_CASDOOR_ID=a387a4892ee19b1a2249
+AUTH_CASDOOR_SECRET=dbf205949d704de81b0b5b3603174e23fbecc354
+
+# MinIO S3 配置
+MINIO_ROOT_USER=YOUR_MINIO_USER
+MINIO_ROOT_PASSWORD=YOUR_MINIO_PASSWORD
+
+# 在下方配置 minio 中添加的桶
+MINIO_LOBE_BUCKET=lobe
+S3_ACCESS_KEY_ID=soaucnP8Bip0TDdUjxng
+S3_SECRET_ACCESS_KEY=ZPUzvY34umfcfxvWKSv0P00vczVMB6YmgJS5J9eO
+

docker-compose/local/docker-compose.yml

@@ -0,0 +1,105 @@
+name: lobe-chat-database
+services:
+  network-service:
+    image: alpine
+    container_name: lobe-network
+    ports:
+      - '${MINIO_PORT}:${MINIO_PORT}' # MinIO API
+      - '9001:9001' # MinIO Console
+      - '${CASDOOR_PORT}:${CASDOOR_PORT}' # Casdoor
+      - '${LOBE_PORT}:3210' # LobeChat
+    command: tail -f /dev/null
+    networks:
+      - lobe-network
+
+  postgresql:
+    image: pgvector/pgvector:pg16
+    container_name: lobe-postgres
+    ports:
+      - '5432:5432'
+    volumes:
+      - './data:/var/lib/postgresql/data'
+    environment:
+      - 'POSTGRES_DB=${LOBE_DB_NAME}'
+      - 'POSTGRES_PASSWORD=${POSTGRES_PASSWORD}'
+    healthcheck:
+      test: ['CMD-SHELL', 'pg_isready -U postgres']
+      interval: 5s
+      timeout: 5s
+      retries: 5
+    restart: always
+    networks:
+      - lobe-network
+
+  minio:
+    image: minio/minio
+    container_name: lobe-minio
+    network_mode: 'service:network-service'
+    volumes:
+      - './s3_data:/etc/minio/data'
+    environment:
+      - 'MINIO_ROOT_USER=${MINIO_ROOT_USER}'
+      - 'MINIO_ROOT_PASSWORD=${MINIO_ROOT_PASSWORD}'
+      - 'MINIO_API_CORS_ALLOW_ORIGIN=http://localhost:${LOBE_PORT}'
+    restart: always
+    command: >
+      server /etc/minio/data --address ":${MINIO_PORT}" --console-address ":9001"
+
+
+  casdoor:
+    image: casbin/casdoor
+    container_name: lobe-casdoor
+    entrypoint: /bin/sh -c './server --createDatabase=true'
+    network_mode: 'service:network-service'
+    depends_on:
+      postgresql:
+        condition: service_healthy
+    environment:
+      RUNNING_IN_DOCKER: 'true'
+      driverName: 'postgres'
+      dataSourceName: 'user=postgres password=${POSTGRES_PASSWORD} host=postgresql port=5432 sslmode=disable dbname=casdoor'
+      origin: 'http://localhost:${CASDOOR_PORT}'
+      runmode: 'dev'
+    volumes:
+      - ./init_data.json:/init_data.json
+
+  lobe:
+    image: lobehub/lobe-chat-database
+    container_name: lobe-chat
+    network_mode: 'service:network-service'
+    depends_on:
+      postgresql:
+        condition: service_healthy
+      network-service:
+        condition: service_started
+      minio:
+        condition: service_started
+      casdoor:
+        condition: service_started
+
+    environment:
+      - 'APP_URL=http://localhost:3210'
+      - 'NEXT_AUTH_SSO_PROVIDERS=casdoor'
+      - 'KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ='
+      - 'NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg'
+      - 'AUTH_URL=http://localhost:${LOBE_PORT}/api/auth'
+      - 'AUTH_CASDOOR_ISSUER=http://localhost:${CASDOOR_PORT}'
+      - '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'
+      - 'LLM_VISION_IMAGE_USE_BASE64=1'
+    env_file:
+      - .env
+    restart: always
+
+volumes:
+  data:
+    driver: local
+  s3_data:
+    driver: local
+
+networks:
+  lobe-network:
+    driver: bridge

docker-compose/local/init_data.json

@@ -0,0 +1,777 @@
+{
+  "adapters": [
+    {
+      "owner": "built-in",
+      "name": "user-adapter-built-in",
+      "createdTime": "2024-09-09T09:26:13Z",
+      "table": "casbin_user_rule",
+      "useSameDb": true,
+      "type": "",
+      "databaseType": "",
+      "host": "",
+      "port": 0,
+      "user": "",
+      "password": "",
+      "database": ""
+    },
+    {
+      "owner": "built-in",
+      "name": "api-adapter-built-in",
+      "createdTime": "2024-09-09T09:26:12Z",
+      "table": "casbin_api_rule",
+      "useSameDb": true,
+      "type": "",
+      "databaseType": "",
+      "host": "",
+      "port": 0,
+      "user": "",
+      "password": "",
+      "database": ""
+    }
+  ],
+  "applications": [
+    {
+      "owner": "admin",
+      "name": "app-built-in",
+      "createdTime": "2024-09-09T09:26:06Z",
+      "displayName": "LobeChat",
+      "logo": "https://lobehub.com/icon-192x192.png",
+      "homepageUrl": "https://lobehub.com",
+      "description": "LobeChat",
+      "organization": "built-in",
+      "cert": "cert-built-in",
+      "headerHtml": "",
+      "enablePassword": true,
+      "enableSignUp": true,
+      "enableSigninSession": false,
+      "enableAutoSignin": false,
+      "enableCodeSignin": false,
+      "enableSamlCompress": false,
+      "enableSamlC14n10": false,
+      "enableSamlPostBinding": false,
+      "enableWebAuthn": false,
+      "enableLinkWithEmail": true,
+      "orgChoiceMode": "",
+      "samlReplyUrl": "",
+      "providers": [],
+      "signinMethods": [
+        {
+          "name": "Password",
+          "displayName": "Password",
+          "rule": "All"
+        }
+      ],
+      "signupItems": [
+        {
+          "name": "ID",
+          "visible": false,
+          "required": true,
+          "prompted": false,
+          "customCss": "",
+          "label": "",
+          "placeholder": "",
+          "regex": "",
+          "rule": "Random"
+        },
+        {
+          "name": "Username",
+          "visible": true,
+          "required": true,
+          "prompted": false,
+          "customCss": "",
+          "label": "",
+          "placeholder": "",
+          "regex": "",
+          "rule": "None"
+        },
+        {
+          "name": "Display name",
+          "visible": true,
+          "required": true,
+          "prompted": false,
+          "customCss": "",
+          "label": "",
+          "placeholder": "",
+          "regex": "",
+          "rule": "None"
+        },
+        {
+          "name": "Password",
+          "visible": true,
+          "required": true,
+          "prompted": false,
+          "customCss": "",
+          "label": "",
+          "placeholder": "",
+          "regex": "",
+          "rule": "None"
+        },
+        {
+          "name": "Confirm password",
+          "visible": true,
+          "required": true,
+          "prompted": false,
+          "customCss": "",
+          "label": "",
+          "placeholder": "",
+          "regex": "",
+          "rule": "None"
+        },
+        {
+          "name": "Signup button",
+          "visible": true,
+          "required": false,
+          "prompted": false,
+          "customCss": "",
+          "label": "",
+          "placeholder": "",
+          "regex": "",
+          "rule": ""
+        }
+      ],
+      "signinItems": [
+        {
+          "name": "Back button",
+          "visible": true,
+          "label": "",
+          "customCss": ".back-button {\n      top: 65px;\n      left: 15px;\n      position: absolute;\n}\n.back-inner-button{}",
+          "placeholder": "",
+          "rule": "None",
+          "isCustom": false
+        },
+        {
+          "name": "Languages",
+          "visible": true,
+          "label": "",
+          "customCss": ".login-languages {\n    top: 55px;\n    right: 5px;\n    position: absolute;\n}",
+          "placeholder": "",
+          "rule": "None",
+          "isCustom": false
+        },
+        {
+          "name": "Logo",
+          "visible": true,
+          "label": "",
+          "customCss": ".login-logo-box {}",
+          "placeholder": "",
+          "rule": "None",
+          "isCustom": false
+        },
+        {
+          "name": "Signin methods",
+          "visible": true,
+          "label": "",
+          "customCss": ".signin-methods {}",
+          "placeholder": "",
+          "rule": "None",
+          "isCustom": false
+        },
+        {
+          "name": "Username",
+          "visible": true,
+          "label": "",
+          "customCss": ".login-username {}\n.login-username-input{}",
+          "placeholder": "",
+          "rule": "None",
+          "isCustom": false
+        },
+        {
+          "name": "Password",
+          "visible": true,
+          "label": "",
+          "customCss": ".login-password {}\n.login-password-input{}",
+          "placeholder": "",
+          "rule": "None",
+          "isCustom": false
+        },
+        {
+          "name": "Agreement",
+          "visible": true,
+          "label": "",
+          "customCss": ".login-agreement {}",
+          "placeholder": "",
+          "rule": "None",
+          "isCustom": false
+        },
+        {
+          "name": "Forgot password?",
+          "visible": true,
+          "label": "",
+          "customCss": ".login-forget-password {\n    display: inline-flex;\n    justify-content: space-between;\n    width: 320px;\n    margin-bottom: 25px;\n}",
+          "placeholder": "",
+          "rule": "None",
+          "isCustom": false
+        },
+        {
+          "name": "Login button",
+          "visible": true,
+          "label": "",
+          "customCss": ".login-button-box {\n    margin-bottom: 5px;\n}\n.login-button {\n    width: 100%;\n}",
+          "placeholder": "",
+          "rule": "None",
+          "isCustom": false
+        },
+        {
+          "name": "Signup link",
+          "visible": true,
+          "label": "",
+          "customCss": ".login-signup-link {\n    margin-bottom: 24px;\n    display: flex;\n    justify-content: end;\n}",
+          "placeholder": "",
+          "rule": "None",
+          "isCustom": false
+        },
+        {
+          "name": "Providers",
+          "visible": true,
+          "label": "",
+          "customCss": ".provider-img {\n      width: 30px;\n      margin: 5px;\n}\n.provider-big-img {\n      margin-bottom: 10px;\n}",
+          "placeholder": "",
+          "rule": "small",
+          "isCustom": false
+        }
+      ],
+      "grantTypes": ["authorization_code"],
+      "organizationObj": null,
+      "certPublicKey": "",
+      "tags": [],
+      "samlAttributes": null,
+      "isShared": false,
+      "clientId": "a387a4892ee19b1a2249",
+      "clientSecret": "dbf205949d704de81b0b5b3603174e23fbecc354",
+      "redirectUris": ["http://localhost:3210/api/auth/callback/casdoor"],
+      "tokenFormat": "JWT",
+      "tokenSigningMethod": "",
+      "tokenFields": [],
+      "expireInHours": 168,
+      "refreshExpireInHours": 0,
+      "signupUrl": "",
+      "signinUrl": "",
+      "forgetUrl": "",
+      "affiliationUrl": "",
+      "termsOfUse": "",
+      "signupHtml": "",
+      "signinHtml": "",
+      "themeData": null,
+      "footerHtml": "",
+      "formCss": "",
+      "formCssMobile": "",
+      "formOffset": 2,
+      "formSideHtml": "",
+      "formBackgroundUrl": "",
+      "failedSigninLimit": 5,
+      "failedSigninFrozenTime": 15
+    }
+  ],
+  "certs": [
+    {
+      "owner": "admin",
+      "name": "cert-built-in",
+      "createdTime": "2024-09-09T09:26:06Z",
+      "displayName": "Built-in Cert",
+      "scope": "JWT",
+      "type": "x509",
+      "cryptoAlgorithm": "RS256",
+      "bitSize": 4096,
+      "expireInYears": 20,
+      "certificate": "-----BEGIN CERTIFICATE-----\nMIIE3TCCAsWgAwIBAgIDAeJAMA0GCSqGSIb3DQEBCwUAMCgxDjAMBgNVBAoTBWFk\nbWluMRYwFAYDVQQDEw1jZXJ0LWJ1aWx0LWluMB4XDTI0MDkwOTA5MjYxMVoXDTQ0\nMDkwOTA5MjYxMVowKDEOMAwGA1UEChMFYWRtaW4xFjAUBgNVBAMTDWNlcnQtYnVp\nbHQtaW4wggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQC3EnylZ2VurCm4\ngVtZHBUw67qvuKoYuU9whqaJr2UQEboIX4ca+FtZCjDgcBoD80lwSoYrcKpTG+DI\nVEMDznUHOjKwongRWclV1jeE3jZqObtmG9872yt/WX+nxQLyDrk+nUGhci6Qrhgo\nYToN1DYaMqMV1Pi8catx8S0W3gg+ilb9mG3xdFpQo89o84mJhajTE/5/0jBuQ50D\nx8CRolpRWjZ6i9RNVfFQglei+aW0RNf1PY6RqMkxc/Hy0XwXf/bjM5Ax7Aajwteh\nx0Q1zeUaRMMhFu6REtz345oJdLJpUkpFwJN4dPQ35a0tqnjkD1MLZjvBhSgOt5IP\nAJA1HmcR83RMBS8B3iV6y/clPjr02cjyasORy+kL/aFMfZfwvuRWX1NqRE99+rUT\nlPszH2SQi7PCUItQK72nnMYWBMXgyS8/Mra48q7LDAB/ZQnWuEG1+P1SdsQUWM2U\naxkgjmfMNATVAgufrLOcOZDxAwVS7+quCF5f/QPTWaFqz5ofcpoUlf0iriv/k1mi\nl7OghX0eqyLI2cCSma+dgB1eMni91eDCLVRT25mGDYreFjkpAwpMx2uaBk5e6ffT\n2jmZ2Zp9iCrUomLXDNiwY2wZDClcDKFiHNhNPAN3IbvBC3c6qpt0dLsWvGYW2IQT\nTnI71r/YY1XN/mTa4t/zwI+/kghjMQIDAQABoxAwDjAMBgNVHRMBAf8EAjAAMA0G\nCSqGSIb3DQEBCwUAA4ICAQBJUMBYJXnNihlGA2NMFIZMlsnW+5tjUqqK/Pv+oSpt\nrqZxwDKFZL0NMxd4pVnLxIdU5HEcN2e01Xyqlaf5Tm3BZN6MaRVZAIRVfvxcNESQ\nYA0jSFjsJzZUFGIQf8P9a5u+7qqSmj4tZx4XaRjOGSOf8t2RMJDmAbUeydLiD8ny\nCcxTzetmyYky8J3NBUoYGRbwU6KKbkxHbT35QheAb3jT4CELopLZ57Aa5Fb8xTjQ\n6tNqwZ+Z3993FkTOWPYLNLM1l46oN3g9yVY4ncGjUJkxsLTpAXB4I+wdqeew9XXe\nxWNcY3cWWjA5VXgCNzntkPFM1D5IWkgP8MYVCvdv0Unfo78PahwVMoQMnDG4xLuS\n50gVKpukHLZQJNFPF0X4u/JeXauKPv/w7ssTTAK+8RIBYxBXQ72zDJNHyTqldR4e\nfPHZfcW7OTmUr5FGNZThyW7ipvZRWcLM4u4IaWF2ncllOSqAXs1gDxkk201J7Lrb\noZOjC3zgxE9HTCXpiszOAt5I38++5ufE3/hJW3ckz0jaJDeFqUphnn8eQhXPSwtC\nR8TL4ZpXSAFEpwahG+fCfZDK2KyPME33eXV3jtsYf0QHerYiMnP+tf1vAk3qtOzo\nE6Iv16fpBUvshk1Gm6E6bdhsP0hCrMwV4dm8uC3S52qcFiWZ6AC/HURaMbY+/lOs\n0A==\n-----END CERTIFICATE-----\n",
+      "privateKey": "-----BEGIN RSA PRIVATE KEY-----\nMIIJKAIBAAKCAgEAtxJ8pWdlbqwpuIFbWRwVMOu6r7iqGLlPcIamia9lEBG6CF+H\nGvhbWQow4HAaA/NJcEqGK3CqUxvgyFRDA851BzoysKJ4EVnJVdY3hN42ajm7Zhvf\nO9srf1l/p8UC8g65Pp1BoXIukK4YKGE6DdQ2GjKjFdT4vHGrcfEtFt4IPopW/Zht\n8XRaUKPPaPOJiYWo0xP+f9IwbkOdA8fAkaJaUVo2eovUTVXxUIJXovmltETX9T2O\nkajJMXPx8tF8F3/24zOQMewGo8LXocdENc3lGkTDIRbukRLc9+OaCXSyaVJKRcCT\neHT0N+WtLap45A9TC2Y7wYUoDreSDwCQNR5nEfN0TAUvAd4lesv3JT469NnI8mrD\nkcvpC/2hTH2X8L7kVl9TakRPffq1E5T7Mx9kkIuzwlCLUCu9p5zGFgTF4MkvPzK2\nuPKuywwAf2UJ1rhBtfj9UnbEFFjNlGsZII5nzDQE1QILn6yznDmQ8QMFUu/qrghe\nX/0D01mhas+aH3KaFJX9Iq4r/5NZopezoIV9HqsiyNnAkpmvnYAdXjJ4vdXgwi1U\nU9uZhg2K3hY5KQMKTMdrmgZOXun309o5mdmafYgq1KJi1wzYsGNsGQwpXAyhYhzY\nTTwDdyG7wQt3OqqbdHS7FrxmFtiEE05yO9a/2GNVzf5k2uLf88CPv5IIYzECAwEA\nAQKCAgEAtGj7fOTQCKiQ1MplgwMxvuwPJWwN9B9qMbIAHF9EcPmHIwlA00s8ehqY\n4BSZDpuKG6bVYam9r/khI0omYHHs0hqAKaFyQWcCChz4yW9SoIwUKSP+cbYiv3Ur\nX+G+bVwlIZdHPhqP2PQ3ylNGKqqeRmLwZGtkVBCQq9DIZmiYJ0mdQHwenHvVJPLJ\nStv1Bhk5rgleHAi+wWrQKRGIq/walWEZntp9dVjkXjqUsn7i1SuixoLLJK/41Us1\ne90FNQNeAbimuQun32n7peoBRiSJScHJqao3n6+/ImqhOgBOcYwutV559ZMLuKoW\nZ5I/YD/ZzroI2USnnRk6Tp53fmFfn55JyLRjXf82jGeavScNEpTfvE+qT9SGOSA9\nF8YkEzsnAOM6tov2NEkY9Ofjh25fc4QAoqbQY8HdIYUwB+BHU63Hhdgz5VVy2f+v\nXJIy4z86QlWsXfQkimz02+AXD2jOSMH+ne3Qs3Z6l2hHhcxJj+lnp2qUXI6iYBOI\nVkQ8D3WPpBldZ5cOGCN0MC/gcv7WTiLDdl4nLba+qeqTFCO2Ygc/knMU7RvZew5U\nCIvxdvkAwjpvY7xN6er/C0jSp57sE2IoqE2QaNBC9YCn34sWgSDb2AkDvmhdSixD\nNCumHKp0at4e13urQTduHKPTZiUkAKG93vcuLONFmDAco0Mp4AECggEBAN1OgCsj\nyucLi5ZSHDYc9yTOKW7nGYHOGIMXdHaPCe+8R/3aW+NwV6QzyHO4WFr6p21JcOse\nldmYlwLRDBaCfteodLGLGrOS9DG8lN5i4F0hiRKwkOma9bRwNNESVLLp9TvXaxVN\nhzofNhnqVBRhP9jEPREVUk3iN4D2+GifEGBVIRqvrPEdN2c2fdIKC8nucmQGg02I\nQxfLRK8IL2COUgoB3f1lf/w6brIySn4sbctw4KSyGPsrrWCCQrARqcZ9gyVCKV6t\n/SMJcvMQ0QG43cQxZK6P21gyd5sRWryo74lQSEWnvt9v6zfMDADMcxErzH6ZCLg1\naBvBwv98vkeClEECggEBANPFjvl8EDx/dSGDBcpFyAt6IV0fijXpzxS4/14Y0J1k\nxBsHfkpeuH65npbHcH9SFqQ/3Nyc6vTA4KVNroH5eyo2Y+PY1NjPOoJTiFf57W/X\ntduukaqUBZ3NsHG176jDgHYyrZPlEBRHquSDxUjkVdx8uQDxL8r6OrF4RgVduk1p\nytMadyXWwJ6AGtSgmHIUH5LMImfrxwh0X8GmzaG0nfjUe8kIzEJIU8xNi7K13UO+\n3B/9uI3fOGYQ/NrCv1RDj49qIj/2NpnSAfeUxaKICZ890ffMC9xJTFrR+QmaqtSc\n7uir0UXx1qH1Tx7HdAHR7Dk4cHW7HhrK33ULcc0eUvECggEAN96Wis2JbtTCU5u9\nFYgweHE3kpDzJosCMy4br8aiqows3JBgvEVjSsfr5hL281juJa/xutnI2Nsl3Icr\n9w7QuN8FPsEwZ39E+L10E8SAgeJyeW5r1x3Qw9HD87gd++EGkSnsFb+x0OGKRfab\nbV2zwaShCgwI8DKY8ozm33qwprE3H0aUcXZ/wyXFk94HZd41sLzYLx2kWoBtgYae\nd1DWs0IPaeZS7jlOMtxxY/MRcNe5TrrLhbVcGs4nyc1bwAl1r1VJnmZsTokXJPfs\n2/NwwRP7J/qXVGfBPDugXZqEhnTnGfakQEI/7qErspPqxL367UbzJZYOB1veP6Od\nYe48QQKCAQBnb1UYEjqz8eU6Cw7m7xJ4WJy3KVKOZrbYfktsoF40oiUOtqg+luky\nLGODbcJKzcN1UiQENTildxfCZaDYpww7X/mGLkA37W+8fCRaJB6OxCN1O1y2njno\nC7EkuSJnoaW7FaGmXPlvjlmv55SSt8QgP2L1TNh1IadNS1uX/2Ghsgx487JCbxQB\n1rxEInSTM7UANGiRrZ23SXAD2/8P/nIyOUaEuKFbtowHe9DB5wY9spk9nuVnliGr\n6Jw4FWryM1WJTOORriaZFvQTAz1M13krqDxH9gfM/pgmu+wRftP1qPkf99vtd+PH\nk1OjyvOkd+4TPLfhKRXZLEHcn0xkTW1hAoIBAD+7+n2Q6dzwFVJLPcPrlQtusEkn\nLYvAZlHqMjIZQGaqhRzunxACOVgbu87CFuf19AxmYC3b45ZfmgCuVTOGXMkZgKGK\njZbyg/bm6XypCwiixC/AIrlU0NG+3uWUSEle+BzYnmYyiAquCLu4TiHFDPWorqfd\nvEz+skrB/2OQe1UWkr66gP0P41hpGFVgz6mFUfJjepYUAUe2X8VfK1zWA97eZzGq\ngQTfC3LeDn3RtEQY6NtBMjfsXRiwtWtJcrSVg8BFp6NJgp8CJAckg03K25UYe8tk\n/YKZaoWowmGQqx7QkJ5Kckz70dS3rWhb8IKcLiir1sLz9UtsQeiue+Q/Ezo=\n-----END RSA PRIVATE KEY-----\n"
+    }
+  ],
+  "enforcers": [
+    {
+      "owner": "built-in",
+      "name": "user-enforcer-built-in",
+      "createdTime": "2024-09-09T09:26:13Z",
+      "updatedTime": "2024-09-09 09:26:13",
+      "displayName": "User Enforcer",
+      "description": "",
+      "model": "built-in/user-model-built-in",
+      "adapter": "built-in/user-adapter-built-in",
+      "modelCfg": null
+    },
+    {
+      "owner": "built-in",
+      "name": "api-enforcer-built-in",
+      "createdTime": "2024-09-09T09:26:12Z",
+      "updatedTime": "2024-09-09 09:26:12",
+      "displayName": "API Enforcer",
+      "description": "",
+      "model": "built-in/api-model-built-in",
+      "adapter": "built-in/api-adapter-built-in",
+      "modelCfg": null
+    }
+  ],
+  "groups": [],
+  "invitations": [],
+  "ldaps": [
+    {
+      "id": "ldap-built-in",
+      "owner": "built-in",
+      "createdTime": "2024-09-09T09:26:12Z",
+      "serverName": "BuildIn LDAP Server",
+      "host": "example.com",
+      "port": 389,
+      "enableSsl": false,
+      "username": "cn=buildin,dc=example,dc=com",
+      "password": "123",
+      "baseDn": "ou=BuildIn,dc=example,dc=com",
+      "filter": "",
+      "filterFields": null,
+      "defaultGroup": "",
+      "autoSync": 0,
+      "lastSync": ""
+    }
+  ],
+  "models": [
+    {
+      "owner": "built-in",
+      "name": "user-model-built-in",
+      "createdTime": "2024-09-09T09:26:13Z",
+      "displayName": "Built-in Model",
+      "description": "",
+      "modelText": "[request_definition]\nr = sub, obj, act\n\n[policy_definition]\np = sub, obj, act\n\n[role_definition]\ng = _, _\n\n[policy_effect]\ne = some(where (p.eft == allow))\n\n[matchers]\nm = g(r.sub, p.sub) \u0026\u0026 r.obj == p.obj \u0026\u0026 r.act == p.act"
+    },
+    {
+      "owner": "built-in",
+      "name": "api-model-built-in",
+      "createdTime": "2024-09-09T09:26:12Z",
+      "displayName": "API Model",
+      "description": "",
+      "modelText": "[request_definition]\nr = subOwner, subName, method, urlPath, objOwner, objName\n\n[policy_definition]\np = subOwner, subName, method, urlPath, objOwner, objName\n\n[role_definition]\ng = _, _\n\n[policy_effect]\ne = some(where (p.eft == allow))\n\n[matchers]\nm = (r.subOwner == p.subOwner || p.subOwner == \"*\") \u0026\u0026 \\\n    (r.subName == p.subName || p.subName == \"*\" || r.subName != \"anonymous\" \u0026\u0026 p.subName == \"!anonymous\") \u0026\u0026 \\\n    (r.method == p.method || p.method == \"*\") \u0026\u0026 \\\n    (r.urlPath == p.urlPath || p.urlPath == \"*\") \u0026\u0026 \\\n    (r.objOwner == p.objOwner || p.objOwner == \"*\") \u0026\u0026 \\\n    (r.objName == p.objName || p.objName == \"*\") || \\\n    (r.subOwner == r.objOwner \u0026\u0026 r.subName == r.objName)"
+    }
+  ],
+  "organizations": [
+    {
+      "owner": "admin",
+      "name": "built-in",
+      "createdTime": "2024-09-09T09:26:04Z",
+      "displayName": "Built-in Organization",
+      "websiteUrl": "https://example.com",
+      "logo": "",
+      "logoDark": "",
+      "favicon": "https://cdn.casbin.org/img/casbin/favicon.ico",
+      "passwordType": "plain",
+      "passwordSalt": "",
+      "passwordOptions": ["AtLeast6"],
+      "countryCodes": ["US", "ES", "FR", "DE", "GB", "CN", "JP", "KR", "VN", "ID", "SG", "IN"],
+      "defaultAvatar": "https://cdn.casbin.org/img/casbin.svg",
+      "defaultApplication": "",
+      "tags": [],
+      "languages": ["en", "zh", "es", "fr", "de", "id", "ja", "ko", "ru", "vi", "pt"],
+      "themeData": null,
+      "masterPassword": "",
+      "defaultPassword": "",
+      "masterVerificationCode": "",
+      "initScore": 2000,
+      "enableSoftDeletion": false,
+      "isProfilePublic": false,
+      "useEmailAsUsername": false,
+      "enableTour": true,
+      "mfaItems": null,
+      "accountItems": [
+        {
+          "name": "Organization",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Admin",
+          "regex": ""
+        },
+        {
+          "name": "ID",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Immutable",
+          "regex": ""
+        },
+        {
+          "name": "Name",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Admin",
+          "regex": ""
+        },
+        {
+          "name": "Display name",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "Avatar",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "User type",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Admin",
+          "regex": ""
+        },
+        {
+          "name": "Password",
+          "visible": true,
+          "viewRule": "Self",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "Email",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "Phone",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "Country code",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Admin",
+          "regex": ""
+        },
+        {
+          "name": "Country/Region",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "Location",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "Affiliation",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "Title",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "Homepage",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "Bio",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "Tag",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Admin",
+          "regex": ""
+        },
+        {
+          "name": "Signup application",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Admin",
+          "regex": ""
+        },
+        {
+          "name": "Roles",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Immutable",
+          "regex": ""
+        },
+        {
+          "name": "Permissions",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Immutable",
+          "regex": ""
+        },
+        {
+          "name": "Groups",
+          "visible": true,
+          "viewRule": "Public",
+          "modifyRule": "Admin",
+          "regex": ""
+        },
+        {
+          "name": "3rd-party logins",
+          "visible": true,
+          "viewRule": "Self",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "Properties",
+          "visible": true,
+          "viewRule": "Admin",
+          "modifyRule": "Admin",
+          "regex": ""
+        },
+        {
+          "name": "Is admin",
+          "visible": true,
+          "viewRule": "Admin",
+          "modifyRule": "Admin",
+          "regex": ""
+        },
+        {
+          "name": "Is forbidden",
+          "visible": true,
+          "viewRule": "Admin",
+          "modifyRule": "Admin",
+          "regex": ""
+        },
+        {
+          "name": "Is deleted",
+          "visible": true,
+          "viewRule": "Admin",
+          "modifyRule": "Admin",
+          "regex": ""
+        },
+        {
+          "name": "Multi-factor authentication",
+          "visible": true,
+          "viewRule": "Self",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "WebAuthn credentials",
+          "visible": true,
+          "viewRule": "Self",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "Managed accounts",
+          "visible": true,
+          "viewRule": "Self",
+          "modifyRule": "Self",
+          "regex": ""
+        },
+        {
+          "name": "MFA accounts",
+          "visible": true,
+          "viewRule": "Self",
+          "modifyRule": "Self",
+          "regex": ""
+        }
+      ]
+    }
+  ],
+  "payments": [],
+  "permissions": [
+    {
+      "owner": "built-in",
+      "name": "permission-built-in",
+      "createdTime": "2024-09-09T09:26:04Z",
+      "displayName": "Built-in Permission",
+      "description": "Built-in Permission",
+      "users": ["built-in/*"],
+      "groups": [],
+      "roles": [],
+      "domains": [],
+      "model": "user-model-built-in",
+      "adapter": "",
+      "resourceType": "Application",
+      "resources": ["app-built-in"],
+      "actions": ["Read", "Write", "Admin"],
+      "effect": "Allow",
+      "isEnabled": true,
+      "submitter": "admin",
+      "approver": "admin",
+      "approveTime": "2024-09-09T09:26:04Z",
+      "state": "Approved"
+    }
+  ],
+  "plans": [],
+  "pricings": [],
+  "products": [],
+  "providers": [],
+  "records": [],
+  "resources": [],
+  "roles": [],
+  "sessions": [],
+  "subscriptions": [],
+  "syncers": [],
+  "tokens": [],
+  "transactions": [],
+  "users": [
+    {
+      "owner": "built-in",
+      "name": "admin",
+      "createdTime": "2024-09-09T09:26:05Z",
+      "updatedTime": "",
+      "deletedTime": "",
+      "id": "bbf2a176-203c-414c-8cdd-ec92b019e07a",
+      "externalId": "",
+      "type": "normal-user",
+      "password": "123",
+      "passwordSalt": "",
+      "passwordType": "plain",
+      "displayName": "Admin",
+      "firstName": "",
+      "lastName": "",
+      "avatar": "https://cdn.casbin.org/img/casbin.svg",
+      "avatarType": "",
+      "permanentAvatar": "",
+      "email": "admin@example.com",
+      "emailVerified": false,
+      "phone": "12345678910",
+      "countryCode": "US",
+      "region": "",
+      "location": "",
+      "address": [],
+      "affiliation": "Example Inc.",
+      "title": "",
+      "idCardType": "",
+      "idCard": "",
+      "homepage": "",
+      "bio": "",
+      "tag": "staff",
+      "language": "",
+      "gender": "",
+      "birthday": "",
+      "education": "",
+      "score": 2000,
+      "karma": 0,
+      "ranking": 1,
+      "balance": 0,
+      "currency": "",
+      "isDefaultAvatar": false,
+      "isOnline": false,
+      "isAdmin": true,
+      "isForbidden": false,
+      "isDeleted": false,
+      "signupApplication": "app-built-in",
+      "hash": "",
+      "preHash": "",
+      "accessKey": "",
+      "accessSecret": "",
+      "accessToken": "",
+      "createdIp": "127.0.0.1",
+      "lastSigninTime": "",
+      "lastSigninIp": "",
+      "github": "",
+      "google": "",
+      "qq": "",
+      "wechat": "",
+      "facebook": "",
+      "dingtalk": "",
+      "weibo": "",
+      "gitee": "",
+      "linkedin": "",
+      "wecom": "",
+      "lark": "",
+      "gitlab": "",
+      "adfs": "",
+      "baidu": "",
+      "alipay": "",
+      "casdoor": "",
+      "infoflow": "",
+      "apple": "",
+      "azuread": "",
+      "azureadb2c": "",
+      "slack": "",
+      "steam": "",
+      "bilibili": "",
+      "okta": "",
+      "douyin": "",
+      "line": "",
+      "amazon": "",
+      "auth0": "",
+      "battlenet": "",
+      "bitbucket": "",
+      "box": "",
+      "cloudfoundry": "",
+      "dailymotion": "",
+      "deezer": "",
+      "digitalocean": "",
+      "discord": "",
+      "dropbox": "",
+      "eveonline": "",
+      "fitbit": "",
+      "gitea": "",
+      "heroku": "",
+      "influxcloud": "",
+      "instagram": "",
+      "intercom": "",
+      "kakao": "",
+      "lastfm": "",
+      "mailru": "",
+      "meetup": "",
+      "microsoftonline": "",
+      "naver": "",
+      "nextcloud": "",
+      "onedrive": "",
+      "oura": "",
+      "patreon": "",
+      "paypal": "",
+      "salesforce": "",
+      "shopify": "",
+      "soundcloud": "",
+      "spotify": "",
+      "strava": "",
+      "stripe": "",
+      "tiktok": "",
+      "tumblr": "",
+      "twitch": "",
+      "twitter": "",
+      "typetalk": "",
+      "uber": "",
+      "vk": "",
+      "wepay": "",
+      "xero": "",
+      "yahoo": "",
+      "yammer": "",
+      "yandex": "",
+      "zoom": "",
+      "metamask": "",
+      "web3onboard": "",
+      "custom": "",
+      "webauthnCredentials": null,
+      "preferredMfaType": "",
+      "recoveryCodes": null,
+      "totpSecret": "",
+      "mfaPhoneEnabled": false,
+      "mfaEmailEnabled": false,
+      "invitation": "",
+      "invitationCode": "",
+      "faceIds": null,
+      "ldap": "",
+      "properties": {},
+      "roles": null,
+      "permissions": null,
+      "groups": null,
+      "lastSigninWrongTime": "",
+      "signinWrongTimes": 0,
+      "managedAccounts": null,
+      "mfaAccounts": null,
+      "needUpdatePassword": false
+    }
+  ],
+  "webhooks": []
+}

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

@@ -0,0 +1,34 @@
+# Logto secret
+AUTH_LOGTO_ID=
+AUTH_LOGTO_SECRET=
+AUTH_LOGTO_ISSUER=
+
+# MinIO S3 configuration
+MINIO_ROOT_USER=YOUR_MINIO_USER
+MINIO_ROOT_PASSWORD=YOUR_MINIO_PASSWORD
+
+# Configure the bucket information of MinIO
+MINIO_LOBE_BUCKET=lobe
+S3_ACCESS_KEY_ID=
+S3_SECRET_ACCESS_KEY=
+
+# Proxy, if you need it
+# HTTP_PROXY=http://localhost:7890
+# HTTPS_PROXY=http://localhost:7890
+
+
+# Other environment variables, as needed. You can refer to the environment variables configuration for the client version, making sure not to have ACCESS_CODE.
+# OPENAI_API_KEY=sk-xxxx
+# OPENAI_PROXY_URL=https://api.openai.com/v1
+# OPENAI_MODEL_LIST=...
+
+
+# ----- Other config -----
+# if no special requirements, no need to change
+LOBE_PORT=3210
+LOGTO_PORT=3001
+MINIO_PORT=9000
+
+# Postgres related, which are the necessary environment variables for DB
+LOBE_DB_NAME=lobechat
+POSTGRES_PASSWORD=uWNZugjBqixf8dxC

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

@@ -0,0 +1,34 @@
+# Logto 鉴权相关
+AUTH_LOGTO_ID=
+AUTH_LOGTO_SECRET=
+AUTH_LOGTO_ISSUER=
+
+# MinIO S3 配置
+MINIO_ROOT_USER=YOUR_MINIO_USER
+MINIO_ROOT_PASSWORD=YOUR_MINIO_PASSWORD
+
+# 在下方配置 minio 中添加的桶
+MINIO_LOBE_BUCKET=lobe
+S3_ACCESS_KEY_ID=
+S3_SECRET_ACCESS_KEY=
+
+
+# Proxy，如果你需要的话（比如你使用 GitHub 作为鉴权服务提供商）
+# HTTP_PROXY=http://localhost:7890
+# HTTPS_PROXY=http://localhost:7890
+
+# 其他环境变量，视需求而定，可以参照客户端版本的环境变量配置，注意不要有 ACCESS_CODE
+# OPENAI_API_KEY=sk-xxxx
+# OPENAI_PROXY_URL=https://api.openai.com/v1
+# OPENAI_MODEL_LIST=...
+
+
+# ----- 相关配置 start -----
+# 如没有特殊需要不用更改
+LOBE_PORT=3210
+LOGTO_PORT=3001
+MINIO_PORT=9000
+
+# Postgres 相关，也即 DB 必须的环境变量
+LOBE_DB_NAME=lobechat
+POSTGRES_PASSWORD=uWNZugjBqixf8dxC

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

@@ -0,0 +1,103 @@
+name: lobe-chat-database
+services:
+  network-service:
+    image: alpine
+    container_name: lobe-network
+    ports:
+      - '${MINIO_PORT}:${MINIO_PORT}' # MinIO API
+      - '9001:9001' # MinIO Console
+      - '${LOGTO_PORT}:${LOGTO_PORT}' # Logto
+      - '3002:3002' # Logto Admin
+      - '${LOBE_PORT}:3210' # LobeChat
+    command: tail -f /dev/null
+    networks:
+      - lobe-network
+
+  postgresql:
+    image: pgvector/pgvector:pg16
+    container_name: lobe-postgres
+    ports:
+      - '5432:5432'
+    volumes:
+      - './data:/var/lib/postgresql/data'
+    environment:
+      - 'POSTGRES_DB=${LOBE_DB_NAME}'
+      - 'POSTGRES_PASSWORD=${POSTGRES_PASSWORD}'
+    healthcheck:
+      test: ['CMD-SHELL', 'pg_isready -U postgres']
+      interval: 5s
+      timeout: 5s
+      retries: 5
+    restart: always
+    networks:
+      - lobe-network
+
+  minio:
+    image: minio/minio
+    container_name: lobe-minio
+    network_mode: 'service:network-service'
+    volumes:
+      - './s3_data:/etc/minio/data'
+    environment:
+      - 'MINIO_ROOT_USER=${MINIO_ROOT_USER}'
+      - 'MINIO_ROOT_PASSWORD=${MINIO_ROOT_PASSWORD}'
+      - 'MINIO_API_CORS_ALLOW_ORIGIN=http://localhost:${LOBE_PORT}'
+    restart: always
+    command: >
+      server /etc/minio/data --address ":${MINIO_PORT}" --console-address ":9001"
+
+
+  logto:
+    image: svhd/logto
+    container_name: lobe-logto
+    network_mode: 'service:network-service'
+    depends_on:
+      postgresql:
+        condition: service_healthy
+    environment:
+      - 'TRUST_PROXY_HEADER=1'
+      - 'PORT=${LOGTO_PORT}'
+      - 'DB_URL=postgresql://postgres:${POSTGRES_PASSWORD}@postgresql:5432/logto'
+      - 'ENDPOINT=http://localhost:${LOGTO_PORT}'
+      - 'ADMIN_ENDPOINT=http://localhost:3002'
+    entrypoint: ['sh', '-c', 'npm run cli db seed -- --swe && npm start']
+
+  lobe:
+    image: lobehub/lobe-chat-database
+    container_name: lobe-chat
+    network_mode: 'service:network-service'
+    depends_on:
+      postgresql:
+        condition: service_healthy
+      network-service:
+        condition: service_started
+      minio:
+        condition: service_started
+      logto:
+        condition: service_started
+
+    environment:
+      - 'APP_URL=http://localhost:3210'
+      - 'NEXT_AUTH_SSO_PROVIDERS=logto'
+      - 'KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ='
+      - 'NEXT_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}'
+      - 'S3_BUCKET=${MINIO_LOBE_BUCKET}'
+      - 'S3_PUBLIC_DOMAIN=http://localhost:${MINIO_PORT}'
+      - 'S3_ENABLE_PATH_STYLE=1'
+    env_file:
+      - .env
+    restart: always
+
+volumes:
+  data:
+    driver: local
+  s3_data:
+    driver: local
+
+networks:
+  lobe-network:
+    driver: bridge

docker-compose/local/setup.sh

@@ -0,0 +1,243 @@
+#!/bin/bash
+
+# ==================
+# == Env settings ==
+# ==================
+
+# ======================
+# == Process the args ==
+# ======================
+
+# 1. Default values of arguments
+# Arg: -f
+# Determine force download asserts, default is not
+FORCE_DOWNLOAD=false
+
+# Arg: -l or --lang
+# Determine the language to show, default is en
+LANGUAGE="en_US"
+
+# Arg: --url
+# Determine the source URL to download files
+SOURCE_URL="https://raw.githubusercontent.com/lobehub/lobe-chat/main"
+
+# 2. Parse script arguments
+while getopts "fl:-:" opt; do
+  case $opt in
+    f)
+      FORCE_DOWNLOAD=true
+      ;;
+    l)
+      LANGUAGE=$OPTARG
+      ;;
+    -)
+      case "${OPTARG}" in
+        lang)
+          LANGUAGE="${!OPTIND}"
+          OPTIND=$(($OPTIND + 1))
+          ;;
+        url)
+          SOURCE_URL="${!OPTIND}"
+          OPTIND=$(($OPTIND + 1))
+          ;;
+        *)
+          echo "Usage: $0 [-f] [-l language|--lang language] [--url source]" >&2
+          exit 1
+          ;;
+      esac
+      ;;
+    *)
+      echo "Usage: $0 [-f] [-l language|--lang language] [--url source]" >&2
+      exit 1
+      ;;
+  esac
+done
+
+# ===============
+# == Variables ==
+# ===============
+# File list
+SUB_DIR="docker-compose/local"
+FILES=(
+  "$SUB_DIR/docker-compose.yml"
+  "$SUB_DIR/.env.example"
+  "$SUB_DIR/init_data.json"
+  "$SUB_DIR/s3_data.tar.gz"
+)
+
+# Supported languages and messages
+# Arg: -l --lang
+# If the language is not supported, default to English
+# Function to show messages
+show_message() {
+  local key="$1"
+  case $key in
+    downloading)
+      case $LANGUAGE in
+        zh_CN)
+          echo "正在下载文件..."
+          ;;
+        *)
+          echo "Downloading files..."
+          ;;
+      esac
+      ;;
+    downloaded)
+      case $LANGUAGE in
+        zh_CN)
+          echo " 已经存在，跳过下载。"
+          ;;
+        *)
+          echo " already exists, skipping download."
+          ;;
+      esac
+      ;;
+    extracted_success)
+      case $LANGUAGE in
+        zh_CN)
+          echo " 解压成功到目录："
+          ;;
+        *)
+          echo " extracted successfully to directory: "
+          ;;
+      esac
+      ;;
+    extracted_failed)
+      case $LANGUAGE in
+        zh_CN)
+          echo " 解压失败。"
+          ;;
+        *)
+          echo " extraction failed."
+          ;;
+      esac
+      ;;
+    file_not_exists)
+      case $LANGUAGE in
+        zh_CN)
+          echo " 不存在。"
+          ;;
+        *)
+          echo " does not exist."
+          ;;
+      esac
+      ;;
+    tips_run_command)
+      case $LANGUAGE in
+        zh_CN)
+          echo "您已经完成了所有配置文件的下载。请运行以下命令启动LobeChat："
+          ;;
+        *)
+          echo "You have completed downloading all configuration files. Please run this command to start LobeChat:"
+          ;;
+      esac
+      ;;
+    tips_show_documentation)
+      case $LANGUAGE in
+        zh_CN)
+          echo "完整的环境变量在'.env'中可以在文档中找到："
+          ;;
+        *)
+          echo "Full environment variables in the '.env' can be found at the documentation on "
+          ;;
+      esac
+      ;;
+    tips_show_documentation_url)
+      case $LANGUAGE in
+        zh_CN)
+          echo "https://lobehub.com/zh/docs/self-hosting/environment-variables"
+          ;;
+        *)
+          echo "https://lobehub.com/docs/self-hosting/environment-variables"
+          ;;
+      esac
+      ;;
+    tips_warning)
+      case $LANGUAGE in
+        zh_CN)
+          echo "警告：不要在生产环境中使用此演示应用程序！！！"
+          ;;
+        *)
+          echo "Warning: do not use this demo application in production!!!"
+          ;;
+      esac
+      ;;
+  esac
+}
+
+# Function to download files
+download_file() {
+  local file_url="$1"
+  local local_file="$2"
+
+  if [ "$FORCE_DOWNLOAD" = false ] && [ -e "$local_file" ]; then
+    echo "$local_file" $(show_message "downloaded")
+    return 0
+  fi
+
+  wget -q --show-progress "$file_url" -O "$local_file"
+}
+
+extract_file() {
+  local file_name=$1
+  local target_dir=$2
+
+  if [ -e "$file_name" ]; then
+    tar -zxvf "$file_name" -C "$target_dir" > /dev/null 2>&1
+    if [ $? -eq 0 ]; then
+      echo "$file_name" $(show_message "extracted_success") "$target_dir"
+    else
+      echo "$file_name" $(show_message "extracted_failed")
+      exit 1
+    fi
+  else
+    echo "$file_name" $(show_message "file_not_exists")
+    exit 1
+  fi
+}
+
+# Define colors
+declare -A colors
+colors=(
+  [black]="\e[30m"
+  [red]="\e[31m"
+  [green]="\e[32m"
+  [yellow]="\e[33m"
+  [blue]="\e[34m"
+  [magenta]="\e[35m"
+  [cyan]="\e[36m"
+  [white]="\e[37m"
+  [reset]="\e[0m"
+)
+
+print_centered() {
+  local text="$1"                                   # Get input texts
+  local color="${2:-reset}"                         # Get color, default to reset
+  local term_width=$(tput cols)                     # Get terminal width
+  local text_length=${#text}                        # Get text length
+  local padding=$(((term_width - text_length) / 2)) # Get padding
+  # Check if the color is valid
+  if [[ -z "${colors[$color]}" ]]; then
+    echo "Invalid color specified. Available colors: ${!colors[@]}"
+    return 1
+  fi
+  # Print the text with padding
+  printf "%*s${colors[$color]}%s${colors[reset]}\n" $padding "" "$text"
+}
+
+# Download files asynchronously
+download_file "$SOURCE_URL/${FILES[0]}" "docker-compose.yml"
+download_file "$SOURCE_URL/${FILES[1]}" ".env"
+download_file "$SOURCE_URL/${FILES[2]}" "init_data.json"
+download_file "$SOURCE_URL/${FILES[3]}" "s3_data.tar.gz"
+
+# Extract .tar.gz file without output
+extract_file "s3_data.tar.gz" "."
+rm s3_data.tar.gz
+
+# Display final message
+printf "\n%s\n\n" "$(show_message "tips_run_command")"
+print_centered "docker compose up -d" "green"
+printf "\n%s" "$(show_message "tips_show_documentation")"
+printf "%s\n" $(show_message "tips_show_documentation_url")
+printf "\n\e[33m%s\e[0m\n" "$(show_message "tips_warning")"

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

@@ -0,0 +1,33 @@
+# Required: LobeChat domain for tRPC calls
+# Ensure this domain is whitelisted in your NextAuth providers and S3 service CORS settings
+APP_URL=http://localhost:3210
+
+# Postgres related environment variables
+# Required: Secret key for encrypting sensitive information. Generate with: openssl rand -base64 32
+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
+NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg
+NEXT_AUTH_SSO_PROVIDERS=zitadel
+# ZiTADEL provider configuration
+# Please refer to：https://lobehub.com/zh/docs/self-hosting/advanced/auth/next-auth/zitadel
+AUTH_ZITADEL_ID=285945938244075523
+AUTH_ZITADEL_SECRET=hkbtzHLaCEIeHeFThym14UcydpmQiEB5JtAX08HSqSoJxhAlVVkyovTuNUZ5TNrT
+AUTH_ZITADEL_ISSUER=http://localhost:8080
+
+# MinIO S3 configuration
+S3_ACCESS_KEY_ID=        
+S3_SECRET_ACCESS_KEY=
+S3_ENDPOINT=http://localhost:9000
+S3_BUCKET=lobe 
+S3_PUBLIC_DOMAIN=http://localhost:9000
+S3_ENABLE_PATH_STYLE=1
+LLM_VISION_IMAGE_USE_BASE64=1
+
+# Other environment variables, as needed. You can refer to the environment variables configuration for the client version, making sure not to have ACCESS_CODE.
+# OPENAI_API_KEY=sk-xxxx
+# OPENAI_PROXY_URL=https://api.openai.com/v1
+# OPENAI_MODEL_LIST=...

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

@@ -0,0 +1,32 @@
+# LobeChat 域名
+APP_URL=http://localhost:3210
+
+# Postgres 相关，也即 DB 必须的环境变量
+# 用于加密敏感信息的密钥，可以使用 openssl rand -base64 32 生成
+KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
+# Postgres 数据库连接字符串
+DATABASE_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/lobechat
+
+# NEXT_AUTH 相关
+NEXTAUTH_URL=http://localhost:3210/api/auth
+NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg
+NEXT_AUTH_SSO_PROVIDERS=zitadel
+# ZiTADEL 鉴权服务提供商部分
+# 请参考：https://lobehub.com/zh/docs/self-hosting/advanced/auth/next-auth/zitadel
+AUTH_ZITADEL_ID=285945938244075523
+AUTH_ZITADEL_SECRET=hkbtzHLaCEIeHeFThym14UcydpmQiEB5JtAX08HSqSoJxhAlVVkyovTuNUZ5TNrT
+AUTH_ZITADEL_ISSUER=http://localhost:8080
+
+# MinIO S3 配置
+S3_ACCESS_KEY_ID=        
+S3_SECRET_ACCESS_KEY=
+S3_ENDPOINT=http://localhost:9000
+S3_BUCKET=lobe 
+S3_PUBLIC_DOMAIN=http://localhost:9000
+S3_ENABLE_PATH_STYLE=1
+LLM_VISION_IMAGE_USE_BASE64=1
+
+# 其他环境变量，视需求而定，可以参照客户端版本的环境变量配置，注意不要有 ACCESS_CODE
+# OPENAI_API_KEY=sk-xxxx
+# OPENAI_PROXY_URL=https://api.openai.com/v1
+# OPENAI_MODEL_LIST=...

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

@@ -0,0 +1,86 @@
+name: lobe-chat-database
+services:
+  network-service:
+    image: alpine
+    container_name: lobe-network
+    ports:
+      - '9000:9000' # MinIO API
+      - '9001:9001' # MinIO Console
+      - '8080:8080' # Zitadel Console
+      - '3210:3210' # LobeChat
+    command: tail -f /dev/null
+    networks:
+      - lobe-network
+
+  postgresql:
+    image: pgvector/pgvector:pg16
+    container_name: lobe-postgres
+    ports:
+      - '5432:5432'
+    volumes:
+      - './data:/var/lib/postgresql/data'
+    environment:
+      - 'POSTGRES_DB=lobechat'
+      - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC'
+    healthcheck:
+      test: ['CMD-SHELL', 'pg_isready -U postgres']
+      interval: 5s
+      timeout: 5s
+      retries: 5
+    restart: always
+    networks:
+      - lobe-network
+
+  minio:
+    image: minio/minio
+    container_name: lobe-minio
+    network_mode: 'service:network-service'
+    volumes:
+      - './s3_data:/etc/minio/data'
+    environment:
+      - 'MINIO_ROOT_USER=YOUR_MINIO_USER'
+      - 'MINIO_ROOT_PASSWORD=YOUR_MINIO_PASSWORD'
+      - 'MINIO_API_CORS_ALLOW_ORIGIN=http://localhost:3210'
+    restart: always
+    command: >
+      server /etc/minio/data --address ":9000" --console-address ":9001"
+
+
+  zitadel:
+    restart: 'always'
+    image: 'ghcr.io/zitadel/zitadel:latest'
+    container_name: lobe-zitadel
+    network_mode: 'service:network-service'
+    command: start-from-init --config /zitadel-config.yaml --steps /zitadel-init-steps.yaml --masterkey "cft3Tekr/rQBOqwoQSCPoncA9BHbn7QJ" --tlsMode disabled #MasterkeyNeedsToHave32Characters
+    volumes:
+      - ./zitadel-config.yaml:/zitadel-config.yaml:ro
+      - ./zitadel-init-steps.yaml:/zitadel-init-steps.yaml:ro
+    depends_on:
+      postgresql:
+        condition: service_healthy
+
+  lobe:
+    image: lobehub/lobe-chat-database
+    container_name: lobe-chat
+    network_mode: 'service:network-service'
+    depends_on:
+      postgresql:
+        condition: service_healthy
+      network-service:
+        condition: service_started
+      minio:
+        condition: service_started
+      zitadel:
+        condition: service_started
+    env_file:
+      - .env
+    restart: always
+
+volumes:
+  data:
+    driver: local
+  s3_data:
+    driver: local
+networks:
+  lobe-network:
+    driver: bridge

docker-compose/local/zitadel/zitadel-config.yaml

@@ -0,0 +1,26 @@
+Log:
+  Level: 'info'
+
+Port: 8080
+ExternalPort: 8080 
+ExternalDomain: localhost
+ExternalSecure: false
+TLS:
+  Enabled: false 
+
+# If not using the docker compose example, adjust these values for connecting ZITADEL to your PostgreSQL
+Database:
+  postgres:
+    Host: postgresql
+    Port: 5432
+    Database: zitadel
+    User:
+      Username: 'zitadel'
+      Password: 'zitadel'
+      SSL:
+        Mode: 'disable'
+    Admin:
+      Username: 'postgres'
+      Password: 'uWNZugjBqixf8dxC' #postgres password
+      SSL:
+        Mode: 'disable'

docker-compose/local/zitadel/zitadel-init-steps.yaml

@@ -0,0 +1,11 @@
+# All possible options and their defaults: https://github.com/zitadel/zitadel/blob/main/cmd/setup/steps.yaml
+FirstInstance:
+  Org:
+    Human:
+      # use the loginname root@zitadel.localhost
+      Username: 'root'
+      # The password must be 8 characters or more and must contain uppercase letters, lowercase letters, symbols, and numbers. The first login will require a password change. 
+      Password: 'Password1!'
+      Email:
+        # Optional, if set, can be used to log in with email.
+        Address: 'example@zitadel.com' # ZITADEL_FIRSTINSTANCE_ORG_HUMAN_EMAIL_ADDRESS  

docker-compose/minio-bucket.config.json

@@ -0,0 +1,34 @@
+{
+  "Statement": [
+    {
+      "Effect": "Allow",
+      "Principal": {
+        "AWS": ["*"]
+      },
+      "Action": ["s3:GetBucketLocation"],
+      "Resource": ["arn:aws:s3:::lobe"]
+    },
+    {
+      "Effect": "Allow",
+      "Principal": {
+        "AWS": ["*"]
+      },
+      "Action": ["s3:ListBucket"],
+      "Resource": ["arn:aws:s3:::lobe"],
+      "Condition": {
+        "StringEquals": {
+          "s3:prefix": ["files/*"]
+        }
+      }
+    },
+    {
+      "Effect": "Allow",
+      "Principal": {
+        "AWS": ["*"]
+      },
+      "Action": ["s3:PutObject", "s3:DeleteObject", "s3:GetObject"],
+      "Resource": ["arn:aws:s3:::lobe/files/**"]
+    }
+  ],
+  "Version": "2012-10-17"
+}

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

@@ -0,0 +1,56 @@
+# Required: LobeChat domain for tRPC calls
+# Ensure this domain is whitelisted in your NextAuth providers and S3 service CORS settings
+APP_URL=https://lobe.example.com/
+
+# Postgres related environment variables
+# Required: Secret key for encrypting sensitive information. Generate with: openssl rand -base64 32
+KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
+# Required: Postgres database connection string
+# Format: postgresql://username:password@host:port/dbname
+# 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
+NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg
+# Required: Specify the authentication provider (e.g., Logto)
+NEXT_AUTH_SSO_PROVIDERS=logto
+# Required: NextAuth URL for callbacks
+NEXTAUTH_URL=https://lobe.example.com/api/auth
+
+# NextAuth 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
+AUTH_LOGTO_ISSUER=https://lobe-auth-api.example.com/oidc
+
+# Proxy settings (if needed, e.g., when using GitHub as an auth provider)
+# HTTP_PROXY=http://localhost:7890
+# HTTPS_PROXY=http://localhost:7890
+
+# S3 related environment variables (example using MinIO)
+# Required: S3 Access Key ID (for MinIO, invalid until manually created in MinIO UI)
+S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID
+# Required: S3 Secret Access Key (for MinIO, invalid until manually created in MinIO UI)
+S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY
+# Required: S3 Endpoint for server/client connections to S3 API
+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
+S3_ENABLE_PATH_STYLE=1
+
+# Other basic environment variables (as needed)
+# See: https://lobehub.com/docs/self-hosting/environment-variables/basic
+# Note: For server versions, the API must support embedding models (OpenAI text-embedding-3-small) for file processing
+# You don't need to specify this model in OPENAI_MODEL_LIST
+# OPENAI_API_KEY=sk-xxxx
+# OPENAI_PROXY_URL=https://api.openai.com/v1
+# OPENAI_MODEL_LIST=...

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

@@ -0,0 +1,55 @@
+# 必填，LobeChat 域名，用于 tRPC 调用
+# 请保证此域名在你的 NextAuth 鉴权服务提供商、S3 服务商的 CORS 白名单中
+APP_URL=https://lobe.example.com/
+
+# Postgres 相关，也即 DB 必需的环境变量
+# 必填，用于加密敏感信息的密钥，可以使用 openssl rand -base64 32 生成
+KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
+# 必填，Postgres 数据库连接字符串，用于连接到数据库
+# 格式：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 生成
+NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg
+# 必填，指定鉴权服务提供商，这里以 Logto 为例
+NEXT_AUTH_SSO_PROVIDERS=logto
+# 必填，NextAuth 的 URL，用于 NextAuth 的回调
+NEXTAUTH_URL=https://lobe.example.com/api/auth
+
+# NextAuth 鉴权服务提供商部分，以 Logto 为例
+# 其他鉴权服务提供商所需的环境变量，请参考：https://lobehub.com/zh/docs/self-hosting/environment-variables/auth
+AUTH_LOGTO_ID=YOUR_LOGTO_ID
+AUTH_LOGTO_SECRET=YOUR_LOGTO_SECRET
+AUTH_LOGTO_ISSUER=https://lobe-auth-api.example.com/oidc
+
+# 代理相关，如果你需要的话（比如你使用 GitHub 作为鉴权服务提供商）
+# HTTP_PROXY=http://localhost:7890
+# HTTPS_PROXY=http://localhost:7890
+
+# S3 相关，也即非结构化数据（文件、图片等）存储必需的环境变量
+# 这里以 MinIO 为例
+# 必填，S3 的 Access Key ID，对于 MinIO 来说，直到在 MinIO UI 中手动创建之前都是无效的
+S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID
+# 必填，S3 的 Secret Access Key，对于 MinIO 来说，直到在 MinIO UI 中手动创建之前都是无效的
+S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY
+# 必填，S3 的 Endpoint，用于服务端/客户端连接到 S3 API
+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
+S3_ENABLE_PATH_STYLE=1
+
+# 其他基础环境变量，视需求而定。注意不要有 ACCESS_CODE
+# 请参考：https://lobehub.com/zh/docs/self-hosting/environment-variables/basic
+# 请注意，对于服务端版本，其 API 必须支持嵌入（即 OpenAI text-embedding-3-small）模型，否则无法对上传文件进行处理，但你无需在 OPENAI_MODEL_LIST 中指定此模型
+# OPENAI_API_KEY=sk-xxxx
+# OPENAI_PROXY_URL=https://api.openai.com/v1
+# OPENAI_MODEL_LIST=...

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

@@ -0,0 +1,71 @@
+name: lobe-chat-database
+services:
+  postgresql:
+    image: pgvector/pgvector:pg16
+    container_name: lobe-postgres
+    ports:
+      - '5432:5432'
+    volumes:
+      - './data:/var/lib/postgresql/data'
+    environment:
+      - 'POSTGRES_DB=lobe'
+      - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC'
+    healthcheck:
+      test: ['CMD-SHELL', 'pg_isready -U postgres']
+      interval: 5s
+      timeout: 5s
+      retries: 5
+    restart: always
+
+  minio:
+    image: minio/minio
+    container_name: lobe-minio
+    ports:
+      - '9000:9000'
+      - '9001:9001'
+    volumes:
+      - './s3_data:/etc/minio/data'
+    environment:
+      - 'MINIO_ROOT_USER=YOUR_MINIO_USER'
+      - 'MINIO_ROOT_PASSWORD=YOUR_MINIO_PASSWORD'
+      - 'MINIO_DOMAIN=lobe-s3-api.example.com'
+      - 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.example.com' # Your LobeChat's domain name.
+    restart: always
+    command: >
+      server /etc/minio/data --address ":9000" --console-address ":9001"
+
+
+  logto:
+    image: svhd/logto
+    container_name: lobe-logto
+    ports:
+      - '3001:3001'
+      - '3002:3002'
+    depends_on:
+      postgresql:
+        condition: service_healthy
+    environment:
+      - 'TRUST_PROXY_HEADER=1'
+      - 'DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/logto'
+      - 'ENDPOINT=https://lobe-auth-api.example.com'
+      - 'ADMIN_ENDPOINT=https://lobe-auth-ui.example.com'
+    entrypoint: ['sh', '-c', 'npm run cli db seed -- --swe && npm start']
+
+  lobe:
+    image: lobehub/lobe-chat-database
+    container_name: lobe-chat
+    ports:
+      - '3210:3210'
+    depends_on:
+      - postgresql
+      - minio
+      - logto
+    env_file:
+      - .env
+    restart: always
+
+volumes:
+  data:
+    driver: local
+  s3_data:
+    driver: local

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

@@ -0,0 +1,53 @@
+# Required: LobeChat domain for tRPC calls
+# Ensure this domain is whitelisted in your NextAuth providers and S3 service CORS settings
+APP_URL=https://lobe.example.com/
+
+# Postgres related environment variables
+# Required: Secret key for encrypting sensitive information. Generate with: openssl rand -base64 32
+KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
+# Required: Postgres database connection string
+# Format: postgresql://username:password@host:port/dbname
+# 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
+NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg
+# Required: Specify the authentication provider
+NEXT_AUTH_SSO_PROVIDERS=zitadel
+
+# ZiTADEL provider configuration
+# Please refer to：https://lobehub.com/zh/docs/self-hosting/advanced/auth/next-auth/zitadel
+AUTH_ZITADEL_ID=285934220675723622
+AUTH_ZITADEL_SECRET=pe7Nh3lopXkZkfqh5YEDYI2xsbIz08eZKqInOUZxssd3refRia518Apbv3DZ
+AUTH_ZITADEL_ISSUER=https://zitadel.example.com
+
+# Proxy settings (if needed, e.g., when using GitHub as an auth provider)
+# HTTP_PROXY=http://localhost:7890
+# HTTPS_PROXY=http://localhost:7890
+
+# S3 related environment variables (example using MinIO)
+# Required: S3 Access Key ID (for MinIO, invalid until manually created in MinIO UI)
+S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID
+# Required: S3 Secret Access Key (for MinIO, invalid until manually created in MinIO UI)
+S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY
+# Required: S3 Endpoint for server/client connections to S3 API
+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
+S3_ENABLE_PATH_STYLE=1
+
+# Other basic environment variables (as needed)
+# See: https://lobehub.com/docs/self-hosting/environment-variables/basic
+# Note: For server versions, the API must support embedding models (OpenAI text-embedding-3-small) for file processing
+# You don't need to specify this model in OPENAI_MODEL_LIST
+# OPENAI_API_KEY=sk-xxxx
+# OPENAI_PROXY_URL=https://api.openai.com/v1
+# OPENAI_MODEL_LIST=...

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

@@ -0,0 +1,48 @@
+# 必填，LobeChat 域名，用于 tRPC 调用
+# 请保证此域名在你的 NextAuth 鉴权服务提供商、S3 服务商的 CORS 白名单中
+APP_URL=https://lobe.example.com/
+
+# Postgres 相关，也即 DB 必需的环境变量
+# 必填，用于加密敏感信息的密钥，可以使用 openssl rand -base64 32 生成
+KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
+# 必填，Postgres 数据库连接字符串，用于连接到数据库
+# 格式：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 生成
+NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg
+# 必填，指定鉴权服务提供商
+NEXT_AUTH_SSO_PROVIDERS=zitadel
+
+# ZiTADEL 鉴权服务提供商部分
+# 请参考：https://lobehub.com/zh/docs/self-hosting/advanced/auth/next-auth/zitadel
+AUTH_ZITADEL_ID=285934220675723622
+AUTH_ZITADEL_SECRET=pe7Nh3lopXkZkfqh5YEDYI2xsbIz08eZKqInOUZxssd3refRia518Apbv3DZ
+AUTH_ZITADEL_ISSUER=https://zitadel.example.com
+
+# S3 相关，也即非结构化数据（文件、图片等）存储必需的环境变量
+# 这里以 MinIO 为例
+# 必填，S3 的 Access Key ID，对于 MinIO 来说，直到在 MinIO UI 中手动创建之前都是无效的
+S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID
+# 必填，S3 的 Secret Access Key，对于 MinIO 来说，直到在 MinIO UI 中手动创建之前都是无效的
+S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY
+# 必填，S3 的 Endpoint，用于服务端/客户端连接到 S3 API
+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
+S3_ENABLE_PATH_STYLE=1
+
+# 其他基础环境变量，视需求而定。注意不要有 ACCESS_CODE
+# 请参考：https://lobehub.com/zh/docs/self-hosting/environment-variables/basic
+# 请注意，对于服务端版本，其 API 必须支持嵌入（即 OpenAI text-embedding-3-small）模型，否则无法对上传文件进行处理，但你无需在 OPENAI_MODEL_LIST 中指定此模型
+# OPENAI_API_KEY=sk-xxxx
+# OPENAI_PROXY_URL=https://api.openai.com/v1
+# OPENAI_MODEL_LIST=...

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

@@ -0,0 +1,69 @@
+name: lobe-chat-database
+services:
+  postgresql:
+    image: pgvector/pgvector:pg16
+    container_name: lobe-postgres
+    ports:
+      - '5432:5432'
+    volumes:
+      - './data:/var/lib/postgresql/data'
+    environment:
+      - 'POSTGRES_DB=lobe'
+      - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC'
+    healthcheck:
+      test: ['CMD-SHELL', 'pg_isready -U postgres']
+      interval: 5s
+      timeout: 5s
+      retries: 5
+    restart: always
+
+  minio:
+    image: minio/minio
+    container_name: lobe-minio
+    ports:
+      - '9000:9000'
+      - '9001:9001'
+    volumes:
+      - './s3_data:/etc/minio/data'
+    environment:
+      - 'MINIO_ROOT_USER=YOUR_MINIO_USER'
+      - 'MINIO_ROOT_PASSWORD=YOUR_MINIO_PASSWORD'
+      - 'MINIO_DOMAIN=lobe-s3-api.example.com'
+      - 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.example.com' # Your LobeChat's domain name.
+    restart: always
+    command: >
+      server /etc/minio/data --address ":9000" --console-address ":9001"
+
+
+  zitadel:
+    restart: always
+    image: ghcr.io/zitadel/zitadel:latest
+    container_name: lobe-zitadel
+    command: start-from-init --config /zitadel-config.yaml --steps /zitadel-init-steps.yaml --masterkey "cft3Tekr/rQBOqwoQSCPoncA9BHbn7QJ" --tlsMode external #MasterkeyNeedsToHave32Characters
+    ports:
+      - 8080:8080
+    volumes:
+      - ./zitadel-config.yaml:/zitadel-config.yaml:ro
+      - ./zitadel-init-steps.yaml:/zitadel-init-steps.yaml:ro
+    depends_on:
+      postgresql:
+        condition: service_healthy
+
+  lobe:
+    image: lobehub/lobe-chat-database
+    container_name: lobe-chat
+    ports:
+      - '3210:3210'
+    depends_on:
+      - postgresql
+      - minio
+      - zitadel
+    env_file:
+      - .env
+    restart: always
+
+volumes:
+  data:
+    driver: local
+  s3_data:
+    driver: local

docker-compose/production/zitadel/zitadel-config.yaml

@@ -0,0 +1,25 @@
+Log:
+  Level: 'info'
+
+ExternalPort: 443 
+ExternalDomain: example.com #Your zitadel's domain name
+ExternalSecure: true 
+TLS:
+  Enabled: false # ZITADEL_TLS_ENABLED
+
+# If not using the docker compose example, adjust these values for connecting ZITADEL to your PostgreSQL
+Database:
+  postgres:
+    Host: postgresql
+    Port: 5432
+    Database: zitadel
+    User:
+      Username: 'zitadel'
+      Password: 'zitadel'
+      SSL:
+        Mode: 'disable'
+    Admin:
+      Username: 'postgres'
+      Password: 'uWNZugjBqixf8dxC' #postgres password
+      SSL:
+        Mode: 'disable'

docker-compose/production/zitadel/zitadel-init-steps.yaml

@@ -0,0 +1,11 @@
+# All possible options and their defaults: https://github.com/zitadel/zitadel/blob/main/cmd/setup/steps.yaml
+FirstInstance:
+  Org:
+    Human:
+      # use the loginname root@zitadel.localhost, replace localhost with your configured external domain
+      Username: 'root'
+      # The password must be 8 characters or more and must contain uppercase letters, lowercase letters, symbols, and numbers. The first login will require a password change. 
+      Password: 'Password1!'
+      Email:
+        # Optional, if set, can be used to log in with email.
+        Address: 'example@zitadel.com' # ZITADEL_FIRSTINSTANCE_ORG_HUMAN_EMAIL_ADDRESS    

docs/self-hosting/advanced/auth.mdx

@@ -0,0 +1,77 @@
+---
+title: LobeChat Authentication Service Configuration
+description: >-
+  Learn how to configure external authentication services using Clerk or Next
+  Auth for centralized user authorization management. Supported authentication
+  services include Auth0, Azure ID, etc.
+tags:
+  - Authentication Service
+  - Next Auth
+  - SSO
+  - Clerk
+---
+
+# Authentication Service
+
+LobeChat supports the configuration of external authentication services using Clerk or Next Auth for internal use within enterprises/organizations to centrally manage user authorization.
+
+## Clerk
+
+Clerk is a comprehensive identity verification solution that has recently gained popularity. It provides a simple yet powerful API and services to handle user authentication and session management. Clerk's design philosophy is to offer a concise and modern authentication solution that enables developers to easily integrate and use it.
+
+LobeChat has deeply integrated with Clerk to provide users with a more secure and convenient login and registration experience. It also relieves developers from the burden of managing authentication logic. Clerk's concise and modern design philosophy aligns perfectly with LobeChat's goals, making user management on the entire platform more efficient and reliable.
+
+By setting the environment variables `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` and `CLERK_SECRET_KEY` in LobeChat's environment, you can enable and use Clerk.
+
+## Next Auth
+
+Before using NextAuth, please set the following variables in LobeChat's environment variables:
+
+| Environment Variable | Type | Description |
+| --- | --- | --- |
+| `NEXT_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. |
+| `NEXTAUTH_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`. |
+
+Currently supported identity verification services include:
+
+<Cards>
+  <Card href={'/docs/self-hosting/advanced/auth/next-auth/auth0'} title={'Auth0'} />
+  <Card
+    href={'/docs/self-hosting/advanced/auth/next-auth/microsoft-entra-id'}
+    title={'Microsoft Entra ID'}
+  />
+  <Card href={'/docs/self-hosting/advanced/auth/next-auth/authentik'} title={'Authentik'} />
+  <Card href={'/docs/self-hosting/advanced/auth/next-auth/github'} title={'Github'} />
+  <Card href={'/docs/self-hosting/advanced/auth/next-auth/zitadel'} title={'ZITADEL'} />
+  <Card
+    href={'/docs/self-hosting/advanced/auth/next-auth/cloudflare-zero-trust'}
+    title={'Cloudflare Zero Trust'}
+  />
+  <Card href={'/docs/self-hosting/advanced/auth/next-auth/authelia'} title={'Authelia'} />
+  <Card href={'/docs/self-hosting/advanced/auth/next-auth/logto'} title={'Logto'} />
+</Cards>
+
+Click on the links to view the corresponding platform's configuration documentation.
+
+## Advanced Configuration
+
+To simultaneously enable multiple identity verification sources, please set the `NEXT_AUTH_SSO_PROVIDERS` environment variable, separating them with commas, for example, `auth0,microsoft-entra-id,authentik`.
+
+The order corresponds to the display order of the SSO providers.
+
+| SSO Provider       | Value       |
+| ------------------ | ----------- |
+| Auth0              | `auth0`     |
+| Authenlia          | `authenlia` |
+| Authentik          | `authentik` |
+| Casdoor            | `casdoor`   |
+| Cloudflare Zero Trust | `cloudflare-zero-trust` |
+| Github             | `github`    |
+| Logto              | `logto`     |
+| Microsoft Entra ID | `microsoft-entra-id`  |
+| ZITADEL            | `zitadel`   |
+
+## Other SSO Providers
+
+Please refer to the [NextAuth.js](https://next-auth.js.org/providers) documentation and feel free to submit a Pull Request.

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

@@ -0,0 +1,74 @@
+---
+title: LobeChat 身份验证服务配置
+description: 了解如何使用 Clerk 或 Next Auth 配置外部身份验证服务，以统一管理用户授权。支持的身份验证服务包括 Auth0、 Azure ID 等。
+tags:
+  - 身份验证服务
+  - LobeChat
+  - SSO
+  - Clerk
+---
+
+# 身份验证服务
+
+LobeChat 支持使用 Clerk 或者 Next Auth 配置外部身份验证服务，供企业 / 组织内部使用，统一管理用户授权。
+
+## Clerk
+
+Clerk 是一个近期流行起来的全面的身份验证解决方案，它提供了简单而强大的 API 和服务来处理用户认证和会话管理。Clerk 的设计哲学是提供一套简洁、现代的认证解决方案，使得开发者可以轻松集成和使用。
+
+LobeChat 与 Clerk 做了深度集成，能够为用户提供一个更加安全、便捷的登录和注册体验，同时也为开发者减轻了管理身份验证逻辑的负担。Clerk 的简洁和现代的设计理念与 LobeChat 的目标非常契合，使得整个平台的用户管理更加高效和可靠。
+
+在 LobeChat 的环境变量中设置 `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` 和 `CLERK_SECRET_KEY`，即可开启和使用 Clerk。
+
+## Next Auth
+
+在使用 NextAuth 之前，请先在 LobeChat 的环境变量中设置以下变量：
+
+| 环境变量 | 类型 | 描述 |
+| --- | --- | --- |
+| `NEXT_AUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令： `openssl rand -base64 32`，或者访问 `https://generate-secret.vercel.app/32` 生成秘钥。 |
+| `NEXTAUTH_URL` | 必选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth` |
+| `NEXT_AUTH_SSO_PROVIDERS` | 可选 | 该环境变量用于同时启用多个身份验证源，以逗号 `,` 分割，例如 `auth0,microsoft-entra-id,authentik`。 |
+
+目前支持的身份验证服务有：
+
+<Cards>
+  <Card href={'/zh/docs/self-hosting/advanced/auth/next-auth/auth0'} title={'Auth0'} />
+  <Card
+    href={'/zh/docs/self-hosting/advanced/auth/next-auth/microsoft-entra-id'}
+    title={'Microsoft Entra ID'}
+  />
+  <Card href={'/zh/docs/self-hosting/advanced/auth/next-auth/authentik'} title={'Authentik'} />
+  <Card href={'/zh/docs/self-hosting/advanced/auth/next-auth/github'} title={'Github'} />
+  <Card href={'/zh/docs/self-hosting/advanced/auth/next-auth/zitadel'} title={'ZITADEL'} />
+  <Card
+    href={'/zh/docs/self-hosting/advanced/auth/next-auth/cloudflare-zero-trust'}
+    title={'Cloudflare Zero Trust'}
+  />
+  <Card href={'/zh/docs/self-hosting/advanced/auth/next-auth/authelia'} title={'Authelia'} />
+  <Card href={'/zh/docs/self-hosting/advanced/auth/next-auth/logto'} title={'Logto'} />
+</Cards>
+
+点击即可查看对应平台的配置文档。
+
+## 进阶配置
+
+同时启用多个身份验证源请设置 `NEXT_AUTH_SSO_PROVIDERS` 环境变量，以逗号 `,` 分割，例如 `auth0,microsoft-entra-id,authentik`。
+
+顺序为 SSO 提供商的显示顺序。
+
+| SSO 提供商         | 值          |
+| ------------------ | ----------- |
+| Auth0              | `auth0`     |
+| Authenlia          | `authenlia` |
+| Authentik          | `authentik` |
+| Casdoor            | `casdoor`   |
+| Cloudflare Zero Trust | `cloudflare-zero-trust` |
+| Github             | `github`    |
+| Logto              | `logto`     |
+| Microsoft Entra ID | `microsoft-entra-id`  |
+| ZITADEL            | `zitadel`   |
+
+## 其他 SSO 提供商
+
+请参考 [NextAuth.js](https://next-auth.js.org/providers) 文档，欢迎提交 Pull Request。

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

@@ -0,0 +1,81 @@
+---
+title: Configure Clerk Authentication Service - Step-by-Step Guide
+description: >-
+  Learn how to set up Clerk authentication with environment variables and
+  webhooks.
+tags:
+  - Clerk Authentication
+  - Environment Variables
+  - Webhook Configuration
+---
+# Configure Clerk Authentication Service
+
+Go to [Clerk](https://clerk.com?utm_source=lobehub\&utm_medium=docs) to register and create an application to obtain the corresponding Public Key and Secret Key.
+
+## Get Environment Variables
+
+<Steps>
+
+### Add Public and Private Key Environment Variables
+
+Add `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` and `CLERK_SECRET_KEY` environment variables. You can click on the "API Keys" in the menu and copy the corresponding values to get these environment variables.
+
+<Image
+alt={'Find the corresponding public and private key environment variables in Clerk'}
+src={'https://github.com/lobehub/lobe-chat/assets/28616219/89883703-7a1a-4a11-b944-5d804544e57c'}>
+
+>
+</Image>
+
+The environment variables required for this step are as follows:
+
+```shell
+NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_live_xxxxxxxxxxx
+CLERK_SECRET_KEY=sk_live_xxxxxxxxxxxxxxxxxxxxxx
+```
+
+### Create and Configure Webhook in Clerk
+
+Since we let Clerk fully handle user authentication and management, we need Clerk to notify our application and store the changes in the user lifecycle (create, update, delete). We achieve this by using the Webhook provided by Clerk.
+
+We need to add an endpoint in Clerk's Webhooks to inform Clerk to send notifications to this endpoint when a user's information changes.
+
+<Image
+alt={'Add Webhooks endpoint in Clerk'}
+src={'https://github.com/lobehub/lobe-chat/assets/28616219/f50f47fb-5e8e-4930-bf4e-8cf6f5b8afb9'}>
+
+>
+</Image>
+
+Fill in your project URL in the endpoint, such as `https://your-project.com/api/webhooks/clerk`. Then, subscribe to events by checking the three user events (`user.created`, `user.deleted`, `user.updated`), and click create.
+
+<Callout type={'warning'}>The `https://` in the URL is essential to maintain the integrity of the URL.</Callout>
+
+<Image
+alt={'Configure URL and user events when adding Clerk Webhooks'}
+src={'https://github.com/lobehub/lobe-chat/assets/28616219/0249ea56-ab17-4aa9-a56c-9ebd556c2645'}>
+
+>
+</Image>
+
+### Add Webhook Secret to Environment Variables
+
+After creating, you can find the secret of this Webhook in the bottom right corner:
+
+<Image
+alt={'View Clerk Webhooks secret'}
+src={'https://github.com/lobehub/lobe-chat/assets/28616219/fab4abb2-584b-49de-9340-813382951635'}>
+
+>
+</Image>
+
+The environment variable corresponding to this secret is `CLERK_WEBHOOK_SECRET`:
+
+```shell
+CLERK_WEBHOOK_SECRET=whsec_xxxxxxxxxxxxxxxxxxxxxx
+```
+
+</Steps>
+
+By following these steps, you have successfully configured the Clerk authentication service.
+

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

@@ -0,0 +1,71 @@
+---
+title: 配置 Clerk 身份验证服务 - 完整指南
+description: 学习如何配置 Clerk 身份验证服务，获取公私钥和设置 Webhook。
+tags:
+  - Clerk
+  - 身份验证
+  - Webhook
+  - 环境变量
+---
+# 配置 Clerk 身份验证服务
+
+前往 [Clerk](https://clerk.com?utm_source=lobehub&utm_medium=docs) 注册并创建应用，获取相应的 Public Key 和 Secret Key。
+
+## 获取环境变量
+
+<Steps>
+
+### 添加公、私钥环境变量
+
+添加 `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` 和 `CLERK_SECRET_KEY` 环境变量。你可以在菜单中点击「API Keys」，然后复制对应的值获取该环境变量。
+
+<Image
+  alt={'在 Clerk 中找到对应的公私钥环境变量'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/89883703-7a1a-4a11-b944-5d804544e57c'}
+></Image>
+
+此步骤所需的环境变量如下：
+
+```shell
+NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_live_xxxxxxxxxxx
+CLERK_SECRET_KEY=sk_live_xxxxxxxxxxxxxxxxxxxxxx
+```
+
+### 在 Clerk 中创建并配置 Webhook
+
+由于我们让 Clerk 完全接管用户鉴权与管理，因此我们需要在 Clerk 用户生命周期变更时（创建、更新、删除）中通知我们的应用并存储落库。我们通过 Clerk 提供的 Webhook 来实现这一诉求。
+
+我们需要在 Clerk 的 Webhooks 中添加一个端点（Endpoint），告诉 Clerk 当用户发生变更时，向这个端点发送通知。
+
+<Image
+  alt={'Clerk 添加 Webhooks 端点'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/f50f47fb-5e8e-4930-bf4e-8cf6f5b8afb9'}
+></Image>
+
+在 endppint 中填写你的项目 URL，如 `https://your-project.com/api/webhooks/clerk`。然后在订阅事件（Subscribe to events）中，勾选 user 的三个事件（`user.created` 、`user.deleted`、`user.updated`），然后点击创建。
+
+<Callout type={'warning'}>URL的`https://`不可缺失，须保持URL的完整性</Callout>
+
+<Image
+  alt={'添加 Clerk Webhooks 时，配置 URL 和用户事件'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/0249ea56-ab17-4aa9-a56c-9ebd556c2645'}
+></Image>
+
+### 将 Webhook 秘钥添加到环境变量
+
+创建完毕后，可以在右下角找到该 Webhook 的秘钥：
+
+<Image
+  alt={'查看 Clerk Webhooks 秘钥'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/fab4abb2-584b-49de-9340-813382951635'}
+></Image>
+
+这个秘钥所对应的环境变量名为 `CLERK_WEBHOOK_SECRET`：
+
+```shell
+CLERK_WEBHOOK_SECRET=whsec_xxxxxxxxxxxxxxxxxxxxxx
+```
+
+</Steps>
+
+这样，你已经成功配置了 Clerk 身份验证服务。

docs/self-hosting/advanced/auth/next-auth/auth0.mdx

@@ -76,14 +76,12 @@ When deploying LobeChat, you need to configure the following environment variabl
 
 | Environment Variable | Type | Description |
 | --- | --- | --- |
-| `ENABLE_OAUTH_SSO` | Required | Enable single sign-on (SSO) for LobeChat. Set to `1` to enable single sign-on. |
-| `NEXTAUTH_SECRET` | Required | Key used to encrypt Auth.js session tokens. You can generate a key using the following command: `openssl rand -base64 32` |
-| `SSO_PROVIDERS` | Optional | Select the single sign-on provider for LoboChat. Use `auth0` for Auth0. |
-| `AUTH0_CLIENT_ID` | Required | Client ID of the Auth0 application |
-| `AUTH0_CLIENT_SECRET` | Required | Client Secret of the Auth0 application |
-| `AUTH0_ISSUER` | Required | Domain of the Auth0 application, `https://example.auth0.com` |
-| `ACCESS_CODE` | Required | Add a password to access this service. You can set a sufficiently long random password to "disable" access code authorization. |
-| `NEXTAUTH_URL` | Optional | The URL is used to specify the callback address for the execution of OAuth authentication in Auth.js. It needs to be set only when the default address is incorrect. `https://example.com/api/auth` |
+| `NEXT_AUTH_SECRET` | Required | Key used to encrypt Auth.js session tokens. You can generate a key using the following command: `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | Required | Select the single sign-on provider for LoboChat. Use `auth0` for Auth0. |
+| `AUTH_AUTH0_ID` | Required | Client ID of the Auth0 application |
+| `AUTH_AUTH0_SECRET` | Required | Client Secret of the Auth0 application |
+| `AUTH_AUTH0_ISSUER` | Required | Domain of the Auth0 application, `https://example.auth0.com` |
+| `NEXTAUTH_URL` | Required | The URL is used to specify the callback address for the execution of OAuth authentication in Auth.js. It needs to be set only when the default address is incorrect. `https://example.com/api/auth` |
 
   <Callout type={'tip'}>
     You can refer to the related variable details at [📘Environment Variables](/docs/self-hosting/environment-variable#auth0).

docs/self-hosting/advanced/auth/next-auth/auth0.zh-CN.mdx

@@ -15,7 +15,7 @@ tags:
 <Steps>
   ### 创建 Auth0 应用
 
-注册并登录 [Auth0][auth0-client-page]，点击左侧导航栏的「Applications」，切换到应用管理界面，点击右上角「Create Application」以创建应用。
+注册并登录 [Auth0](https://manage.auth0.com/dashboard)，点击左侧导航栏的「Applications」，切换到应用管理界面，点击右上角「Create Application」以创建应用。
 
 <Image
   alt="创建 Auth0 应用 S1"
@@ -71,17 +71,15 @@ http(s)://your-domain/api/auth/callback/auth0
 
 | 环境变量 | 类型 | 描述 |
 | --- | --- | --- |
-| `ENABLE_OAUTH_SSO` | 必选 | 为 LobeChat 启用单点登录 (SSO)。设置为 `1` 以启用单点登录。 |
-| `NEXTAUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32` |
-| `SSO_PROVIDERS` | 必选 | 选择 LoboChat 的单点登录提供商。使用 Auth0 请填写 `auth0`。 |
-| `AUTH0_CLIENT_ID` | 必选 | Auth0 应用程序的 Client ID |
-| `AUTH0_CLIENT_SECRET` | 必选 | Auth0 应用程序的 Client Secret |
-| `AUTH0_ISSUER` | 必选 | Auth0 应用程序的 Domain，`https://example.auth0.com` |
-| `ACCESS_CODE` | 必选 | 添加访问此服务的密码，你可以设置一个足够长的随机密码以 “禁用” 访问码授权 |
-| `NEXTAUTH_URL` | 可选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth` |
+| `NEXT_AUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | 必选 | 选择 LoboChat 的单点登录提供商。使用 Auth0 请填写 `auth0`。 |
+| `AUTH_AUTH0_ID` | 必选 | Auth0 应用程序的 Client ID |
+| `AUTH_AUTH0_SECRET` | 必选 | Auth0 应用程序的 Client Secret |
+| `AUTH_AUTH0_ISSUER` | 必选 | Auth0 应用程序的 Domain，`https://example.auth0.com` |
+| `NEXTAUTH_URL` | 必选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth` |
 
   <Callout type={'tip'}>
-    前往 [📘 环境变量](/docs/self-hosting/environment-variable#auth0) 可查阅相关变量详情。
+    前往 [📘 环境变量](/zh/docs/self-hosting/environment-variables/auth#auth-0) 可查阅相关变量详情。
 
 </Callout>
 </Steps>
@@ -96,7 +94,7 @@ http(s)://your-domain/api/auth/callback/auth0
 
 如果你的企业或组织已有现有的统一身份认证设施，可在 Applications -> SSO Integrations 中，连接现有的单点登录服务。
 
-Auth0 支持 Azure Active Directory / Slack / Google Workspace / Office 365 / Zoom 等单点登录服务，详细支持列表可参考 [这里][auth0-sso-integrations]
+Auth0 支持 Azure Active Directory / Slack / Google Workspace / Office 365 / Zoom 等单点登录服务，详细支持列表可参考 [这里](https://marketplace.auth0.com/features/sso-integrations)
 
 <Image
   alt="Connecting to an Existing Single Sign-On Service"
@@ -118,9 +116,6 @@ Auth0 支持 Azure Active Directory / Slack / Google Workspace / Office 365 / Zo
 
 <Callout>
   如果你需要限制登录人员，务必配置 **阻止策略**： 请在打开社交登录选项后，参考
-  [这篇文章][auth0-login-actions-manual] 创建 Action 来设置阻止 / 允许列表。
+  [这篇文章](https://auth0.com/blog/permit-or-deny-login-requests-using-auth0-actions/) 创建 Action
+  来设置阻止 / 允许列表。
 </Callout>
-
-[auth0-client-page]: https://manage.auth0.com/dashboard
-[auth0-login-actions-manual]: https://auth0.com/blog/permit-or-deny-login-requests-using-auth0-actions/
-[auth0-sso-integrations]: https://marketplace.auth0.com/features/sso-integrations

docs/self-hosting/advanced/auth/next-auth/authelia.mdx

@@ -0,0 +1,75 @@
+---
+title: Configuring Authelia Authentication Service for LobeChat
+description: >-
+  Learn how to configure Authelia authentication service in LobeChat, including
+  creating a provider, configuring environment variables, and deploying
+  LobeChat. Detailed steps and necessary environment variable settings.
+tags:
+  - Authelia Configuration
+  - Single Sign-On (SSO)
+  - LobeChat Authentication
+  - Environment Variables
+  - Deployment Instructions
+---
+
+## Configuring Authelia Authentication Service
+
+## Authelia Configuration Flow
+
+<Steps>
+### Create an Authelia Identity Provider
+
+We assume you are already familiar with using Authelia. Let's say your LobeChat instance is deployed at https://lobe.example.com/.
+Note that currently only localhost supports HTTP access; other domains need to enable TLS, otherwise Authelia will actively interrupt authentication by default.
+
+Now, let's open and edit the configuration file of your Authelia instance:
+
+Add a new lobe-chat item under identity_providers -> oidc:
+
+```yaml
+identity_providers:
+  oidc:
+    ...
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    - id: lobe-chat
+      description: LobeChat
+      secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
+      public: false
+      authorization_policy: two_factor
+      redirect_uris:
+        - https://chat.example.com/api/auth/callback/authelia
+      scopes:
+        - openid
+        - profile
+        - email
+      userinfo_signing_algorithm: none
+```
+
+Make sure to replace secret and redirect_urls with your own values.
+Note! The secret configured in Authelia is ciphertext, i.e., a salted hash value. Its corresponding plaintext needs to be filled in LobeChat later.
+
+Save the configuration file and restart the Authelia service. Now we have completed the Authelia configuration.
+
+### Configure Environment Variables
+
+When deploying LobeChat, you need to configure the following environment variables:
+
+| Environment Variable | Type | Description |
+| --- | --- | --- |
+| `NEXT_AUTH_SECRET` | Required | The secret used to encrypt Auth.js session tokens. You can generate a secret using the following command: `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | Required | Select the SSO provider for LoboChat. Use `authentik` for Authentik. |
+| `AUTH_AUTHELIA_ID` | Required | The id just configured in Authelia, example value is lobe-chat |
+| `AUTH_AUTHELIA_SECRET` | Required | The plaintext corresponding to the secret just configured in Authelia, example value is insecure_secret |
+| `AUTH_AUTHELIA_ISSUER` | Required | Your Authelia URL, for example https://sso.example.com |
+| `NEXTAUTH_URL` | Required | This URL is used to specify the callback address for Auth.js when performing OAuth verification. It only needs to be set when the default generated redirect address is incorrect. https://chat.example.com/api/auth |
+
+<Callout type={'tip'}>
+  Go to  [📘 Environment Variables](/docs/self-hosting/environment-variable#Authelia) for details about the variables.
+</Callout>
+</Steps>
+
+<Callout type={'info'}>
+  After a successful deployment, users will be able to use LobeChat by authenticating with the users
+  configured in Authelia.
+</Callout>

docs/self-hosting/advanced/auth/next-auth/authelia.zh-CN.mdx

@@ -0,0 +1,73 @@
+---
+title: 在 LobeChat 中配置 Authelia 身份验证服务
+description: 学习如何在 LobeChat 中配置 Authelia 身份验证服务，包括创建提供程序、配置环境变量和部署 LobeChat。详细步骤和必要环境变量设置。
+tags:
+  - Authelia
+  - 身份验证
+  - 单点登录
+  - 环境变量
+  - LobeChat
+---
+
+# 配置 Authelia 身份验证服务
+
+## Authelia 配置流程
+
+<Steps>
+### 创建 Authelia 提供应用
+
+我们现在默认您已经了解了如何使用 Authelia。假设您的 LobeChat 实例部署在 `https://lobe.example.com/` 中。
+注意，目前只有 `localhost` 支持 HTTP 访问，其他域名需要启用 TLS，否则 Authelia 默认将主动中断身份认证。
+
+现在，我们打开 Authelia 实例的配置文件进行编辑：
+
+在 `identity_providers`-> `oidc` 下新增一个 `lobe-chat` 的项目：
+
+```yaml
+...
+identity_providers:
+  oidc:
+    ...
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    - id: lobe-chat
+      description: LobeChat
+      secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
+      public: false
+      authorization_policy: two_factor
+      redirect_uris:
+        - https://chat.example.com/api/auth/callback/authelia
+      scopes:
+        - openid
+        - profile
+        - email
+      userinfo_signing_algorithm: none
+```
+
+请您确保 `secret` 和 `redirect_urls` 替换成您自己的值。
+注意！Authelia 中配置 `secret` 是密文，即加盐哈希值。其对应的明文稍后需要填写在 lobeChat 中。
+
+保存配置文件，然后重启 Authelia 服务。现在我们完成了 Authelia 的配置工作。
+
+### 配置环境变量
+
+在部署 LobeChat 时，你需要配置以下环境变量：
+
+| 环境变量 | 类型 | 描述 |
+| --- | --- | --- |
+| `NEXT_AUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | 必选 | 选择 LoboChat 的单点登录提供商。使用 Authelia 请填写 `authelia`。 |
+| `AUTH_AUTHELIA_ID` | 必选 | 刚刚在 Authelia 配置的 `id`，示例值是 `lobe-chat` |
+| `AUTH_AUTHELIA_SECRET` | 必选 | 刚刚在 Authelia 配置的 `secret` 对应的明文，示例值是 `insecure_secret` |
+| `AUTH_AUTHELIA_ISSUER` | 必选 |您的 Authelia 的网址，例如 `https://sso.example.com` |
+| `NEXTAUTH_URL` | 必选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://chat.example.com/api/auth` |
+
+  <Callout type={'tip'}>
+    前往 [📘 环境变量](/zh/docs/self-hosting/environment-variable#Authelia) 可查阅相关变量详情。
+
+</Callout>
+</Steps>
+
+<Callout type={'info'}>
+  部署成功后，用户将可以使用 Authelia 中配置的用户通过身份认证并使用 LobeChat。
+</Callout>

docs/self-hosting/advanced/auth/next-auth/authentik.mdx

@@ -54,14 +54,12 @@ When deploying LobeChat, you need to configure the following environment variabl
 
 | Environment Variable | Type | Description |
 | --- | --- | --- |
-| `ENABLE_OAUTH_SSO` | Required | Enable Single Sign-On (SSO) for LobeChat. Set to `1` to enable SSO. |
-| `NEXTAUTH_SECRET` | Required | The secret used to encrypt Auth.js session tokens. You can generate a secret using the following command: `openssl rand -base64 32` |
-| `SSO_PROVIDERS` | Required | Select the SSO provider for LoboChat. Use `authentik` for Authentik. |
-| `AUTHENTIK_CLIENT_ID` | Required | The Client ID from the Authentik application provider details page |
-| `AUTHENTIK_CLIENT_SECRET` | Required | The Client Secret from the Authentik application provider details page |
-| `AUTHENTIK_ISSUER` | Required | The OpenID Configuration Issuer from the Authentik application provider details page |
-| `ACCESS_CODE` | Required | Add a password to access this service, you can set a sufficiently long random password to "disable" access code authorization |
-| `NEXTAUTH_URL` | Optional | This URL is used to specify the callback address for Auth.js when performing OAuth authentication. It only needs to be set when the default generated redirect address is incorrect. `https://example.com/api/auth` |
+| `NEXT_AUTH_SECRET` | Required | The secret used to encrypt Auth.js session tokens. You can generate a secret using the following command: `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | Required | Select the SSO provider for LoboChat. Use `authentik` for Authentik. |
+| `AUTH_AUTHENTIK_ID` | Required | The Client ID from the Authentik application provider details page |
+| `AUTH_AUTHENTIK_SECRET` | Required | The Client Secret from the Authentik application provider details page |
+| `AUTH_AUTHENTIK_ISSUER` | Required | The OpenID Configuration Issuer from the Authentik application provider details page |
+| `NEXTAUTH_URL` | Required | This URL is used to specify the callback address for Auth.js when performing OAuth authentication. It only needs to be set when the default generated redirect address is incorrect. `https://example.com/api/auth` |
 
   <Callout type={'tip'}>
     Go to  [📘 Environment Variables](/docs/self-hosting/environment-variable#Authentik) for details about the variables.

docs/self-hosting/advanced/auth/next-auth/authentik.zh-CN.mdx

@@ -27,8 +27,8 @@ https://your-domain/api/auth/callback/authentik
 ```
 
 <Callout type={'info'}>
-  - 可以之后再填写或修改 `重定向 URL/Origin（正则）`，但是务必保证填写的 URL 与部署的 URL 一致。 -
-  your-domain 请替换为自己的域名
+  - 可以之后再填写或修改 `重定向 URL/Origin（正则）`，但是务必保证填写的 URL 与部署的 URL 一致。 
+  - your-domain 请替换为自己的域名
 </Callout>
 
 <Image
@@ -49,17 +49,15 @@ https://your-domain/api/auth/callback/authentik
 
 | 环境变量 | 类型 | 描述 |
 | --- | --- | --- |
-| `ENABLE_OAUTH_SSO` | 必选 | 为 LobeChat 启用单点登录 (SSO)。设置为 `1` 以启用单点登录。 |
-| `NEXTAUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32` |
-| `SSO_PROVIDERS` | 必选 | 选择 LoboChat 的单点登录提供商。使用 Authentik 请填写 `authentik`。 |
-| `AUTHENTIK_CLIENT_ID` | 必选 | Authentik 提供程序详情页的 客户端 ID |
-| `AUTHENTIK_CLIENT_SECRET` | 必选 | Authentik 提供程序详情页的 客户端 Secret |
-| `AUTHENTIK_ISSUER` | 必选 | Authentik 提供程序详情页的 OpenID 配置颁发者 |
-| `ACCESS_CODE` | 必选 | 添加访问此服务的密码，你可以设置一个足够长的随机密码以 “禁用” 访问码授权 |
-| `NEXTAUTH_URL` | 可选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth` |
+| `NEXT_AUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | 必选 | 选择 LoboChat 的单点登录提供商。使用 Authentik 请填写 `authentik`。 |
+| `AUTH_AUTHENTIK_ID` | 必选 | Authentik 提供程序详情页的 客户端 ID |
+| `AUTH_AUTHENTIK_SECRET` | 必选 | Authentik 提供程序详情页的 客户端 Secret |
+| `AUTH_AUTHENTIK_ISSUER` | 必选 | Authentik 提供程序详情页的 OpenID 配置颁发者 |
+| `NEXTAUTH_URL` | 必选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth` |
 
   <Callout type={'tip'}>
-    前往 [📘 环境变量](/docs/self-hosting/environment-variable#Authentik) 可查阅相关变量详情。
+    前往 [📘 环境变量](/zh/docs/self-hosting/environment-variable#Authentik) 可查阅相关变量详情。
 
 </Callout>
 </Steps>

docs/self-hosting/advanced/auth/next-auth/casdoor.mdx

@@ -0,0 +1,122 @@
+---
+title: Configuring Casdoor Authentication Service in LobeChat
+description: >-
+  Learn how to configure the Casdoor authentication service in LobeChat,
+  including deployment, creation, permission settings, and environment
+  variables.
+tags:
+  - Casdoor Authentication
+  - Environment Variable Configuration
+  - Single Sign-On
+  - LobeChat
+---
+
+# Configuring Casdoor Authentication Service
+
+[Casdoor](https://github.com/casdoor/casdoor) is an open-source authentication service that is rich in features and easy to use.
+
+<Callout type={'tip'}>
+  If you want to privately deploy Casdoor, we recommend using Docker Compose to deploy it together with the LobeChat database version, allowing LobeChat to share the same Postgres instance.
+</Callout>
+
+## Casdoor Configuration Process
+
+If you are deploying using a local network IP, the following assumptions apply:
+
+- Your LobeChat database version IP/port is `http://LOBECHAT_IP:3210`.
+- You privately deploy Casdoor, and its domain is `http://CASDOOR_IP:8000`.
+
+If you are deploying using a public network, the following assumptions apply:
+
+- Your LobeChat database version domain is `https://lobe.example.com`.
+- You privately deploy Casdoor, and its domain is `https://lobe-auth-api.example.com`.
+
+<Steps>
+  ### Create a Casdoor Application
+
+Access your privately deployed Casdoor WebUI (default is `http://localhost:8000/`) to enter the console. The default account is `admin`, and the password is `123`.
+
+Go to `Authentication` -> `Applications`, create a `LobeChat` application or directly modify the built-in `built-in` application. You can explore other fields, but you must configure at least the following fields:
+
+- Name, Display Name: `LobeChat`
+- Redirect URLs:
+  - Local Development Environment: `http://localhost:3210/api/auth/callback/casdoor`
+  - Local Network IP Deployment: `http://LOBECHAT_IP:3210/api/auth/callback/casdoor`
+  - Public Network Environment: `https://lobe.example.com/api/auth/callback/casdoor`
+
+There are also some optional fields that can enhance user experience:
+
+- Logo: `https://lobehub.com/icon-192x192.png`
+- Form CSS, Form CSS (Mobile):
+
+  ```html
+  <style>
+    .login-panel {
+      padding: 40px 70px 0 70px;
+      border-radius: 10px;
+      background-color: #ffffff;
+      box-shadow: rgba(17, 12, 46, 0.15) 0px 48px 100px 0px;
+    }
+    .panel-logo {
+      width: 64px;
+    }
+    .login-logo-box {
+      margin-top: 20px;
+    }
+
+    #parent-area
+      > main
+      > div
+      > div.login-content
+      > div.login-panel
+      > div.login-form
+      > div
+      > div
+      > button {
+      box-shadow: none !important;
+      border-radius: 10px !important;
+      transition-property: all;
+      transition-timing-function: cubic-bezier(0.4, 0, 0.2, 1);
+      transition-duration: 150ms;
+      border: 1px solid #eee !important;
+    }
+
+    @media (max-width: 640px) {
+      .login-panel {
+        padding: 40px 0 0 0;
+        box-shadow: none;
+      }
+    }
+  </style>
+  ```
+
+Then, copy the `Client ID` and `Client Secret` and save them.
+
+### Configure Environment Variables
+
+Set the obtained `Client ID` and `Client Secret` as `AUTH_CASDOOR_ID` and `AUTH_CASDOOR_SECRET` in the LobeChat environment variables.
+
+Configure `AUTH_CASDOOR_ISSUER` in the LobeChat environment variables as follows:
+
+- `http://localhost:8000/` if you are in a local development environment.
+- `http://CASDOOR_IP:8000/` if you are privately deploying Casdoor in a local network.
+- `https://lobe-auth-api.example.com/` if you are deploying Casdoor in a public network environment.
+
+When deploying LobeChat, you need to configure the following environment variables:
+
+| Environment Variable | Type | Description |
+| --- | --- | --- |
+| `NEXT_AUTH_SECRET` | Required | A key for encrypting Auth.js session tokens. You can generate a key using the command: `openssl rand -base64 32`. |
+| `NEXT_AUTH_SSO_PROVIDERS` | Required | Select the single sign-on provider for LobeChat. Fill in `casdoor` for using Casdoor. |
+| `AUTH_CASDOOR_ID` | Required | The client ID from the Casdoor application details page. |
+| `AUTH_CASDOOR_SECRET` | Required | The client secret from the Casdoor application details page. |
+| `AUTH_CASDOOR_ISSUER` | Required | The OpenID Connect issuer for the Casdoor provider. |
+| `NEXTAUTH_URL` | Required | This URL specifies the callback address for Auth.js during OAuth verification and needs to be set only if the default generated redirect address is incorrect. `https://lobe.example.com/api/auth` |
+
+  <Callout type={'tip'}>
+    Visit [📘 Environment Variables](/docs/self-hosting/environment-variables/auth#casdoor) for details on related variables.
+ 
+</Callout>
+</Steps>
+
+<Callout type={'info'}>Once deployed successfully, users will be able to authenticate via Casdoor and use LobeChat.</Callout>

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

@@ -0,0 +1,120 @@
+---
+title: 在 LobeChat 中配置 Casdoor 身份验证服务
+description: 学习如何在 LobeChat 中配置 Casdoor 身份验证服务，包括部署、创建、设置权限和环境变量。
+tags:
+  - Casdoor 身份验证
+  - 环境变量配置
+  - 单点登录
+  - LobeChat
+---
+
+# 配置 Casdoor 身份验证服务
+
+[Casdoor](https://github.com/casdoor/casdoor) 是一个开源的身份验证服务，功能配置丰富且易于上手。
+
+<Callout type={'tip'}>
+  若你想要私有部署 Casdoor，我们建议你将之与 LobeChat 数据库版本一同使用 Docker Compose 部署，此时
+  LobeChat 可以与之共用同一个 Postgres 实例。
+</Callout>
+
+## Casdoor 配置流程
+
+若你使用局域网 IP 部署，下文假设：
+
+- 你的 LobeChat 数据库版本 IP / 端口为 `http://LOBECHAT_IP:3210`。
+- 你私有部署 Casdoor，其域名为 `http://CASDOOR_IP:8000`。
+
+若你使用公网部署，下文假设：
+
+- 你的 LobeChat 数据库版本域名为 `https://lobe.example.com`。
+- 你私有部署 Casdoor，其域名为 `https://lobe-auth-api.example.com`。
+
+<Steps>
+  ### 创建 Casdoor 应用
+
+访问你私有部署的 Casdoor WebUI（默认为 `http://localhost:8000/`） 进入控制台，默认账号为 `admin`，密码为 `123`。
+
+前往 `身份认证` -> `应用`，创建一个 `LobeChat` 应用或直接修改内置的 `built-in` 应用，其他字段可以自行探索，但你至少需要配置以下字段：
+
+- 名称、显示名称：`LobeChat`
+- 重定向 URLs：
+  - 本地开发环境：`http://localhost:3210/api/auth/callback/casdoor`
+  - 局域网 IP 部署：`http://LOBECHAT_IP:3210/api/auth/callback/casdoor`
+  - 公网环境：`https://lobe.example.com/api/auth/callback/casdoor`
+
+还有一些不必需但是可以提高用户体验的字段：
+
+- Logo：`https://lobehub.com/icon-192x192.png`
+- 表单 CSS、表单 CSS（移动端）：
+
+  ```html
+  <style>
+    .login-panel {
+      padding: 40px 70px 0 70px;
+      border-radius: 10px;
+      background-color: #ffffff;
+      box-shadow: rgba(17, 12, 46, 0.15) 0px 48px 100px 0px;
+    }
+    .panel-logo {
+      width: 64px;
+    }
+    .login-logo-box {
+      margin-top: 20px;
+    }
+
+    #parent-area
+      > main
+      > div
+      > div.login-content
+      > div.login-panel
+      > div.login-form
+      > div
+      > div
+      > button {
+      box-shadow: none !important;
+      border-radius: 10px !important;
+      transition-property: all;
+      transition-timing-function: cubic-bezier(0.4, 0, 0.2, 1);
+      transition-duration: 150ms;
+      border: 1px solid #eee !important;
+    }
+
+    @media (max-width: 640px) {
+      .login-panel {
+        padding: 40px 0 0 0;
+        box-shadow: none;
+      }
+    }
+  </style>
+  ```
+
+随后，复制 `客户端 ID` 和 `客户端密钥`，并保存。
+
+### 配置环境变量
+
+将获取到的 `客户端 ID` 和 `客户端`，设为 LobeChat 环境变量中的 `AUTH_CASDOOR_ID` 和 `AUTH_CASDOOR_SECRET`。
+
+配置 LobeChat 环境变量中 `AUTH_CASDOOR_ISSUER` 为：
+
+- `http://localhost:8000/`，若你是本地开发环境
+- `http://CASDOOR_IP:8000/`，若你是局域网私有部署的 Casdoor
+- `https://lobe-auth-api.example.com/`，若你是公网环境部署的 Casdoor
+
+在部署 LobeChat 时，你需要配置以下环境变量：
+
+| 环境变量 | 类型 | 描述 |
+| --- | --- | --- |
+| `NEXT_AUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | 必选 | 选择 LoboChat 的单点登录提供商。使用 Casdoor 请填写 `casdoor`。 |
+| `AUTH_CASDOOR_ID` | 必选 | Casdoor 应用详情页的客户端 ID |
+| `AUTH_CASDOOR_SECRET` | 必选 | Casdoor 应用详情页的客户端密钥 |
+| `AUTH_CASDOOR_ISSUER` | 必选 | Casdoor 提供程序的 OpenID Connect 颁发者。 |
+| `NEXTAUTH_URL` | 必选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://lobe.example.com/api/auth` |
+
+  <Callout type={'tip'}>
+    前往 [📘 环境变量](/zh/docs/self-hosting/environment-variables/auth#casdoor) 可查阅相关变量详情。
+ 
+</Callout>
+</Steps>
+
+<Callout type={'info'}>部署成功后，用户将可以通过 Casdoor 身份认证并使用 LobeChat。</Callout>

docs/self-hosting/advanced/auth/next-auth/cloudflare-zero-trust.mdx

@@ -0,0 +1,68 @@
+---
+title: Configuring Cloudflare Zero Trust Authentication Service for LobeChat
+description: >-
+  Learn how to configure Cloudflare Zero Trust for Single Sign-On (SSO) for
+  LobeChat, including creating an application provider, setting environment
+  variables, and deployment instructions.
+tags:
+  - Cloudflare Zero Trust
+  - Single Sign-On (SSO)
+  - LobeChat Authentication
+  - Environment Variables
+  - Deployment Instructions
+---
+
+# Configuring Cloudflare Zero Trust Authentication Service
+
+## Cloudflare Zero Trust Configuration Flow
+
+<Steps>
+### Creating an Application in Cloudflare Zero Trust
+
+We assume you are already familiar with using the Cloudflare Zero Trust platform and that your LobeChat instance is deployed at `https://chat.example.com`.
+
+First, we need to visit `https://one.dash.cloudflare.com/` and navigate to `Access - Applications`.
+
+![image](https://github.com/user-attachments/assets/4d671a7c-5d94-4c4b-b4fd-71a5a0e9d227)
+
+Now, on the current page, click `Add an application` and select `SaaS`.
+
+![image](https://github.com/user-attachments/assets/3da4c8c4-88c6-40a9-8005-6a0a44aa3b1f)
+
+In the `Application` text box, enter the application name, such as `LobeChat SSO`. Then click `Select OIDC`, followed by clicking `Add application`.
+
+![image](https://github.com/user-attachments/assets/16cd9aef-c87b-48a4-95c0-b666082e7515)
+
+At this point, you have successfully created a SaaS application named `LobeChat SSO` in Cloudflare Zero Trust.
+
+Next, we need to enter `https://chat.example.com/api/auth/callback/cloudflare-zero-trust` in the `Redirect URLs` field (note that `chat.example.com` should be replaced with your instance's address).
+
+![image](https://github.com/user-attachments/assets/433fdce4-0af5-417f-b80d-163c2d4f02f6)
+
+Finally, scroll down the page and record the following three values: `Client secret`, `Client ID`, and `Issuer`. You will need these for setting the environment variables when deploying LobeChat.
+
+![image](https://github.com/user-attachments/assets/2dd3cde5-fa0d-4f52-b82b-28d9e89379a0)
+
+### Configure Environment Variables
+
+When deploying LobeChat, you need to configure the following environment variables:
+
+| Environment Variable | Type | Description |
+| --- | --- | --- |
+| `NEXT_AUTH_SECRET` | Required | The secret used to encrypt Auth.js session tokens. You can generate a secret using the following command: `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | Required | Select the SSO provider for LoboChat. Use `cloudflare-zero-trust` for Cloudflare Zero Trust. |
+| `AUTH_CLOUDFLARE_ZERO_TRUST_ID` | Required | The Client ID from the Cloudflare Zero Trust application provider details page |
+| `AUTH_CLOUDFLARE_ZERO_TRUST_SECRET` | Required | The Client Secret from the Cloudflare Zero Trust application provider details page |
+| `AUTH_CLOUDFLARE_ZERO_TRUST_ISSUER` | Required | The OpenID Configuration Issuer from the Cloudflare Zero Trust application provider details page |
+| `NEXTAUTH_URL` | Required | This URL is used to specify the callback address for Auth.js when performing OAuth authentication. It only needs to be set when the default generated redirect address is incorrect. `https://example.com/api/auth` |
+
+  <Callout type={'tip'}>
+    Go to  [📘 Environment Variables](/docs/self-hosting/environment-variable#Cloudflare%20Zero%20Trust) for details about the variables.
+
+</Callout>
+</Steps>
+
+<Callout type={'info'}>
+  After a successful deployment, users will be able to use LobeChat by authenticating with the users
+  configured in Cloudflare Zero Trust.
+</Callout>

docs/self-hosting/advanced/auth/next-auth/cloudflare-zero-trust.zh-CN.mdx

@@ -0,0 +1,64 @@
+---
+title: 在 LobeChat 中配置 Cloudflare Zero Trust 身份验证服务
+description: >-
+  学习如何在 LobeChat 中配置 Cloudflare Zero Trust 身份验证服务，包括创建提供程序、配置环境变量和部署
+  LobeChat。详细步骤和必要环境变量设置。
+tags:
+  - Cloudflare Zero Trust
+  - 身份验证
+  - 单点登录
+  - 环境变量
+  - LobeChat
+---
+
+# 配置 Cloudflare Zero Trust 身份验证服务
+
+## Cloudflare Zero Trust 配置流程
+
+<Steps>
+### 在 Cloudflare Zero Trust 中创建应用
+
+我们现在默认您已经了解了如何使用 Cloudflare Zero Trust 平台且假设您的 LobeChat 实例部署在 `https://chat.example.com` 中。
+
+首先我们需要访问 `https://one.dash.cloudflare.com/` 并前往 `Access - Applications` 中。
+
+![image](https://github.com/user-attachments/assets/4d671a7c-5d94-4c4b-b4fd-71a5a0e9d227)
+
+现在，在所在页面点击 `Add an application` 并选择 `SaaS`。
+
+![image](https://github.com/user-attachments/assets/3da4c8c4-88c6-40a9-8005-6a0a44aa3b1f)
+
+在 `Application` 文本框内填入应用名称，如：`LobeChat SSO`，然后点击 `Select OIDC` 后点击 `Add applicaiton`
+
+![image](https://github.com/user-attachments/assets/16cd9aef-c87b-48a4-95c0-b666082e7515)
+
+至此您已成功在 Clouflare Zero Trust 中创建了一个名为 `LobeChat SSO` 的 SaaS 应用。
+
+接下来我们需要在 `Redirect URLs` 中填入 `https://chat.example.com/api/auth/callback/cloudflare-zero-trust`（注意此处的 `chat.example.com` 需要替换为您的实例地址） ![image](https://github.com/user-attachments/assets/433fdce4-0af5-417f-b80d-163c2d4f02f6)
+
+最后我们将页面往下滚动，您将需要记录以下三个值 `Client secret`, `Client ID` 及 `Issuer` 以备后续部署 LobeChat 环境变量使用。
+
+![image](https://github.com/user-attachments/assets/2dd3cde5-fa0d-4f52-b82b-28d9e89379a0)
+
+### 配置环境变量
+
+在部署 LobeChat 时，你需要配置以下环境变量：
+
+| 环境变量 | 类型 | 描述 |
+| --- | --- | --- |
+| `NEXT_AUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | 必选 | 选择 LoboChat 的单点登录提供商。使用 Cloudflare Zero Trust 请填写 `cloudflare-zero-trust`。 |
+| `AUTH_CLOUDFLARE_ZERO_TRUST_ID` | 必选 | 在 Cloudflare Zero Trust 生成的 `Client ID`，示例值是 `lobe-chat` |
+| `AUTH_CLOUDFLARE_ZERO_TRUST_SECRET` | 必选 | 在 Cloudflare Zero Trust 生成的 `Client secret`，示例值是 `insecure_secret` |
+| `AUTH_CLOUDFLARE_ZERO_TRUST_ISSUER` | 必选 | 在 Cloudflare Zero Trust 生成的 `Issuer`，例如 `https://example.cloudflareaccess.com/cdn-cgi/access/sso/oidc/7db0f` |
+| `NEXTAUTH_URL` | 必选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://chat.example.com/api/auth` |
+
+  <Callout type={'tip'}>
+    前往 [📘 环境变量](/zh/docs/self-hosting/environment-variable#Cloudflare%20Zero%20Trust) 可查阅相关变量详情。
+
+</Callout>
+</Steps>
+
+<Callout type={'info'}>
+  部署成功后，用户将可以使用 Cloudflare Zero Trust 中配置的用户通过身份认证并使用 LobeChat。
+</Callout>

docs/self-hosting/advanced/auth/next-auth/github.mdx

@@ -82,16 +82,14 @@ When deploying LobeChat, you need to configure the following environment variabl
 
 | Environment Variable | Type | Description |
 | --- | --- | --- |
-| `ENABLE_OAUTH_SSO` | Required | Enable Single Sign-On (SSO) for LobeChat. Set to `1` to enable SSO. |
-| `NEXTAUTH_SECRET` | Required | Key used to encrypt Auth.js session tokens. You can generate the key using the command: `openssl rand -base64 32` |
-| `SSO_PROVIDERS` | Required | Select the Single Sign-On provider for LobeChat. Use `github` for Github. |
-| `GITHUB_CLIENT_ID` | Required | Client ID in the Github App details page. |
-| `GITHUB_CLIENT_SECRET` | Required | Client Secret in the Github App details page. |
-| `ACCESS_CODE` | Required | Add a password for accessing this service. You can set a long random password to "disable" access code authorization. |
-| `NEXTAUTH_URL` | Optional | This URL is used to specify the callback address for Auth.js when performing OAuth authentication. Only set it if the default generated redirect address is incorrect. `https://example.com/api/auth` |
+| `NEXT_AUTH_SECRET` | Required | Key used to encrypt Auth.js session tokens. You can generate the key using the command: `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | Required | Select the Single Sign-On provider for LobeChat. Use `github` for Github. |
+| `AUTH_GITHUB_ID` | Required | Client ID in the Github App details page. |
+| `AUTH_GITHUB_SECRET` | Required | Client Secret in the Github App details page. |
+| `NEXTAUTH_URL` | Required | This URL is used to specify the callback address for Auth.js when performing OAuth authentication. Only set it if the default generated redirect address is incorrect. `https://example.com/api/auth` |
 
 <Callout type={'tip'}>
-  Go to [📘 Environment Variables](/docs/self-hosting/environment-variable#Github) for detailed
+  Go to [📘 Environment Variables](/docs/self-hosting/environment-variables/auth#github) for detailed
   information on these variables.
 </Callout>
 </Steps>

docs/self-hosting/advanced/auth/next-auth/github.zh-CN.mdx

@@ -1,6 +1,6 @@
 ---
 title: 在 LobeChat 中配置 Github 身份验证服务
-description: 学习如何在 LobeChat 中配置Github身份验证服务，包括创建新的Github App、设置权限和环境变量。
+description: 学习如何在 LobeChat 中配置 Github 身份验证服务，包括创建新的 Github App、设置权限和环境变量。
 tags:
   - Github 身份验证
   - Github App
@@ -16,9 +16,9 @@ tags:
 <Steps>
   ### 创建 Github 提供应用
 
-点击[这里](https://github.com/settings/apps/new) 创建一个新的 Github App。
+点击 [这里](https://github.com/settings/apps/new) 创建一个新的 Github App。
 
-填写Github App name、Homepage URL、Callbak URL
+填写 Github App name、Homepage URL、Callbak URL
 
 <Image
   alt="创建 Github 提供程序"
@@ -78,16 +78,14 @@ tags:
 
 | 环境变量 | 类型 | 描述 |
 | --- | --- | --- |
-| `ENABLE_OAUTH_SSO` | 必选 | 为 LobeChat 启用单点登录 (SSO)。设置为 `1` 以启用单点登录。 |
-| `NEXTAUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32` |
-| `SSO_PROVIDERS` | 必选 | 选择 LoboChat 的单点登录提供商。使用 Github 请填写 `github`。 |
-| `GITHUB_CLIENT_ID` | 必选 | Github App详情页的 客户端 ID |
-| `GITHUB_CLIENT_SECRET` | 必选 | Github App详情页的 客户端 Secret |
-| `ACCESS_CODE` | 必选 | 添加访问此服务的密码，你可以设置一个足够长的随机密码以 “禁用” 访问码授权 |
-| `NEXTAUTH_URL` | 可选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth` |
+| `NEXT_AUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | 必选 | 选择 LoboChat 的单点登录提供商。使用 Github 请填写 `github`。 |
+| `AUTH_GITHUB_ID` | 必选 | Github App详情页的 客户端 ID |
+| `AUTH_GITHUB_SECRET` | 必选 | Github App详情页的 客户端 Secret |
+| `NEXTAUTH_URL` | 必选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth` |
 
   <Callout type={'tip'}>
-    前往 [📘 环境变量](/docs/self-hosting/environment-variable#Github) 可查阅相关变量详情。
+    前往 [📘 环境变量](/zh/docs/self-hosting/environment-variables/auth#github) 可查阅相关变量详情。
 
 </Callout>
 </Steps>

docs/self-hosting/advanced/auth/next-auth/logto.mdx

@@ -0,0 +1,76 @@
+---
+title: Configuring Logto Authentication Service in LobeChat
+description: >-
+  Learn how to configure Logto authentication service in LobeChat, including
+  deployment, creation, setting permissions, and environment variables.
+tags:
+  - Logto Authentication
+  - Environment Variable Configuration
+  - Single Sign-On
+  - LobeChat
+---
+
+# Configuring Logto Authentication Service
+
+[Logto](https://github.com/logto-io/logto) is an open-source authentication service with a simple and beautiful interface, rich in features and easy to use. You can choose to use the official Logto Cloud or opt for a private deployment of Logto.
+
+<Callout type={'tip'}>
+  If you want to deploy Logto privately, we recommend using Docker Compose to deploy it together
+  with the LobeChat database version. In this case, LobeChat can share the same Postgres instance
+  with it.
+</Callout>
+
+## Logto Configuration Process
+
+The following assumes your LobeChat database version domain is `https://lobe.example.com`.
+
+If you are using a privately deployed Logto, assume its endpoint domain is `https://lobe-auth-api.example.com`.
+
+If you are using Logto Cloud, assume its endpoint domain is `https://example.logto.app`.
+
+<Steps>
+  ### Create Logto Application
+
+  Access your privately deployed Logto WebUI or [Logto Cloud](http://cloud.logto.io/) to enter the console, and create a `Next.js (App Router)` application under `Applications` with any name.
+
+  ### Configure Logto
+
+  Set the `Redirect URI` to `https://lobe.example.com/api/auth/callback/logto` and the `Post sign-out redirect URI` to `https://lobe.example.com/`.
+
+  Set `CORS allowed origins` to `https://lobe.example.com`.
+
+  <Image alt="Configure Logto" inStep src="https://github.com/user-attachments/assets/5b816379-c07b-40ea-bde4-df16e2e4e523" />
+
+  After successful creation, save the `Client ID` and `Client Secret`.
+
+  ### Configure Environment Variables
+
+  <Image alt="Configure Environment Variables" inStep src="https://github.com/user-attachments/assets/15af6d94-af4f-4aa9-bbab-7a46e9f9e837" />
+
+  Set the obtained `Client ID` and `Client Secret` as `AUTH_LOGTO_ID` and `AUTH_LOGTO_SECRET` in the LobeChat environment variables.
+
+  Configure `AUTH_LOGTO_ISSUER` in the LobeChat environment variables as follows:
+
+  - `https://lobe-auth-api.example.com/oidc` if you are using a privately deployed Logto
+  - `https://example.logto.app/oidc` if you are using Logto Cloud
+
+  When deploying LobeChat, you need to configure the following environment variables:
+
+  | Environment Variable      | Type     | Description                                                                                                                                                                            |
+  | ------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+  | `NEXT_AUTH_SECRET`        | Required | The key used to encrypt Auth.js session tokens. You can generate a key using the command: `openssl rand -base64 32`                                                                    |
+  | `NEXT_AUTH_SSO_PROVIDERS` | Required | Select the single sign-on provider for LobeChat. For Logto, enter `logto`.                                                                                                             |
+  | `AUTH_LOGTO_ID`           | Required | The Client ID from the Logto App details page                                                                                                                                          |
+  | `AUTH_LOGTO_SECRET`       | Required | The Client Secret from the Logto App details page                                                                                                                                      |
+  | `AUTH_LOGTO_ISSUER`       | Required | OpenID Connect issuer of the Logto provider                                                                                                                                            |
+  | `NEXTAUTH_URL`            | Required | This URL specifies the callback address for Auth.js during OAuth verification, needed only if the default generated redirect address is incorrect. `https://lobe.example.com/api/auth` |
+
+  <Callout type={'tip'}>
+    Visit [📘 Environment Variables](/docs/self-hosting/environment-variables/auth#logto) for details on related variables.
+ 
+</Callout>
+</Steps>
+
+<Callout type={'info'}>
+  After successful deployment, users will be able to authenticate via Logto and use LobeChat.
+</Callout>

docs/self-hosting/advanced/auth/next-auth/logto.zh-CN.mdx

@@ -0,0 +1,78 @@
+---
+title: 在 LobeChat 中配置 Logto 身份验证服务
+description: 学习如何在 LobeChat 中配置 Logto 身份验证服务，包括部署、创建、设置权限和环境变量。
+tags:
+  - Logto 身份验证
+  - 环境变量配置
+  - 单点登录
+  - LobeChat
+---
+
+# 配置 Logto 身份验证服务
+
+[Logto](https://github.com/logto-io/logto) 是一个开源的身份验证服务，界面简洁美观、功能配置丰富且易于上手，你即可以选择使用其官方提供的 Logto Cloud，也可以选择私有部署 Logto。
+
+<Callout type={'tip'}>
+    若你想要私有部署 Logto，我们建议你将之与 LobeChat 数据库版本一同使用 Docker Compose 部署，此时 LobeChat 可以与之共用同一个 Postgres 实例。
+</Callout>
+
+## Logto 配置流程
+
+下文假设你的 LobeChat 数据库版本域名为 `https://lobe.example.com`。
+
+若你是私有部署的 Logto，假设其 endpoint 域名为 `https://lobe-auth-api.example.com`。
+
+若你是使用的 Logto Cloud，假设其 endpoint 域名为 `https://example.logto.app`。
+
+<Steps>
+  ### 创建 Logto 应用
+
+访问你私有部署的 Logto WebUI 或者 [Logto Cloud](http://cloud.logto.io/) 进入控制台，在 `Applications` 里创建一个 `Next.js (App Router)` 应用，名称随意
+
+### 配置 Logto
+
+配置 `Redirect URI` 为 `https://lobe.example.com/api/auth/callback/logto`，`Post sign-out redirect URI` 为 `https://lobe.example.com/`
+
+配置 `CORS allowed origins` 为 `https://lobe.example.com`
+
+<Image
+  alt="配置 Logto"
+  inStep
+  src="https://github.com/user-attachments/assets/5b816379-c07b-40ea-bde4-df16e2e4e523"
+/>
+
+创建成功后， 将 `Client ID` 和 `Client Secret` 保存下来。
+
+### 配置环境变量
+
+<Image
+  alt="配置环境变量"
+  inStep
+  src="https://github.com/user-attachments/assets/15af6d94-af4f-4aa9-bbab-7a46e9f9e837"
+/>
+
+将获取到的 `Client ID` 和 `Client Secret`，设为 LobeChat 环境变量中的 `AUTH_LOGTO_ID` 和 `AUTH_LOGTO_SECRET`。
+
+配置 LobeChat 环境变量中 `AUTH_LOGTO_ISSUER` 为：
+
+- `https://lobe-auth-api.example.com/oidc`，若你是私有部署的 Logto
+- `https://example.logto.app/oidc`，若你是使用的 Logto Cloud
+
+在部署 LobeChat 时，你需要配置以下环境变量：
+
+| 环境变量 | 类型 | 描述 |
+| --- | --- | --- |
+| `NEXT_AUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | 必选 | 选择 LoboChat 的单点登录提供商。使用 Logto 请填写 `logto`。 |
+| `AUTH_LOGTO_ID` | 必选 | Logto App 详情页的 Client ID |
+| `AUTH_LOGTO_SECRET` | 必选 | Logto App 详情页的 Client Secret |
+| `AUTH_LOGTO_ISSUER` | 必选 | Logto 提供程序的 OpenID Connect 颁发者 |
+| `NEXTAUTH_URL` | 必选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://lobe.example.com/api/auth` |
+
+  <Callout type={'tip'}>
+    前往 [📘 环境变量](/zh/docs/self-hosting/environment-variables/auth#logto) 可查阅相关变量详情。
+ 
+</Callout>
+</Steps>
+
+<Callout type={'info'}>部署成功后，用户将可以通过 Logto 身份认证并使用 LobeChat。</Callout>

docs/self-hosting/advanced/auth/next-auth/microsoft-entra-id.mdx

@@ -25,7 +25,7 @@ Fill in the desired application name to be displayed to organizational users, ch
 In the `Redirect URI (optional)` section, for the application type, select `Web`, and in the Callback URL, enter:
 
 ```bash
-https://your-domain/api/auth/callback/azure-ad
+https://your-domain/api/auth/callback/microsoft-entra-id
 ```
 
 <Callout type={'info'}>
@@ -71,14 +71,12 @@ When deploying LobeChat, you need to configure the following environment variabl
 
 | Environment Variable | Type | Description |
 | --- | --- | --- |
-| `ENABLE_OAUTH_SSO` | Required | Enable single sign-on (SSO) for LobeChat. Set to `1` to enable single sign-on. |
-| `NEXTAUTH_SECRET` | Required | Key used to encrypt Auth.js session tokens. You can generate the key using the following command: `openssl rand -base64 32` |
-| `SSO_PROVIDERS` | Required | Select the single sign-on provider for LoboChat. Use `azure-ad` for Microsoft Entra ID. |
-| `AZURE_AD_CLIENT_ID` | Required | Client ID of the Microsoft Entra ID application. |
-| `AZURE_AD_CLIENT_SECRET` | Required | Client Secret of the Microsoft Entra ID application. |
-| `AZURE_AD_TENANT_ID` | Required | Tenant ID of the Microsoft Entra ID application. |
-| `ACCESS_CODE` | Required | Add a password for accessing this service, you can set a sufficiently long random password to "disable" access code authorization. |
-| `NEXTAUTH_URL` | Optional | This URL is used to specify the callback address for Auth.js when performing OAuth authentication. It is only necessary to set it when the default generated redirect address is incorrect. `https://example.com/api/auth` |
+| `NEXT_AUTH_SECRET` | Required | Key used to encrypt Auth.js session tokens. You can generate the key using the following command: `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | Required | Select the single sign-on provider for LoboChat. Use `microsoft-entra-id` for Microsoft Entra ID. |
+| `AUTH_MICROSOFT_ENTRA_ID_ID` | Required | Client ID of the Microsoft Entra ID application. |
+| `AUTH_MICROSOFT_ENTRA_ID_SECRET` | Required | Client Secret of the Microsoft Entra ID application. |
+| `AUTH_MICROSOFT_ENTRA_ID_TENANT_ID` | Required | Tenant ID of the Microsoft Entra ID application. |
+| `NEXTAUTH_URL` | Required | This URL is used to specify the callback address for Auth.js when performing OAuth authentication. It is only necessary to set it when the default generated redirect address is incorrect. `https://example.com/api/auth` |
 
 <Callout type={'tip'}>
   You can refer to [📘 environment

docs/self-hosting/advanced/auth/next-auth/microsoft-entra-id.zh-CN.mdx

@@ -24,7 +24,7 @@ tags:
 在 `Redirect URI (optional)` 中，应用类型选择 `Web`，Callback URL, 处填写：
 
 ```bash
-https://your-domain/api/auth/callback/azure-ad
+https://your-domain/api/auth/callback/microsoft-entra-id
 ```
 
 <Callout type={'info'}>
@@ -68,17 +68,15 @@ https://your-domain/api/auth/callback/azure-ad
 
 | 环境变量 | 类型 | 描述 |
 | --- | --- | --- |
-| `ENABLE_OAUTH_SSO` | 必选 | 为 LobeChat 启用单点登录 (SSO)。设置为 `1` 以启用单点登录。 |
-| `NEXTAUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32` |
-| `SSO_PROVIDERS` | 必选 | 选择 LoboChat 的单点登录提供商。使用 Microsoft Entra ID 请填写 `azure-ad`。 |
-| `AZURE_AD_CLIENT_ID` | 必选 | Microsoft Entra ID 应用程序的 Client ID |
-| `AZURE_AD_CLIENT_SECRET` | 必选 | Microsoft Entra ID 应用程序的 Client Secret |
-| `AZURE_AD_TENANT_ID` | 必选 | Microsoft Entra ID 应用程序的 Tenant ID |
-| `ACCESS_CODE` | 必选 | 添加访问此服务的密码，你可以设置一个足够长的随机密码以 “禁用” 访问码授权 |
-| `NEXTAUTH_URL` | 可选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth` |
+| `NEXT_AUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | 必选 | 选择 LoboChat 的单点登录提供商。使用 Microsoft Entra ID 请填写 `microsoft-entra-id`。 |
+| `AUTH_MICROSOFT_ENTRA_ID_ID` | 必选 | Microsoft Entra ID 应用程序的 Client ID |
+| `AUTH_MICROSOFT_ENTRA_ID_SECRET` | 必选 | Microsoft Entra ID 应用程序的 Client Secret |
+| `AUTH_MICROSOFT_ENTRA_ID_TENANT_ID` | 必选 | Microsoft Entra ID 应用程序的 Tenant ID |
+| `NEXTAUTH_URL` | 必选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth` |
 
   <Callout type={'tip'}>
-    前往 [📘 环境变量](/docs/self-hosting/environment-variable#microsoft-entra-id) 可查阅相关变量详情。
+    前往 [📘 环境变量](/zh/docs/self-hosting/environment-variable#microsoft-entra-id) 可查阅相关变量详情。
 
 </Callout>
 </Steps>

docs/self-hosting/advanced/auth/next-auth/zitadel.mdx

@@ -57,7 +57,8 @@ http(s)://your-domain/api/auth/callback/zitadel
   - You can fill in or modify redirect URIs after creating the application, but make sure the filled
   URL is consistent with the deployed URL.
 
-  - Replace `http(s)://your-domain` with the actual URL that LobeChat is deployed to.
+- Replace `http(s)://your-domain` with the actual URL that LobeChat is deployed to.
+
 </Callout>
 
 Confirm the configuration and click **Create**.
@@ -76,8 +77,7 @@ Save the **ClientId** and **ClientSecret** for later use.
   src="https://github.com/lobehub/lobe-chat/assets/8692892/407b4eed-7f21-4aa6-b68f-9bae2faf09d0"
 />
 
-In the application settings page, navigate to the **Token Settings** tab, enable **User Info inside
-ID Token** option, and click **Save**.
+In the application settings page, navigate to the **Token Settings** tab, enable **User Info inside ID Token** option, and click **Save**.
 
 <Image
   alt="Create ZITADEL Application S7"
@@ -99,14 +99,12 @@ When deploying LobeChat, you need to configure the following environment variabl
 
 | Environment Variable | Type | Description |
 | --- | --- | --- |
-| `ENABLE_OAUTH_SSO` | Required | Enable single sign-on (SSO) for LobeChat. Set to `1` to enable single sign-on. |
-| `NEXTAUTH_SECRET` | Required | Key used to encrypt Auth.js session tokens. You can generate a key using the following command: `openssl rand -base64 32` |
-| `SSO_PROVIDERS` | Optional | Select the single sign-on provider for LoboChat. Use `zitadel` for ZITADEL. |
-| `ZITADEL_CLIENT_ID` | Required | Client ID (`ClientId` as shown in ZITADEL) of the ZITADEL application |
-| `ZITADEL_CLIENT_SECRET` | Required | Client Secret (`ClientSecret` as shown in ZITADEL) of the ZITADEL application |
-| `ZITADEL_ISSUER` | Required | Issuer URL of the ZITADEL application |
-| `ACCESS_CODE` | Required | Add a password to access this service. You can set a sufficiently long random password to "disable" access code authorization. |
-| `NEXTAUTH_URL` | Optional | The URL is used to specify the callback address for the execution of OAuth authentication in Auth.js. It needs to be set only when the default address is incorrect. `https://example.com/api/auth` |
+| `NEXT_AUTH_SECRET` | Required | Key used to encrypt Auth.js session tokens. You can generate a key using the following command: `openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | Required | Select the single sign-on provider for LoboChat. Use `zitadel` for ZITADEL. |
+| `AUTH_ZITADEL_ID` | Required | Client ID (`ClientId` as shown in ZITADEL) of the ZITADEL application |
+| `AUTH_ZITADEL_SECRET` | Required | Client Secret (`ClientSecret` as shown in ZITADEL) of the ZITADEL application |
+| `AUTH_ZITADEL_ISSUER` | Required | Issuer URL of the ZITADEL application |
+| `NEXTAUTH_URL` | Required | The URL is used to specify the callback address for the execution of OAuth authentication in Auth.js. It needs to be set only when the default address is incorrect. `https://example.com/api/auth` |
 
   <Callout type={'tip'}>
     You can refer to the related variable details at [📘Environment Variables](/docs/self-hosting/environment-variables/auth#zitadel).

docs/self-hosting/advanced/auth/next-auth/zitadel.zh-CN.mdx

@@ -53,7 +53,8 @@ http(s)://your-domain/api/auth/callback/zitadel
 <Callout type={'important'}>
   - 可以创建应用后再填写或修改重定向 URL，但请确保填写的 URL 与部署的 URL 一致。
 
-  - 请将 `http(s)://your-domain` 替换为 LobeChat 部署的实际 URL。
+- 请将 `http(s)://your-domain` 替换为 LobeChat 部署的实际 URL。
+
 </Callout>
 
 确认配置并点击「创建」。
@@ -94,17 +95,15 @@ http(s)://your-domain/api/auth/callback/zitadel
 
 | 环境变量 | 类型 | 描述 |
 | --- | --- | --- |
-| `ENABLE_OAUTH_SSO` | 必选 | 为 LobeChat 启用单点登录（SSO）。设置为 `1` 以启用单点登录。 |
-| `NEXTAUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成密钥：`openssl rand -base64 32` |
-| `SSO_PROVIDERS` | 可选 | 为 LobeChat 选择单点登录提供程序。对于 ZITADEL，请填写 `zitadel`。 |
-| `ZITADEL_CLIENT_ID` | 必选 | ZITADEL 应用的 Client ID（`ClientId`）。 |
-| `ZITADEL_CLIENT_SECRET` | 必选 | ZITADEL 应用的 Client Secret（`ClientSecret`）。 |
-| `ZITADEL_ISSUER` | 必选 | ZITADEL 应用的 OpenID Connect 颁发者（issuer）URL。 |
-| `ACCESS_CODE` | 必选 | 添加访问此服务的代码。您可以设置一个足够长的随机密码以「禁用」访问码授权。 |
-| `NEXTAUTH_URL` | 可选 | 该 URL 用于指定 Auth.js 中执行 OAuth 认证的回调地址。仅当默认地址不正确时才需要设置。`https://example.com/api/auth` |
+| `NEXT_AUTH_SECRET` | 必选 | 用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成密钥：`openssl rand -base64 32` |
+| `NEXT_AUTH_SSO_PROVIDERS` | 必选 | 为 LobeChat 选择单点登录提供程序。对于 ZITADEL，请填写 `zitadel`。 |
+| `AUTH_ZITADEL_ID` | 必选 | ZITADEL 应用的 Client ID（`ClientId`）。 |
+| `AUTH_ZITADEL_SECRET` | 必选 | ZITADEL 应用的 Client Secret（`ClientSecret`）。 |
+| `AUTH_ZITADEL_ISSUER` | 必选 | ZITADEL 应用的 OpenID Connect 颁发者（issuer）URL。 |
+| `NEXTAUTH_URL` | 必选 | 该 URL 用于指定 Auth.js 中执行 OAuth 认证的回调地址。仅当默认地址不正确时才需要设置。`https://example.com/api/auth` |
 
   <Callout type={'tip'}>
-    您可以在 [📘 环境变量](/docs/self-hosting/environment-variables/auth#zitadel) 中查看相关变量的详细信息。
+    您可以在 [📘 环境变量](/zh/docs/self-hosting/environment-variables/auth#zitadel) 中查看相关变量的详细信息。
 
 </Callout>
 </Steps>

docs/self-hosting/advanced/authentication.mdx

@@ -1,51 +0,0 @@
----
-title: >-
-  LobeChat Identity Verification Service - Centralized User Authorization
-  Management
-description: >-
-  Learn about LobeChat's support for configuring external identity verification
-  services for centralized user authorization within enterprises/organizations.
-  Explore supported services like Auth0, Microsoft Entra ID, Authentik, Github,
-  and ZITADEL.
-tags:
-  - Identity Verification Service
-  - Centralized User Authorization
-  - SSO Providers
-  - Auth0
-  - Microsoft Entra ID
-  - Authentik
-  - Github
-  - ZITADEL
----
-
-# Identity Verification Service
-
-LobeChat supports the configuration of external identity verification services for internal use within enterprises/organizations to centrally manage user authorization.
-
-Currently supported identity verification services include:
-
-- [Auth0](/docs/self-hosting/advanced/sso-providers/auth0)
-- [Microsoft Entra ID](/docs/self-hosting/advanced/sso-providers/microsoft-entra-id)
-- [Authentik](/docs/self-hosting/advanced/sso-providers/authentik)
-- [Github](/docs/self-hosting/advanced/sso-providers/github)
-- [ZITADEL](/docs/self-hosting/advanced/sso-providers/zitadel)
-
-Click on the links to view the corresponding platform's configuration documentation.
-
-## Advanced Configuration
-
-To simultaneously enable multiple identity verification sources, please set the `SSO_PROVIDERS` environment variable, separating them with commas, for example, `auth0,azure-ad,authentik`.
-
-The order corresponds to the display order of the SSO providers.
-
-| SSO Provider       | Value       |
-| ------------------ | ----------- |
-| Auth0              | `auth0`     |
-| Microsoft Entra ID | `azure-ad`  |
-| Authentik          | `authentik` |
-| Github             | `github`    |
-| ZITADEL            | `zitadel`   |
-
-## Other SSO Providers
-
-Please refer to the [NextAuth.js](https://next-auth.js.org/providers) documentation and feel free to submit a Pull Request.

docs/self-hosting/advanced/authentication.zh-CN.mdx

@@ -1,47 +0,0 @@
----
-title: LobeChat 外部身份验证服务配置指南
-description: >-
-  了解如何配置外部身份验证服务以统一管理用户授权。支持的身份验证服务包括 Auth0, Microsoft Entra ID, Authentik,
-  Github, 和 ZITADEL。
-tags:
-  - 身份验证服务
-  - LobeChat
-  - SSO
-  - Auth0
-  - Microsoft Entra ID
-  - Authentik
-  - Github
-  - ZITADEL
----
-
-# 身份验证服务
-
-LobeChat 支持配置外部身份验证服务，供企业 / 组织内部使用，统一管理用户授权。
-
-目前支持的身份验证服务有：
-
-- [Auth0](/docs/self-hosting/advanced/sso-providers/auth0)
-- [Microsoft Entra ID](/docs/self-hosting/advanced/sso-providers/microsoft-entra-id)
-- [Authentik](/docs/self-hosting/advanced/sso-providers/authentik)
-- [Github](/docs/self-hosting/advanced/sso-providers/github)
-- [ZITADEL](/docs/self-hosting/advanced/sso-providers/zitadel)
-
-点击链接可以查看对应平台的配置文档。
-
-## 进阶配置
-
-同时启用多个身份验证源请设置 `SSO_PROVIDERS` 环境变量，以逗号 `,` 分割，例如 `auth0,azure-ad,authentik`。
-
-顺序为 SSO 提供商的显示顺序。
-
-| SSO 提供商         | 值          |
-| ------------------ | ----------- |
-| Auth0              | `auth0`     |
-| Microsoft Entra ID | `azure-ad`  |
-| Authentik          | `authentik` |
-| Github             | `github`    |
-| ZITADEL            | `zitadel`   |
-
-## 其他 SSO 提供商
-
-请参考 [NextAuth.js](https://next-auth.js.org/providers) 文档，欢迎提交 Pull Request。

docs/self-hosting/advanced/feature-flags.mdx

@@ -0,0 +1,51 @@
+---
+title: LobeChat Feature Flags Environment Variables Configuration Guide
+description: >-
+  Learn how to use environment variables to customize LobeChat's feature flags,
+  including controlling whether a feature is enabled or disabled, or enabling or
+  disabling features for specific user groups or environments as needed.
+tags:
+  - LobeChat
+  - Environment Variables
+  - Configuration Guide
+  - Feature Flags
+---
+
+# Feature Flags
+
+In addition to basic environment variable configuration, LobeChat also offers feature flags to control whether a feature is enabled globally, or to enable or disable features for specific user groups or environments as needed.
+
+## Feature Flags Environment Variable `FEATURE_FLAGS`
+
+- Type: Optional
+- Description: Used to control LobeChat's feature functionalities. Supports multiple feature flags, using `+` to add a feature and `-` to disable a feature. Separate multiple feature flags with a comma `,` and enclose the entire value in quotes `"` to avoid parsing errors.
+- Default: `-`
+- Example: `"-welcome_suggest"`
+
+All features are controlled by the `FEATURE_FLAGS` variable as the sole configuration variable.
+
+You can achieve various feature combinations using the above configuration syntax. All feature flags are Boolean values, enabled with `+` and disabled with `-`.
+
+<Callout type={'tip'}>
+  Attention: Unlike the `OPENAI_MODEL_LIST` variable, the `FEATURE_FLAGS` variable does not support
+  the `all` keyword. You need to manually control all feature flags (otherwise, they will adopt
+  their default values).
+</Callout>
+
+| Configuration Item        | Description                                     | Default Value |
+| ------------------------- | ----------------------------------------------- | ------------- |
+| `webrtc_sync`             | Enables WebRTC sync functionality.              | Disabled      |
+| `language_model_settings` | Enables language model settings.                | Enabled       |
+| `openai_api_key`          | Allows users to customize the OpenAI API Key.   | Enabled       |
+| `openai_proxy_url`        | Allows users to customize the OpenAI proxy URL. | Enabled       |
+| `create_session`          | Allows users to create sessions.                | Enabled       |
+| `edit_agent`              | Allows users to edit assistants.                | Enabled       |
+| `dalle`                   | Enables the DALL-E functionality.               | Enabled       |
+| `check_updates`           | Allows checking for updates.                    | Enabled       |
+| `welcome_suggest`         | Displays welcome suggestions.                   | Enabled       |
+| `market`                  | Enables the assistant market functionality.     | Enabled       |
+| `speech_to_text`          | Enables speech-to-text functionality.           | Enabled       |
+| `knowledge_base`          | Enables the knowledge base functionality.       | Enabled       |
+| `clerk_sign_up`           | Enables the Clerk SignUp functionality.         | Enabled       |
+
+You can always check the [featureFlags](https://github.com/lobehub/lobe-chat/blob/main/src/config/featureFlags/schema.ts) to get the latest list of feature flags.

docs/self-hosting/advanced/feature-flags.zh-CN.mdx

@@ -0,0 +1,47 @@
+---
+title: LobeChat 特性标志环境变量配置指南
+description: 了解如何使用环境变量自定义 LobeChat 的特性标志，包括控制否启用某个功能、或者根据需要对特定用户群体或环境启用或禁用功能。
+tags:
+  - LobeChat
+  - 环境变量
+  - 配置指南
+  - 特征标志
+---
+
+# 特性标志
+
+除了基础的环境变量配置外，LobeChat 还提供了一些特性标志（Feature Flags），用于控制是否全局启用某个功能，或者根据需要对特定用户群体或环境启用或禁用功能。
+
+## 特性标志环境变量 `FEATURE_FLAGS`
+
+- 类型：可选
+- 描述：用于控制 LobeChat 的特性功能，支持多个功能标志，使用 `+` 增加一个功能，使用 `-` 来关闭一个功能，多个功能标志之间使用英文逗号 `,` 隔开，最外层建议添加引号 `"` 以避免解析错误。
+- 默认值：`-`
+- 示例：`"-welcome_suggest"`
+
+所有的功能统一以特性标志 `FEATURE_FLAGS` 作为唯一的配置变量。
+
+你可以通过上述配置语法来实现更多的功能组合。所有的功能配置项都是布尔类型，通过 `+` 来启用，通过 `-` 来关闭。
+
+<Callout type={'tip'}>
+  注意：与 `OPENAI_MODEL_LIST` 变量不同，`FEATURE_FLAGS` 变量不支持 `all`
+  关键字，你需要手动控制所有的功能标志（否则它们会采用对应的默认值）。
+</Callout>
+
+| 配置项                    | 解释                             | 默认值 |
+| ------------------------- | -------------------------------- | ------ |
+| `webrtc_sync`             | 启用 WebRTC 同步功能。           | 关闭   |
+| `language_model_settings` | 启用语言模型设置。               | 开启   |
+| `openai_api_key`          | 允许用户自定义 OpenAI API Key。  | 开启   |
+| `openai_proxy_url`        | 允许用户自定义 OpenAI 代理 URL。 | 开启   |
+| `create_session`          | 允许用户创建会话。               | 开启   |
+| `edit_agent`              | 允许用户编辑助手。               | 开启   |
+| `dalle`                   | 启用 DALL-E 功能。               | 开启   |
+| `check_updates`           | 允许检查更新。                   | 开启   |
+| `welcome_suggest`         | 显示欢迎建议。                   | 开启   |
+| `market`                  | 启用助手市场功能。               | 开启   |
+| `speech_to_text`          | 启用语音转文本功能。             | 开启   |
+| `knowledge_base`          | 启用知识库功能。                 | 开启   |
+| `clerk_sign_up`          | 启用Clerk注册功能。                 | 开启   |
+
+你可以随时检查 [featureFlags](https://github.com/lobehub/lobe-chat/blob/main/src/config/featureFlags/schema.ts) 以获取最新的特性标志列表。

docs/self-hosting/advanced/knowledge-base.mdx

@@ -0,0 +1,53 @@
+# Knowledge Base / File Upload
+
+LobeChat supports file upload and knowledge base management. This feature relies on the following core technical components. Understanding these components will help you successfully deploy and maintain the knowledge base system.
+
+## Core Components
+
+### 1. PostgreSQL and PGVector
+
+PostgreSQL is a powerful open-source relational database system, and PGVector is its extension for vector operations.
+
+- **Purpose**: Store structured data and vector indexes
+- **Deployment Tip**: Use official Docker image for quick deployment
+
+Deployment script example:
+
+```
+docker run -p 5432:5432 -d --name pg -e POSTGRES_PASSWORD=mysecretpassword pgvector/pgvector:pg16
+```
+
+- **Note**: Ensure sufficient resources for vector operations
+
+### 2. S3-compatible Object Storage
+
+S3 (or S3-compatible storage services) is used for storing uploaded files.
+
+- **Purpose**: Store raw files
+- **Options**: AWS S3, MinIO, or other S3-compatible services
+- **Note**: Configure appropriate access permissions and security policies
+
+### 3. OpenAI Embedding
+
+OpenAI's Embedding service is used to convert text into vector representations.
+
+<Callout type={'info'}>
+
+LobeChat currently uses OpenAI's `text-embedding-3-small` model by default. Ensure your API Key has access to this model.
+
+</Callout>
+
+- **Purpose**: Generate vector representations for semantic search
+- **Notes**:
+  - Requires valid OpenAI API key
+  - Implement proper API call limits and error handling
+
+### 4. Unstructured.io (Optional)
+
+Unstructured.io is a powerful document processing tool.
+
+- **Purpose**: Process complex document formats, extract structured information
+- **Use Case**: Handle non-plain text formats like PDF, Word
+- **Note**: Evaluate processing needs based on document complexity
+
+By correctly configuring and integrating these core components, you can build a powerful and efficient knowledge base system for LobeChat. Each component plays a crucial role in the overall architecture, supporting advanced document management and intelligent retrieval functions.

docs/self-hosting/advanced/knowledge-base.zh-CN.mdx

@@ -0,0 +1,53 @@
+# 知识库 / 文件上传
+
+LobeChat 支持文件上传 / 知识库管理。该功能依赖于以下核心技术组件，了解这些组件将有助于你成功部署和维护知识库系统。
+
+## 核心组件
+
+### 1. PostgreSQL 与 PGVector
+
+PostgreSQL 是一个强大的开源关系型数据库系统，而 PGVector 是其扩展，为向量操作提供支持。
+
+- **用途**：存储结构化数据和向量索引
+- **部署建议**：使用官方 Docker 镜像可以快速部署 PostgreSQL 和 PGVector
+
+示例部署脚本：
+
+```
+docker run -p 5432:5432 -d --name pg -e POSTGRES_PASSWORD=mysecretpassword pgvector/pgvector:pg16
+```
+
+- **注意事项**：确保分配足够的资源以处理向量操作
+
+### 2. S3 兼容的对象存储
+
+S3（或兼容 S3 协议的存储服务）用于存储上传的文件。
+
+- **用途**：存储原始文件
+- **选项**：可以使用 AWS S3、MinIO 或其他兼容 S3 协议的存储服务
+- **注意事项**：配置适当的访问权限和安全策略
+
+### 3. OpenAI Embedding
+
+OpenAI 的嵌入（Embedding）服务用于将文本转化为向量表示。
+
+<Callout type={'info'}>
+
+LobeChat 当前默认使用 OpenAI `text-embedding-3-small` 模型，请确保你的 API Key 可以访问该模型。
+
+</Callout>
+
+- **用途**：生成文本的向量表示，用于语义搜索
+- **注意事项**：
+  - 需要有效的 OpenAI API 密钥
+  - 实施适当的 API 调用限制和错误处理机制
+
+### 4. Unstructured.io（可选）
+
+Unstructured.io 是一个强大的文档处理工具。
+
+- **用途**：处理复杂的文档格式，提取结构化信息
+- **应用场景**：处理 PDF、Word 等非纯文本格式的文档
+- **注意事项**：评估处理需求，根据文档复杂度决定是否部署
+
+通过正确配置和集成这些核心组件，您可以为 LobeChat 构建一个强大、高效的知识库系统。每个组件都在整体架构中扮演着关键角色，共同支持高级的文档管理和智能检索功能。

docs/self-hosting/advanced/model-list.mdx

@@ -12,10 +12,12 @@ tags:
 
 # Model List
 
-LobeChat supports customizing the model list during deployment. You can use `+` to add a model, `-` to hide a model, and use `model name=display name<extension configuration>` to customize the display name of a model, separated by English commas. The basic syntax is as follows:
+LobeChat supports customizing the model list during deployment. This configuration is done in the environment for each [model provider](/docs/self-hosting/environment-variables/model-provider). 
 
-```shell
-id=displayName < maxToken:vision:fc:file > ,model2,model3
+You can use `+` to add a model, `-` to hide a model, and use `model name=display name<extension configuration>` to customize the display name of a model, separated by English commas. The basic syntax is as follows:
+
+```text
+id=displayName<maxToken:vision:fc:file>,model2,model3
 ```
 
 For example: `+qwen-7b-chat,+glm-6b,-gpt-3.5-turbo,gpt-4-0125-preview=gpt-4-turbo`
@@ -36,7 +38,7 @@ Examples are as follows:
 
 - `chatglm-6b=ChatGLM 6B<4096>`: ChatGLM 6B, maximum context of 4k, no advanced capabilities;
 - `spark-v3.5=讯飞星火 v3.5<8192:fc>`: Xunfei Spark 3.5 model, maximum context of 8k, supports Function Call;
-- `gemini-pro-vision=Gemini Pro Vision<16000:vision>`: Google Vision model, maximum context of 16k, supports image recognition;
+- `gemini-1.5-flash-latest=Gemini 1.5 Flash<16000:vision>`: Google Vision model, maximum context of 16k, supports image recognition;
 - `gpt-4-all=ChatGPT Plus<128000:fc:vision:file>`, hacked version of ChatGPT Plus web, context of 128k, supports image recognition, Function Call, file upload.
 
 Currently supported extension capabilities are:

docs/self-hosting/advanced/model-list.zh-CN.mdx

@@ -8,12 +8,15 @@ tags:
   - 模型展示名
   - 模型能力
 ---
+
 # Model List
 
-LobeChat 支持在部署时自定义模型列表，可以使用 `+` 增加一个模型，使用 `-` 来隐藏一个模型，使用 `模型名=展示名<扩展配置>` 来自定义模型的展示名，用英文逗号隔开。通过 `<>` 来添加扩展配置。基本语法如下：
+LobeChat 支持在部署时自定义模型列表，详情请参考 [模型提供商](/zh/docs/self-hosting/environment-variables/model-provider) 。
 
-```shell
-id=displayName < maxToken:vision:fc:file > ,model2,model3
+你可以使用 `+` 增加一个模型，使用 `-` 来隐藏一个模型，使用 `模型名=展示名<扩展配置>` 来自定义模型的展示名，用英文逗号隔开。通过 `<>` 来添加扩展配置。基本语法如下：
+
+```text
+id=displayName<maxToken:vision:fc:file>,model2,model3
 ```
 
 例如： `+qwen-7b-chat,+glm-6b,-gpt-3.5-turbo,gpt-4-0125-preview=gpt-4-turbo`
@@ -34,7 +37,7 @@ id=displayName<maxToken:vision:fc:file>
 
 - `chatglm-6b=ChatGLM 6B<4096>`：ChatGLM 6B，最大上下文 4k，没有高阶能力；
 - `spark-v3.5=讯飞星火 v3.5<8192:fc>`：讯飞星火 3.5 模型，最大上下文 8k，支持 Function Call；
-- `gemini-pro-vision=Gemini Pro Vision<16000:vision>`：Google 视觉模型，最大上下文 16k，支持图像识别；
+- `gemini-1.5-flash-latest=Gemini 1.5 Flash<16000:vision>`：Google 视觉模型，最大上下文 16k，支持图像识别；
 - `gpt-4-all=ChatGPT Plus<128000:fc:vision:file>`，hack 的 ChatGPT Plus 网页版，上下 128k ，支持图像识别、Function Call、文件上传
 
 目前支持的扩展能力有：

docs/self-hosting/advanced/s3.mdx

@@ -0,0 +1,91 @@
+---
+title: Configuring S3 Storage Service for AI - LobeChat
+description: Learn how to configure S3 storage for LobeChat's multimodal AI conversations.
+tags:
+  - S3 Storage
+  - LobeChat
+  - AI Conversations
+  - Cloud Storage
+  - Image Upload
+---
+# Configuring S3 Storage Service
+
+LobeChat has supported multimodal AI conversations since [a long time ago](https://x.com/lobehub/status/1724289575672291782), which involves the function of uploading images to AI. In the client-side database solution, image files are stored as binary data directly in the browser's IndexedDB database. However, this solution is not feasible in the server-side database. Storing file-like data directly in Postgres would greatly waste database storage space and slow down computational performance.
+
+The best practice in this area is to use a file storage service (S3) to store image files. S3 is also the storage solution on which the file upload/knowledge base function depends.
+
+<Callout type={'info'}>
+In this documentation, S3 refers to a compatible S3 storage solution, which supports the Amazon S3 API for object storage systems. Common examples include Cloudflare R2, Alibaba Cloud OSS, and self-deployable Minio, all of which support the S3 compatible API.
+</Callout>
+
+## Core Environment Variables
+
+<Steps>
+  ### `S3_ACCESS_KEY_ID` and `S3_SECRET_ACCESS_KEY`
+
+  These are the two keys required by all S3 compatible storage services to access the S3 storage service, not detailed here.
+
+  ### `S3_ENDPOINT`
+
+  The request endpoint of the storage bucket. Note that this link should not contain the name of the storage bucket.
+
+  <Callout type={'warning'}>`S3_ENDPOINT` must remove the suffix path, otherwise the uploaded files will not be accessible</Callout>
+
+  For example, for Cloudflare:
+
+  ```shell
+  S3_ENDPOINT=https://0b33a03b5c993fd2f453379dc36558e5.r2.cloudflarestorage.com
+  ```
+
+  ### `S3_BUCKET` and `S3_REGION`
+
+  The name and region of the storage bucket. `S3_BUCKET` is required to specify the name of the storage bucket. `S3_REGION` is optional and is used to specify the region of the storage bucket. Generally, it does not need to be added, but some service providers may require configuration.
+
+  ### `S3_SET_ACL`
+
+  Whether to set the ACL to `public-read` when uploading files. This option is enabled by default. If the service provider does not support setting individual ACLs for files (i.e., all files inherit the ACL of the storage bucket), enabling this option may cause request errors. Set `S3_SET_ACL` to `0` to disable it.
+
+  ### `S3_PUBLIC_DOMAIN`
+
+  The public access domain of the storage bucket, used to access files in the storage bucket. This address needs to be **publicly readable**. The reason is that when OpenAI's gpt-4o and other vision models recognize images, OpenAI will try to download this image link on their servers. Therefore, this link must be publicly accessible. If it is a private link, OpenAI will not be able to access the image and thus will not be able to recognize the image content properly.
+
+  <Callout type={'warning'}>
+    Additionally, since this access domain is often a separate URL, it needs to be configured to allow cross-origin access to the site. Otherwise, cross-origin issues will occur in the browser.
+ 
+</Callout>
+
+  ### `S3_ENABLE_PATH_STYLE`
+
+  Whether to enable the `path-style` access mode of S3. This option is disabled by default. If your S3 service provider uses `path-style`, set `S3_ENABLE_PATH_STYLE` to `1` to enable it.
+
+  <Callout type={'info'}>
+
+  `path-style` and `virtual-host` are different ways to access buckets and objects in S3, with different URL structures and domain name resolutions.
+
+  Assuming the domain name of the S3 service provider is s3.example.net, the bucket is mybucket, and the object is config.env, the specific differences are as follows:
+  - path-style: `s3.example.net/mybucket/config.env`
+  - virtual-host: `mybucket.s3.example.net/config.env`
+
+ 
+</Callout>
+
+  <Callout type={'tip'}>
+
+  Common S3 cloud service providers often default to the `virtual-host` mode, while self-deployed services like Minio default to using `path-style`. Therefore, if you use Minio as the S3 service, you need to set `S3_ENABLE_PATH_STYLE=1`.
+
+ 
+</Callout>
+
+</Steps>
+
+## S3 Configuration Guide
+
+Currently, the S3 configuration tutorials included in the documentation are:
+
+<Cards>
+  <Card href={'/docs/self-hosting/advanced/s3/cloudflare-r2'} title={'Cloudflare R2'} />
+  <Card href={'/docs/self-hosting/advanced/s3/tencent-cloud'} title={'Tencent Cloud COS'} />
+</Cards>
+
+Click to view the tutorial for the corresponding platform. If the above tutorials do not include the S3 service provider you are using, feel free to submit a Pull Request to collectively improve the guide on S3 object storage.
+

docs/self-hosting/advanced/s3.zh-CN.mdx

@@ -0,0 +1,89 @@
+---
+title: 配置 S3 存储服务 - 多模态 AI 会话
+description: 了解如何配置 S3 存储服务以支持多模态 AI 会话和图片上传。
+tags:
+  - S3 存储
+  - 多模态 AI
+  - 图片上传
+  - 文件存储
+---
+
+# 配置 S3 存储服务
+
+LobeChat 在 [很早以前](https://x.com/lobehub/status/1724289575672291782) 就支持了多模态的 AI 会话，其中涉及到图片上传给大模型的功能。在客户端数据库方案中，图片文件直接以二进制数据存储在浏览器 IndexedDB 数据库，但在服务端数据库中这个方案并不可行。因为在 Postgres 中直接存储文件类二进制数据会大大浪费宝贵的数据库存储空间，并拖慢计算性能。
+
+这块最佳实践是使用文件存储服务（S3）来存储图片文件，同时 S3 也是文件上传/知识库功能所依赖的大容量静态文件存储方案。
+
+<Callout type={'info'}>
+  在本文档库中，S3 所指代的是指兼容 S3 存储方案，即支持 Amazon S3 API 的对象存储系统，常见例如
+  Cloudflare R2 、阿里云 OSS，可以自部署的 minio 等均支持 S3 兼容 API。
+</Callout>
+
+## 核心环境变量
+
+<Steps>
+  ### `S3_ACCESS_KEY_ID` 与 `S3_SECRET_ACCESS_KEY`
+
+所有 S3 兼容存储服务都需要的两个密钥，用于访问 S3 存储服务，不详细展开。
+
+### `S3_ENDPOINT`
+
+存储桶的请求端点， 注意此处链接不应该包含存储桶的名称。
+
+<Callout type={'warning'}>`S3_ENDPOINT`必须删除后缀路径，否则会无法访问所上传文件</Callout>
+
+例如 Cloudflare 为：
+
+```shell
+S3_ENDPOINT=https://0b33a03b5c993fd2f453379dc36558e5.r2.cloudflarestorage.com
+```
+
+### `S3_BUCKET` 和 `S3_REGION`
+
+存储桶的名称和区域，`S3_BUCKET` 是必须的，用于指定存储桶的名称。 `S3_REGION` 是可选的，用于指定存储桶的区域，一般来说不需要添加，但某些服务商则需要配置。
+
+### `S3_SET_ACL`
+
+是否在上传文件时设置 ACL 为 `public-read`。该选项默认启用。如果服务商不支持为文件设置单独的 ACL（即所有文件继承存储桶的 ACL），启用此选项可能会导致请求错误，将 `S3_SET_ACL` 设置为 `0` 即可关闭。
+
+### `S3_PUBLIC_DOMAIN`
+
+存储桶对外的访问域名，用于访问存储桶中的文件，这个地址需要**允许互联网可读**。 原因是 OpenAI 的 gpt-4o 等视觉模型识别图片时，OpenAI 会尝试在他们的服务器中下载这个图片链接，因此这个链接必须是公开可访问的，如果是私有的链接，OpenAI 将无法访问到这个图片，进而无法正常识别到图片内容。
+
+  <Callout type={'warning'}>
+    此外，由于该访问域名往往是一个独立的网址，因此需要配置允许站点的跨域访问，否则会在浏览器中出现跨域问题。
+
+</Callout>
+
+### `S3_ENABLE_PATH_STYLE`
+
+是否启用 S3 的 `path-style` 访问模式。此选项默认禁用。如果您的 S3 服务提供商使用 `path-style`，请将 `S3_ENABLE_PATH_STYLE` 设置为 `1` 以启用它。
+
+<Callout type={'info'}>
+
+`path-style` 和 `virtual-host` 在 S3 中是访问 bucket 和 object 的不同方式，URL 的结构和域名解析不太一样
+
+假设 S3 服务商的域名是 s3.example.net ，bucket为mybucket，object为config.env，具体区别如下：
+- path-style : `s3.example.net/mybucket/config.env`
+- virtual-host : `mybucket.s3.example.net/config.env`
+
+</Callout>
+
+<Callout type={'tip'}>
+
+常见的 S3 Cloud 服务商往往默认采用 `virtual-host` 模式，而自部署服务 minio 则默认使用的是 `path-style`。 因此如果你使用了 minio 作为 S3 服务，你需要设置 `S3_ENABLE_PATH_STYLE=1` 。
+
+</Callout>
+
+</Steps>
+
+## S3 配置指南
+
+目前文档中包含的 S3 配置指南如下：
+
+<Cards>
+  <Card href={'/zh/docs/self-hosting/advanced/s3/cloudflare-r2'} title={'Cloudflare R2'} />
+  <Card href={'/zh/docs/self-hosting/advanced/s3/tencent-cloud'} title={'腾讯云 COS'} />
+</Cards>
+
+点击即可查看对应 S3 服务的部署指南，如果上述指南中不包含你所使用的 S3 服务商，欢迎提交 PR ，将共同完善 S3 对象存储的指南。

docs/self-hosting/advanced/s3/cloudflare-r2.mdx

@@ -0,0 +1,146 @@
+---
+title: Configuring Cloudflare R2 Storage Service
+description: Step-by-step guide to configure Cloudflare R2 for S3 storage.
+tags:
+  - Cloudflare R2
+  - S3 Storage
+  - Configuration Guide
+---
+# Configuring Cloudflare R2 Storage Service
+
+We need to configure an S3 storage service in the server-side database to store files.
+
+## Configuration Steps
+
+<Steps>
+
+### Configure and Obtain S3 Bucket
+
+You need to go to your S3 service provider (such as AWS S3, Cloudflare R2, etc.) and create a new storage bucket. The following is an example using Cloudflare R2 to guide you through the creation process.
+
+The interface of Cloudflare R2 is shown below:
+
+<Image
+  alt={'Cloudflare R2 Storage Interface'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/41f7f677-0153-4a96-b849-5ac9b7ebefee'}
+></Image>
+
+When creating the bucket, specify its name and then click create.
+<Image
+  alt={'Create Bucket in R2'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/9c0d184c-3169-40fa-9115-011cfffb9ca7'}
+></Image>
+
+### Obtain Environment Variables for the Bucket
+
+In the settings of the R2 storage bucket, you can view the bucket configuration information:
+
+<Image
+  alt={'View relevant information of the bucket'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/2ceb210c-eca0-4439-ba27-8734d4ebb3ee'}
+></Image>
+
+The corresponding environment variables are:
+
+```shell
+# Bucket name
+S3_BUCKET=lobechat
+# Request endpoint of the bucket (note that the path in this link includes the bucket name, which must be removed, or use the link provided on the page for applying S3 API token)
+S3_ENDPOINT=https://0b33a03b5c993fd2f453379dc36558e5.r2.cloudflarestorage.com
+# Access domain of the bucket
+S3_PUBLIC_DOMAIN=https://s3-for-lobechat.your-domain.com
+```
+
+<Callout type={'warning'}>`S3_ENDPOINT` must have its path removed, otherwise uploaded files cannot be accessed.</Callout>
+
+### Obtain S3 Key Environment Variables
+
+You need to obtain the access key for S3 so that the LobeChat server has permission to access the S3 storage service. In R2, you can configure the access key in the account details:
+
+<Image
+  alt={'View access key of the bucket'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/be0c95c0-6693-44ee-a490-7e8dfaa8b34d'}
+></Image>
+
+Click the button in the upper right corner to create an API token and enter the create API Token page.
+
+<Image
+  alt={'Create corresponding API token'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/7b0ea46c-5157-40a8-888f-f47664a4884f'}
+></Image>
+
+Since our server-side database needs to read and write to the S3 storage service, the permission needs to be set to `Object Read and Write`, then click create.
+
+<Image
+  alt={'Configure API token permissions'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/d6f5a918-7b50-4d6e-83a6-3894ab930ddf'}
+></Image>
+
+After creation, you can see the corresponding S3 API token.
+
+<Image
+  alt={'Copy API token'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/763b18f9-2b5f-44bb-a479-9b56d46f7397'}
+></Image>
+
+The corresponding environment variables are:
+
+```shell
+S3_ACCESS_KEY_ID=9998d6757e276cf9f1edbd325b7083a6
+S3_SECRET_ACCESS_KEY=55af75d8eb6b99f189f6a35f855336ea62cd9c4751a5cf4337c53c1d3f497ac2
+```
+
+### Configure Cross-Origin Resource Sharing (CORS)
+
+Since S3 storage services are often on a separate domain, cross-origin access needs to be configured.
+
+In R2, you can find the CORS configuration in the settings of the storage bucket:
+
+<Image
+  alt={'Cross-Origin Settings in Cloudflare R2'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/ab008be7-26b2-4b78-8bd9-24301bf34d23'}
+></Image>
+
+Add a CORS rule to allow requests from your domain (in the previous section, it is `https://your-project.vercel.app`):
+
+<Image
+  alt={'Configure allowed site domain'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/dfcc2cb3-2958-4498-a8a4-51bec584fe7d'}
+></Image>
+
+Example configuration is as follows:
+
+```json
+[
+  {
+    "AllowedOrigins": ["https://your-project.vercel.app"],
+    "AllowedMethods": ["GET", "PUT", "HEAD", "POST", "DELETE"],
+    "AllowedHeaders": ["*"]
+  }
+]
+```
+
+After configuration, click save.
+
+</Steps>
+
+## Overview of Environment Variables
+
+<Callout type={'warning'}>The `https://` in the URL is essential and must be included to maintain the integrity of the URL.</Callout>
+
+```shell
+# S3 Keys
+S3_ACCESS_KEY_ID=9998d6757e276cf9f1edbd325b7083a6
+S3_SECRET_ACCESS_KEY=55af75d8eb6b99f189f6a35f855336ea62cd9c4751a5cf4337c53c1d3f497ac2
+
+# Bucket Name
+S3_BUCKET=lobechat
+# Bucket Request Endpoint
+S3_ENDPOINT=https://0b33a03b5c993fd2f453379dc36558e5.r2.cloudflarestorage.com
+# Public Access Domain for the Bucket
+S3_PUBLIC_DOMAIN=https://s3-dev.your-domain.com
+
+# Bucket Region, such as us-west-1. Generally not required, but some service providers may need it.
+# S3_REGION=us-west-1
+```
+

docs/self-hosting/advanced/s3/cloudflare-r2.zh-CN.mdx

@@ -0,0 +1,148 @@
+---
+title: 配置 Cloudflare R2 存储服务
+description: 详细步骤配置 Cloudflare R2 存储服务，确保文件存储顺利进行。
+tags:
+  - Cloudflare R2
+  - S3 存储
+  - 文件存储
+  - 环境变量
+---
+
+# 配置 Cloudflare R2 存储服务
+
+在服务端数据库中我们需要配置 S3 存储服务来存储文件。
+
+## 配置步骤
+
+<Steps>
+
+### 配置并获取 S3 存储桶
+
+你需要前往你的 S3 服务提供商（如 AWS S3、Cloudflare R2 等）并创建一个新的存储桶（Bucket）。接下来以 Cloudflare R2 为例，介绍创建流程。
+
+下图是 Cloudflare R2 的界面：
+
+<Image
+  alt={'Cloudflare R2 存储界面'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/41f7f677-0153-4a96-b849-5ac9b7ebefee'}
+/>
+
+创建存储桶时将指定其名称，然后点击创建。
+
+<Image
+  alt={'R2 创建存储桶'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/9c0d184c-3169-40fa-9115-011cfffb9ca7'}
+/>
+
+### 获取存储桶相关环境变量
+
+在 R2 存储桶的设置中，可以看到桶配置的信息：
+
+<Image
+  alt={'查看存储桶的相关信息'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/2ceb210c-eca0-4439-ba27-8734d4ebb3ee'}
+/>
+
+其对应的环境变量为：
+
+```shell
+# 存储桶的名称
+S3_BUCKET=lobechat
+# 存储桶的请求端点(注意此处链接的路径带存储桶名称，必须删除该路径，或使用申请 S3 API token 页面所提供的链接)
+S3_ENDPOINT=https://0b33a03b5c993fd2f453379dc36558e5.r2.cloudflarestorage.com
+# 存储桶对外的访问域名
+S3_PUBLIC_DOMAIN=https://s3-for-lobechat.your-domain.com
+```
+
+<Callout type={'warning'}>`S3_ENDPOINT`必须删除其路径，否则会无法访问所上传文件</Callout>
+
+### 获取 S3 密钥环境变量
+
+你需要获取 S3 的访问密钥，以便 LobeChat 的服务端有权限访问 S3 存储服务。在 R2 中，你可以在账户详情中配置访问密钥：
+
+<Image
+  alt={'查看存储桶的访问秘钥'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/be0c95c0-6693-44ee-a490-7e8dfaa8b34d'}
+/>
+
+点击右上角按钮创建 API token，进入创建 API Token 页面
+
+<Image
+  alt={'创建对应 API token'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/7b0ea46c-5157-40a8-888f-f47664a4884f'}
+/>
+
+鉴于我们的服务端数据库需要读写 S3 存储服务，因此权限需要选择`对象读与写`，然后点击创建。
+
+<Image
+  alt={'配置 API token 权限'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/d6f5a918-7b50-4d6e-83a6-3894ab930ddf'}
+/>
+
+创建完成后，就可以看到对应的 S3 API token
+
+<Image
+  alt={'复制 API token'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/763b18f9-2b5f-44bb-a479-9b56d46f7397'}
+/>
+
+其对应的环境变量为：
+
+```shell
+S3_ACCESS_KEY_ID=9998d6757e276cf9f1edbd325b7083a6
+S3_SECRET_ACCESS_KEY=55af75d8eb6b99f189f6a35f855336ea62cd9c4751a5cf4337c53c1d3f497ac2
+```
+
+### 配置跨域
+
+由于 S3 存储服务往往是一个独立的网址，因此需要配置跨域访问。
+
+在 R2 中，你可以在存储桶的设置中找到跨域配置：
+
+<Image
+  alt={'Cloudflare R2 的跨域设置'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/ab008be7-26b2-4b78-8bd9-24301bf34d23'}
+/>
+
+添加跨域规则，允许你的域名（在上文是 `https://your-project.vercel.app`）来源的请求：
+
+<Image
+  alt={'配置允许你的站点域名'}
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/dfcc2cb3-2958-4498-a8a4-51bec584fe7d'}
+/>
+
+示例配置如下：
+
+```json
+[
+  {
+    "AllowedOrigins": ["https://your-project.vercel.app"],
+    "AllowedMethods": ["GET", "PUT", "HEAD", "POST", "DELETE"],
+    "AllowedHeaders": ["*"]
+  }
+]
+```
+
+配置后点击保存即可。
+
+</Steps>
+
+## 环境变量一览
+
+<Callout type={'warning'}>URL的`https://`不可缺失，须保持URL的完整性</Callout>
+
+```shell
+# S3 秘钥
+S3_ACCESS_KEY_ID=9998d6757e276cf9f1edbd325b7083a6
+S3_SECRET_ACCESS_KEY=55af75d8eb6b99f189f6a35f855336ea62cd9c4751a5cf4337c53c1d3f497ac2
+
+# 存储桶的名称
+S3_BUCKET=lobechat
+# 存储桶的请求端点
+S3_ENDPOINT=https://0b33a03b5c993fd2f453379dc36558e5.r2.cloudflarestorage.com
+# 存储桶对外的访问域名
+S3_PUBLIC_DOMAIN=https://s3-dev.your-domain.com
+
+# 桶的区域，如 us-west-1，一般来说不需要添加，但某些服务商则需要配置
+# S3_REGION=us-west-1
+```

docs/self-hosting/advanced/s3/tencent-cloud.mdx

@@ -0,0 +1,66 @@
+---
+title: Configuring Tencent Cloud COS Storage Service
+description: >-
+  Detailed steps to configure Tencent Cloud COS storage service for smooth file
+  storage.
+tags:
+  - Tencent Cloud COS
+  - S3 Storage
+  - File Storage
+  - Environment Variables
+---
+
+# Configuring Tencent Cloud COS Storage Service
+
+We need to configure S3 storage service for file storage in the server-side database.
+
+## Configuration Steps
+
+<Steps>
+  ### Configure and Obtain S3 Bucket
+
+  Create a new bucket on [Tencent Cloud COS](https://console.cloud.tencent.com/cos/bucket):
+
+  <Image alt={'Tencent Cloud COS Storage Interface'} src={'https://github.com/user-attachments/assets/d3626294-74ba-4944-9a63-052e6cf719ab'} />
+
+  Name the bucket (e.g., 'lobe'). Choose 'Public Read, Private Write', select any region, and keep other settings default.
+
+  <Image alt={'COS Create Bucket'} src={'https://github.com/user-attachments/assets/7257eb0e-4e2c-4db2-981d-354598e2c60f'} />
+
+  ### Get Bucket-related Environment Variables
+
+  View bucket information in COS bucket overview:
+
+  <Image alt={'View Bucket Information'} src={'https://github.com/user-attachments/assets/d7d65e32-679d-4e50-a933-28cf5dde1330'} />
+
+  Corresponding environment variables:
+
+  ```shell
+  S3_BUCKET=lobe-130xxxxxx2
+  S3_ENDPOINT=https://cos.ap-chengdu.myqcloud.com
+  S3_REGION=ap-chengdu
+  S3_PUBLIC_DOMAIN=https://lobe-1251234567.cos.ap-chengdu.myqcloud.com
+  ```
+
+  <Callout type={'warning'}>
+    Note: `S3_ENDPOINT` should be `https://cos.ap-chengdu.myqcloud.com`, not `https://lobe-130xxxxxx2.cos.ap-chengdu.myqcloud.com`
+
+    Include `https://` in the URL
+ 
+</Callout>
+
+  ### Configure CORS
+
+  Add the following in 'Security Management - CORS Settings':
+
+  <Image alt={'Configure CORS'} src={'https://github.com/user-attachments/assets/35164b25-c964-42ce-9cb0-32f6ebe1d07c'} />
+
+  ### Get S3 Keys
+
+  Create a new SecretId and SecretKey at [Tencent Cloud API Key Management](https://console.cloud.tencent.com/cam/capi). Use as `S3_ACCESS_KEY_ID` and `S3_SECRET_ACCESS_KEY`.
+</Steps>
+
+### Additional Notes
+
+- Consider setting up CDN acceleration for improved access speed and reduced costs.
+- Use role management when creating API keys for enhanced security.

docs/self-hosting/advanced/s3/tencent-cloud.zh-CN.mdx

@@ -0,0 +1,82 @@
+---
+title: 配置腾讯云 COS 存储服务
+description: 详细步骤配置腾讯云 COS 存储服务，确保文件存储顺利进行。
+tags:
+  - 腾讯云 COS
+  - S3 存储
+  - 文件存储
+  - 环境变量
+---
+
+# 配置腾讯云 COS 存储服务
+
+在服务端数据库中我们需要配置 S3 存储服务来存储文件。
+
+## 配置步骤
+
+<Steps>
+
+### 配置并获取 S3 存储桶
+
+你需要首先前往 [腾讯云 COS](https://console.cloud.tencent.com/cos/bucket) 并创建一个新的存储桶（Bucket）：
+
+<Image
+  alt={'腾讯云 COS 存储界面'}
+  src={'https://github.com/user-attachments/assets/d3626294-74ba-4944-9a63-052e6cf719ab'}
+/>
+
+创建存储桶时将指定其名称，下文以 `lobe` 为例。选择 `公有读私有写`，地域随意，其余配置一概默认即可，然后点击创建。
+
+<Image
+  alt={'COS 创建存储桶'}
+  src={'https://github.com/user-attachments/assets/7257eb0e-4e2c-4db2-981d-354598e2c60f'}
+/>
+
+### 获取存储桶相关环境变量
+
+在 COS 存储桶的概览设置中，可以看到桶配置的信息：
+
+<Image
+  alt={'查看存储桶的相关信息'}
+  src={'https://github.com/user-attachments/assets/d7d65e32-679d-4e50-a933-28cf5dde1330'}
+/>
+
+其对应的环境变量为：
+
+```shell
+# 存储桶的名称
+S3_BUCKET=lobe-130xxxxxx2
+# 存储桶的请求端点，注意没有前面的桶名
+S3_ENDPOINT=https://cos.ap-chengdu.myqcloud.com
+# 桶的区域
+S3_REGION=ap-chengdu
+# 存储桶对外的访问域名
+S3_PUBLIC_DOMAIN=https://lobe-1251234567.cos.ap-chengdu.myqcloud.com
+```
+
+<Callout type={'warning'}>
+请注意，`S3_ENDPOINT` 的值为 `https://cos.ap-chengdu.myqcloud.com`，而不是 `https://lobe-130xxxxxx2.cos.ap-chengdu.myqcloud.com`
+
+且此处 URL 的 `https://` 不可缺失，须保持 URL 的完整性
+
+</Callout>
+
+### 配置跨域
+
+在左侧 `安全管理 - 跨域访问 CORS 设置` 中，添加以下配置并保存：
+
+<Image
+  alt={'配置跨域'}
+  src={'https://github.com/user-attachments/assets/35164b25-c964-42ce-9cb0-32f6ebe1d07c'}
+/>
+
+### 获取 S3 秘钥
+
+前往 [腾讯云 API 密钥管理](https://console.cloud.tencent.com/cam/capi) 创建一个新的 SecretId 和 SecretKey，填写为 `S3_ACCESS_KEY_ID` 和 `S3_SECRET_ACCESS_KEY` 即可。
+
+</Steps>
+
+### 附加说明
+
+- 对于对象存储，你可以选择设置 CDN 加速，以提高不同区域的访问速度，提高并发的同时减少下行费用。
+- 创建 API 密钥时，推荐使用角色管理，以提高安全性。

docs/self-hosting/advanced/settings-url-share.mdx

@@ -1,9 +1,25 @@
-# Share settings via URL 
+---
+title: Share Settings via URL - Import and Export Configuration Settings
+description: >-
+  Learn how to import and export configuration settings for LobeChat via URL.
+  Understand the supported settings, URL format, and parameter schema for
+  keyVaults and languageModel.
+tags:
+  - Share Settings
+  - URL Import
+  - URL Export
+  - Configuration Settings
+  - LobeChat
+  - Parameter Schema
+---
+
+# Share settings via URL
 
 LobeChat support import settings from external URL to quickly set up LobeChat configuration.
 
 The currently supported settings are:
 
+- `keyVaults`: provider api key and baseURL settings
 - `languageModel`: Language model settings
 
 ## Import from URL
@@ -12,18 +28,18 @@ Use the following URL format to import settings parameters from an external URL:
 
 ```plaintext
 https://lobehub.com/?settings=<settings object in JSON format>
-https://lobehub.com/?settings={"languageModel":{"openai":{"apiKey":"user-key","endpoint":"https://lobehub.com/v1"}}}
+https://lobehub.com/?settings={"keyVaults":{"openai":{"apiKey":"user-key","baseURL":"https://your-proxy.com/v1"}}}
 ```
 
 Example of settings in JSON format:
 
 ```json
 {
-    "languageModel": {
-        "openai": {
-            "apiKey": "user-key"
-        }
+  "keyVaults": {
+    "openai": {
+      "apiKey": "user-key"
     }
+  }
 }
 ```
 
@@ -32,69 +48,100 @@ Example of settings in JSON format:
 ```ts
 // Generate settings to export to URL
 const settings = {
-    languageModel: {
+  keyVaults: {
     openai: {
-        apiKey: 'user-key',
-        endpoint: 'https://lobehub.com/v1'
+      apiKey: 'user-key',
+      baseURL: 'https://your-proxy.com/v1',
     },
-}};
+  },
+};
 // Convert settings to a JSON formatted string
 const url = `/?settings=${JSON.stringify(settings)}`;
-console.log(url); 
-// /?settings={"languageModel":{"openai":{"apiKey":"user-key","endpoint":"https://lobehub.com/v1"}}}
+console.log(url);
+// /?settings={"keyVaults":{"openai":{"apiKey":"user-key","baseURL":"https://your-proxy.com/v1"}}}
 ```
 
 <Callout type={'warning'}>
-    LobeChat does not verify the correctness of the settings parameters in the URL, nor provide encryption or decryption methods. Please use with caution.
+  LobeChat does not verify the correctness of the settings parameters in the URL, nor provide
+  encryption or decryption methods. Please use with caution.
 </Callout>
 
 ## Parameter schema
 
-### languageModel
+### keyVaults
 
 - Property name and type
 
-| Property name | Type                           |
-|---------------|--------------------------------|
-| anthropic     | GeneralModelProviderConfig      |
-| azure         | AzureOpenAIConfig               |
-| bedrock       | AWSBedrockConfig                |
-| google        | GeneralModelProviderConfig      |
-| groq          | GeneralModelProviderConfig      |
-| minimax       | GeneralModelProviderConfig      |
-| mistral       | GeneralModelProviderConfig      |
-| moonshot      | GeneralModelProviderConfig      |
-| ollama        | GeneralModelProviderConfig      |
-| openai        | GeneralModelProviderConfig      |
-| openrouter    | GeneralModelProviderConfig      |
-| perplexity    | GeneralModelProviderConfig      |
-| togetherai    | GeneralModelProviderConfig      |
-| zeroone       | GeneralModelProviderConfig      |
-| zhipu         | GeneralModelProviderConfig      |
+| Property name | Type                       |
+| ------------- | -------------------------- |
+| anthropic     | `OpenAICompatibleKeyVault` |
+| azure         | `AzureOpenAIKeyVault`      |
+| bedrock       | `AWSBedrockKeyVault`       |
+| google        | `OpenAICompatibleKeyVault` |
+| groq          | `OpenAICompatibleKeyVault` |
+| minimax       | `OpenAICompatibleKeyVault` |
+| mistral       | `OpenAICompatibleKeyVault` |
+| moonshot      | `OpenAICompatibleKeyVault` |
+| ollama        | `OpenAICompatibleKeyVault` |
+| openai        | `OpenAICompatibleKeyVault` |
+| openrouter    | `OpenAICompatibleKeyVault` |
+| perplexity    | `OpenAICompatibleKeyVault` |
+| togetherai    | `OpenAICompatibleKeyVault` |
+| zeroone       | `OpenAICompatibleKeyVault` |
+| zhipu         | `OpenAICompatibleKeyVault` |
 
-- Type `GeneralModelProviderConfig`
+- Type `OpenAICompatibleKeyVault`
 
-| Property name | Type                           | Description                                                                 |
-|-----------------------|--------------------------|-----------------------------------------------------------------------------|
-| apiKey                | string                   | The API key for the model provider.                                          |
-| autoFetchModelLists   | boolean                  | Whether to automatically fetch model lists.                                  |
-| enabled               | boolean                  | Whether the model provider is enabled.                                       |
-| enabledModels         | string[] | null         | The IDs of the enabled models.                                               |
-| endpoint              | string                   | The endpoint for the model provider.                                         |
-| fetchOnClient         | boolean                  | Whether to fetch on the client.                                              |
+| Property name | Type   | Description                          |
+| ------------- | ------ | ------------------------------------ |
+| apiKey        | string | The API key for the model provider.  |
+| baseURL       | string | The endpoint for the model provider. |
 
-- Type `AzureOpenAIConfig`
-> Inherits the fields from `GeneralModelProviderConfig`
+- Type `AzureOpenAIKeyVault`
 
-| Property name | Type                           | Description                                                                 |
-|-----------------------|--------------------------|-----------------------------------------------------------------------------|
-| apiVersion                | string                   | The API version for Azure OpenAI.                                          |
+| Property name | Type   | Description                          |
+| ------------- | ------ | ------------------------------------ |
+| apiVersion    | string | The API version for Azure OpenAI.    |
+| apiKey        | string | The API key for the model provider.  |
+| endpoint      | string | The endpoint for the model provider. |
 
-- Type `AWSBedrockConfig`
-> Inherits all fields from `GeneralModelProviderConfig` except `apiKey, endpoint`
+- Type `AWSBedrockKeyVault`
 
-| Property name | Type                           | Description                                                                 |
-| accessKeyId           | string                   | The access key ID for AWS Bedrock.                                           |
-| region                | string                   | The region for AWS Bedrock.                                                  |
-| secretAccessKey       | string                   | The secret access key for AWS Bedrock.                                       |
+| Property name   | Type   | Description                            |
+| --------------- | ------ | -------------------------------------- |
+| accessKeyId     | string | The access key ID for AWS Bedrock.     |
+| region          | string | The region for AWS Bedrock.            |
+| secretAccessKey | string | The secret access key for AWS Bedrock. |
 
+### languageModel
+
+```ts
+export type UserModelProviderConfig = Record<string, ProviderConfig>;
+```
+
+| Property name | Type             |
+| ------------- | ---------------- |
+| anthropic     | `ProviderConfig` |
+| azure         | `ProviderConfig` |
+| bedrock       | `ProviderConfig` |
+| google        | `ProviderConfig` |
+| groq          | `ProviderConfig` |
+| minimax       | `ProviderConfig` |
+| mistral       | `ProviderConfig` |
+| moonshot      | `ProviderConfig` |
+| ollama        | `ProviderConfig` |
+| openai        | `ProviderConfig` |
+| openrouter    | `ProviderConfig` |
+| perplexity    | `ProviderConfig` |
+| togetherai    | `ProviderConfig` |
+| zeroone       | `ProviderConfig` |
+| zhipu         | `ProviderConfig` |
+
+- Type `ProviderConfig`
+
+| Property name       | Type     | Description                                 |
+| ------------------- | -------- | ------------------------------------------- | ------------------------------ |
+| autoFetchModelLists | boolean  | Whether to automatically fetch model lists. |
+| enabled             | boolean  | Whether the model provider is enabled.      |
+| enabledModels       | string[] | null                                        | The IDs of the enabled models. |
+| fetchOnClient       | boolean  | Whether to fetch on the client.             |

docs/self-hosting/advanced/settings-url-share.zh-CN.mdx

@@ -1,10 +1,25 @@
+---
+title: URL 分享设置参数 - LobeChat 配置快速设置
+description: 了解如何从外部 URL 导入和导出 LobeChat 的设置参数，包括 keyVaults 和 languageModel，以及参数格式和类型。
+tags:
+  - URL 分享
+  - 设置参数
+  - LobeChat
+  - keyVaults
+  - languageModel
+  - JSON 格式
+  - URL 导入
+  - URL 导出
+---
+
 # URL 分享设置参数
 
 LobeChat 支持从外部 URL 导入设置参数，以便于快速设置 LobeChat 的配置。
 
 目前支持的设置项有：
 
-- `languageModel`：语言模型设置 
+- `keyVaults`: 模型供应商相关秘钥设置
+- `languageModel`：语言模型设置
 
 ## 从 URL 中导入
 
@@ -12,18 +27,18 @@ LobeChat 支持从外部 URL 导入设置参数，以便于快速设置 LobeChat
 
 ```plaintext
 https://lobehub.com/?settings=<JSON格式的设置对象>
-https://lobehub.com/?settings={"languageModel":{"openai":{"apiKey":"user-key","endpoint":"https://lobehub.com/v1"}}}
+https://lobehub.com/?settings={"keyVaults":{"openai":{"apiKey":"user-key","baseURL":"https://your-proxy.com/v1"}}}
 ```
 
 JSON格式的设置示例：
 
 ```json
 {
-    "languageModel": {
-        "openai": {
-            "apiKey": "user-key"
-        }
+  "keyVaults": {
+    "openai": {
+      "apiKey": "user-key"
     }
+  }
 }
 ```
 
@@ -32,69 +47,99 @@ JSON格式的设置示例：
 ```ts
 // 生成要导出到 URL 的设置
 const settings = {
-    languageModel: {
+  keyVaults: {
     openai: {
-        apiKey: 'user-key',
-        endpoint: 'https://lobehub.com/v1'
+      apiKey: 'user-key',
+      baseURL: 'https://your-proxy.com/v1',
     },
-}};
-// 将设置转为 JSON 格式的字符串
+  },
+};
+// Convert settings to a JSON formatted string
 const url = `/?settings=${JSON.stringify(settings)}`;
-console.log(url); 
-// /?settings={"languageModel":{"openai":{"apiKey":"user-key","endpoint":"https://lobehub.com/v1"}}}
+console.log(url);
+// /?settings={"keyVaults":{"openai":{"apiKey":"user-key","baseURL":"https://your-proxy.com/v1"}}}
 ```
 
 <Callout type={'warning'}>
-    LobeChat 不对 URL 中的设置参数进行正确性校验，也不提供加密、解密方法，请谨慎使用。
+  LobeChat 不对 URL 中的设置参数进行正确性校验，也不提供 URL 的加密、解密方法，请谨慎使用。
 </Callout>
 
 ## 参数格式
 
-### languageModel
+### keyVaults
 
 - 参数及其类型
 
-| 参数名称 | 类型                           |
-|---------------|--------------------------------|
-| anthropic     | GeneralModelProviderConfig      |
-| azure         | AzureOpenAIConfig               |
-| bedrock       | AWSBedrockConfig                |
-| google        | GeneralModelProviderConfig      |
-| groq          | GeneralModelProviderConfig      |
-| minimax       | GeneralModelProviderConfig      |
-| mistral       | GeneralModelProviderConfig      |
-| moonshot      | GeneralModelProviderConfig      |
-| ollama        | GeneralModelProviderConfig      |
-| openai        | GeneralModelProviderConfig      |
-| openrouter    | GeneralModelProviderConfig      |
-| perplexity    | GeneralModelProviderConfig      |
-| togetherai    | GeneralModelProviderConfig      |
-| zeroone       | GeneralModelProviderConfig      |
-| zhipu         | GeneralModelProviderConfig      |
+| 参数名称   | 类型                       |
+| ---------- | -------------------------- |
+| anthropic  | `OpenAICompatibleKeyVault` |
+| azure      | `AzureOpenAIKeyVault`      |
+| bedrock    | `AWSBedrockKeyVault`       |
+| google     | `OpenAICompatibleKeyVault` |
+| groq       | `OpenAICompatibleKeyVault` |
+| minimax    | `OpenAICompatibleKeyVault` |
+| mistral    | `OpenAICompatibleKeyVault` |
+| moonshot   | `OpenAICompatibleKeyVault` |
+| ollama     | `OpenAICompatibleKeyVault` |
+| openai     | `OpenAICompatibleKeyVault` |
+| openrouter | `OpenAICompatibleKeyVault` |
+| perplexity | `OpenAICompatibleKeyVault` |
+| togetherai | `OpenAICompatibleKeyVault` |
+| zeroone    | `OpenAICompatibleKeyVault` |
+| zhipu      | `OpenAICompatibleKeyVault` |
 
-- 类型 `GeneralModelProviderConfig`
+- Type `OpenAICompatibleKeyVault`
 
-| 参数               | TS 类型                       | 描述                                                                 |
-|-----------------------|--------------------------|-----------------------------------------------------------------------------|
-| apiKey | string | 模型的 API 密钥。 |
-| autoFetchModelLists | boolean | 是否自动获取模型列表。 |
-| enabled | boolean | 是否启用该模型。 |
-| enabledModels | string[] | 启用的模型的 ID。 |
-| endpoint | string | 模型API端点。 |
-| fetchOnClient | boolean | 是否在客户端发起请求，默认在服务端发起请求。 |
+| 参数    | 类型   | 描述              |
+| ------- | ------ | ----------------- |
+| apiKey  | string | 模型的 API 密钥。 |
+| baseURL | string | 模型API端点。     |
 
-- 类型 `AzureOpenAIConfig`
-> 继承 `GeneralModelProviderConfig` 中的字段
+- Type `AzureOpenAIKeyVault`
 
-| 参数               | TS 类型                       | 描述                                                                 |
-|-----------------------|--------------------------|-----------------------------------------------------------------------------|
+| 参数       | 类型   | 描述                       |
+| ---------- | ------ | -------------------------- |
 | apiVersion | string | Azure OpenAI 的 API 版本。 |
+| apiKey     | string | 模型的 API 密钥。          |
+| baseURL    | string | 模型API端点。              |
 
-- 类型 `AWSBedrockConfig`
-> 继承 `GeneralModelProviderConfig` 中除 `apiKey, endpoint` 外的所有字段
+- Type `AWSBedrockKeyVault`
 
-| 参数               | TS 类型                       | 描述                                                                 |
-|-----------------------|--------------------------|-----------------------------------------------------------------------------|
-| accessKeyId | string | AWS Bedrock 的访问密钥 ID。 |
-| region | string | AWS Bedrock 的区域。 |
-| secretAccessKey | string | AWS Bedrock 的访问密钥。 |
+| 参数            | 类型   | 描述                        |
+| --------------- | ------ | --------------------------- |
+| accessKeyId     | string | AWS Bedrock 的访问密钥 ID。 |
+| region          | string | AWS Bedrock 的区域。        |
+| secretAccessKey | string | AWS Bedrock 的访问密钥。    |
+
+### languageModel
+
+```ts
+export type UserModelProviderConfig = Record<string, ProviderConfig>;
+```
+
+| 参数名称   | 类型             |
+| ---------- | ---------------- |
+| anthropic  | `ProviderConfig` |
+| azure      | `ProviderConfig` |
+| bedrock    | `ProviderConfig` |
+| google     | `ProviderConfig` |
+| groq       | `ProviderConfig` |
+| minimax    | `ProviderConfig` |
+| mistral    | `ProviderConfig` |
+| moonshot   | `ProviderConfig` |
+| ollama     | `ProviderConfig` |
+| openai     | `ProviderConfig` |
+| openrouter | `ProviderConfig` |
+| perplexity | `ProviderConfig` |
+| togetherai | `ProviderConfig` |
+| zeroone    | `ProviderConfig` |
+| zhipu      | `ProviderConfig` |
+
+- 类型 `ProviderConfig`
+
+| 参数                | TS 类型  | 描述                                         |
+| ------------------- | -------- | -------------------------------------------- |
+| autoFetchModelLists | boolean  | 是否自动获取模型列表。                       |
+| enabled             | boolean  | 是否启用该模型。                             |
+| enabledModels       | string[] | 启用的模型的 ID。                            |
+| fetchOnClient       | boolean  | 是否在客户端发起请求，默认在服务端发起请求。 |

docs/self-hosting/advanced/upstream-sync.mdx

@@ -40,6 +40,18 @@ After forking the project, due to Github's limitations, you need to manually ena
   src="https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/266985177-7677b4ce-c348-4145-9f60-829d448d5be6.png"
 />
 
+If you encounter a sync failure, you need to manually click "Update Branch" once.
+
+<Image
+  alt="GitHub Action Sync Failure"
+  src="https://github.com/user-attachments/assets/9baacac6-5af4-460b-862d-682b76c18459"
+/>
+
+<Image
+  alt="Manually Sync 'Update Branch'"
+  src="https://github.com/user-attachments/assets/d524c20d-306a-45bc-971b-96920b87fab4"
+/>
+
 ## `B` Docker Deployment
 
 Upgrading the Docker deployment version is very simple, you just need to redeploy the latest LobeChat image. Here are the commands required to perform these steps:
@@ -126,20 +138,20 @@ if [ $? -eq 0 ]; then
   exit 0
 fi
 
-echo "Detected Lobe-Chat update"
+echo "Detected lobe-chat update"
 
 # Remove the old container
-echo "Removed: $(docker rm -f Lobe-Chat)"
+echo "Removed: $(docker rm -f lobe-chat)"
 
-# Run the new container
-echo "Started: $(docker run -d --network=host --env-file /path/to/lobe.env --name=Lobe-Chat --restart=always lobehub/lobe-chat)"
+# Run the new container(Please change the path to the env file)
+echo "Started: $(docker run -d --network=host --env-file /path/to/lobe.env --name=lobe-chat --restart=always lobehub/lobe-chat)"
 
 # Print the update time and version
 echo "Update time: $(date)"
 echo "Version: $(docker inspect lobehub/lobe-chat:latest | grep 'org.opencontainers.image.version' | awk -F'"' '{print $4}')"
 
 # Clean up unused images
-docker images | grep 'lobehub/lobe-chat' | grep -v 'latest' | awk '{print $3}' | xargs -r docker rmi > /dev/null 2>&1
+docker images | grep 'lobehub/lobe-chat' | grep -v 'lobehub/lobe-chat-database' | grep -v 'latest' | awk '{print $3}' | xargs -r docker rmi > /dev/null 2>&1
 echo "Removed old images."
 ```
 

docs/self-hosting/advanced/upstream-sync.zh-CN.mdx

@@ -35,6 +35,18 @@ tags:
   src="https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/266985177-7677b4ce-c348-4145-9f60-829d448d5be6.png"
 />
 
+如果你遇到了同步失败的情况，你需要手动重新点一次 「Update Branch」。
+
+<Image
+  alt="GitHub Action 同步失败"
+  src="https://github.com/user-attachments/assets/9baacac6-5af4-460b-862d-682b76c18459"
+/>
+
+<Image
+  alt="手动同步 「Update Branch」"
+  src="https://github.com/user-attachments/assets/d524c20d-306a-45bc-971b-96920b87fab4"
+/>
+
 ## `B` Docker 部署
 
 Docker 部署版本的升级非常简单，只需要重新部署 LobeChat 的最新镜像即可。 以下是执行这些步骤所需的指令：
@@ -103,7 +115,7 @@ OPENAI_MODEL_LIST=-gpt-4,-gpt-4-32k,-gpt-3.5-turbo-16k,gpt-3.5-turbo-1106=gpt-3.
 # auto-update-lobe-chat.sh
 
 # 设置代理（可选）
-export https_proxy=http://127.0.0.1:7890 http_proxy=http://127.0.0.1:7890 all_proxy=socks5://127.0.0.1:7890
+# export https_proxy=http://127.0.0.1:7890 http_proxy=http://127.0.0.1:7890 all_proxy=socks5://127.0.0.1:7890
 
 # 拉取最新的镜像并将输出存储在变量中
 output=$(docker pull lobehub/lobe-chat:latest 2>&1)
@@ -121,20 +133,20 @@ if [ $? -eq 0 ]; then
   exit 0
 fi
 
-echo "Detected Lobe-Chat update"
+echo "Detected lobe-chat update"
 
 # 删除旧的容器
-echo "Removed: $(docker rm -f Lobe-Chat)"
+echo "Removed: $(docker rm -f lobe-chat)"
 
-# 运行新的容器
-echo "Started: $(docker run -d --network=host --env-file /path/to/lobe.env --name=Lobe-Chat --restart=always lobehub/lobe-chat)"
+# 运行新的容器(请将env配置文件地址改为你的实际地址)
+echo "Started: $(docker run -d --network=host --env-file path/to/lobe.env --name=lobe-chat --restart=always lobehub/lobe-chat)"
 
 # 打印更新的时间和版本
 echo "Update time: $(date)"
 echo "Version: $(docker inspect lobehub/lobe-chat:latest | grep 'org.opencontainers.image.version' | awk -F'"' '{print $4}')"
 
 # 清理不再使用的镜像
-docker images | grep 'lobehub/lobe-chat' | grep -v 'latest' | awk '{print $3}' | xargs -r docker rmi > /dev/null 2>&1
+docker images | grep 'lobehub/lobe-chat' | grep -v 'lobehub/lobe-chat-database' | grep -v 'latest' | awk '{print $3}' | xargs -r docker rmi > /dev/null 2>&1
 echo "Removed old images."
 ```
 

docs/self-hosting/advanced/webrtc.mdx

@@ -0,0 +1,92 @@
+---
+title: LobeChat WebRTC Sync - Real-Time Data Sharing
+description: >-
+  Explore LobeChat's WebRTC sync for real-time data sharing and privacy without
+  servers.
+tags:
+  - WebRTC
+  - LobeChat
+  - Data Synchronization
+  - Real-Time Communication
+  - Peer-to-Peer
+---
+# LobeChat WebRTC Sync
+
+## Introduction to WebRTC
+
+WebRTC (Web Real-Time Communication) is a technology that enables peer-to-peer communication between browsers. In LobeChat, we experimentally implemented real-time data synchronization between devices based on WebRTC and YJS, without relying on traditional server databases. This solution offers high privacy, zero conflicts, and provides a real-time session synchronization experience.
+
+## Configuring WebRTC for Synchronization
+
+To use the WebRTC synchronization feature in LobeChat, you need to complete the following steps:
+
+<Steps>
+
+### Deploy Signaling Server
+
+Deploy a WebRTC signaling server with one click using the Zeabur platform:
+
+[![Deploy on Zeabur](https://zeabur.com/button.svg)](https://zeabur.com/templates/MY0JZG?referralCode=arvinxx)
+
+Alternatively, you can view the [source code](https://github.com/lobehub/y-webrtc-signaling) and deploy it on your own.
+
+After deployment, you will receive a URL, for example: `https://my-signaling-server.zeabur.app`.
+
+### Enable WebRTC Sync in the Deployment Instance
+
+The WebRTC sync feature in LobeChat is hidden by default and needs to be enabled by adding the environment variable `FEATURE_FLAGS=+webrtc_sync`.
+
+### Configure WebRTC Sync Settings in LobeChat
+
+1. Open LobeChat settings -> Data Sync
+2. Enter the signaling server address in the WebRTC sync section;
+3. Set the sync channel name and password
+
+<Image
+  alt={'LobeChat Data Sync Settings Page'}
+  height={356}
+  inStep
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/bf86bf1e-87fb-4015-8587-15ff28bb9c24'}
+/>
+
+### Repeat the Above Configuration on Devices that Need to Sync
+
+Ensure all devices use the same signaling server, channel name, and password. Once configured, the devices should automatically start syncing data.
+
+</Steps>
+
+## Limitations and Known Issues
+
+Although WebRTC has the advantages of no database and flexibility, after extensive community testing, the following limitations and known issues have been identified:
+
+### Requirement for Devices to be Online Simultaneously
+
+WebRTC requires devices to be online simultaneously to synchronize, meaning changes cannot be made on one device while offline and then synced later on another device.
+
+This limitation is due to the communication nature of WebRTC. In a pure frontend, serverless scenario, data synchronization between two devices can only be achieved through peer-to-peer communication. When one device is online and the other is offline, it is impossible to determine where the data should come from. Only when both devices are online can data communication occur. This mode is more like an online chat room where everyone needs to be online to see each other's data and achieve synchronization.
+
+Therefore, in certain situations, WebRTC's pure peer-to-peer approach may not fully meet users' needs (e.g., one device is a work computer, and the other is a home computer), and there are also some issues with data synchronization.
+
+### Network Issues Leading to Sync Failures
+
+Due to the implementation mechanism of WebRTC, its peer-to-peer communication has strict network requirements. Many of our users have reported:
+
+- Syncing between PCs is possible, but syncing between a mobile device with a SIM card and a PC is not, although syncing is possible when using the same WIFI as the PC;
+- Syncing fails when switching networks.
+
+### Stability and Performance Issues
+
+- Some users have reported ICE connection failures on the Firefox browser: [WebRTC Data Sync Feedback](https://github.com/lobehub/lobe-chat/issues/1683#issuecomment-2094745907)
+- For extremely long text or large amounts of conversation records, the synchronization process may slow down or become unstable: [When the model outputs a very long conversation, the end of the conversation will contain synchronization-related content tags, leading to sync failures](https://github.com/lobehub/lobe-chat/issues/1962)
+
+## Our Recommendations
+
+Considering the above reasons, we recommend users treat the WebRTC sync feature as experimental and regularly back up important data.
+
+We have already released a more stable and user-friendly server database synchronization solution ([deployment guide](/docs/self-hosting/advanced/server-database)). We recommend users prioritize using the server database synchronization solution.
+
+<Callout type={'warning'}>
+  Please note that we have officially announced the archiving of this sync feature in [PR
+  3182](https://github.com/lobehub/lobe-chat/pull/3182), and the above issues will no longer be
+  considered for fixes.
+</Callout>

docs/self-hosting/advanced/webrtc.zh-CN.mdx

@@ -0,0 +1,87 @@
+---
+title: LobeChat WebRTC 同步配置指南
+description: 在 LobeChat 中实现基于 WebRTC 和 YJS 的设备间实时数据同步。了解如何配置 WebRTC 并开启同步功能，以及使用局限性和已知问题。
+tags:
+  - YJS
+  - 信令服务器
+---
+
+# LobeChat WebRTC 同步
+
+## WebRTC 简介
+
+WebRTC (Web Real-Time Communication) 是一项实现浏览器之间点对点通信的技术。在 LobeChat 中,我们实验性地基于 WebRTC 和 YJS 实现了设备间的实时数据同步,无需依赖传统的服务器数据库。这种方案具有高度隐私性、零冲突性，并能提供实时会话同步体验。
+
+## 配置 WebRTC 并实现同步
+
+要使用 LobeChat 的 WebRTC 同步功能,需要完成以下步骤:
+
+<Steps>
+
+### 部署信令服务器
+
+使用 Zeabur 平台一键部署 WebRTC 信令服务器：
+
+[![Deploy on Zeabur](https://zeabur.com/button.svg)](https://zeabur.com/templates/MY0JZG?referralCode=arvinxx)
+
+或者查看 [源码](https://github.com/lobehub/y-webrtc-signaling) 自行部署。
+
+部署完成后，可以得到一个 URL，例如：`https://my-signaling-server.zeabur.app`。
+
+### 在部署实例中开启 WebRTC 同步
+
+LobeChat 默认隐藏了 WebRTC 同步功能，需要通过添加环境变量 `FEATURE_FLAGS=+webrtc_sync` 来开启 WebRTC 同步特性。
+
+### 配置 LobeChat 的 WebRTC 同步设置
+
+1. 打开 LobeChat 设置 -> 数据同步
+2. 在 WebRTC 同步中填写信令服务器地址；
+3. 设置同步频道名称和密码
+
+<Image
+  alt={'LobeChat 数据同步设置页'}
+  height={356}
+  inStep
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/bf86bf1e-87fb-4015-8587-15ff28bb9c24'}
+/>
+
+### 在需要同步的设备上重复以上配置
+
+确保所有设备使用相同的信令服务器、频道名称和密码，完成配置后,设备间应该可以开始自动同步数据。
+
+</Steps>
+
+## 使用局限性和已知问题
+
+虽然 WebRTC 具有无数据库、比较灵活的特性，但目前该功能经过大范围社区测试，存在以下局限性和已知问题：
+
+### 设备同时在线要求
+
+WebRTC 要求设备同时在线才能进行同步，这意味着无法在一台设备离线时在另一台设备上进行更改并稍后同步。
+
+这是 WebRTC 本身的通信特性有关系，由于在纯前端、无服务端的情况下，两个设备的数据同步只能通过点对点通信的形式达成。当一个设备在线，一个设备离线的情况下，我们无从感知数据到底应该从哪来，只有当两台设备都在线的时候，双发数据才能通信。其实这种模式更像是一个在线聊天室，大家都在线时才能看到对方的数据，然后达成同步。
+
+因此 WebRTC 这种纯点对点的方式在某些情况下并无法完全满足用户的诉求（例如一个是公司电脑，一个是家里电脑），同时也存在一些数据同步层面的问题。
+
+### 网络问题可能导致同步失败
+
+由于 WebRTC 的实现机制，其点对点通信对于网络要求非常苛刻，我们的很多用户反馈：
+
+- 在 PC 上可以互相同步、 手机 sim 卡无法和 PC 同步、但是换成和PC一样的WIFI可以和 PC 同步；
+- 任何切换网络都无法同步；
+
+### 稳定性与性能问题
+
+- 部分用户报告在 Firefox 浏览器上遇到 ICE 连接失败的问题：[WebRTC Data Sync Feedback](https://github.com/lobehub/lobe-chat/issues/1683#issuecomment-2094745907)
+- 对于超长文本或大量对话记录,同步过程可能变慢或不稳定：[当模型输出超长对话时，对话末尾会出现同步相关的内容标签，导致同步失败](https://github.com/lobehub/lobe-chat/issues/1962)
+
+## 我们的建议
+
+鉴于以上原因，我们建议用户将 WebRTC 同步功能视为实验性功能,并定期备份重要数据。
+
+目前我们已经发布了更稳定、更用户友好的服务端数据库同步方案（[部署指南](/zh/docs/self-hosting/advanced/server-database)），我们建议用户优先考虑使用服务端数据库同步方案。
+
+<Callout type={'warning'}>
+  请注意，我们已经在 [PR 3182](https://github.com/lobehub/lobe-chat/pull/3182)
+  中正式宣布归档该同步特性，上述问题将不再考虑进行修复。
+</Callout>

docs/self-hosting/environment-variables.mdx

@@ -18,5 +18,77 @@ LobeChat provides some additional configuration options when deployed, which can
   <Card href={'environment-variables/basic'} title={'Basic Environment Variables'} />
   <Card href={'environment-variables/model-provider'} title={'Model Service Providers'} />
   <Cards href={'environment-variables/auth'} title={'Authentication'} />
+  <Cards href={'environment-variables/s3'} title={'S3 Storage Service'} />
   <Cards href={'environment-variables/analytics'} title={'Data Analytics'} />
 </Cards>
+
+## Building a Custom Image with Overridden NEXT_PUBLIC Variables
+
+If you need to override NEXT_PUBLIC environment variables, you can build a custom Docker image using GitHub Actions
+without forking the entire LobeChat repository. Here's a guide on how to do this:
+
+1. Create a new GitHub repository for your custom build.
+
+2. In your new repository, create a `.github/workflows` directory.
+
+3. Inside the `.github/workflows` directory, create a file named `build-custom-lobe.yml`:
+```yaml
+name: Build Custom Image
+
+on:
+  workflow_dispatch: # Manual trigger
+
+env:
+  REGISTRY: ghcr.io
+  IMAGE_NAME: ${{ github.repository_owner }}/lobe-chat-database # Name of your image
+
+jobs:
+  build-and-push:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v3
+        with:
+          repository: lobehub/lobe-chat
+
+      - name: Log in to the Container registry
+        uses: docker/login-action@v2
+        with:
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Extract metadata (tags, labels) for Docker
+        id: meta
+        uses: docker/metadata-action@v4
+        with:
+          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+
+      - name: Build and push Docker image
+        uses: docker/build-push-action@v4
+        with:
+          context: .
+          file: Dockerfile.database # Change dockerfile if needed
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          # List all variables you need to overwrite
+          build-args: |
+            NEXT_PUBLIC_BASE_PATH=${{ secrets.NEXT_PUBLIC_BASE_PATH }}
+            NEXT_PUBLIC_SERVICE_MODE=${{ secrets.NEXT_PUBLIC_SERVICE_MODE }}
+```
+
+4. In your GitHub Repository settings > Secrets and variables > Actions > Repository secrets,
+add any NEXT_PUBLIC variables you want to override
+
+5. Set "Read and write" permissions for workflows in  Repository settings > Actions > General > Workflow permissions.
+
+6. To build your custom image, go to the "Actions" tab in your GitHub repository and manually trigger the
+"Build Custom LobeChat Image" workflow.
+
+This approach allows you to create a custom build with your desired NEXT_PUBLIC variables without maintaining
+a full fork of the LobeChat repository. You can trigger a new build whenever you need to update your custom image.

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

@@ -16,5 +16,6 @@ LobeChat 在部署时提供了一些额外的配置项，你可以使用环境
   <Cards href={'environment-variables/basic'} title={'基础环境变量'} />
   <Cards href={'environment-variables/model-provider'} title={'模型服务商'} />
   <Cards href={'environment-variables/auth'} title={'身份验证'} />
+  <Cards href={'environment-variables/s3'} title={'S3 存储服务'} />
   <Cards href={'environment-variables/analytics'} title={'数据统计'} />
 </Cards>

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

@@ -1,7 +1,5 @@
 ---
-title: >-
-  Integrating Data Analytics Services in LobeChat: Environment Variables and
-  Configuration
+title: Integrating Analytics in LobeChat
 description: >-
   Learn how to configure environment variables for Vercel Analytics, Google
   Analytics, PostHog Analytics, and Umami Analytics in LobeChat for data
@@ -36,44 +34,30 @@ We have integrated several free/open-source data analytics services in LobeChat
 
 ## Google Analytics
 
-### `ENABLE_GOOGLE_ANALYTICS`
-
-- Type: Optional
-- Description: Used to configure the environment variable for Google Analytics. Set to `1` to enable Google Analytics.
-- Default: `-`
-- Example: `1`
-
 ### `GOOGLE_ANALYTICS_MEASUREMENT_ID`
 
 - Type: Required
-- Description: Google Analytics Measurement ID，you can get it from the Google Analytics dashboard.
+- Description: Google Analytics Measurement ID，you can get it from the Google Analytics dashboard. Add it will auto enable Google Analytics.
 - Default: `-`
 - Example: `G-63LP2TV03T`
 
 ## Posthog Analytics
 
-### `NEXT_PUBLIC_ANALYTICS_POSTHOG`
+### `POSTHOG_KEY`
 
-- Type: Optional
-- Description: Used to enable the environment variable for [PostHog Analytics][posthog-analytics-url]. Set to `1` to enable PostHog Analytics.
-- Default: `-`
-- Example: `1`
-
-### `NEXT_PUBLIC_POSTHOG_KEY`
-
-- Type: Optional
-- Description: Set the PostHog project Key.
+- Type: Required
+- Description: Set the PostHog project Key. Add it will auto enable PostHog Analytics.
 - Default: `-`
 - Example: `phc_xxxxxxxx`
 
-### `NEXT_PUBLIC_POSTHOG_HOST`
+### `POSTHOG_HOST`
 
 - Type: Optional
 - Description: Set the deployment address of the PostHog service, defaulting to the official SAAS address.
 - Default: `https://app.posthog.com`
 - Example: `https://example.com`
 
-### `NEXT_PUBLIC_POSTHOG_DEBUG`
+### `DEBUG_POSTHOG_ANALYTICS`
 
 - Type: Optional
 - Description: Enable the debug mode for PostHog.
@@ -82,26 +66,19 @@ We have integrated several free/open-source data analytics services in LobeChat
 
 ## Umami Analytics
 
-### `NEXT_PUBLIC_ANALYTICS_UMAMI`
+### `UMAMI_WEBSITE_ID`
 
-- Type: Optional
-- Description: Used to enable the environment variable for [Umami Analytics][umami-analytics-url]. Set to `1` to enable Umami Analytics.
+- Type: Required
+- Description: Your Umami Website ID. Add it will auto enable Umami Analytics.
 - Default: `-`
-- Example: `1`
+- Example: `E738D82A-EE9E-4806-A81F-0CA3CAE57F65`
 
-### `NEXT_PUBLIC_UMAMI_SCRIPT_URL`
+### `UMAMI_SCRIPT_URL`
 
 - Type: Optional
 - Description: The URL of the Umami script, defaulting to the script URL provided by Umami Cloud.
 - Default: `https://analytics.umami.is/script.js`
 - Example: `https://umami.your-site.com/script.js`
 
-### `NEXT_PUBLIC_UMAMI_WEBSITE_ID`
-
-- Type: Required
-- Description: Your Umami Website ID.
-- Default: `-`
-- Example: `E738D82A-EE9E-4806-A81F-0CA3CAE57F65`
-
 [posthog-analytics-url]: https://posthog.com
 [umami-analytics-url]: https://umami.is

docs/self-hosting/environment-variables/analytics.zh-CN.mdx

@@ -32,44 +32,30 @@ tags:
 
 ## Google Analytics
 
-### `ENABLE_GOOGLE_ANALYTICS`
-
-- 类型：必选
-- 描述：用于配置 Google Analytics 的环境变量，当设为 `1` 时开启 Google Analytics
-- 默认值： `-`
-- 示例：`1`
-
 ### `GOOGLE_ANALYTICS_MEASUREMENT_ID`
 
 - 类型：必选
-- 描述：Google Analytics 的 Measurement ID，如果开启了 Google Analytics，此项必填
+- 描述：Google Analytics 的 Measurement ID，填写此项后将自动开启 Google Analytics
 - 默认值： `-`
 - 示例：`G-63LP2TV03T`
 
 ## Posthog Analytics
 
-### `NEXT_PUBLIC_ANALYTICS_POSTHOG`
+### `POSTHOG_KEY`
 
-- 类型：可选
-- 描述：用于开启 [PostHog Analytics][posthog-analytics-url] 的环境变量，设为 `1` 时开启 PostHog Analytics
-- 默认值： `-`
-- 示例：`1`
-
-### `NEXT_PUBLIC_POSTHOG_KEY`
-
-- 类型：可选
-- 描述：设置 PostHog 项目 Key
+- 类型：必选
+- 描述：设置 PostHog 项目 Key，设置此项后将自动开启 PostHog Analytics
 - 默认值： `-`
 - 示例：`phc_xxxxxxxx`
 
-### `NEXT_PUBLIC_POSTHOG_HOST`
+### `POSTHOG_HOST`
 
 - 类型：可选
-- 描述：设置 PostHog 服务的部署地址，默认为官方的 SAAS 地址
+- 描述：设置 PostHog 服务的部署地址，默认为官方的 SaaS 地址
 - 默认值：`https://app.posthog.com`
 - 示例：`https://example.com`
 
-### `NEXT_PUBLIC_POSTHOG_DEBUG`
+### `POSTHOG_DEBUG`
 
 - 类型：可选
 - 描述：开启 PostHog 的调试模式
@@ -78,26 +64,19 @@ tags:
 
 ## Umami Analytics
 
-### `NEXT_PUBLIC_ANALYTICS_UMAMI`
+### `UMAMI_WEBSITE_ID`
 
-- 类型：可选
-- 描述：用于开启 [Umami Analytics][umami-analytics-url] 的环境变量，设为 `1` 时开启 Umami Analytics
-- 默认值： `-`
-- 示例：`1`
+- 类型：必选
+- 描述：你的 Umami 的 Website ID，填写此项后将自动开启 Umami Analytics
+- 默认值：`-`
+- 示例：`E738D82A-EE9E-4806-A81F-0CA3CAE57F65`
 
-### `NEXT_PUBLIC_UMAMI_SCRIPT_URL`
+### `UMAMI_SCRIPT_URL`
 
 - 类型：可选
 - 描述：Umami 脚本的网址，默认为 Umami Cloud 提供的脚本网址
 - 默认值：`https://analytics.umami.is/script.js`
 - 示例：`https://umami.your-site.com/script.js`
 
-### `NEXT_PUBLIC_UMAMI_WEBSITE_ID`
-
-- 类型：必选
-- 描述：你的 Umami 的 Website ID
-- 默认值：`-`
-- 示例：`E738D82A-EE9E-4806-A81F-0CA3CAE57F65`
-
 [posthog-analytics-url]: https://posthog.com
 [umami-analytics-url]: https://umami.is

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

@@ -5,158 +5,282 @@ description: >-
   services in LobeChat, including OAuth SSO, NextAuth settings, and
   provider-specific details.
 tags:
-  - LobeChat
   - Authentication Service
-  - Environment Variables
   - OAuth SSO
+  - Clerk
   - NextAuth
-  - Provider Details
 ---
 
-## Authentication Service
+# Authentication Service
 
 LobeChat provides a complete authentication service capability when deployed. The following are the relevant environment variables. You can use these environment variables to easily define the identity verification services that need to be enabled in LobeChat.
 
-## General Settings
+## Next Auth
 
-### `ENABLE_OAUTH_SSO`
+### General Settings
 
-- Type: Required
-- Description: Enable single sign-on (SSO) for LobeChat. Set to `1` to enable single sign-on.
-- Default: `-`
-- Example: `1`
-
-### `SSO_PROVIDERS`
-
-- Type: Required
-- Description: Select the single sign-on provider for LoboChat. For multiple SSO Providers separating them with commas, for example, `auth0,azure-ad,authentik`.
-- Default: `auth0`
-- Example: `auth0,azure-ad,authentik`
-
-### `NEXTAUTH_SECRET`
+#### `NEXT_AUTH_SECRET`
 
 - Type: Required
 - Description: Key used to encrypt the session tokens in Auth.js. You can generate the key using the following command: `openssl rand -base64 32`.
 - Default: `-`
 - Example: `Tfhi2t2pelSMEA8eaV61KaqPNEndFFdMIxDaJnS1CUI=`
 
-### `NEXTAUTH_URL`
+#### `NEXT_AUTH_SSO_PROVIDERS`
+
+- Type: Optional
+- Description: Select the single sign-on provider for LoboChat. For multiple SSO Providers separating them with commas, for example, `auth0,microsoft-entra-id,authentik`.
+- Default: `auth0`
+- Example: `auth0,microsoft-entra-id,authentik`
+
+#### `NEXTAUTH_URL`
 
 - Type: Optional
 - Description: This URL is used to specify the callback address for Auth.js during OAuth authentication. It does not need to be set when deploying on Vercel.
 - Default: `-`
 - Example: `https://example.com/api/auth`
 
-## Auth0
+### Auth0
 
-### `AUTH0_CLIENT_ID`
+#### `AUTH_AUTH0_ID`
 
 - Type: Required
 - Description: Client ID of the Auth0 application. You can access it [here](https://manage.auth0.com/dashboard) and navigate to the application settings to view.
 - Default: `-`
 - Example: `evCnOJP1UX8FMnXR9Xkj5t0NyFn5p70P`
 
-### `AUTH0_CLIENT_SECRET`
+#### `AUTH_AUTH0_SECRET`
 
 - Type: Required
 - Description: Client Secret of the Auth0 application.
 - Default: `-`
 - Example: `wnX7UbZg85ZUzF6ioxPLnJVEQa1Elbs7aqBUSF16xleBS5AdkVfASS49-fQIC8Rm`
 
-### `AUTH0_ISSUER`
+#### `AUTH_AUTH0_ISSUER`
 
 - Type: Required
 - Description: Issuer/domain of the Auth0 application.
 - Default: `-`
 - Example: `https://example.auth0.com`
 
-## Microsoft Entra ID
+### Authelia
 
-### `AZURE_AD_CLIENT_ID`
+#### `AUTH_AUTHELIA_ID`
 
 - Type: Required
-- Description: Client ID of the Microsoft Entra ID application.
+- Description: Client ID of the Authelia provider application.
 - Default: `-`
-- Example: `be8f6da1-58c3-4f16-ff1b-78f5148e10df`
+- Example: `lobe-chat`
 
-### `AZURE_AD_CLIENT_SECRET`
+#### `AUTH_AUTHELIA_SECRET`
 
 - Type: Required
-- Description: Client Secret of the Microsoft Entra ID application.
+- Description: The plaintext of the Client Secret for the Authelia provider
 - Default: `-`
-- Example: `~gI8Q.pTiN1vwB6Gl.E1yFT1ojcXABkdACfJXaNj`
+- Example: `insecure_secret`
 
-### `AZURE_AD_TENANT_ID`
+#### `AUTH_AUTHELIA_ISSUER`
 
 - Type: Required
-- Description: Tenant ID of the Microsoft Entra ID application.
+- Description: Issuer of the Authelia provider application.
 - Default: `-`
-- Example: `c8ae2f36-edf6-4cda-96b9-d3e198a47cba`
+- Example: `https://sso.example.com`
 
-## Authentik
+### Authentik
 
-### `AUTHENTIK_CLIENT_ID`
+#### `AUTH_AUTHENTIK_ID`
 
 - Type: Required
-- Description: Client ID of the Authentik provider application. You can access it [here][auth0-client-page] and navigate to the application settings to view.
+- Description: Client ID of the Authentik provider application.
 - Default: `-`
 - Example: `evCnOJP1UX8FMnXR9Xkj5t0NyFn5p70P`
 
-### `AUTHENTIK_CLIENT_SECRET`
+#### `AUTH_AUTHENTIK_SECRET`
 
 - Type: Required
 - Description: Client Secret of the Authentik provider application.
 - Default: `-`
 - Example: `wnX7UbZg85ZUzF6ioxPLnJVEQa1Elbs7aqBUSF16xleBS5AdkVfASS49-fQIC8Rm`
 
-### `AUTHENTIK_ISSUER`
+#### `AUTH_AUTHENTIK_ISSUER`
 
 - Type: Required
 - Description: Issuer/domain of the Authentik provider application.
 - Default: `-`
 - Example: `https://your-authentik-domain.com/application/o/slug/`
 
-## Github
+### Casdoor
 
-### `GITHUB_CLIENT_ID`
+#### `AUTH_CASDOOR_ID`
+
+- Type: Required
+- Description: Client ID provided by Casdoor
+- Default: `-`
+- Example: `570bfa85a21800a25198`
+
+#### `AUTH_CASDOOR_SECRET`
+
+- Type: Required
+- Description: Plaintext Client Secret provided by Casdoor
+- Default: `-`
+- Example: `233a623a15eac2db2e43bb8a323eda729552c405`
+
+#### `AUTH_CASDOOR_ISSUER`
+
+- Type: Required
+- Description: OpenID Connect issuer provided by Casdoor
+- Default: `-`
+- Example: `https://lobe-auth-api.example.com/`
+
+### Cloudflare Zero Trust
+
+#### `AUTH_CLOUDFLARE_ZERO_TRUST_ID`
+
+- Type: Required
+- Description: Client ID of the Cloudflare Zero Trust provider application.
+- Default: `-`
+- Example: `711963a58df8c943cfd6c487cac99ce9f6ee0c88c0b7bf94584b8ff052fcb09c`
+
+#### `AUTH_CLOUDFLARE_ZERO_TRUST_SECRET`
+
+- Type: Required
+- Description: The plaintext of the Client Secret for the Cloudflare Zero Trust provider
+- Default: `-`
+- Example: `8f26d4ef834a828045b401e032ae128dbb00471bca53f0d25332323f525dfa30`
+
+#### `AUTH_CLOUDFLARE_ZERO_TRUST_ISSUER`
+
+- Type: Required
+- Description: Issuer of the Cloudflare Zero Trust provider application.
+- Default: `-`
+- Example: `https://example.cloudflareaccess.com/cdn-cgi/access/sso/oidc/711963a58df8c943cfd6c487cac99ce9f6ee0c88c0b7bf94584b8ff052fcb09c`
+
+### Github
+
+#### `AUTH_GITHUB_ID`
 
 - Type: Required
 - Description: Client ID of the Github application. You can access it [here](https://github.com/settings/apps) and navigate to the application settings to view.
 - Default: `-`
 - Example: `abd94200333283550508`
 
-### `GITHUB_CLIENT_SECRET`
+#### `AUTH_GITHUB_SECRET`
 
 - Type: Required
 - Description: Client Secret of the Github application.
 - Default: `-`
 - Example: `dd262976ac0931d947e104891586a053f3d3750b`
 
-## ZITADEL
+### Logto
 
-### `ZITADEL_CLIENT_ID`
+#### `AUTH_LOGTO_ID`
+
+- Type: Required
+- Description: The Client ID of the Logto application. You can find it in the Logto console for private deployment or [Logto Cloud](http://cloud.logto.io/) depending on the deployment mode.
+- Default value: `-`
+- Example: `123456789012345678@your-project`
+
+#### `AUTH_LOGTO_SECRET`
+
+- Type: Required
+- Description: The Client Secret of the Logto application.
+- Default value: `-`
+- Example: `9QF1n5ATzU7Z3mHp2Iw4gKX8kY6oR7uW1DnKcV3LqX2jF6iG3fBmJ1kV7nS5zE6A`
+
+#### `AUTH_LOGTO_ISSUER`
+
+- Type: Required
+- Description: The OpenID Connect issuer of the Logto application. You can find it in the Logto console for private deployment or [Logto Cloud](http://cloud.logto.io/) depending on the deployment mode.
+- Default value: `-`
+- Example: `https://lobe-auth-api.example.com/oidc`
+
+### Microsoft Entra ID
+
+#### `AUTH_AZURE_AD_ID`
+
+- Type: Required
+- Description: Client ID of the Microsoft Entra ID application.
+- Default: `-`
+- Example: `be8f6da1-58c3-4f16-ff1b-78f5148e10df`
+
+#### `AUTH_AZURE_AD_SECRET`
+
+- Type: Required
+- Description: Client Secret of the Microsoft Entra ID application.
+- Default: `-`
+- Example: `~gI8Q.pTiN1vwB6Gl.E1yFT1ojcXABkdACfJXaNj`
+
+#### `AUTH_AZURE_AD_TENANT_ID`
+
+- Type: Required
+- Description: Tenant ID of the Microsoft Entra ID application.
+- Default: `-`
+- Example: `c8ae2f36-edf6-4cda-96b9-d3e198a47cba`
+
+### ZITADEL
+
+#### `AUTH_ZITADEL_ID`
 
 - Type: Required
 - Description: Client ID of the ZITADEL application. This can be found under your application in the ZITADEL console.
 - Default: `-`
 - Example: `123456789012345678@your-project`
 
-### `ZITADEL_CLIENT_SECRET`
+#### `AUTH_ZITADEL_SECRET`
 
 - Type: Required
 - Description: Client Secret of the ZITADEL application.
 - Default: `-`
 - Example: `9QF1n5ATzU7Z3mHp2Iw4gKX8kY6oR7uW1DnKcV3LqX2jF6iG3fBmJ1kV7nS5zE6A`
 
-### `ZITADEL_ISSUER`
+#### `AUTH_ZITADEL_ISSUER`
 
 - Type: Required
 - Description: Issuer of the ZITADEL application. This is usually the URL of the ZITADEL instance, and can be found in `URLs` tab of your application in the console.
 - Default: `-`
 - Example: `https://your-instance-abc123.zitadel.cloud`
 
+### Generic OIDC
+
+#### `AUTH_GENERIC_OIDC_ID`
+
+- Type: Required
+- Description: Client ID of the Generic OIDC provider application.
+- Default: `-`
+- Example: `_client_id_for_lobe_chat_`
+
+#### `AUTH_GENERIC_OIDC_SECRET`
+
+- Type: Required
+- Description: The plaintext of the Client Secret for the Generic OIDC provider
+- Default: `-`
+- Example: `_client_secret_for_lobe_chat_`
+
+#### `AUTH_GENERIC_OIDC_ISSUER`
+
+- Type: Required
+- Description: Issuer of the Generic OIDC provider application.
+- Default: `-`
+- Example: `https://sso.example.com`
+
 <Callout>
   Currently, we only support providers above. If you need to use other identity verification service
   providers, you can submit a [feature
   request](https://github.com/lobehub/lobe-chat/issues/new/choose) or Pull Request.
 </Callout>
+
+## Clerk
+
+### `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY`
+
+- Type: Required
+- Description: Publishable key of the Clerk application. You can access it [here](https://dashboard.clerk.com) and navigate to the API Keys to view.
+- Default: `-`
+- Example: `pk_test_Zmxvd4luZy1wdW1hLTIyLmNsXXJrTmFjY291bnRzLmRldiQ` in dev / `pk_live_Y2xlcdsubG9iZWh1Yi1cbmMuY24k` in production
+
+### `CLERK_SECRET_KEY`
+
+- Type: Required
+- Description: Secret key of the Clerk application.
+- Default: `-`
+- Example: `sk_test_513Ma0P7IAWM1XMv4waxZjRYRajWTaCfJLjpEO3SD2` in dev / `sk_live_eMMlHjwJvZFUfczFljSKqZdwQtLvmczmsJSNmdrpeZ` in production

docs/self-hosting/environment-variables/auth.zh-CN.mdx

@@ -1,162 +1,283 @@
 ---
 title: LobeChat 身份验证服务设置
-description: >-
-  了解如何配置 LobeChat 的身份验证服务环境变量，包括单点登录 (SSO)、Auth0、Microsoft Entra
-  ID、Authentik、Github 和 ZITADEL。
+description: 了解如何配置 LobeChat 的身份验证服务环境变量。
 tags:
   - LobeChat
   - 身份验证服务
   - 单点登录
-  - Auth0
-  - Microsoft Entra ID
-  - Authentik
-  - Github
-  - ZITADEL
+  - Next Auth
+  - Clerk
 ---
 
 # 身份验证服务
 
 LobeChat 在部署时提供了完善的身份验证服务能力，以下是相关的环境变量，你可以使用这些环境变量轻松定义需要在 LobeChat 中开启的身份验证服务。
 
-## 通用设置
+## Next Auth
 
-### `ENABLE_OAUTH_SSO`
+### 通用设置
 
-- 类型：必选
-- 描述：为 LobeChat 启用单点登录 (SSO)。设置为 `1` 以启用单点登录。
-- 默认值: `-`
-- 示例: `1`
-
-### `SSO_PROVIDERS`
-
-- Type: 必需
-- 描述：选择 LoboChat 的单点登录提供商。如果有多个单点登录提供商，请用逗号分隔，例如 `auth0,azure-ad,authentik`
-- 默认值: `auth0`
-- 示例: `auth0,azure-ad,authentik`
-
-### `NEXTAUTH_SECRET`
+#### `NEXT_AUTH_SECRET`
 
 - 类型：必选
 - 描述：用于加密 Auth.js 会话令牌的密钥。您可以使用以下命令生成秘钥： `openssl rand -base64 32`.
 - 默认值: `-`
 - 示例: `Tfhi2t2pelSMEA8eaV61KaqPNEndFFdMIxDaJnS1CUI=`
 
-### `NEXTAUTH_URL`
+#### `NEXT_AUTH_SSO_PROVIDERS`
+
+- 类型：可选
+- 描述：选择 LoboChat 的单点登录提供商。如果有多个单点登录提供商，请用逗号分隔，例如 `auth0,microsoft-entra-id,authentik`
+- 默认值: `auth0`
+- 示例: `auth0,microsoft-entra-id,authentik`
+
+#### `NEXTAUTH_URL`
 
 - 类型：可选
 - 描述：该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，在 Vercel 上部署时无需设置。
 - 默认值：`-`
 - 示例：`https://example.com/api/auth`
 
-## Auth0
+### Auth0
 
-### `AUTH0_CLIENT_ID`
+#### `AUTH_AUTH0_ID`
 
 - 类型：必选
 - 描述: Auth0 应用程序的 Client ID，您可以访问[这里](https://manage.auth0.com/dashboard)并导航至应用程序设置来查看
 - 默认值: `-`
 - 示例: `evCnOJP1UX8FMnXR9Xkj5t0NyFn5p70P`
 
-### `AUTH0_CLIENT_SECRET`
+#### \`AUTH_AUTH_SECRET
 
 - 类型：必选
 - 描述: Auth0 应用程序的 Client Secret
 - 默认值: `-`
 - 示例: `wnX7UbZg85ZUzF6ioxPLnJVEQa1Elbs7aqBUSF16xleBS5AdkVfASS49-fQIC8Rm`
 
-### `AUTH0_ISSUER`
+#### `AUTH_AUTH0_ISSUER`
 
 - 类型：必选
 - 描述: Auth0 应用程序的签发人 / 域
 - 默认值: `-`
 - 示例: `https://example.auth0.com`
 
-## Microsoft Entra ID
+### Authelia
 
-### `AZURE_AD_CLIENT_ID`
+#### `AUTH_AUTHELIA_ID`
 
-- 类型：必需
-- 描述：Microsoft Entra ID 应用程序的客户端 ID。
-- 默认值：`-`
-- 示例：`be8f6da1-58c3-4f16-ff1b-78f5148e10df`
+- 类型：必选
+- 描述: Authelia 提供程序的 Client ID
+- 默认值: `-`
+- 示例: `lobe-chat`
 
-### `AZURE_AD_CLIENT_SECRET`
+#### `AUTH_AUTHELIA_SECRET`
 
-- 类型：必需
-- 描述：Microsoft Entra ID 应用程序的客户端密钥。
-- 默认值：`-`
-- 示例：`~gI8Q.pTiN1vwB6Gl.E1yFT1ojcXABkdACfJXaNj`
+- 类型：必选
+- 描述: Authelia 提供程序的 Client Secret 的明文
+- 默认值: `-`
+- 示例: `insecure_secret`
 
-### `AZURE_AD_TENANT_ID`
+#### `AUTH_AUTHELIA_ISSUER`
 
-- 类型：必需
-- 描述：Microsoft Entra ID 应用程序的租户 ID。
-- 默认值：`-`
-- 示例：`c8ae2f36-edf6-4cda-96b9-d3e198a47cba`
+- 类型：必选
+- 描述: Authentik 提供程序的 OpenID Connect 颁发者
+- 默认值: `-`
+- 示例: `https://sso.example.com`
 
-## Authentik
+### Authentik
 
-### `AUTHENTIK_CLIENT_ID`
+#### `AUTH_AUTHENTIK_ID`
 
 - 类型：必选
 - 描述: Authentik 提供程序的 Client ID
 - 默认值: `-`
 - 示例: `YNtbIRlYF8Kj66mTLue59nsGLlb7HNyx1qjPH6VS`
 
-### `AUTHENTIK_CLIENT_SECRET`
+#### `AUTH_AUTHENTIK_SECRET`
 
 - 类型：必选
 - 描述: Authentik 提供程序的 Client Secret
 - 默认值: `-`
 - 示例: `h3lMI1vPUzqyqqeIDUbH5UNNOxyQLXk35h89yETeaAwHk7qVXBG3sJQWeqHBU5pyggwhP9u0eaZ1eq6DHUddVPLoS4gncqD37yuCr8jI8dY66WAt45MStDsDcQm0Ygze`
 
-### `AUTHENTIK_ISSUER`
+#### `AUTH_AUTHENTIK_ISSUER`
 
 - 类型：必选
 - 描述: Authentik 提供程序的 OpenID Connect 颁发者
 - 默认值: `-`
 - 示例: `https://your-authentik-domain.com/application/o/slug/`
 
-## Github
+### Casdoor
 
-### `GITHUB_CLIENT_ID`
+#### `AUTH_CASDOOR_ID`
 
-- Type: Required
-- Description: Github应用的客户端ID。您可以在[这里](https://github.com/settings/apps)访问，并导航到应用程序设置以查看。
-- Default: `-`
-- Example: `abd94200333283550508`
+- 类型：必选
+- 描述: Casdoor 提供程序的 Client ID
+- 默认值: `-`
+- 示例: `570bfa85a21800a25198`
 
-### `GITHUB_CLIENT_SECRET`
+#### `AUTH_CASDOOR_SECRET`
 
-- Type: Required
-- Description: Github应用的客户端密钥。
-- Default: `-`
-- Example: `dd262976ac0931d947e104891586a053f3d3750b`
+- 类型：必选
+- 描述: Casdoor 提供程序的 Client Secret 的明文
+- 默认值: `-`
+- 示例: `233a623a15eac2db2e43bb8a323eda729552c405`
 
-## ZITADEL
+#### `AUTH_CASDOOR_ISSUER`
 
-### `ZITADEL_CLIENT_ID`
+- 类型：必选
+- 描述: Casdoor 提供程序的 OpenID Connect 颁发者
+- 默认值: `-`
+- 示例: `https://lobe-auth-api.example.com/`
+
+### Cloudflare Zero Trust
+
+#### `AUTH_CLOUDFLARE_ZERO_TRUST_ID`
+
+- 类型：必选
+- 描述: Cloudflare Zero Trust 提供程序的 Client ID
+- 默认值: `-`
+- 示例: `711963a58df8c943cfd6c487cac99ce9f6ee0c88c0b7bf94584b8ff052fcb09c`
+
+#### `AUTH_CLOUDFLARE_ZERO_TRUST_SECRET`
+
+- 类型：必选
+- 描述: Cloudflare Zero Trust 提供程序的 Client Secret 的明文
+- 默认值: `-`
+- 示例: `8f26d4ef834a828045b401e032ae128dbb00471bca53f0d25332323f525dfa30`
+
+#### `AUTH_CLOUDFLARE_ZERO_TRUST_ISSUER`
+
+- 类型：必选
+- 描述: Cloudflare Zero Trust 提供程序的 OpenID Connect 颁发者
+- 默认值: `-`
+- 示例: `https://example.cloudflareaccess.com/cdn-cgi/access/sso/oidc/711963a58df8c943cfd6c487cac99ce9f6ee0c88c0b7bf94584b8ff052fcb09c`
+
+### Github
+
+#### `AUTH_GITHUB_ID`
+
+- 类型：必选
+- 描述: Github 应用的客户端 ID。您可以在[这里](https://github.com/settings/apps)访问，并导航到应用程序设置以查看。
+- 默认值: `-`
+- 示例: `abd94200333283550508`
+
+#### `AUTH_GITHUB_SECRET`
+
+- 类型：必选
+- 描述: Github 应用的客户端密钥。
+- 默认值: `-`
+- 示例: `dd262976ac0931d947e104891586a053f3d3750b`
+
+### Logto
+
+#### `AUTH_LOGTO_ID`
+
+- 类型：必选
+- 描述：Logto 应用程序的 Client ID。您可以在根据部署模式，在私有部署的 Logto 控制台或 [Logto Cloud](http://cloud.logto.io/) 中找到。
+- 默认值：`-`
+- 示例：`123456789012345678@your-project`
+
+#### `AUTH_LOGTO_SECRET`
+
+- 类型：必选
+- 描述：Logto 应用程序的 Client Secret。
+- 默认值：`-`
+- 示例：`9QF1n5ATzU7Z3mHp2Iw4gKX8kY6oR7uW1DnKcV3LqX2jF6iG3fBmJ1kV7nS5zE6A`
+
+#### `AUTH_LOGTO_ISSUER`
+
+- 类型：必选
+- 描述：Logto 应用程序的 OpenID Connect 颁发者（issuer）。根据部署模式，您可以在私有部署的 Logto 控制台或 [Logto Cloud](http://cloud.logto.io/) 中找到。
+- 默认值：`-`
+- 示例：`https://lobe-auth-api.example.com/oidc`
+
+### Microsoft Entra ID
+
+#### `AUTH_AZURE_AD_ID`
+
+- 类型：必选
+- 描述：Microsoft Entra ID 应用程序的客户端 ID。
+- 默认值：`-`
+- 示例：`be8f6da1-58c3-4f16-ff1b-78f5148e10df`
+
+#### `AUTH_AZURE_AD_SECRET`
+
+- 类型：必选
+- 描述：Microsoft Entra ID 应用程序的客户端密钥。
+- 默认值：`-`
+- 示例：`~gI8Q.pTiN1vwB6Gl.E1yFT1ojcXABkdACfJXaNj`
+
+#### `AUTH_AZURE_AD_TENANT_ID`
+
+- 类型：必选
+- 描述：Microsoft Entra ID 应用程序的租户 ID。
+- 默认值：`-`
+- 示例：`c8ae2f36-edf6-4cda-96b9-d3e198a47cba`
+
+### ZITADEL
+
+#### `AUTH_ZITADEL_ID`
 
 - 类型：必选
 - 描述：ZITADEL 应用的 Client ID。您可以在 ZITADEL 控制台应用设置中找到 Client ID。
 - 默认值：`-`
 - 示例：`123456789012345678@your-project`
 
-### `ZITADEL_CLIENT_SECRET`
+#### `AUTH_ZITADEL_SECRET`
 
 - 类型：必选
 - 描述：ZITADEL 应用的 Client Secret。
 - 默认值：`-`
 - 示例：`9QF1n5ATzU7Z3mHp2Iw4gKX8kY6oR7uW1DnKcV3LqX2jF6iG3fBmJ1kV7nS5zE6A`
 
-### `ZITADEL_ISSUER`
+#### `AUTH_ZITADEL_ISSUER`
 
 - 类型：必选
 - 描述：ZITADEL 应用的 OpenID Connect 颁发者（issuer），通常为 ZITADEL 实例的 URL。您可以在 ZITADEL 控制台应用设置中的 `URLs` 选项卡中找到 issuer。
 - 默认值：`-`
 - 示例：`https://your-instance-abc123.zitadel.cloud`
 
+### Generic OIDC
+
+#### `AUTH_GENERIC_OIDC_ID`
+
+- 类型：必选
+- 描述: Generic OIDC 提供程序的 Client ID
+- 默认值: `-`
+- 示例: `_client_id_for_lobe_chat_`
+
+#### `AUTH_GENERIC_OIDC_SECRET`
+
+- 类型：必选
+- 描述: Generic OIDC 提供程序的 Client Secret 的明文
+- 默认值: `-`
+- 示例: `_client_secret_for_lobe_chat_`
+
+#### `AUTH_GENERIC_OIDC_ISSUER`
+
+- 类型：必选
+- 描述: Generic OIDC 提供程序的 OpenID Connect 颁发者
+- 默认值: `-`
+- 示例: `https://sso.example.com`
+
 <Callout>
   如果您需要使用其他身份验证服务提供商，可以提交
   [功能请求](https://github.com/lobehub/lobe-chat/issues/new/choose) 或 Pull Request。
 </Callout>
+
+## Clerk
+
+### `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY`
+
+- 类型：必选
+- 描述： Clerk 应用程序的 Publishable key。您可以在[这里](https://dashboard.clerk.com)访问，并导航到 API Keys 以查看。
+- 默认值：`-`
+- 示例： `pk_test_Zmxvd4luZy1wdW1hLTIyLmNsXXJrTmFjY291bnRzLmRldiQ` （测试环境） / `pk_live_Y2xlcdsubG9iZWh1Yi1cbmMuY24k` （生产环境）
+
+### `CLERK_SECRET_KEY`
+
+- 类型：必选
+- 描述： Clerk 应用程序的 Secret key。您可以在[这里](https://dashboard.clerk.com)访问，并导航到 API Keys 以查看。
+- 默认值：`-`
+- 示例： `sk_test_513Ma0P7IAWM1XMv4waxZjRYRajWTaCfJLjpEO3SD2` （测试环境） / `sk_live_eMMlHjwJvZFUfczFljSKqZdwQtLvmczmsJSNmdrpeZ`（生产环境）

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

@@ -36,14 +36,7 @@ LobeChat provides some additional configuration options during deployment, which
 
 When using the `random` mode, a random API Key will be selected from the available multiple API Keys.
 
-When using the `turn` mode, the API Keys will be retrieved in a round-robin manner according to the specified order.
-
-### `ENABLE_OAUTH_SSO`
-
-- Type: Optional
-- Description: Enable Single Sign-On (SSO) for LobeChat. Set to `1` to enable SSO. For more information, see [Authentication Services](#authentication-services).
-- Default: -
-- Example: `1`
+When using the `turn` mode, the API Keys will be retrieved in a polling manner according to the specified order.
 
 ### `NEXT_PUBLIC_BASE_PATH`
 
@@ -57,7 +50,7 @@ When using the `turn` mode, the API Keys will be retrieved in a round-robin mann
 - Type: Optional
 - Description: Used to configure the default settings for the LobeChat default agent. It supports various data types and structures, including key-value pairs, nested fields, array values, and more.
 - Default: -
-- Example: `'model=gpt-4-1106-preview;params.max_tokens=300;plugins=search-engine,lobe-image-designer`
+- Example: `'model=gpt-4-1106-preview;params.max_tokens=300;plugins=search-engine,lobe-image-designer'`
 
 The `DEFAULT_AGENT_CONFIG` is used to configure the default settings for the LobeChat default agent. It supports various data types and structures, including key-value pairs, nested fields, array values, and more. The table below provides detailed information on the configuration options, examples, and corresponding explanations for the `DEFAULT_AGENT_CONFIG` environment variable:
 
@@ -68,8 +61,8 @@ The `DEFAULT_AGENT_CONFIG` is used to configure the default settings for the Lob
 | Array | `plugins=search-engine,lobe-image-designer` | Enable the `search-engine` and `lobe-image-designer` plugins. |
 | Chinese Comma | `plugins=search-engine，lobe-image-designer` | Same as above, demonstrating support for Chinese comma separation. |
 | Multiple Configurations | `model=glm-4;provider=zhipu` | Set the model to `glm-4` and the model provider to `zhipu`. |
-| Numeric Value | `params.max_tokens=300` | Set the maximum tokens to `300`. |
-| Boolean Value | `enableAutoCreateTopic=true` | Enable automatic topic creation. |
+| Numeric Value | `params.max_tokens=300`, `chatConfig.historyCount=5` | Set the maximum tokens to `300`, Set the number of historical messages to 5. |
+| Boolean Value | `chatConfig.enableAutoCreateTopic=true`, `chatConfig.enableCompressThreshold=true`, `chatConfig.enableHistoryCount=true` | Enable automatic topic creation, History length compression threshold, number of historical records. |
 | Special Characters | `inputTemplate="Hello; I am a bot;"` | Set the input template to `Hello; I am a bot;`. |
 | Error Handling | `model=gpt-4;maxToken` | Ignore invalid entry `maxToken` and only parse `model=gpt-4`. |
 | Value Override | `model=gpt-4;model=gpt-4-1106-preview` | If a key is repeated, use the value that appears last; in this case, the value of `model` is `gpt-4-1106-preview`. |
@@ -78,6 +71,28 @@ Further reading:
 
 - [[RFC] 022 - Default Assistant Parameters Configuration via Environment Variables](https://github.com/lobehub/lobe-chat/discussions/913)
 
+### `FEATURE_FLAGS`
+
+- Type: Optional
+- Description: Used to control LobeChat's feature functionalities. Supports multiple feature flags, using `+` to add a feature and `-` to disable a feature. Separate multiple feature flags with a comma `,` and enclose the entire value in quotes `"` to avoid parsing errors.
+- Default: `-`
+- Example: `"-welcome_suggest"`
+
+For specific content, please refer to the [Feature Flags](/docs/self-hosting/advanced/feature-flags) documentation.
+
+### `PROXY_URL`
+
+- Type: Optional
+- Description: Used to specify the proxy URL for connecting to external services. The value of this variable should be different in different deployment environments.
+- Default: -
+- Example: `http://127.0.0.1:7890` or `socks5://localhost:7891`
+
+<Callout type="info">
+  If you're using Docker Desktop on Windows or macOS, it relies on a virtual machine. In this setup,
+  `localhost` / `127.0.0.1` refers to the localhost of the container itself. In such cases, please
+  try using `host.docker.internal` instead of `localhost`.
+</Callout>
+
 ## Plugin Service
 
 ### `PLUGINS_INDEX_URL`