@lobehub/chat 1.44.3 → 1.45.0

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

@@ -26,60 +26,55 @@ The best practice in this area is to use a file storage service (S3) to store im
 <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.
+  These are the two keys required by all S3 compatible storage services to access the S3 storage service, not detailed here.
 
-### `S3_ENDPOINT`
+  ### `S3_ENDPOINT`
 
-The request endpoint of the storage bucket. Note that this link should not contain the name of the storage bucket.
+  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>
+  <Callout type={'warning'}>
+    `S3_ENDPOINT` must remove the suffix path, otherwise the uploaded files will not be accessible
+  </Callout>
 
-For example, for Cloudflare:
+  For example, for Cloudflare:
 
-```shell
-S3_ENDPOINT=https://0b33a03b5c993fd2f453379dc36558e5.r2.cloudflarestorage.com
-```
+  ```shell
+  S3_ENDPOINT=https://0b33a03b5c993fd2f453379dc36558e5.r2.cloudflarestorage.com
+  ```
 
-### `S3_BUCKET` and `S3_REGION`
+  ### `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.
+  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`
+  ### `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.
+  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`
+  ### `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.
+  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>
+  <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`
+  ### `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.
+  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.
 
-`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:
+    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>
+    - 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>
-
+    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
@@ -88,6 +83,7 @@ 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>
 

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

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

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

@@ -139,9 +139,9 @@ export type UserModelProviderConfig = Record<string, 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.             |
+| 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.             |                                |

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

@@ -30,7 +30,7 @@ https://lobehub.com/?settings=<JSON格式的设置对象>
 https://lobehub.com/?settings={"keyVaults":{"openai":{"apiKey":"user-key","baseURL":"https://your-proxy.com/v1"}}}
 ```
 
-JSON格式的设置示例：
+JSON 格式的设置示例：
 
 ```json
 {
@@ -70,7 +70,7 @@ console.log(url);
 
 - 参数及其类型
 
-| 参数名称   | 类型                       |
+| 参数名称       | 类型                         |
 | ---------- | -------------------------- |
 | anthropic  | `OpenAICompatibleKeyVault` |
 | azure      | `AzureOpenAIKeyVault`      |
@@ -90,25 +90,25 @@ console.log(url);
 
 - Type `OpenAICompatibleKeyVault`
 
-| 参数    | 类型   | 描述              |
-| ------- | ------ | ----------------- |
+| 参数      | 类型     | 描述          |
+| ------- | ------ | ----------- |
 | apiKey  | string | 模型的 API 密钥。 |
-| baseURL | string | 模型API端点。     |
+| baseURL | string | 模型 API 端点。  |
 
 - Type `AzureOpenAIKeyVault`
 
-| 参数       | 类型   | 描述                       |
-| ---------- | ------ | -------------------------- |
+| 参数         | 类型     | 描述                     |
+| ---------- | ------ | ---------------------- |
 | apiVersion | string | Azure OpenAI 的 API 版本。 |
-| apiKey     | string | 模型的 API 密钥。          |
-| baseURL    | string | 模型API端点。              |
+| apiKey     | string | 模型的 API 密钥。            |
+| baseURL    | string | 模型 API 端点。             |
 
 - Type `AWSBedrockKeyVault`
 
-| 参数            | 类型   | 描述                        |
-| --------------- | ------ | --------------------------- |
+| 参数              | 类型     | 描述                    |
+| --------------- | ------ | --------------------- |
 | accessKeyId     | string | AWS Bedrock 的访问密钥 ID。 |
-| region          | string | AWS Bedrock 的区域。        |
+| region          | string | AWS Bedrock 的区域。      |
 | secretAccessKey | string | AWS Bedrock 的访问密钥。    |
 
 ### languageModel
@@ -117,7 +117,7 @@ console.log(url);
 export type UserModelProviderConfig = Record<string, ProviderConfig>;
 ```
 
-| 参数名称   | 类型             |
+| 参数名称       | 类型               |
 | ---------- | ---------------- |
 | anthropic  | `ProviderConfig` |
 | azure      | `ProviderConfig` |
@@ -137,9 +137,9 @@ export type UserModelProviderConfig = Record<string, ProviderConfig>;
 
 - 类型 `ProviderConfig`
 
-| 参数                | TS 类型  | 描述                                         |
-| ------------------- | -------- | -------------------------------------------- |
-| autoFetchModelLists | boolean  | 是否自动获取模型列表。                       |
-| enabled             | boolean  | 是否启用该模型。                             |
-| enabledModels       | string[] | 启用的模型的 ID。                            |
-| fetchOnClient       | boolean  | 是否在客户端发起请求，默认在服务端发起请求。 |
+| 参数                  | TS 类型     | 描述                     |
+| ------------------- | --------- | ---------------------- |
+| autoFetchModelLists | boolean   | 是否自动获取模型列表。            |
+| enabled             | boolean   | 是否启用该模型。               |
+| enabledModels       | string\[] | 启用的模型的 ID。             |
+| fetchOnClient       | boolean   | 是否在客户端发起请求，默认在服务端发起请求。 |

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

@@ -30,27 +30,15 @@ If you deployed your project according to the one-click deployment steps in the
 
 After forking the project, due to Github's limitations, you need to manually enable Workflows on the Actions page of your forked project and start the Upstream Sync Action. Once enabled, you can set up automatic updates to occur every hour.
 
-<Image
-  alt="Enable Automatic Updates S1"
-  src="https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/266985117-4d48fe7b-0412-4667-8129-b25ebcf2c9de.png"
-/>
+<Image alt="Enable Automatic Updates S1" src="https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/266985117-4d48fe7b-0412-4667-8129-b25ebcf2c9de.png" />
 
-<Image
-  alt="Enable Automatic Updates S2"
-  src="https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/266985177-7677b4ce-c348-4145-9f60-829d448d5be6.png"
-/>
+<Image alt="Enable Automatic Updates S2" 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="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"
-/>
+<Image alt="Manually Sync 'Update Branch'" src="https://github.com/user-attachments/assets/d524c20d-306a-45bc-971b-96920b87fab4" />
 
 ## `B` Docker Deployment
 
@@ -59,34 +47,33 @@ Upgrading the Docker deployment version is very simple, you just need to redeplo
 <Steps>
   ### Stop and Remove the Current Running LobeChat Container
 
-Assuming the LobeChat container is named `lobe-chat`, use the following commands to stop and remove the currently running LobeChat container:
+  Assuming the LobeChat container is named `lobe-chat`, use the following commands to stop and remove the currently running LobeChat container:
 
-```fish
-docker stop lobe-chat
-docker rm lobe-chat
-```
+  ```fish
+  docker stop lobe-chat
+  docker rm lobe-chat
+  ```
 
-### Pull the Latest LobeChat Image
+  ### Pull the Latest LobeChat Image
 
-Use the following command to pull the latest Docker image for LobeChat:
+  Use the following command to pull the latest Docker image for LobeChat:
 
-```fish
-docker pull lobehub/lobe-chat
-```
+  ```fish
+  docker pull lobehub/lobe-chat
+  ```
 
-### Restart the Docker Container
+  ### Restart the Docker Container
 
-Redeploy the LobeChat container using the newly pulled image:
-
-```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
-```
+  Redeploy the LobeChat container using the newly pulled image:
 
+  ```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
+  ```
 </Steps>
 
 Ensure that you have sufficient permissions to stop and remove the container before executing these commands, and that Docker has sufficient permissions to pull the new image.
@@ -94,80 +81,77 @@ Ensure that you have sufficient permissions to stop and remove the container bef
 <Callout type={'tip'}>
   **If I redeploy, will I lose my local chat records?**
 
-No need to worry, you won't. All of LobeChat's chat records are stored in your local browser. Therefore, when redeploying LobeChat using Docker, your chat records will not be lost.
-
+  No need to worry, you won't. All of LobeChat's chat records are stored in your local browser. Therefore, when redeploying LobeChat using Docker, your chat records will not be lost.
 </Callout>
 
 If you wish to automate the above steps, you can follow the method below and use Crontab scheduling to complete it. The specific steps are as follows.
 
 <Steps>
+  ### Write automatic update scripts and configuration files
 
-### Write automatic update scripts and configuration files
-
-First, create a `lobe.env` configuration file with various environment variables, for example:
+  First, create a `lobe.env` configuration file with various environment variables, for example:
 
-```env
-OPENAI_API_KEY=sk-xxxx
-OPENAI_PROXY_URL=https://api-proxy.com/v1
-ACCESS_CODE=arthals2333
-OPENAI_MODEL_LIST=-gpt-4,-gpt-4-32k,-gpt-3.5-turbo-16k,gpt-3.5-turbo-1106=gpt-3.5-turbo-16k,gpt-4-0125-preview=gpt-4-turbo,gpt-4-vision-preview=gpt-4-vision
-```
+  ```env
+  OPENAI_API_KEY=sk-xxxx
+  OPENAI_PROXY_URL=https://api-proxy.com/v1
+  ACCESS_CODE=arthals2333
+  OPENAI_MODEL_LIST=-gpt-4,-gpt-4-32k,-gpt-3.5-turbo-16k,gpt-3.5-turbo-1106=gpt-3.5-turbo-16k,gpt-4-0125-preview=gpt-4-turbo,gpt-4-vision-preview=gpt-4-vision
+  ```
 
-Then, you can use the following script to automate the update:
+  Then, you can use the following script to automate the update:
 
-```bash
-#!/bin/bash
-# auto-update-lobe-chat.sh
+  ```bash
+  #!/bin/bash
+  # auto-update-lobe-chat.sh
 
-# Set up proxy (optional)
-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
+  # Set up proxy (optional)
+  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
 
-# Pull the latest image and store the output in a variable
-output=$(docker pull lobehub/lobe-chat:latest 2>&1)
+  # Pull the latest image and store the output in a variable
+  output=$(docker pull lobehub/lobe-chat:latest 2>&1)
 
-# Check if the pull command was executed successfully
-if [ $? -ne 0 ]; then
-  exit 1
-fi
+  # Check if the pull command was executed successfully
+  if [ $? -ne 0 ]; then
+    exit 1
+  fi
 
-# Check if the output contains a specific string
-echo "$output" | grep -q "Image is up to date for lobehub/lobe-chat:latest"
+  # Check if the output contains a specific string
+  echo "$output" | grep -q "Image is up to date for lobehub/lobe-chat:latest"
 
-# If the image is already up to date, do nothing
-if [ $? -eq 0 ]; then
-  exit 0
-fi
+  # If the image is already up to date, do nothing
+  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)"
+  # Remove the old container
+  echo "Removed: $(docker rm -f 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)"
+  # 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}')"
+  # 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 'lobehub/lobe-chat-database' | grep -v 'latest' | awk '{print $3}' | xargs -r docker rmi > /dev/null 2>&1
-echo "Removed old images."
-```
-
-<Callout type={'warning'}>
-  This script can be used in Crontab, but please ensure that your Crontab can find the correct
-  Docker command. It is recommended to use absolute paths.
-</Callout>
+  # Clean up unused images
+  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."
+  ```
 
-Configure Crontab to execute the script every 5 minutes:
+  <Callout type={'warning'}>
+    This script can be used in Crontab, but please ensure that your Crontab can find the correct
+    Docker command. It is recommended to use absolute paths.
+  </Callout>
 
-### Configure Crontab to automatically execute scripts
+  Configure Crontab to execute the script every 5 minutes:
 
-The following command configures Crontab to execute scripts every 5 minutes, or as often as you like:
+  ### Configure Crontab to automatically execute scripts
 
-```bash
-*/5 * * * * /path/to/auto-update-lobe-chat.sh >> /path/to/auto-update-lobe-chat.log 2>&1
-```
+  The following command configures Crontab to execute scripts every 5 minutes, or as often as you like:
 
+  ```bash
+  */5 * * * * /path/to/auto-update-lobe-chat.sh >> /path/to/auto-update-lobe-chat.log 2>&1
+  ```
 </Steps>