2.6.2:重构Docker运行架构；新增上传时目录自动建议功能

Author: MarSeventh

README.md

@@ -66,6 +66,7 @@
 > ### 升级前：备份数据
 >
 > 1. 备份数据：在管理面板下载备份文件（若原来使用本地R2存储需要全部下载重传）
+> 2. 备份data文件夹
 >
 > ### 升级步骤
 >
@@ -91,7 +92,7 @@
 >
 > 4. 恢复数据：在管理面板恢复全部数据（原来的R2文件需要重传）
 > 
-> ### 升级异常：恢复数据
+> ### 升级异常：回退版本
 >
 > 如果升级后出现异常，可通过以下步骤回退：
 >
@@ -101,14 +102,7 @@
 >    docker compose down
 >    ```
 >
-> 2. 恢复备份数据（将 `20260304` 替换为你实际的备份日期）：
->
->    ```bash
->    rm -rf ./data
->    cp -r ./data_backup_20260304 ./data
->    ```
->
-> 3. 回退到旧版本镜像：
+> 2. 回退到旧版本镜像：
 >
 >    ```bash
 >    # amd64
@@ -124,7 +118,7 @@
 >    ```
 >
 > **注意事项**：
-> - 升级前请务必确认备份完整
+> - 升级前请务必确认备份完整，必要时备份一份data文件夹
 > - 如果你使用了自定义的 `docker-compose.yml` 配置（如自定义端口、环境变量等），升级时请注意保留
 > - 遇到问题请先查阅文档和已有 issues，或提交新的 issue
 

README_en.md

@@ -60,6 +60,7 @@
 > ### Before Upgrading: Back Up Data
 >
 > 1. Back up data: Download the backup file from the admin panel (if you were using local R2 storage, you need to download and re-upload all files)
+> 2. Back up the data folder
 >
 > ### Upgrade Steps
 >
@@ -85,7 +86,7 @@
 >
 > 4. Restore data: Restore all data from the admin panel (R2 files from the old version need to be re-uploaded)
 > 
-> ### Rollback: Restore Data
+> ### Rollback to Previous Version
 >
 > If something goes wrong after upgrading, follow these steps to roll back:
 >
@@ -95,14 +96,7 @@
 >    docker compose down
 >    ```
 >
-> 2. Restore the backup (replace `20260304` with your actual backup date):
->
->    ```bash
->    rm -rf ./data
->    cp -r ./data_backup_20260304 ./data
->    ```
->
-> 3. Pull the previous image version:
+> 2. Pull the previous image version:
 >
 >    ```bash
 >    # amd64
@@ -118,7 +112,7 @@
 >    ```
 >
 > **Notes**:
-> - Make sure the backup is complete before upgrading
+> - Make sure the backup is complete before upgrading, and back up the data folder if necessary
 > - If you have a custom `docker-compose.yml` (e.g., custom ports, environment variables), preserve those settings during the upgrade
 > - For issues, please check the documentation and existing issues first, or submit a new issue