chore(deps): bump jsdom from 26.1.0 to 30.0.1 in /web

Bumps [jsdom](https://github.com/jsdom/jsdom) from 26.1.0 to 30.0.1. - [Release notes](https://github.com/jsdom/jsdom/releases) - [Commits](https://github.com/jsdom/jsdom/compare/v26.1.0...v30.0.1) --- updated-dependencies: - dependency-name: jsdom dependency-version: 30.0.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Merge pull request #129 from Awuqing/dependabot/npm_and_yarn/web/react-router-dom-7.0.0
2026-08-25 01:59:46 +08:00 · 2026-08-23 19:25:27 +00:00 · 2026-08-17 18:03:34 +08:00 · 2026-08-17 18:02:52 +08:00 · 2026-08-17 18:02:49 +08:00 · 2026-08-17 09:58:30 +00:00
430 changed files with 73641 additions and 5187 deletions
--- a/.dockerignore
+++ b/.dockerignore
@@ -0,0 +1,26 @@
+# Dependencies
+web/node_modules/
+
+# Build artifacts
+server/bin/
+web/dist/
+
+# Data & logs
+data/
+*.db
+*.log
+
+# IDE & OS
+.idea/
+.vscode/
+*.swp
+*.swo
+.DS_Store
+
+# Git
+.git/
+.github/
+
+# Docker
+Dockerfile
+docker-compose*.yml
--- a/.editorconfig
+++ b/.editorconfig
@@ -0,0 +1,25 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.{go,mod,sum}]
+indent_style = tab
+indent_size = 4
+
+[Makefile]
+indent_style = tab
+
+[*.{js,jsx,ts,tsx,json,yml,yaml,css,scss,html,md,mdx}]
+indent_style = space
+indent_size = 2
+
+[*.sh]
+indent_style = space
+indent_size = 4
+
+[*.md]
+trim_trailing_whitespace = false
--- a/.gitattributes
+++ b/.gitattributes
@@ -0,0 +1,15 @@
+* text=auto eol=lf
+
+*.bat text eol=crlf
+*.cmd text eol=crlf
+
+*.gif binary
+*.ico binary
+*.jpg binary
+*.jpeg binary
+*.png binary
+*.webp binary
+*.woff binary
+*.woff2 binary
+*.gz binary
+*.zip binary
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -1,14 +1,14 @@
 ---
-name: "\U0001F41B Bug 报告"
-about: "报告一个 Bug，帮助我们改进 BackupX"
+name: "Bug 报告"
+about: "提交可复现的缺陷报告"
 title: "[Bug] "
 labels: ["bug"]
 assignees: []
 ---

-## 描述
+## 问题描述

-<!-- 清晰简洁地描述这个 Bug -->
+<!-- 清晰说明发生了什么，以及它为什么是缺陷。 -->

 ## 复现步骤

@@ -18,26 +18,39 @@ assignees: []

 ## 期望行为

-<!-- 描述你期望发生什么 -->
+<!-- 描述正确结果。 -->

 ## 实际行为

-<!-- 描述实际发生了什么 -->
+<!-- 描述实际结果，包括稳定复现还是偶发。 -->

 ## 环境信息

- **OS**: <!-- 例如 Ubuntu 22.04 -->
- **Go 版本**: <!-- 例如 1.21 -->
- **Node.js 版本**: <!-- 例如 18.17 -->
- **浏览器**: <!-- 例如 Chrome 120 -->
- **BackupX 版本**: <!-- 例如 v1.0.0 -->
+- BackupX 版本或提交：
+- 部署方式（Docker、裸机、集群）：
+- 操作系统与架构：
+- 数据库或备份类型：
+- 浏览器版本（仅界面问题）：
+- 是否使用代理、私有 CA 或堡垒机：
+
+## 最小配置
+
+<!-- 仅保留复现所需字段。删除密码、Token、域名、IP 和存储凭据。 -->
+
+```yaml
+
+```

 ## 相关日志

-```
-<!-- 粘贴相关日志输出 -->
+<!-- 附问题发生前后的最小日志片段，并先删除所有敏感信息。 -->
+
+```text
+
 ```

-## 截图
+## 补充信息

-<!-- 如有截图请附上 -->
+<!-- 可附截图、相关 Issue、临时缓解方式或其他上下文。 -->
+
+请勿提交数据库文件、完整配置、备份数据、API Key、Agent Token、安装命令或未脱敏日志。安全漏洞请使用私密漏洞报告入口。
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,5 +1,5 @@
 blank_issues_enabled: false
 contact_links:
-  - name: 💬 讨论区 / Discussions
-    url: https://github.com/Awuqing/GoogleDriverBackupEveryDay/discussions
-    about: 提问、讨论功能想法或分享使用经验
+  - name: 安全漏洞 / Security vulnerability
+    url: https://github.com/Awuqing/BackupX/security/advisories/new
+    about: 请通过私密渠道报告安全问题，不要创建公开 Issue。
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -1,23 +1,36 @@
 ---
-name: "\U0001F680 功能请求"
-about: "建议一个新功能或改进"
+name: "功能请求"
+about: "建议一个可落地的新功能或改进"
 title: "[Feature] "
 labels: ["enhancement"]
 assignees: []
 ---

-## 需求描述
-
-<!-- 清晰简洁地描述你希望的功能 -->
-
 ## 使用场景

-<!-- 描述你在什么场景下需要这个功能 -->
+<!-- 描述谁在什么环境中遇到了什么问题。 -->

-## 建议的解决方案
+## 期望结果

-<!-- 描述你认为应该如何实现（可选） -->
+<!-- 说明用户最终需要完成的任务，不要只描述界面元素。 -->
+
+## 建议方案
+
+<!-- 可选：描述 API、配置、工作流或界面交互。 -->
+
+## 替代方案
+
+<!-- 说明当前绕过方式，以及它为什么不足。 -->
+
+## 兼容性与风险
+
+<!-- 是否影响现有配置、数据格式、部署方式、权限或集群节点。 -->
+
+## 验收标准
+
+- [ ]
+- [ ]

 ## 补充信息

-<!-- 任何其他相关信息、截图或上下文 -->
+<!-- 可附相关文档、日志、截图或同类实现。不要附敏感信息。 -->
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,29 +1,48 @@
-## Pull Request
+## 变更说明 / Summary

-### 变更类型 / Type of Change
+<!-- 说明做了什么、为什么需要，以及对用户或运维人员的影响。 -->

- [ ] 🐛 Bug 修复 (非破坏性变更)
- [ ] ✨ 新功能 (非破坏性变更)
- [ ] 💥 破坏性变更 (修复或功能导致现有功能变更)
- [ ] 📝 文档更新
- [ ] ♻️ 代码重构 (不影响功能)
- [ ] ⚡ 性能优化
+## 变更类型 / Type of Change

-### 描述 / Description
+- [ ] 缺陷修复
+- [ ] 新功能
+- [ ] 破坏性变更
+- [ ] 性能优化
+- [ ] 重构或工程化
+- [ ] 文档更新

-<!-- 描述你做了什么更改以及为什么 -->
+## 相关 Issue / Related Issue

-### 相关 Issue / Related Issue
+<!-- 例如：Closes #123。没有关联 Issue 时写“无”。 -->

-<!-- 关联的 Issue 编号，如 Fixes #123 -->
+## 验证 / Validation

-### 测试 / Testing
+<!-- 只勾选实际执行过的项目，并在下方补充无法执行的原因。 -->

- [ ] 后端测试通过 (`go test ./...`)
- [ ] 前端测试通过 (`npm run test`)
- [ ] 前端构建成功 (`npm run build`)
- [ ] 已在本地环境手动测试
+- [ ] 后端格式、静态检查与测试通过
+- [ ] 前端测试与生产构建通过
+- [ ] 文档类型检查与中英文生产构建通过
+- [ ] 配置、迁移或部署兼容性已验证
+- [ ] 已完成与变更范围相符的手动验证

-### 截图 / Screenshots
+验证命令与结果：

-<!-- 如有 UI 变更请附上截图 -->
+```text
+
+```
+
+## 风险与回滚 / Risk and Rollback
+
+<!-- 说明兼容性风险、数据迁移、配置变化和回滚方法。无风险时写“无”。 -->
+
+## 界面变更 / UI Changes
+
+<!-- 有界面变更时附前后截图；无界面变更时写“无”。 -->
+
+## 提交前检查 / Checklist
+
+- [ ] 提交信息符合 Conventional Commits
+- [ ] 未提交密钥、Token、真实配置、数据库或日志
+- [ ] 新行为已补充测试和中英文文档
+- [ ] 前端未使用 Emoji、渐变、阴影、独立字体或超过 4px 的圆角
+- [ ] 没有夹带与本 PR 无关的格式化或重构
--- a/.github/SECURITY.md
+++ b/.github/SECURITY.md
@@ -1,34 +1,40 @@
-# 安全漏洞披露政策 / Security Policy
+# 安全策略 / Security Policy

-## 支持的版本 / Supported Versions
+## 支持范围 / Supported Versions

-| Version | Supported          |
-|---------|--------------------|
-| latest  | ✅                 |
-| < latest | ❌                |
+安全修复面向最新稳定版本和 `main` 分支。旧版本不会单独维护安全补丁；升级前请先阅读对应 Release Notes 和升级恢复文档。

-## 报告安全漏洞 / Reporting a Vulnerability
+Security fixes target the latest stable release and the `main` branch. Older versions do not receive separate security patches. Review the release notes and upgrade documentation before updating.

-如果您发现了安全漏洞，**请不要通过公开 Issue 报告**。
+| Version | Status |
+|---------|--------|
+| Latest stable release | Supported |
+| `main` | Development support |
+| Older releases | Unsupported |

-请发送邮件至项目维护者，包含以下信息：
+## 报告漏洞 / Reporting a Vulnerability

-1. 漏洞描述
-2. 复现步骤
-3. 受影响的版本
-4. 可能的影响范围
+请勿通过公开 Issue、Discussion 或 Pull Request 披露安全漏洞。使用 GitHub 的[私密漏洞报告入口](https://github.com/Awuqing/BackupX/security/advisories/new)提交报告。

-我们会在 48 小时内确认收到并开始处理。
+Do not disclose vulnerabilities in a public Issue, Discussion, or Pull Request. Submit the report through GitHub's [private vulnerability reporting form](https://github.com/Awuqing/BackupX/security/advisories/new).

---
+报告应包含：

-If you discover a security vulnerability, **please do NOT open a public issue**.
+1. 受影响版本或提交；
+2. 漏洞描述、攻击前提和影响范围；
+3. 最小复现步骤或验证代码；
+4. 已知缓解措施；
+5. 希望使用的署名信息。

-Instead, email the project maintainer with the following details:
+不要上传真实密钥、Token、备份数据、数据库或包含客户信息的日志。必要时请先脱敏，并使用最小化测试数据。

-1. Description of the vulnerability
-2. Steps to reproduce
-3. Affected versions
-4. Potential impact
+Do not upload real credentials, tokens, backup data, databases, or logs containing customer information. Redact sensitive values and use minimal test data.

-We will acknowledge receipt within 48 hours and begin working on a fix.
+## 处理流程 / Response Process
+
+- 维护者会尽快确认报告并进行初步分级；
+- 修复期间请保持细节私密，避免影响仍未升级的部署；
+- 修复发布后会在安全公告或 Release Notes 中说明受影响范围、缓解措施和升级版本；
+- 披露时间由报告者与维护者协调确定。
+
+The maintainer will acknowledge and triage the report as soon as practical. Details should remain private until a fix and coordinated disclosure are ready.
--- a/.github/dependabot.yml
+++ b/.github/dependabot.yml
@@ -0,0 +1,86 @@
+version: 2
+
+updates:
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+      day: monday
+      time: "03:00"
+      timezone: Asia/Shanghai
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: chore(deps)
+    groups:
+      github-actions:
+        patterns:
+          - "*"
+
+  - package-ecosystem: gomod
+    directory: /server
+    schedule:
+      interval: weekly
+      day: monday
+      time: "03:10"
+      timezone: Asia/Shanghai
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: chore(deps)
+    groups:
+      go-minor-and-patch:
+        patterns:
+          - "*"
+        update-types:
+          - minor
+          - patch
+
+  - package-ecosystem: npm
+    directory: /web
+    schedule:
+      interval: weekly
+      day: monday
+      time: "03:20"
+      timezone: Asia/Shanghai
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: chore(deps)
+    groups:
+      web-minor-and-patch:
+        patterns:
+          - "*"
+        update-types:
+          - minor
+          - patch
+
+  - package-ecosystem: npm
+    directory: /docs-site
+    schedule:
+      interval: weekly
+      day: monday
+      time: "03:30"
+      timezone: Asia/Shanghai
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: chore(deps)
+    groups:
+      docs-minor-and-patch:
+        patterns:
+          - "*"
+        update-types:
+          - minor
+          - patch
+
+  - package-ecosystem: docker
+    directory: /
+    schedule:
+      interval: weekly
+      day: monday
+      time: "03:40"
+      timezone: Asia/Shanghai
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: chore(deps)
+    groups:
+      container-images:
+        patterns:
+          - "*"
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -2,23 +2,50 @@ name: CI

 on:
  push:
-    branches: [main, master]
+    branches: [main]
  pull_request:
-    branches: [main, master]
+    branches: [main]
+  workflow_dispatch:
+
+# 最小权限：构建/测试仅需读取仓库内容，显式声明以收敛默认的可写令牌。
+permissions:
+  contents: read
+
+concurrency:
+  group: ci-${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true

 jobs:
  backend:
    name: Go Build & Test
    runs-on: ubuntu-latest
+    timeout-minutes: 20
    steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7

      - name: Set up Go
-        uses: actions/setup-go@v5
+        uses: actions/setup-go@v7
        with:
-          go-version: '1.21'
+          go-version: '1.25'
          cache-dependency-path: server/go.sum

+      - name: Verify modules
+        working-directory: server
+        run: go mod verify
+
+      - name: Check formatting
+        working-directory: server
+        run: |
+          unformatted="$(gofmt -l .)"
+          if [ -n "$unformatted" ]; then
+            printf '%s\n' "$unformatted"
+            exit 1
+          fi
+
+      - name: Vet
+        working-directory: server
+        run: go vet ./...
+
      - name: Build
        working-directory: server
        run: go build ./...
@@ -30,13 +57,14 @@ jobs:
  frontend:
    name: React Build & Test
    runs-on: ubuntu-latest
+    timeout-minutes: 20
    steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7

      - name: Set up Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v7
        with:
-          node-version: '18'
+          node-version: '24'
          cache: 'npm'
          cache-dependency-path: web/package-lock.json

@@ -44,14 +72,10 @@ jobs:
        working-directory: web
        run: npm ci

-      - name: Type Check
-        working-directory: web
-        run: npx tsc --noEmit -p tsconfig.json
-
      - name: Test
        working-directory: web
        run: npm run test

-      - name: Build
+      - name: Type Check & Build
        working-directory: web
        run: npm run build
--- a/.github/workflows/docs.yml
+++ b/.github/workflows/docs.yml
@@ -0,0 +1,80 @@
+name: Deploy Docs
+
+# 触发条件：
+#   - PR 修改 docs-site/ 时执行类型检查和构建
+#   - 推送 main 时构建并部署 GitHub Pages
+#   - 手动触发（在 Actions 页面）
+on:
+  pull_request:
+    branches:
+      - main
+    paths:
+      - 'docs-site/**'
+      - '.github/workflows/docs.yml'
+  push:
+    branches:
+      - main
+    paths:
+      - 'docs-site/**'
+      - '.github/workflows/docs.yml'
+  workflow_dispatch:
+
+# 默认只读；Pages 写权限仅授予部署任务。
+permissions:
+  contents: read
+
+# 同一分支只保留最新一次构建，避免旧提交覆盖新结果。
+concurrency:
+  group: docs-${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  build:
+    name: Build Docs
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    defaults:
+      run:
+        working-directory: docs-site
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v7
+        with:
+          node-version: '24'
+          cache: 'npm'
+          cache-dependency-path: docs-site/package-lock.json
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Type check
+        run: npm run typecheck
+
+      - name: Build site
+        run: npm run build
+
+      - name: Upload artifact
+        if: github.event_name != 'pull_request'
+        uses: actions/upload-pages-artifact@v5
+        with:
+          path: docs-site/build
+
+  deploy:
+    name: Deploy Docs
+    if: github.event_name != 'pull_request'
+    needs: build
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    permissions:
+      pages: write
+      id-token: write
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v5
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -1,63 +1,232 @@
+# 自动化发版流水线
+#
+# 触发方式：
+#   1. 推送 tag：git tag v1.2.3 && git push --tags
+#   2. 手动触发：GitHub Actions 页面 → Run workflow → 输入版本号
+#
+# 产出物：
+#   - GitHub Release：linux/amd64 + linux/arm64 预编译 tar.gz
+#   - Docker Hub：awuqing/backupx:latest + awuqing/backupx:v1.2.3（多架构）
+#
+# 前置配置：
+#   在仓库 Settings → Secrets → Actions 添加：
+#   - DOCKERHUB_USERNAME（Docker Hub 用户名）
+#   - DOCKERHUB_TOKEN（Docker Hub Access Token）
+
 name: Release

 on:
  push:
    tags:
      - 'v*'
+  workflow_dispatch:
+    inputs:
+      version:
+        description: '版本号（如 v1.2.3）'
+        required: true
+        type: string

 permissions:
-  contents: write
+  contents: read
+
+# 统一版本号：tag 推送取 ref_name，手动触发取 inputs.version
+env:
+  VERSION: ${{ github.event.inputs.version || github.ref_name }}
+
+concurrency:
+  group: release-${{ github.ref }}-${{ github.event.inputs.version || 'tag' }}
+  cancel-in-progress: false

 jobs:
-  release:
-    name: Build & Release
+  # ─── Job 0: 校验版本与测试 ───
+  verify:
+    name: Validate Release
    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        goos: [linux]
-        goarch: [amd64, arm64]
+    timeout-minutes: 25
    steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
+
+      - name: Validate release input
+        shell: bash
+        env:
+          RELEASE_VERSION: ${{ env.VERSION }}
+          RELEASE_EVENT: ${{ github.event_name }}
+          RELEASE_REF: ${{ github.ref }}
+        run: |
+          if [[ ! "$RELEASE_VERSION" =~ ^v[0-9]+\.[0-9]+\.[0-9]+(-[0-9A-Za-z][0-9A-Za-z.-]*)?$ ]]; then
+            echo "Version must be a SemVer tag such as v1.2.3 or v1.2.3-rc.1"
+            exit 1
+          fi
+          if [[ "$RELEASE_EVENT" == "workflow_dispatch" && "$RELEASE_REF" != "refs/heads/main" ]]; then
+            echo "Manual releases must run from the main branch"
+            exit 1
+          fi

      - name: Set up Go
-        uses: actions/setup-go@v5
+        uses: actions/setup-go@v7
        with:
-          go-version: '1.21'
+          go-version: '1.25'
          cache-dependency-path: server/go.sum

+      - name: Verify backend
+        working-directory: server
+        run: |
+          go mod verify
+          unformatted="$(gofmt -l .)"
+          if [ -n "$unformatted" ]; then
+            printf '%s\n' "$unformatted"
+            exit 1
+          fi
+          go vet ./...
+          go test ./...
+
      - name: Set up Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v7
        with:
-          node-version: '18'
+          node-version: '24'
          cache: 'npm'
          cache-dependency-path: web/package-lock.json

-      - name: Build frontend
+      - name: Verify frontend
+        working-directory: web
+        run: |
+          npm ci
+          npm run test
+
+  # ─── Job 1: 构建前端 ───
+  build-web:
+    name: Build Frontend
+    needs: verify
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    steps:
+      - uses: actions/checkout@v7
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v7
+        with:
+          node-version: '24'
+          cache: 'npm'
+          cache-dependency-path: web/package-lock.json
+
+      - name: Install & Build
        working-directory: web
        run: |
          npm ci
          npm run build

-      - name: Build backend
+      - name: Upload frontend artifact
+        uses: actions/upload-artifact@v7
+        with:
+          name: web-dist
+          path: web/dist
+          retention-days: 1
+
+  # ─── Job 2: 预编译二进制 → GitHub Release ───
+  build-release:
+    name: Build ${{ matrix.goarch }}
+    needs: build-web
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    permissions:
+      contents: write
+    strategy:
+      matrix:
+        include:
+          - goos: linux
+            goarch: amd64
+          - goos: linux
+            goarch: arm64
+    steps:
+      - uses: actions/checkout@v7
+
+      - name: Set up Go
+        uses: actions/setup-go@v7
+        with:
+          go-version: '1.25'
+          cache-dependency-path: server/go.sum
+
+      - name: Download frontend artifact
+        uses: actions/download-artifact@v8
+        with:
+          name: web-dist
+          path: web/dist
+
+      - name: Build binary
        working-directory: server
        env:
          GOOS: ${{ matrix.goos }}
          GOARCH: ${{ matrix.goarch }}
-          CGO_ENABLED: 1
+          CGO_ENABLED: '0'
        run: |
-          go build -ldflags "-s -w -X main.version=${{ github.ref_name }}" -o ../backupx-${{ matrix.goos }}-${{ matrix.goarch }} ./cmd/backupx
+          go build \
+            -trimpath \
+            -ldflags "-s -w -X main.version=${VERSION}" \
+            -o ../backupx \
+            ./cmd/backupx

      - name: Package release
        run: |
-          mkdir -p release
-          cp backupx-${{ matrix.goos }}-${{ matrix.goarch }} release/
-          cp -r web/dist release/web
-          cp server/config.example.yaml release/
-          cp deploy/install.sh release/ 2>/dev/null || true
-          cd release && tar czf ../backupx-${{ github.ref_name }}-${{ matrix.goos }}-${{ matrix.goarch }}.tar.gz .
+          ARCHIVE_NAME="backupx-${VERSION}-${{ matrix.goos }}-${{ matrix.goarch }}"
+          mkdir -p "${ARCHIVE_NAME}"
+          cp backupx "${ARCHIVE_NAME}/"
+          cp -r web/dist "${ARCHIVE_NAME}/web"
+          cp server/config.example.yaml "${ARCHIVE_NAME}/"
+          cp deploy/install.sh "${ARCHIVE_NAME}/" 2>/dev/null || true
+          cp deploy/backupx.service "${ARCHIVE_NAME}/" 2>/dev/null || true
+          # v2.2+: 随发布包提供 Grafana dashboard 与 nginx.conf 模板
+          if [ -d deploy/grafana ]; then
+            cp -r deploy/grafana "${ARCHIVE_NAME}/grafana"
+          fi
+          cp deploy/nginx.conf "${ARCHIVE_NAME}/nginx.conf" 2>/dev/null || true
+          tar czf "${ARCHIVE_NAME}.tar.gz" "${ARCHIVE_NAME}"
+          cp "${ARCHIVE_NAME}.tar.gz" "backupx-${{ matrix.goos }}-${{ matrix.goarch }}.tar.gz"
+          sha256sum "${ARCHIVE_NAME}.tar.gz" > "${ARCHIVE_NAME}.tar.gz.sha256"
+          sha256sum "backupx-${{ matrix.goos }}-${{ matrix.goarch }}.tar.gz" > "backupx-${{ matrix.goos }}-${{ matrix.goarch }}.tar.gz.sha256"

-      - name: Upload Release Asset
-        uses: softprops/action-gh-release@v2
+      - name: Upload to GitHub Release
+        uses: softprops/action-gh-release@v3
        with:
-          files: backupx-${{ github.ref_name }}-${{ matrix.goos }}-${{ matrix.goarch }}.tar.gz
+          tag_name: ${{ env.VERSION }}
+          files: |
+            backupx-${{ env.VERSION }}-${{ matrix.goos }}-${{ matrix.goarch }}.tar.gz
+            backupx-${{ env.VERSION }}-${{ matrix.goos }}-${{ matrix.goarch }}.tar.gz.sha256
+            backupx-${{ matrix.goos }}-${{ matrix.goarch }}.tar.gz
+            backupx-${{ matrix.goos }}-${{ matrix.goarch }}.tar.gz.sha256
+          fail_on_unmatched_files: true
          generate_release_notes: true
+
+  # ─── Job 3: Docker 多架构 → Docker Hub ───
+  build-docker:
+    name: Build & Push Docker
+    needs: build-web
+    runs-on: ubuntu-latest
+    timeout-minutes: 45
+    steps:
+      - uses: actions/checkout@v7
+
+      - name: Set up QEMU
+        uses: docker/setup-qemu-action@v4
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v4
+
+      - name: Login to Docker Hub
+        uses: docker/login-action@v4
+        with:
+          username: ${{ secrets.DOCKERHUB_USERNAME }}
+          password: ${{ secrets.DOCKERHUB_TOKEN }}
+
+      - name: Build & Push
+        uses: docker/build-push-action@v7
+        with:
+          context: .
+          platforms: linux/amd64,linux/arm64
+          push: true
+          build-args: |
+            VERSION=${{ env.VERSION }}
+          tags: |
+            ${{ secrets.DOCKERHUB_USERNAME }}/backupx:latest
+            ${{ secrets.DOCKERHUB_USERNAME }}/backupx:${{ env.VERSION }}
+          cache-from: type=gha
+          cache-to: type=gha,mode=max
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,38 @@
-web/node_modules/
+# Dependencies
+web/node_modules/
+docs-site/node_modules/
+
+# Build and test artifacts
+web/dist/
+docs-site/build/
+docs-site/.docusaurus/
+server/bin/
+coverage/
+*.out
+*.tsbuildinfo
+web/vite.config.js
+web/vite.config.d.ts
+
+# Runtime data and local configuration
+data/
+tmp/
+temp/
+*.db
+*.db-shm
+*.db-wal
+*.log
+.env
+.env.*
+!.env*.example
+
+# Editors, operating systems, and local tools
+.idea/
+.vscode/
+.DS_Store
+Thumbs.db
+desktop.ini
+*.swp
+*.swo
+*~
+.claude/
+.codex/
--- a/.node-version
+++ b/.node-version
@@ -0,0 +1 @@
+24
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -0,0 +1,113 @@
+# Contributing to BackupX
+
+感谢你对 BackupX 的关注！本指南介绍如何搭建开发环境并提交贡献。
+Thanks for your interest in contributing to BackupX! This guide covers how to set up your environment and submit changes.
+
+## 开发环境 / Development Setup
+
+### 依赖 / Prerequisites
+
+- **Go** 1.25+（见 `server/go.mod`）
+- **Node.js** 24 LTS（见 `.node-version`，CI 与 Docker 使用同一主版本）
+- **npm** 11+
+
+### 快速开始 / Quick Start
+
+分别在两个终端启动前后端（后端 :8340，前端 Vite HMR）：
+
+```bash
+git clone https://github.com/Awuqing/BackupX.git && cd BackupX
+npm --prefix web ci
+npm --prefix docs-site ci
+
+# 终端 1 —— 后端（默认 http://localhost:8340）
+make dev-server
+
+# 终端 2 —— 前端（Vite 热更新，/api 代理到 8340）
+make dev-web
+```
+
+### 构建 / Building
+
+```bash
+make build          # 同时构建后端与前端
+make build-server   # 仅后端 → server/bin/backupx
+make build-web      # 仅前端 → web/dist
+make build-docs     # 仅文档站 → docs-site/build
+make docker         # 构建 Docker 镜像
+make docker-cn      # 国内镜像源加速构建
+```
+
+> 后端会自动托管 `web/dist`（或 `server.web_root` 指定目录），因此本地裸机部署无需额外的反向代理即可访问控制台。
+
+## 测试 / Testing
+
+提交前应执行与 CI 一致的完整验证：
+
+```bash
+make verify         # 格式、依赖、静态检查、测试与三端构建
+make test           # 仅后端 + 前端测试
+make test-server    # 仅后端：cd server && go test ./...
+make test-web       # 仅前端：cd web && npm run test（vitest）
+make check-docs     # 文档类型检查 + 中英文站点构建
+```
+
+新增功能或修复缺陷时，请补充对应测试。文档变更也必须通过严格断链检查，不能只依赖合并后的 Pages 部署结果。
+
+## 提交信息规范 / Commit Messages
+
+本项目采用 **Conventional Commits**，正文用中文撰写：
+
+```
+<type>(<scope>): <subject>
+
+<body>
+```
+
+| type | 说明 |
+|------|------|
+| `feat` | 新功能 |
+| `fix` | 缺陷修复 |
+| `docs` | 文档变更 |
+| `style` | 不影响逻辑的格式调整 |
+| `refactor` | 重构 |
+| `perf` | 性能优化 |
+| `test` | 测试相关 |
+| `chore` | 构建/依赖/工具链 |
+
+示例：
+
+```
+feat(storage): 新增 Wasabi S3 后端支持
+fix(cluster): 修复跨节点恢复的终态处理
+docs: 补充 CONTRIBUTING 指南
+```
+
+## Pull Request 流程
+
+1. **Fork** 仓库并从最新的 `main` 切出特性分支；
+2. **开发**功能或修复，必要时补充测试；
+3. **自测**：确保 `make verify` 通过；
+4. **提交**：使用上述 Conventional Commits（中文）；
+5. **推送**并对着 `main` 发起 PR。
+
+### PR 描述建议
+
+- 清晰说明本 PR 做了什么；
+- 对新功能/修复，补充动机与背景；
+- 关联相关 Issue（如 `Closes #62`）；
+- 纯文档 PR 至少应附上 `make check-docs` 的结果。
+
+> 请保持分支基于较新的 `main`：基线过旧的分支容易产生大范围冲突，难以评审与合入。
+
+## 编码规范 / Coding Conventions
+
+- **Go**：遵循现有 handler → service → repository 分层；避免把连续业务流程拆成大量无复用价值的独立函数。所有错误必须处理，日志使用 `zap`，禁止 `fmt.Println`，提交前执行 `gofmt` 与 `go vet`。
+- **前端组件**：复用并组合现有组件，不在页面内复制同类交互逻辑，不擅自改变共享组件的基础样式，不引入新的 CSS 框架或 UI 库。
+- **前端视觉**：不使用 Emoji、渐变和 `box-shadow`；图标统一使用项目 SVG 图标组件；圆角为 0–4px；不引入独立字体，不用加粗字体制造层级，减少 Card，不使用数据左侧装饰竖线。
+- **包管理**：`web/` 与 `docs-site/` 均使用 npm；依赖变更必须同步提交对应的 `package-lock.json`。
+- **文档**：英文源文件与 `zh-CN` 翻译应同步维护；新增页面必须加入侧边栏并通过两种语言的生产构建。
+
+## License
+
+向 BackupX 贡献即表示你同意你的贡献以 [Apache License 2.0](LICENSE) 授权。
--- a/98
+++ b/98
@@ -0,0 +1,98 @@
+# BackupX 多阶段构建
+#
+# 用法：
+#   国际构建（默认）：docker build -t backupx .
+#   国内加速构建：    docker build --build-arg USE_CHINA_MIRROR=true -t backupx .
+#   注入版本号：      docker build --build-arg VERSION=v1.2.3 -t backupx .
+
+# 全局构建参数
+ARG USE_CHINA_MIRROR=false
+
+
+# ---- Stage 1: Build frontend ----
+FROM node:26-alpine AS web-builder
+ARG USE_CHINA_MIRROR
+
+# 国内镜像：npm 使用淘宝源
+RUN if [ "$USE_CHINA_MIRROR" = "true" ]; then \
+      npm config set registry https://registry.npmmirror.com; \
+    fi
+
+WORKDIR /build/web
+COPY web/package.json web/package-lock.json ./
+RUN npm ci
+COPY web/ ./
+RUN npm run build
+
+
+# ---- Stage 2: Build backend ----
+FROM golang:1.26-alpine AS server-builder
+ARG USE_CHINA_MIRROR
+ARG VERSION=dev
+
+# 国内镜像：Go 模块使用七牛代理
+RUN if [ "$USE_CHINA_MIRROR" = "true" ]; then \
+      go env -w GOPROXY=https://goproxy.cn,direct; \
+    fi
+
+WORKDIR /build/server
+COPY server/go.mod server/go.sum ./
+RUN go mod download
+COPY server/ ./
+RUN CGO_ENABLED=0 go build -trimpath -ldflags="-s -w -X main.version=${VERSION}" -o backupx ./cmd/backupx
+
+
+# ---- Stage 3: Production image ----
+FROM alpine:3.24
+ARG USE_CHINA_MIRROR
+
+# 国内镜像：Alpine apk 使用阿里云源
+RUN if [ "$USE_CHINA_MIRROR" = "true" ]; then \
+      sed -i 's|dl-cdn.alpinelinux.org|mirrors.aliyun.com|g' /etc/apk/repositories; \
+    fi
+
+# Database client binaries are required by MySQL and PostgreSQL backup tasks.
+RUN apk add --no-cache \
+    tzdata \
+    ca-certificates \
+    su-exec \
+    mysql-client \
+    postgresql16-client \
+    && rm -rf /var/cache/apk/*
+
+# Create app user
+RUN addgroup -S backupx && adduser -S -G backupx -h /app backupx
+
+# Copy backend binary
+COPY --from=server-builder /build/server/backupx /app/bin/backupx
+
+# Copy frontend static files
+COPY --from=web-builder /build/web/dist /app/web
+
+# Copy entrypoint
+COPY deploy/docker/entrypoint.sh /app/entrypoint.sh
+RUN chmod +x /app/entrypoint.sh
+
+# Create data directories
+RUN mkdir -p /app/data /tmp/backupx && \
+    touch /app/data/.backupx-owner-v2 && \
+    chown -R backupx:backupx /app/data /tmp/backupx && \
+    chmod 0750 /app/data /tmp/backupx
+
+WORKDIR /app
+EXPOSE 8340
+
+VOLUME ["/app/data"]
+
+ENV BACKUPX_SERVER_HOST=0.0.0.0 \
+    BACKUPX_SERVER_PORT=8340 \
+    BACKUPX_SERVER_WEB_ROOT=/app/web
+
+USER root
+
+HEALTHCHECK --interval=30s --timeout=5s --start-period=10s --retries=3 \
+    CMD su-exec backupx:backupx wget -q -T 3 -O /dev/null http://127.0.0.1:8340/ready || exit 1
+
+STOPSIGNAL SIGTERM
+
+ENTRYPOINT ["/app/entrypoint.sh"]
--- a/50
+++ b/50
@@ -1,22 +1,30 @@
-.PHONY: build dev test clean
+.PHONY: build build-server build-web build-docs dev-server dev-web \
+	test test-server test-web check-docs format-check vet-server \
+	verify verify-server verify-web verify-docs clean docker docker-cn

-# 一次性构建前后端
+# 自动获取版本号（从 git tag 或 commit hash）
+VERSION ?= $(shell git describe --tags --always --dirty 2>/dev/null || echo dev)
+
+# ── 一键构建 ──
 build: build-server build-web

 build-server:
-	cd server && go build -o bin/backupx ./cmd/backupx
+	cd server && CGO_ENABLED=0 go build -trimpath -ldflags "-s -w -X main.version=$(VERSION)" -o bin/backupx ./cmd/backupx

 build-web:
 	cd web && npm run build

-# 开发模式（分别在两个终端运行）
+build-docs:
+	cd docs-site && npm run build
+
+# ── 开发模式（分别在两个终端运行）──
 dev-server:
 	cd server && go run ./cmd/backupx

 dev-web:
 	cd web && npm run dev

-# 运行所有测试
+# ── 测试 ──
 test: test-server test-web

 test-server:
@@ -25,6 +33,36 @@ test-server:
 test-web:
 	cd web && npm run test

-# 清理构建产物
+check-docs:
+	cd docs-site && npm run typecheck && npm run build
+
+format-check:
+	@unformatted="$$(gofmt -l server)"; \
+	if [ -n "$$unformatted" ]; then \
+		printf '%s\n' "$$unformatted"; \
+		exit 1; \
+	fi
+
+vet-server:
+	cd server && go mod verify && go vet ./...
+
+# ── 提交前完整验证 ──
+verify: verify-server verify-web verify-docs
+
+verify-server: format-check vet-server test-server build-server
+
+verify-web: test-web build-web
+
+verify-docs: check-docs
+
+# ── Docker 构建 ──
+docker:
+	docker build --build-arg VERSION=$(VERSION) -t backupx:$(VERSION) -t backupx:latest .
+
+# 国内加速构建（使用国内镜像源）
+docker-cn:
+	docker build --build-arg VERSION=$(VERSION) --build-arg USE_CHINA_MIRROR=true -t backupx:$(VERSION) -t backupx:latest .
+
+# ── 清理 ──
 clean:
 	rm -rf server/bin web/dist
--- a/README.md
+++ b/README.md
@@ -1,497 +1,136 @@
 <p align="right">
-  <a href="README_EN.md">English</a> | <strong>中文</strong>
+  <strong>English</strong> | <a href="README.zh-CN.md">中文</a>
 </p>
 <p align="center">
-  <h1 align="center">🛡️ BackupX</h1>
+  <h1 align="center">BackupX</h1>
  <p align="center">
-    <strong>Self-hosted Server Backup Management Platform with Web UI</strong>
-  </p>
-  <p align="center">
-    <a href="#features">Features</a> •
-    <a href="#quick-start">Quick Start</a> •
-    <a href="#configuration">Configuration</a> •
-    <a href="#architecture">Architecture</a> •
-    <a href="#cluster-mode">Cluster</a> •
-    <a href="#development">Development</a> •
-    <a href="#api-reference">API</a>
+    <strong>Self-hosted server backup management</strong><br>
+    One binary, one command — manage every backup of every server.
  </p>
  <p align="center">
    <a href="https://github.com/Awuqing/BackupX/stargazers"><img src="https://img.shields.io/github/stars/Awuqing/BackupX?style=flat-square&color=f5c542" alt="Stars"></a>
    <a href="https://github.com/Awuqing/BackupX/releases"><img src="https://img.shields.io/github/v/release/Awuqing/BackupX?style=flat-square&color=brightgreen" alt="Release"></a>
-    <img src="https://img.shields.io/badge/Go-1.21+-00ADD8?style=flat-square&logo=go" alt="Go">
+    <a href="https://github.com/Awuqing/BackupX/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/Awuqing/BackupX/ci.yml?branch=main&style=flat-square" alt="CI"></a>
+    <a href="https://github.com/Awuqing/BackupX/actions/workflows/docs.yml"><img src="https://img.shields.io/github/actions/workflow/status/Awuqing/BackupX/docs.yml?branch=main&style=flat-square&label=docs" alt="Docs"></a>
+    <img src="https://img.shields.io/badge/Go-1.25+-00ADD8?style=flat-square&logo=go" alt="Go">
    <img src="https://img.shields.io/badge/React-18-61DAFB?style=flat-square&logo=react" alt="React">
-    <img src="https://img.shields.io/badge/TypeScript-5-3178C6?style=flat-square&logo=typescript" alt="TypeScript">
    <img src="https://img.shields.io/badge/SQLite-embedded-003B57?style=flat-square&logo=sqlite" alt="SQLite">
    <a href="LICENSE"><img src="https://img.shields.io/github/license/Awuqing/BackupX?style=flat-square" alt="License"></a>
-    <a href="https://github.com/Awuqing/BackupX/issues"><img src="https://img.shields.io/github/issues/Awuqing/BackupX?style=flat-square" alt="Issues"></a>
+  </p>
+  <p align="center">
+    <a href="https://awuqing.github.io/BackupX/"><strong>Docs</strong></a> ·
+    <a href="https://github.com/Awuqing/BackupX/releases"><strong>Downloads</strong></a> ·
+    <a href="https://hub.docker.com/r/awuqing/backupx"><strong>Docker Hub</strong></a>
  </p>
 </p>

 ---

-BackupX 是一个面向 **Linux / macOS 服务器**的自托管备份管理平台。通过企业级 Web 控制台，轻松配置目录备份、数据库备份，并将备份文件安全存储到阿里云 OSS、腾讯云 COS、七牛云 Kodo、Google Drive、S3 兼容存储、WebDAV、FTP/FTPS 或本地磁盘。
+<table>
+<tr>
+<td width="50%"><img src="screenshots/dashboard.png" alt="BackupX dashboard with 30-day backup trends, storage distribution, and task health"><br><sub><strong>Dashboard</strong> — 30-day success and failure trends, storage distribution, task volume, and cluster health.</sub></td>
+<td width="50%"><img src="screenshots/backup-tasks.png" alt="BackupX task list with schedules, targets, retention, tags, RPO, and verification status"><br><sub><strong>Backup tasks</strong> — schedules, multi-target policies, retention, tags, RPO goals, and recurring verification.</sub></td>
+</tr>
+<tr>
+<td><img src="screenshots/storage-targets.png" alt="BackupX storage targets with connection health, capacity usage, and redundancy roles"><br><sub><strong>Storage targets</strong> — connection health, live capacity, favourites, and redundancy roles at a glance.</sub></td>
+<td><img src="screenshots/backup-records.png" alt="BackupX backup history with success and failure states, checksums, destinations, and retention locks"><br><sub><strong>Backup records</strong> — success and failure states, checksums, destinations, execution logs, and retention locks.</sub></td>
+</tr>
+</table>

-支持 **多节点集群管理**，可统一管控分布在不同服务器上的备份任务。
+## Highlights

-> **适用人群**：拥有 Linux 服务器的个人开发者 / 小团队 / 企业运维
-
-## Screenshots
-
-### 登录页面
-![登录页面](screenshots/login.png)
-
-### 仪表盘
-![仪表盘](screenshots/dashboard.png)
-
-### 备份任务
-![备份任务](screenshots/backup-tasks.png)
-
-### 备份记录
-![备份记录](screenshots/backup-records.png)
-
-### 存储目标
-![存储目标](screenshots/storage-targets.png)
-
-### 节点管理
-![节点管理](screenshots/nodes.png)
-
-### 通知配置
-![通知配置](screenshots/notifications.png)
-
-### 系统设置
-![系统设置](screenshots/settings.png)
-
-## Features
-
-### 📦 多种备份类型
- **文件/目录** — 支持自定义排除规则（如 `node_modules`、`*.log`）
- **MySQL** — 通过 `mysqldump` 原生工具
- **SQLite** — 安全文件拷贝
- **PostgreSQL** — 通过 `pg_dump` 原生工具
- **SAP HANA** — 通过 `hdbsql` 原生工具（支持多租户数据库）
-
-### ☁️ 多云存储后端
-| 厂商 | 类型 | 说明 |
-|------|------|------|
-| 🇨🇳 **阿里云 OSS** | `aliyun_oss` | 自动组装 Endpoint，支持内网传输 |
-| 🇨🇳 **腾讯云 COS** | `tencent_cos` | 自动组装 Endpoint |
-| 🇨🇳 **七牛云 Kodo** | `qiniu_kodo` | 6 大区域精确映射 |
-| 🌍 **S3 Compatible** | `s3` | AWS S3 / MinIO / Cloudflare R2 等 |
-| 🌍 **Google Drive** | `google_drive` | 完整 OAuth 2.0 授权流程 |
-| 🌍 **WebDAV** | `webdav` | 坚果云 / Nextcloud 等 |
-| 🌍 **FTP / FTPS** | `ftp` | 标准 FTP 协议，支持 Explicit TLS 加密 |
-| 💾 **本地磁盘** | `local_disk` | 备份到服务器本地目录 |
-
-> 国内云厂商仅需填写 **Region** 和 **AccessKey**，系统自动完成 Endpoint 组装，底层复用 S3 引擎零额外依赖。
-
-### 🖥️ 集群管理 (Master-Agent)
- **节点管理** — 注册远程服务器节点，Token 认证
- **本机节点** — 自动创建，单机用户零感知升级
- **目录浏览** — 可视化文件树选择备份源路径，告别手动输入
- **Agent 心跳** — 节点在线状态实时监控
- **任务标签** — 按标签/节点分类管理备份任务
-
-### ⏰ 自动化与调度
- Cron 表达式定时调度
- 可视化 Cron 编辑器
- 自动保留策略（按天数 / 按份数过期清理）
- 最大并发备份数限制
-
-### 🔐 安全
- JWT 认证 + bcrypt 密码存储
- AES-256-GCM 加密存储敏感配置（数据库密码、OAuth Token）
- 可选备份文件加密
- 登录限流防暴力破解
- 节点 Token 认证（一次性显示，安全传输）
-
-### 📊 监控与通知
- 仪表盘统计（成功率、存储用量、备份趋势图表）
- 邮件 / Webhook / Telegram 通知
- 实时备份执行日志 (SSE)
-
-### 🌐 其他
- 中英文国际化 (i18n)
- 零外部依赖（内嵌 SQLite，单二进制部署）
- systemd 服务支持
+| Capability | Details |
+|-----------|---------|
+| **Backup Types** | Files/directories (multi-source), MySQL, PostgreSQL, SQLite, SAP HANA (full / incremental / differential / log + parallel channels + retry) |
+| **SAP HANA Backint Agent** | Built-in Backint protocol — HANA's native interface routes data directly to any BackupX storage backend |
+| **70+ Storage Backends** | Alibaba OSS, Tencent COS, Qiniu, S3, Google Drive, WebDAV, FTP + SFTP, Azure Blob, Dropbox, OneDrive and dozens more via rclone |
+| **Scheduling** | Cron + visual editor + auto-retention (by days/count + empty-directory cleanup) |
+| **Multi-Node Cluster** | Outbound-only Master-Agent polling with proxy, private-CA, and SSH-bastion support; Agents run tasks locally with no reverse connectivity required |
+| **Security** | JWT + bcrypt + AES-256-GCM encrypted config + optional backup encryption + full audit log |
+| **Notifications** | Email / Webhook / Telegram on success or failure |
+| **Observability** | Prometheus `/metrics` endpoint + `/health` + `/ready` probes + SLA breach gauge |
+| **Audit Webhook** | HMAC-SHA256 signed forwarding to SIEM / WORM storage for compliance (SOC2 / GDPR) |
+| **Flow Control** | Per-node bandwidth cap + per-node concurrency limit — tune big/small nodes independently |
+| **Deployment** | Single binary + embedded SQLite; no external control-plane database (database backup tools are required on the execution host) |

 ## Quick Start

-### 从源码构建
+Docker Compose (recommended):
+
+```bash
+git clone --depth 1 https://github.com/Awuqing/BackupX.git
+cd BackupX
+docker compose up -d
+```
+
+Prebuilt archive:
+
+```bash
+curl -LO https://github.com/Awuqing/BackupX/releases/latest/download/backupx-linux-amd64.tar.gz
+curl -LO https://github.com/Awuqing/BackupX/releases/latest/download/backupx-linux-amd64.tar.gz.sha256
+sha256sum -c backupx-linux-amd64.tar.gz.sha256
+tar xzf backupx-linux-amd64.tar.gz
+cd backupx-*-linux-amd64
+sudo ./install.sh
+```
+
+Build and install on bare metal:

 ```bash
-# 克隆项目
 git clone https://github.com/Awuqing/BackupX.git
 cd BackupX
-
-# 一键构建前后端
 make build
-
-# 启动后端服务（默认监听 :8340）
-cd server && ./bin/backupx
-```
-
-### 访问 Web UI
-
-打开浏览器访问 `http://your-server:8340`，首次使用会引导您创建管理员账户。
-
-## Configuration
-
-配置文件路径默认为 `./config.yaml`，也可通过环境变量 `BACKUPX_` 前缀覆盖。
-
-```yaml
-# config.yaml
-server:
-  host: "0.0.0.0"
-  port: 8340
-  mode: "release"              # debug | release
-
-database:
-  path: "./data/backupx.db"    # SQLite 数据库路径
-
-security:
-  jwt_secret: ""               # 留空则自动生成
-  jwt_expire: "24h"
-  encryption_key: ""           # AES 加密密钥，留空自动生成
-
-backup:
-  temp_dir: "/tmp/backupx"     # 备份临时文件目录
-  max_concurrent: 2            # 最大并发备份数
-
-log:
-  level: "info"                # debug | info | warn | error
-  file: "./data/backupx.log"
-  max_size: 100                # 日志文件大小上限 (MB)
-  max_backups: 3               # 保留旧日志文件数
-  max_age: 30                  # 日志保留天数
-```
-
-> 💡 `jwt_secret` 和 `encryption_key` 首次启动时自动生成并持久化到数据库，无需手动配置。
-
-## Architecture
-
-```
-                        ┌─────────────────────┐
-                        │   Nginx (反向代理)    │
-                        │  / → 前端静态文件    │
-                        │  /api → :8340       │
-                        └─────────┬───────────┘
-                                  │
-                                  ▼
-┌──────────────────────────────────────────────────────┐
-│              BackupX Master (Go API Server)           │
-│                      :8340                            │
-│                                                      │
-│  ┌──────┐  ┌────────────┐  ┌───────────────────────┐│
-│  │ Auth │  │Backup Engine│  │  Storage Registry     ││
-│  └──────┘  └──────┬─────┘  │  ┌─────────────────┐  ││
-│                   │        │  │ Aliyun OSS       │  ││
-│  ┌──────────┐    │        │  │ Tencent COS      │  ││
-│  │ Cron     │◄───┘        │  │ Qiniu Kodo       │  ││
-│  │Scheduler │             │  │ S3 Compatible    │  ││
-│  └──────────┘             │  │ Google Drive     │  ││
-│                           │  │ WebDAV           │  ││
-│                           │  │ FTP / FTPS       │  ││
-│  ┌──────────┐             │  │ Local Disk       │  ││
-│  │ Notify   │             │  └─────────────────┘  ││
-│  │ Module   │             └───────────────────────┘│
-│  └──────────┘                                      │
-│                                                      │
-│  ┌──────────────┐   ┌────────────────────┐          │
-│  │ Node Manager │   │ SQLite (backupx.db)│          │
-│  └──────┬───────┘   └────────────────────┘          │
-└─────────┼────────────────────────────────────────────┘
-          │ Heartbeat / Task Dispatch
-          ▼
-┌──────────────────┐  ┌──────────────────┐
-│   Agent Node A   │  │   Agent Node B   │
-│   (远程服务器)    │  │   (远程服务器)    │
-└──────────────────┘  └──────────────────┘
-```
-
-### 技术栈
-
-| 组件 | 技术 |
-|------|------|
-| **后端** | Go · Gin · GORM · SQLite · robfig/cron |
-| **前端** | React 18 · TypeScript · ArcoDesign · Vite · Zustand · ECharts |
-| **存储** | AWS SDK v2 (S3/OSS/COS/Kodo) · Google Drive API v3 · gowebdav · jlaffaye/ftp |
-| **安全** | JWT · bcrypt · AES-256-GCM |
-| **日志** | zap + lumberjack (自动轮转) |
-
-## Cluster Mode
-
-BackupX 支持 **Master-Agent** 模式，可管理多台服务器的备份任务。
-
-### 工作原理
-
-1. **Master** 为运行 BackupX Web 控制台的主控服务器
-2. **Agent** 部署在需要备份的远程服务器上
-3. Agent 启动后通过 Token 向 Master 注册并定期发送心跳
-4. Master 将备份任务下发至对应 Agent 执行
-
-### 添加节点
-
-```bash
-# 在 Web 控制台 → 节点管理 → 添加节点
-# 系统将生成一个唯一的 64 位十六进制 Token
-
-# 在远程服务器上配置 Agent 启动参数
-./backupx-agent --master http://master-server:8340 --token <your-token>
-```
-
-### 目录探针 API
-
-Master 提供 `GET /api/nodes/:id/fs/list?path=/` 接口，可远程浏览节点的文件系统目录。前端在创建备份任务的"源路径"输入时可使用树形选择器直接浏览目标机器的目录结构。
-
-## Project Structure
-
-```
-BackupX/
-├── server/                        # Go 后端
-│   ├── cmd/backupx/               #   程序入口
-│   ├── internal/
-│   │   ├── app/                   #   应用组装 (DI)
-│   │   ├── apperror/              #   统一错误类型
-│   │   ├── backup/                #   备份引擎 (file/mysql/sqlite/pgsql/saphana)
-│   │   │   └── retention/         #     保留策略
-│   │   ├── config/                #   配置加载 (viper)
-│   │   ├── database/              #   数据库初始化 + 迁移
-│   │   ├── http/                  #   HTTP 处理器 + 路由 + 中间件
-│   │   ├── httpapi/               #   HTTP API 辅助工具
-│   │   ├── logger/                #   日志初始化 (zap + lumberjack)
-│   │   ├── model/                 #   GORM 数据模型
-│   │   ├── notify/                #   通知 (email/webhook/telegram)
-│   │   ├── repository/            #   数据访问层
-│   │   ├── scheduler/             #   Cron 调度器
-│   │   ├── security/              #   JWT + 限流
-│   │   ├── service/               #   业务逻辑层
-│   │   └── storage/               #   存储后端 (插件化接口)
-│   │       ├── aliyun/            #     阿里云 OSS
-│   │       ├── tencent/           #     腾讯云 COS
-│   │       ├── qiniu/             #     七牛云 Kodo
-│   │       ├── s3/                #     S3 Compatible 核心
-│   │       ├── s3provider/        #     S3 Provider 辅助
-│   │       ├── googledrive/       #     Google Drive
-│   │       ├── webdav/            #     WebDAV 核心
-│   │       ├── webdavprovider/    #     WebDAV Provider 辅助
-│   │       ├── localdisk/         #     本地磁盘
-│   │       ├── ftp/               #     FTP / FTPS
-│   │       └── codec/             #     配置编解码
-│   └── pkg/                       #   工具包 (compress/crypto/response)
-├── web/                           # React 前端
-│   └── src/
-│       ├── components/            #   通用组件 (CronEditor/FormDrawer/...)
-│       ├── hooks/                 #   自定义 Hooks
-│       ├── layouts/               #   布局组件 (AppLayout)
-│       ├── pages/                 #   页面模块
-│       │   ├── dashboard/         #     仪表盘
-│       │   ├── backup-tasks/      #     备份任务
-│       │   ├── backup-records/    #     备份记录
-│       │   ├── storage-targets/   #     存储目标
-│       │   ├── nodes/             #     节点管理
-│       │   ├── notifications/     #     通知配置
-│       │   ├── settings/          #     系统设置
-│       │   └── login/             #     登录页
-│       ├── services/              #   API 请求封装
-│       ├── stores/                #   Zustand 状态管理
-│       ├── styles/                #   全局样式
-│       ├── types/                 #   TypeScript 类型定义
-│       ├── utils/                 #   工具函数
-│       ├── locales/               #   i18n 语言包 (zh-CN / en-US)
-│       └── router/                #   路由配置
-├── deploy/                        # 部署配置
-│   ├── nginx.conf                 #   Nginx 参考配置
-│   ├── backupx.service            #   systemd 服务单元
-│   └── install.sh                 #   一键安装脚本
-├── .github/                       # GitHub 配置
-│   ├── workflows/ci.yml           #   CI 工作流
-│   ├── workflows/release.yml      #   Release 工作流
-│   └── ISSUE_TEMPLATE/            #   Issue 模板
-└── Makefile                       # 构建命令
-```
-
-## Development
-
-### 前置条件
-
- **Go** ≥ 1.21
- **Node.js** ≥ 18
- **npm**
-
-### 开发模式
-
-```bash
-# 终端 1：启动后端 (热重载需配合 air)
-make dev-server
-
-# 终端 2：启动前端 (Vite HMR)
-make dev-web
-```
-
-### 运行测试
-
-```bash
-# 运行全部测试
-make test
-
-# 仅后端
-make test-server    # go test ./...
-
-# 仅前端
-make test-web       # npm run test
-```
-
-### 构建
-
-```bash
-# 构建前后端
-make build
-
-# 清理构建产物
-make clean
-```
-
-## Deployment
-
-### 一键安装 (推荐)
-
-```bash
-# 先构建
-make build
-
-# 以 root 执行安装脚本
 sudo ./deploy/install.sh
 ```

-安装脚本将自动：
-1. 创建 `backupx` 系统用户
-2. 安装二进制到 `/opt/backupx/bin/`
-3. 部署前端到 `/opt/backupx/web/`
-4. 生成配置文件 `/etc/backupx/config.yaml`
-5. 注册并启动 systemd 服务
-6. 配置 Nginx 反向代理（如已安装）
+For ARM64 hosts, use `backupx-linux-arm64.tar.gz`. The archive contains `backupx`, `web/`, `config.example.yaml`, and `install.sh`; run `install.sh` from the extracted directory.

-### 手动部署
+The Compose quick start defaults to `latest` for evaluation. Pin `BACKUPX_IMAGE` to a release tag or digest and review the security and recovery guides before production.
+
+Open `http://your-server:8340`, choose English or Chinese on the setup screen, create the first administrator account, then follow the [5-minute Quick Start](https://awuqing.github.io/BackupX/docs/getting-started/quick-start).
+
+## Documentation
+
+The full docs live at **https://awuqing.github.io/BackupX/** — Getting Started, Deployment, Operations, SAP HANA, Multi-Node Cluster, API reference, and more. Switch to Chinese via the language dropdown in the top-right nav.
+
+Quick links:
+
+- [Quick Start](https://awuqing.github.io/BackupX/docs/getting-started/quick-start) — first backup in five minutes
+- [Installation](https://awuqing.github.io/BackupX/docs/getting-started/installation) — Docker / bare metal / source
+- [Upgrade & Recovery](https://awuqing.github.io/BackupX/docs/operations/upgrade-recovery) — snapshots, upgrades, rollback, and disaster recovery
+- [Security Hardening](https://awuqing.github.io/BackupX/docs/operations/security) — production exposure, roles, and secrets
+- [Monitoring & Alerts](https://awuqing.github.io/BackupX/docs/operations/monitoring) — probes, metrics, and initial alerts
+- [Troubleshooting](https://awuqing.github.io/BackupX/docs/operations/troubleshooting) — Master, proxy, Agent, and task diagnostics
+- [Multi-Node Cluster](https://awuqing.github.io/BackupX/docs/features/multi-node) — deploy the Agent on remote servers
+- [SAP HANA Support](https://awuqing.github.io/BackupX/docs/features/sap-hana) — hdbsql Runner and native Backint
+- [API Reference](https://awuqing.github.io/BackupX/docs/reference/api) — REST endpoints
+
+## Development

 ```bash
-# 1. 构建
-cd server && go build -o backupx ./cmd/backupx
-cd ../web && npm run build
-
-# 2. 部署文件
-scp server/backupx your-server:/opt/backupx/bin/
-scp -r web/dist/ your-server:/opt/backupx/web/
-scp server/config.example.yaml your-server:/etc/backupx/config.yaml
-
-# 3. 启动
-ssh your-server '/opt/backupx/bin/backupx -config /etc/backupx/config.yaml'
+git clone https://github.com/Awuqing/BackupX.git && cd BackupX
+make dev-server          # Terminal 1 — backend (:8340)
+make dev-web             # Terminal 2 — frontend (Vite HMR)
+make test                # run all tests
+make build               # produce server/bin/backupx + web/dist
 ```

-### Nginx 配置示例
-
-```nginx
-server {
-    listen 80;
-    server_name backup.example.com;
-
-    # 前端静态文件
-    location / {
-        root /opt/backupx/web;
-        try_files $uri $uri/ /index.html;
-    }
-
-    # API 反向代理
-    location /api/ {
-        proxy_pass http://127.0.0.1:8340;
-        proxy_set_header Host $host;
-        proxy_set_header X-Real-IP $remote_addr;
-    }
-}
-```
-
-## API Reference
-
-所有 API 均以 `/api` 为前缀，使用 JWT Bearer Token 认证（除特殊标注外）。
-
-| 模块 | 端点 | 说明 |
-|------|------|------|
-| **认证** | `POST /api/auth/setup` | 首次初始化管理员 |
-| | `POST /api/auth/login` | 登录获取 Token |
-| | `POST /api/auth/logout` | 登出 |
-| | `GET /api/auth/profile` | 当前用户信息 |
-| | `PUT /api/auth/password` | 修改密码 |
-| **备份任务** | `GET/POST /api/backup/tasks` | 任务列表 / 创建 |
-| | `GET/PUT/DELETE /api/backup/tasks/:id` | 详情 / 更新 / 删除 |
-| | `PUT /api/backup/tasks/:id/toggle` | 启用/禁用 |
-| | `POST /api/backup/tasks/:id/run` | 手动触发执行 |
-| **备份记录** | `GET /api/backup/records` | 记录列表 (支持筛选) |
-| | `GET /api/backup/records/:id` | 记录详情 |
-| | `GET /api/backup/records/:id/logs/stream` | 实时执行日志 (SSE) |
-| | `GET /api/backup/records/:id/download` | 下载备份文件 |
-| | `POST /api/backup/records/:id/restore` | 恢复备份 |
-| **存储目标** | `GET/POST /api/storage-targets` | 存储列表 / 添加 |
-| | `GET/PUT/DELETE /api/storage-targets/:id` | 详情 / 更新 / 删除 |
-| | `POST /api/storage-targets/test` | 测试连接 |
-| | `POST /api/storage-targets/:id/test` | 测试已保存连接 |
-| | `GET /api/storage-targets/:id/usage` | 查询用量 |
-| **节点管理** | `GET/POST /api/nodes` | 节点列表 / 添加 |
-| | `GET/DELETE /api/nodes/:id` | 详情 / 删除 |
-| | `GET /api/nodes/:id/fs/list` | 目录浏览 |
-| | `POST /api/agent/heartbeat` | Agent 心跳 ⚡ |
-| **通知** | `GET/POST /api/notifications` | 通知列表 / 添加 |
-| | `POST /api/notifications/test` | 测试通知 |
-| | `POST /api/notifications/:id/test` | 测试已保存通知 |
-| **仪表盘** | `GET /api/dashboard/stats` | 概览统计 |
-| | `GET /api/dashboard/timeline` | 备份趋势时间线 |
-| **系统** | `GET /api/system/info` | 系统信息 (版本/磁盘) |
-| | `GET/PUT /api/settings` | 系统设置读写 |
-
-> ⚡ `POST /api/agent/heartbeat` 为公开端点，使用 Node Token 认证而非 JWT。
-
-## 云存储配置指南
-
-### 阿里云 OSS
-
-1. 登录[阿里云控制台](https://oss.console.aliyun.com/)，创建 Bucket
-2. 前往 RAM 控制台创建 AccessKey
-3. 在 BackupX 添加存储目标时选择"阿里云 OSS"
-4. 填写 Region（如 `cn-hangzhou`）和 AccessKey，系统自动组装 Endpoint
-
-### 腾讯云 COS
-
-1. 登录[腾讯云控制台](https://console.cloud.tencent.com/cos)，创建存储桶
-2. 前往 API 密钥管理创建 SecretId/SecretKey
-3. Bucket 名称格式为 `BucketName-APPID`（如 `backup-1250000000`）
-
-### 七牛云 Kodo
-
-1. 登录[七牛云控制台](https://portal.qiniu.com/)，创建存储空间
-2. 支持区域：`z0`(华东) / `cn-east-2`(华东-浙江2) / `z1`(华北) / `z2`(华南) / `na0`(北美) / `as0`(东南亚)
-
-### Google Drive
-
-1. 前往 [Google Cloud Console](https://console.cloud.google.com/) 创建项目
-2. 启用 **Google Drive API**
-3. 创建 **OAuth 2.0 客户端 ID**（Web 应用类型）
-4. 添加重定向 URI：`http://your-server/api/storage-targets/google-drive/callback`
-5. 在 BackupX 存储管理页面填入 Client ID / Secret，点击授权
+See the [development guide](https://awuqing.github.io/BackupX/docs/development/setup) for more.

 ## Contributing

-欢迎提交 Issue 和 Pull Request！
+Issues and pull requests welcome. Please read the [contributing guide](https://awuqing.github.io/BackupX/docs/development/contributing) before opening a PR — commit messages and PRs on this project are written in Chinese.

-1. Fork 本项目
-2. 创建功能分支 (`git checkout -b feature/amazing-feature`)
-3. 提交更改 (`git commit -m 'Add amazing feature'`)
-4. 推送到分支 (`git push origin feature/amazing-feature`)
-5. 创建 Pull Request
+## Star History
+
+<a href="https://www.star-history.com/?repos=Awuqing%2FBackupX&type=date&legend=top-left">
+ <picture>
+   <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=Awuqing/BackupX&type=date&theme=dark&legend=top-left" />
+   <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=Awuqing/BackupX&type=date&legend=top-left" />
+   <img alt="Star History Chart" src="https://api.star-history.com/chart?repos=Awuqing/BackupX&type=date&legend=top-left" />
+ </picture>
+</a>

 ## License

-本项目采用 [Apache License 2.0](LICENSE) 开源协议。
-
---
-
-<p align="center">
-  Made with ❤️ for self-hosters
-</p>
+[Apache License 2.0](LICENSE)
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -0,0 +1,126 @@
+<p align="right">
+  <a href="README.md">English</a> | <strong>中文</strong>
+</p>
+<p align="center">
+  <h1 align="center">BackupX</h1>
+  <p align="center">
+    <strong>自托管服务器备份管理平台</strong><br>
+    一个二进制，一条命令，管好你所有服务器的备份。
+  </p>
+  <p align="center">
+    <a href="https://github.com/Awuqing/BackupX/stargazers"><img src="https://img.shields.io/github/stars/Awuqing/BackupX?style=flat-square&color=f5c542" alt="Stars"></a>
+    <a href="https://github.com/Awuqing/BackupX/releases"><img src="https://img.shields.io/github/v/release/Awuqing/BackupX?style=flat-square&color=brightgreen" alt="Release"></a>
+    <a href="https://github.com/Awuqing/BackupX/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/Awuqing/BackupX/ci.yml?branch=main&style=flat-square" alt="CI"></a>
+    <a href="https://github.com/Awuqing/BackupX/actions/workflows/docs.yml"><img src="https://img.shields.io/github/actions/workflow/status/Awuqing/BackupX/docs.yml?branch=main&style=flat-square&label=docs" alt="Docs"></a>
+    <img src="https://img.shields.io/badge/Go-1.25+-00ADD8?style=flat-square&logo=go" alt="Go">
+    <img src="https://img.shields.io/badge/React-18-61DAFB?style=flat-square&logo=react" alt="React">
+    <img src="https://img.shields.io/badge/SQLite-embedded-003B57?style=flat-square&logo=sqlite" alt="SQLite">
+    <a href="LICENSE"><img src="https://img.shields.io/github/license/Awuqing/BackupX?style=flat-square" alt="License"></a>
+  </p>
+  <p align="center">
+    <a href="https://awuqing.github.io/BackupX/zh-Hans/"><strong>文档</strong></a> ·
+    <a href="https://github.com/Awuqing/BackupX/releases"><strong>下载</strong></a> ·
+    <a href="https://hub.docker.com/r/awuqing/backupx"><strong>Docker Hub</strong></a>
+  </p>
+</p>
+
+---
+
+<table>
+<tr>
+<td width="50%"><img src="screenshots/dashboard.png" alt="BackupX 仪表盘，展示 30 天备份趋势、存储分布和任务健康度"><br><sub><strong>仪表盘</strong> — 30 天成功/失败趋势、存储分布、任务规模与集群健康度。</sub></td>
+<td width="50%"><img src="screenshots/backup-tasks.png" alt="BackupX 备份任务列表，展示调度、存储目标、保留策略、标签、RPO 和验证状态"><br><sub><strong>备份任务</strong> — 调度、双目标策略、保留规则、标签、RPO 与定时验证。</sub></td>
+</tr>
+<tr>
+<td><img src="screenshots/storage-targets.png" alt="BackupX 存储目标，展示连接状态、容量使用和冗余角色"><br><sub><strong>存储目标</strong> — 连接状态、实时容量、收藏及冗余角色一目了然。</sub></td>
+<td><img src="screenshots/backup-records.png" alt="BackupX 备份历史，展示成功失败状态、校验和、存储位置及保留锁"><br><sub><strong>备份记录</strong> — 成功/失败状态、校验和、落盘位置、执行日志与保留锁定。</sub></td>
+</tr>
+</table>
+
+## 功能亮点
+
+| 能力 | 说明 |
+|------|------|
+| **备份类型** | 文件/目录（多源路径）、MySQL、PostgreSQL、SQLite、SAP HANA（完整/增量/差异/日志备份 + 并行通道 + 失败重试） |
+| **SAP HANA Backint 代理** | 内置 SAP HANA Backint 协议代理，HANA 原生备份接口可直接把数据路由到 BackupX 支持的任意存储后端 |
+| **70+ 存储后端** | 内置阿里云 OSS / 腾讯云 COS / 七牛云 / S3 / Google Drive / WebDAV / FTP + 通过 rclone 集成 SFTP、Azure Blob、Dropbox、OneDrive 等 70+ 后端 |
+| **自动调度** | Cron 定时 + 可视化编辑器 + 自动保留策略（按天数/份数清理，自动回收空目录） |
+| **多节点集群** | Master-Agent 模式，基于 Agent 主动出站的 HTTP 轮询跨服务器管理备份，支持代理、私有 CA 与 SSH 堡垒机，无需反向连通性 |
+| **安全** | JWT + bcrypt + AES-256-GCM 加密配置 + 可选备份文件加密 + 完整审计日志 |
+| **通知** | 邮件 / Webhook / Telegram，备份成功或失败时自动推送 |
+| **可观测性** | Prometheus `/metrics` 端点 + `/health` + `/ready` 探针 + SLA 违约监控 |
+| **审计外输** | HMAC-SHA256 签名 Webhook，对接 SIEM / WORM 存储满足 SOC2 / GDPR 合规 |
+| **流控** | 节点级带宽限速 + 节点级并发控制，大小节点分别配置，避免小内存 Agent 被挤爆 |
+| **部署** | 单二进制 + 内嵌 SQLite，无需外部控制面数据库（数据库备份工具需安装在任务执行主机） |
+
+## 快速开始
+
+Docker Compose（推荐）：
+
+```bash
+git clone --depth 1 https://github.com/Awuqing/BackupX.git
+cd BackupX
+docker compose up -d
+```
+
+预编译包：
+
+```bash
+curl -LO https://github.com/Awuqing/BackupX/releases/latest/download/backupx-linux-amd64.tar.gz
+curl -LO https://github.com/Awuqing/BackupX/releases/latest/download/backupx-linux-amd64.tar.gz.sha256
+sha256sum -c backupx-linux-amd64.tar.gz.sha256
+tar xzf backupx-linux-amd64.tar.gz
+cd backupx-*-linux-amd64
+sudo ./install.sh
+```
+
+从源码构建并裸机安装：
+
+```bash
+git clone https://github.com/Awuqing/BackupX.git
+cd BackupX
+make build
+sudo ./deploy/install.sh
+```
+
+ARM64 主机请下载 `backupx-linux-arm64.tar.gz`。预编译包内包含 `backupx`、`web/`、`config.example.yaml` 和 `install.sh`，请在解压后的目录内执行 `install.sh`。
+
+Compose 快速开始为便于体验默认使用 `latest`。生产环境应把 `BACKUPX_IMAGE` 固定到 Release 标签或摘要，并先阅读安全与恢复指南。
+
+打开 `http://your-server:8340`，在初始化页选择中文或 English 并创建首个管理员账户，按 [5 分钟快速开始](https://awuqing.github.io/BackupX/zh-Hans/docs/getting-started/quick-start) 完成首次备份。
+
+## 文档
+
+完整文档见 **https://awuqing.github.io/BackupX/zh-Hans/** — 快速开始、部署、运维、SAP HANA、多节点集群、API 参考等。
+
+快捷链接：
+
+- [快速开始](https://awuqing.github.io/BackupX/zh-Hans/docs/getting-started/quick-start) — 五分钟跑通第一个备份
+- [安装](https://awuqing.github.io/BackupX/zh-Hans/docs/getting-started/installation) — Docker / 裸机 / 源码
+- [升级与恢复](https://awuqing.github.io/BackupX/zh-Hans/docs/operations/upgrade-recovery) — 快照、升级、回滚与灾难恢复
+- [安全加固](https://awuqing.github.io/BackupX/zh-Hans/docs/operations/security) — 生产暴露、角色与密钥
+- [监控与告警](https://awuqing.github.io/BackupX/zh-Hans/docs/operations/monitoring) — 探针、指标与初始告警
+- [故障排查](https://awuqing.github.io/BackupX/zh-Hans/docs/operations/troubleshooting) — Master、代理、Agent 与任务诊断
+- [多节点集群](https://awuqing.github.io/BackupX/zh-Hans/docs/features/multi-node) — 远程服务器部署 Agent
+- [SAP HANA 支持](https://awuqing.github.io/BackupX/zh-Hans/docs/features/sap-hana) — hdbsql Runner 与原生 Backint
+- [API 参考](https://awuqing.github.io/BackupX/zh-Hans/docs/reference/api) — REST 端点
+
+## 开发
+
+```bash
+git clone https://github.com/Awuqing/BackupX.git && cd BackupX
+make dev-server          # 终端 1：后端（:8340）
+make dev-web             # 终端 2：前端（Vite HMR）
+make test                # 运行全部测试
+make build               # 产出 server/bin/backupx + web/dist
+```
+
+更多细节见 [开发指南](https://awuqing.github.io/BackupX/zh-Hans/docs/development/setup)。
+
+## 贡献
+
+欢迎提交 Issue 与 Pull Request。提交 PR 前请先阅读 [贡献指南](https://awuqing.github.io/BackupX/zh-Hans/docs/development/contributing) — 本项目的 commit message 和 PR 正文均使用中文。
+
+## License
+
+[Apache License 2.0](LICENSE)
--- a/README_EN.md
+++ b/README_EN.md
@@ -1,498 +0,0 @@
-<p align="right">
-  <strong>English</strong> | <a href="README.md">中文</a>
-</p>
-<p align="center">
-  <h1 align="center">🛡️ BackupX</h1>
-  <p align="center">
-    <strong>Self-hosted Server Backup Management Platform with Web UI</strong>
-  </p>
-  <p align="center">
-    <a href="#features">Features</a> •
-    <a href="#quick-start">Quick Start</a> •
-    <a href="#configuration">Configuration</a> •
-    <a href="#architecture">Architecture</a> •
-    <a href="#cluster-mode">Cluster</a> •
-    <a href="#development">Development</a> •
-    <a href="#api-reference">API</a>
-  </p>
-  <p align="center">
-    <a href="https://github.com/Awuqing/BackupX/stargazers"><img src="https://img.shields.io/github/stars/Awuqing/BackupX?style=flat-square&color=f5c542" alt="Stars"></a>
-    <a href="https://github.com/Awuqing/BackupX/releases"><img src="https://img.shields.io/github/v/release/Awuqing/BackupX?style=flat-square&color=brightgreen" alt="Release"></a>
-    <img src="https://img.shields.io/badge/Go-1.21+-00ADD8?style=flat-square&logo=go" alt="Go">
-    <img src="https://img.shields.io/badge/React-18-61DAFB?style=flat-square&logo=react" alt="React">
-    <img src="https://img.shields.io/badge/TypeScript-5-3178C6?style=flat-square&logo=typescript" alt="TypeScript">
-    <img src="https://img.shields.io/badge/SQLite-embedded-003B57?style=flat-square&logo=sqlite" alt="SQLite">
-    <a href="LICENSE"><img src="https://img.shields.io/github/license/Awuqing/BackupX?style=flat-square" alt="License"></a>
-    <a href="https://github.com/Awuqing/BackupX/issues"><img src="https://img.shields.io/github/issues/Awuqing/BackupX?style=flat-square" alt="Issues"></a>
-  </p>
-</p>
-
---
-
-BackupX is a self-hosted backup management platform for **Linux / macOS servers**. Through an enterprise-grade Web console, you can easily configure directory backups, database backups, and securely store backup files to Alibaba Cloud OSS, Tencent Cloud COS, Qiniu Cloud Kodo, Google Drive, S3-compatible storage, WebDAV, FTP/FTPS, or local disk.
-
-Supports **multi-node cluster management** for unified control of backup tasks across different servers.
-
-> **For**: Individual developers / small teams / DevOps with Linux servers
-
-## Screenshots
-
-### Login
-![Login](screenshots/login.png)
-
-### Dashboard
-![Dashboard](screenshots/dashboard.png)
-
-### Backup Tasks
-![Backup Tasks](screenshots/backup-tasks.png)
-
-### Backup Records
-![Backup Records](screenshots/backup-records.png)
-
-### Storage Targets
-![Storage Targets](screenshots/storage-targets.png)
-
-### Node Management
-![Node Management](screenshots/nodes.png)
-
-### Notification Settings
-![Notification Settings](screenshots/notifications.png)
-
-### System Settings
-![System Settings](screenshots/settings.png)
-
-## Features
-
-### 📦 Multiple Backup Types
- **Files / Directories** — Custom exclude rules (e.g. `node_modules`, `*.log`)
- **MySQL** — Via native `mysqldump` tool
- **SQLite** — Safe file copy
- **PostgreSQL** — Via native `pg_dump` tool
- **SAP HANA** — Via native `hdbsql` tool (multi-tenant database support)
-
-### ☁️ Multi-Cloud Storage Backends
-| Provider | Type | Description |
-|----------|------|-------------|
-| 🇨🇳 **Alibaba Cloud OSS** | `aliyun_oss` | Auto endpoint assembly, internal network support |
-| 🇨🇳 **Tencent Cloud COS** | `tencent_cos` | Auto endpoint assembly |
-| 🇨🇳 **Qiniu Cloud Kodo** | `qiniu_kodo` | 6 region precise mapping |
-| 🌍 **S3 Compatible** | `s3` | AWS S3 / MinIO / Cloudflare R2, etc. |
-| 🌍 **Google Drive** | `google_drive` | Full OAuth 2.0 flow |
-| 🌍 **WebDAV** | `webdav` | Nextcloud / Nutstore, etc. |
-| 🌍 **FTP / FTPS** | `ftp` | Standard FTP protocol with Explicit TLS support |
-| 💾 **Local Disk** | `local_disk` | Backup to local server directory |
-
-> Chinese cloud providers only require **Region** and **AccessKey** — the system auto-assembles the endpoint. Powered by the S3 engine under the hood with zero extra dependencies.
-
-### 🖥️ Cluster Management (Master-Agent)
- **Node Management** — Register remote server nodes with Token authentication
- **Local Node** — Auto-created, zero-friction upgrade for single-machine users
- **Directory Browser** — Visual file tree selector for backup source paths
- **Agent Heartbeat** — Real-time node online status monitoring
- **Task Tags** — Categorize and manage backup tasks by tags/nodes
-
-### ⏰ Automation & Scheduling
- Cron expression scheduling
- Visual Cron editor
- Auto-retention policy (by days / by count)
- Max concurrent backup limit
-
-### 🔐 Security
- JWT authentication + bcrypt password hashing
- AES-256-GCM encrypted sensitive config storage (DB passwords, OAuth tokens)
- Optional backup file encryption
- Login rate limiting (brute force protection)
- Node Token authentication (one-time display, secure transport)
-
-### 📊 Monitoring & Notifications
- Dashboard stats (success rate, storage usage, backup trend charts)
- Email / Webhook / Telegram notifications
- Real-time backup execution logs (SSE)
-
-### 🌐 Other
- Chinese & English i18n
- Zero external dependencies (embedded SQLite, single binary deployment)
- systemd service support
-
-## Quick Start
-
-### Build from Source
-
-```bash
-# Clone the project
-git clone https://github.com/Awuqing/BackupX.git
-cd BackupX
-
-# Build frontend and backend
-make build
-
-# Start the backend service (default port :8340)
-cd server && ./bin/backupx
-```
-
-### Access Web UI
-
-Open `http://your-server:8340` in your browser. First-time use will guide you through creating an admin account.
-
-## Configuration
-
-The config file defaults to `./config.yaml`. Settings can also be overridden via `BACKUPX_` prefixed environment variables.
-
-```yaml
-# config.yaml
-server:
-  host: "0.0.0.0"
-  port: 8340
-  mode: "release"              # debug | release
-
-database:
-  path: "./data/backupx.db"    # SQLite database path
-
-security:
-  jwt_secret: ""               # Leave empty to auto-generate
-  jwt_expire: "24h"
-  encryption_key: ""           # AES encryption key, auto-generated if empty
-
-backup:
-  temp_dir: "/tmp/backupx"     # Backup temp directory
-  max_concurrent: 2            # Max concurrent backups
-
-log:
-  level: "info"                # debug | info | warn | error
-  file: "./data/backupx.log"
-  max_size: 100                # Max log file size (MB)
-  max_backups: 3               # Number of old log files to retain
-  max_age: 30                  # Log retention days
-```
-
-> 💡 `jwt_secret` and `encryption_key` are auto-generated on first startup and persisted to the database.
-
-## Architecture
-
-```
-                        ┌─────────────────────┐
-                        │   Nginx (Reverse     │
-                        │   Proxy)             │
-                        │  / → Static Files    │
-                        │  /api → :8340        │
-                        └─────────┬───────────┘
-                                  │
-                                  ▼
-┌──────────────────────────────────────────────────────┐
-│              BackupX Master (Go API Server)           │
-│                      :8340                            │
-│                                                      │
-│  ┌──────┐  ┌────────────┐  ┌───────────────────────┐│
-│  │ Auth │  │Backup Engine│  │  Storage Registry     ││
-│  └──────┘  └──────┬─────┘  │  ┌─────────────────┐  ││
-│                   │        │  │ Alibaba Cloud    │  ││
-│  ┌──────────┐    │        │  │ Tencent Cloud    │  ││
-│  │ Cron     │◄───┘        │  │ Qiniu Cloud      │  ││
-│  │Scheduler │             │  │ S3 Compatible    │  ││
-│  └──────────┘             │  │ Google Drive     │  ││
-│                           │  │ WebDAV           │  ││
-│                           │  │ FTP / FTPS       │  ││
-│  ┌──────────┐             │  │ Local Disk       │  ││
-│  │ Notify   │             │  └─────────────────┘  ││
-│  │ Module   │             └───────────────────────┘│
-│  └──────────┘                                      │
-│                                                      │
-│  ┌──────────────┐   ┌────────────────────┐          │
-│  │ Node Manager │   │ SQLite (backupx.db)│          │
-│  └──────┬───────┘   └────────────────────┘          │
-└─────────┼────────────────────────────────────────────┘
-          │ Heartbeat / Task Dispatch
-          ▼
-┌──────────────────┐  ┌──────────────────┐
-│   Agent Node A   │  │   Agent Node B   │
-│   (Remote Server)│  │   (Remote Server)│
-└──────────────────┘  └──────────────────┘
-```
-
-### Tech Stack
-
-| Component | Technology |
-|-----------|-----------|
-| **Backend** | Go · Gin · GORM · SQLite · robfig/cron |
-| **Frontend** | React 18 · TypeScript · ArcoDesign · Vite · Zustand · ECharts |
-| **Storage** | AWS SDK v2 (S3/OSS/COS/Kodo) · Google Drive API v3 · gowebdav · jlaffaye/ftp |
-| **Security** | JWT · bcrypt · AES-256-GCM |
-| **Logging** | zap + lumberjack (auto-rotation) |
-
-## Cluster Mode
-
-BackupX supports **Master-Agent** mode for managing backup tasks across multiple servers.
-
-### How It Works
-
-1. **Master** is the server running the BackupX Web console
-2. **Agent** is deployed on remote servers that need to be backed up
-3. Agents register with the Master using a Token and send periodic heartbeats
-4. Master dispatches backup tasks to the corresponding Agent for execution
-
-### Adding Nodes
-
-```bash
-# In Web Console → Node Management → Add Node
-# The system generates a unique 64-character hex Token
-
-# Configure the Agent on the remote server
-./backupx-agent --master http://master-server:8340 --token <your-token>
-```
-
-### Directory Probe API
-
-Master provides `GET /api/nodes/:id/fs/list?path=/` to remotely browse a node's file system. The frontend uses a tree selector to browse the target machine's directory structure when creating backup tasks.
-
-## Project Structure
-
-```
-BackupX/
-├── server/                        # Go backend
-│   ├── cmd/backupx/               #   Entry point
-│   ├── internal/
-│   │   ├── app/                   #   App assembly (DI)
-│   │   ├── apperror/              #   Unified error types
-│   │   ├── backup/                #   Backup engine (file/mysql/sqlite/pgsql/saphana)
-│   │   │   └── retention/         #     Retention policy
-│   │   ├── config/                #   Config loading (viper)
-│   │   ├── database/              #   Database init + migrations
-│   │   ├── http/                  #   HTTP handlers + routes + middleware
-│   │   ├── httpapi/               #   HTTP API helpers
-│   │   ├── logger/                #   Logger init (zap + lumberjack)
-│   │   ├── model/                 #   GORM data models
-│   │   ├── notify/                #   Notifications (email/webhook/telegram)
-│   │   ├── repository/            #   Data access layer
-│   │   ├── scheduler/             #   Cron scheduler
-│   │   ├── security/              #   JWT + rate limiting
-│   │   ├── service/               #   Business logic
-│   │   └── storage/               #   Storage backends (plugin interface)
-│   │       ├── aliyun/            #     Alibaba Cloud OSS
-│   │       ├── tencent/           #     Tencent Cloud COS
-│   │       ├── qiniu/             #     Qiniu Cloud Kodo
-│   │       ├── s3/                #     S3 Compatible core
-│   │       ├── s3provider/        #     S3 Provider helper
-│   │       ├── googledrive/       #     Google Drive
-│   │       ├── webdav/            #     WebDAV core
-│   │       ├── webdavprovider/    #     WebDAV Provider helper
-│   │       ├── localdisk/         #     Local disk
-│   │       ├── ftp/               #     FTP / FTPS
-│   │       └── codec/             #     Config codec
-│   └── pkg/                       #   Utilities (compress/crypto/response)
-├── web/                           # React frontend
-│   └── src/
-│       ├── components/            #   Shared components (CronEditor/FormDrawer/...)
-│       ├── hooks/                 #   Custom Hooks
-│       ├── layouts/               #   Layout components (AppLayout)
-│       ├── pages/                 #   Page modules
-│       │   ├── dashboard/         #     Dashboard
-│       │   ├── backup-tasks/      #     Backup tasks
-│       │   ├── backup-records/    #     Backup records
-│       │   ├── storage-targets/   #     Storage targets
-│       │   ├── nodes/             #     Node management
-│       │   ├── notifications/     #     Notification settings
-│       │   ├── settings/          #     System settings
-│       │   └── login/             #     Login page
-│       ├── services/              #   API request wrappers
-│       ├── stores/                #   Zustand state management
-│       ├── styles/                #   Global styles
-│       ├── types/                 #   TypeScript type definitions
-│       ├── utils/                 #   Utility functions
-│       ├── locales/               #   i18n language packs (zh-CN / en-US)
-│       └── router/                #   Route configuration
-├── deploy/                        # Deployment configs
-│   ├── nginx.conf                 #   Nginx reference config
-│   ├── backupx.service            #   systemd service unit
-│   └── install.sh                 #   One-click install script
-├── .github/                       # GitHub configuration
-│   ├── workflows/ci.yml           #   CI workflow
-│   ├── workflows/release.yml      #   Release workflow
-│   └── ISSUE_TEMPLATE/            #   Issue templates
-└── Makefile                       # Build commands
-```
-
-## Development
-
-### Prerequisites
-
- **Go** ≥ 1.21
- **Node.js** ≥ 18
- **npm**
-
-### Dev Mode
-
-```bash
-# Terminal 1: Start backend (use air for hot-reload)
-make dev-server
-
-# Terminal 2: Start frontend (Vite HMR)
-make dev-web
-```
-
-### Run Tests
-
-```bash
-# Run all tests
-make test
-
-# Backend only
-make test-server    # go test ./...
-
-# Frontend only
-make test-web       # npm run test
-```
-
-### Build
-
-```bash
-# Build frontend and backend
-make build
-
-# Clean build artifacts
-make clean
-```
-
-## Deployment
-
-### One-Click Install (Recommended)
-
-```bash
-# Build first
-make build
-
-# Run install script as root
-sudo ./deploy/install.sh
-```
-
-The install script will automatically:
-1. Create a `backupx` system user
-2. Install the binary to `/opt/backupx/bin/`
-3. Deploy the frontend to `/opt/backupx/web/`
-4. Generate config at `/etc/backupx/config.yaml`
-5. Register and start the systemd service
-6. Configure Nginx reverse proxy (if installed)
-
-### Manual Deployment
-
-```bash
-# 1. Build
-cd server && go build -o backupx ./cmd/backupx
-cd ../web && npm run build
-
-# 2. Deploy files
-scp server/backupx your-server:/opt/backupx/bin/
-scp -r web/dist/ your-server:/opt/backupx/web/
-scp server/config.example.yaml your-server:/etc/backupx/config.yaml
-
-# 3. Start
-ssh your-server '/opt/backupx/bin/backupx -config /etc/backupx/config.yaml'
-```
-
-### Nginx Config Example
-
-```nginx
-server {
-    listen 80;
-    server_name backup.example.com;
-
-    # Frontend static files
-    location / {
-        root /opt/backupx/web;
-        try_files $uri $uri/ /index.html;
-    }
-
-    # API reverse proxy
-    location /api/ {
-        proxy_pass http://127.0.0.1:8340;
-        proxy_set_header Host $host;
-        proxy_set_header X-Real-IP $remote_addr;
-    }
-}
-```
-
-## API Reference
-
-All APIs are prefixed with `/api` and use JWT Bearer Token authentication (unless noted otherwise).
-
-| Module | Endpoint | Description |
-|--------|----------|-------------|
-| **Auth** | `POST /api/auth/setup` | Initialize admin (first time) |
-| | `POST /api/auth/login` | Login to get Token |
-| | `POST /api/auth/logout` | Logout |
-| | `GET /api/auth/profile` | Current user info |
-| | `PUT /api/auth/password` | Change password |
-| **Backup Tasks** | `GET/POST /api/backup/tasks` | List / Create tasks |
-| | `GET/PUT/DELETE /api/backup/tasks/:id` | Detail / Update / Delete |
-| | `PUT /api/backup/tasks/:id/toggle` | Enable / Disable |
-| | `POST /api/backup/tasks/:id/run` | Trigger manual execution |
-| **Backup Records** | `GET /api/backup/records` | List records (with filter) |
-| | `GET /api/backup/records/:id` | Record detail |
-| | `GET /api/backup/records/:id/logs/stream` | Real-time execution logs (SSE) |
-| | `GET /api/backup/records/:id/download` | Download backup file |
-| | `POST /api/backup/records/:id/restore` | Restore backup |
-| **Storage Targets** | `GET/POST /api/storage-targets` | List / Add targets |
-| | `GET/PUT/DELETE /api/storage-targets/:id` | Detail / Update / Delete |
-| | `POST /api/storage-targets/test` | Test connection |
-| | `POST /api/storage-targets/:id/test` | Test saved connection |
-| | `GET /api/storage-targets/:id/usage` | Query usage |
-| **Nodes** | `GET/POST /api/nodes` | List / Add nodes |
-| | `GET/DELETE /api/nodes/:id` | Detail / Delete |
-| | `GET /api/nodes/:id/fs/list` | Directory browser |
-| | `POST /api/agent/heartbeat` | Agent heartbeat ⚡ |
-| **Notifications** | `GET/POST /api/notifications` | List / Add |
-| | `POST /api/notifications/test` | Test notification |
-| | `POST /api/notifications/:id/test` | Test saved notification |
-| **Dashboard** | `GET /api/dashboard/stats` | Overview statistics |
-| | `GET /api/dashboard/timeline` | Backup trend timeline |
-| **System** | `GET /api/system/info` | System info (version/disk) |
-| | `GET/PUT /api/settings` | System settings |
-
-> ⚡ `POST /api/agent/heartbeat` is a public endpoint authenticated via Node Token instead of JWT.
-
-## Cloud Storage Setup Guide
-
-### Alibaba Cloud OSS
-
-1. Log in to [Alibaba Cloud Console](https://oss.console.aliyun.com/), create a Bucket
-2. Go to RAM Console to create an AccessKey
-3. Select "Alibaba Cloud OSS" when adding a storage target in BackupX
-4. Enter the Region (e.g. `cn-hangzhou`) and AccessKey — the system auto-assembles the endpoint
-
-### Tencent Cloud COS
-
-1. Log in to [Tencent Cloud Console](https://console.cloud.tencent.com/cos), create a bucket
-2. Go to API Key Management to create SecretId/SecretKey
-3. Bucket name format is `BucketName-APPID` (e.g. `backup-1250000000`)
-
-### Qiniu Cloud Kodo
-
-1. Log in to [Qiniu Cloud Console](https://portal.qiniu.com/), create a storage space
-2. Supported regions: `z0` (East China) / `cn-east-2` (East China-Zhejiang 2) / `z1` (North China) / `z2` (South China) / `na0` (North America) / `as0` (Southeast Asia)
-
-### Google Drive
-
-1. Go to [Google Cloud Console](https://console.cloud.google.com/) and create a project
-2. Enable the **Google Drive API**
-3. Create an **OAuth 2.0 Client ID** (Web application type)
-4. Add redirect URI: `http://your-server/api/storage-targets/google-drive/callback`
-5. Enter the Client ID / Secret in BackupX storage management and click Authorize
-
-## Contributing
-
-Issues and Pull Requests are welcome!
-
-1. Fork this repository
-2. Create a feature branch (`git checkout -b feature/amazing-feature`)
-3. Commit your changes (`git commit -m 'Add amazing feature'`)
-4. Push to the branch (`git push origin feature/amazing-feature`)
-5. Open a Pull Request
-
-## License
-
-This project is licensed under the [Apache License 2.0](LICENSE).
-
---
-
-<p align="center">
-  Made with ❤️ for self-hosters
-</p>
--- a/deploy/backupx.service
+++ b/deploy/backupx.service
@@ -12,6 +12,7 @@ ExecStart=/opt/backupx/bin/backupx -config /etc/backupx/config.yaml
 Restart=on-failure
 RestartSec=5
 NoNewPrivileges=true
+UMask=0027
 LimitNOFILE=65535

 [Install]
--- a/deploy/docker/entrypoint.sh
+++ b/deploy/docker/entrypoint.sh
@@ -0,0 +1,18 @@
+#!/bin/sh
+set -eu
+
+# 旧镜像曾以 root 写入数据卷。Master 启动时做一次所有权迁移，随后
+# 降权运行；Agent 模式由部署命令显式决定用户，以访问宿主机备份路径。
+if [ "$(id -u)" -eq 0 ] && [ "${1:-}" != "agent" ]; then
+    chown backupx:backupx /app/data /tmp/backupx
+    if [ ! -f /app/data/.backupx-owner-v2 ]; then
+        chown -R backupx:backupx /app/data
+        su-exec backupx:backupx touch /app/data/.backupx-owner-v2
+    fi
+    export HOME=/app
+    exec su-exec backupx:backupx /app/bin/backupx "$@"
+fi
+
+# Web 静态文件由 BackupX 后端直接托管。容器只运行一个前台进程，
+# 让 Docker 准确传递信号、收集退出码并执行健康检查。
+exec /app/bin/backupx "$@"
--- a/deploy/grafana/README.md
+++ b/deploy/grafana/README.md
@@ -0,0 +1,34 @@
+# BackupX Grafana Dashboard
+
+对接 BackupX v2.1+ 暴露的 Prometheus `/metrics` 端点。
+
+## 导入步骤
+
+1. 在 Grafana 配置 Prometheus 数据源指向你的 Prometheus（例如 `http://prometheus:9090`）
+2. 在 Prometheus 配置抓取 BackupX：
+
+```yaml
+scrape_configs:
+  - job_name: 'backupx'
+    scrape_interval: 30s
+    static_configs:
+      - targets: ['backupx-master:8340']
+```
+
+3. Grafana → Dashboards → Import → 上传 `backupx-dashboard.json` → 选 Prometheus 数据源 → Import
+
+## 面板内容
+
+- 当前运行任务数 / SLA 违约数 / 在线节点 / 24h 成功率 / 应用版本
+- 任务执行速率（按 success/failed 堆叠）
+- 任务耗时 P50/P95/P99（按任务类型）
+- 任务产出字节速率
+- 存储目标用量 TopN 柱状图
+- 节点在线状态表（红/绿标色）
+- 验证 / 恢复 / 复制的成功率时间线
+
+## 自定义建议
+
+- 将 `backupx_sla_breach_tasks > 0` 配为 AlertManager 告警
+- `sum(backupx_node_online) < N` 触发集群容量告警（N 为你集群的最少节点数）
+- P99 任务耗时突变可用于发现慢任务和资源压力
--- a/deploy/grafana/backupx-dashboard.json
+++ b/deploy/grafana/backupx-dashboard.json
@@ -0,0 +1,193 @@
+{
+  "annotations": {
+    "list": [
+      {
+        "builtIn": 1,
+        "datasource": {"type": "grafana", "uid": "-- Grafana --"},
+        "enable": true,
+        "hide": true,
+        "iconColor": "rgba(0, 211, 255, 1)",
+        "name": "Annotations & Alerts",
+        "type": "dashboard"
+      }
+    ]
+  },
+  "description": "BackupX v2.1+ 核心指标面板。对接 /metrics 端点，抓取周期建议 30s（与服务端 Gauge collector 同步）。",
+  "editable": true,
+  "fiscalYearStartMonth": 0,
+  "graphTooltip": 1,
+  "id": null,
+  "links": [
+    {
+      "title": "BackupX 文档",
+      "url": "https://awuqing.github.io/BackupX/",
+      "type": "link",
+      "targetBlank": true
+    }
+  ],
+  "liveNow": false,
+  "panels": [
+    {
+      "type": "stat",
+      "title": "正在运行的任务",
+      "gridPos": {"h": 4, "w": 4, "x": 0, "y": 0},
+      "datasource": {"type": "prometheus", "uid": "${DS_PROMETHEUS}"},
+      "targets": [{"expr": "backupx_task_running", "refId": "A"}],
+      "fieldConfig": {
+        "defaults": {
+          "unit": "short",
+          "thresholds": {"mode": "absolute", "steps": [{"color": "green", "value": null}, {"color": "yellow", "value": 5}]}
+        }
+      },
+      "options": {"colorMode": "value", "graphMode": "area", "textMode": "auto"}
+    },
+    {
+      "type": "stat",
+      "title": "SLA 违约任务数",
+      "gridPos": {"h": 4, "w": 4, "x": 4, "y": 0},
+      "datasource": {"type": "prometheus", "uid": "${DS_PROMETHEUS}"},
+      "targets": [{"expr": "backupx_sla_breach_tasks", "refId": "A"}],
+      "fieldConfig": {
+        "defaults": {
+          "unit": "short",
+          "thresholds": {"mode": "absolute", "steps": [{"color": "green", "value": null}, {"color": "red", "value": 1}]}
+        }
+      }
+    },
+    {
+      "type": "stat",
+      "title": "在线节点",
+      "gridPos": {"h": 4, "w": 4, "x": 8, "y": 0},
+      "datasource": {"type": "prometheus", "uid": "${DS_PROMETHEUS}"},
+      "targets": [{"expr": "sum(backupx_node_online)", "refId": "A"}],
+      "fieldConfig": {
+        "defaults": {"unit": "short", "color": {"mode": "thresholds"}, "thresholds": {"steps": [{"color": "red", "value": null}, {"color": "green", "value": 1}]}}
+      }
+    },
+    {
+      "type": "stat",
+      "title": "24h 任务成功率",
+      "gridPos": {"h": 4, "w": 6, "x": 12, "y": 0},
+      "datasource": {"type": "prometheus", "uid": "${DS_PROMETHEUS}"},
+      "targets": [{
+        "expr": "sum(rate(backupx_task_run_total{status=\"success\"}[24h])) / sum(rate(backupx_task_run_total[24h])) * 100",
+        "refId": "A"
+      }],
+      "fieldConfig": {
+        "defaults": {
+          "unit": "percent", "decimals": 2,
+          "thresholds": {"mode": "absolute", "steps": [{"color": "red", "value": null}, {"color": "yellow", "value": 95}, {"color": "green", "value": 99}]}
+        }
+      }
+    },
+    {
+      "type": "stat",
+      "title": "应用版本",
+      "gridPos": {"h": 4, "w": 6, "x": 18, "y": 0},
+      "datasource": {"type": "prometheus", "uid": "${DS_PROMETHEUS}"},
+      "targets": [{"expr": "backupx_app_info", "refId": "A", "format": "table", "instant": true}],
+      "options": {"textMode": "value_and_name", "reduceOptions": {"calcs": ["last"], "fields": "/^version$/"}}
+    },
+    {
+      "type": "timeseries",
+      "title": "任务执行速率（按状态）",
+      "gridPos": {"h": 8, "w": 12, "x": 0, "y": 4},
+      "datasource": {"type": "prometheus", "uid": "${DS_PROMETHEUS}"},
+      "targets": [{
+        "expr": "sum by (status) (rate(backupx_task_run_total[5m]))",
+        "refId": "A",
+        "legendFormat": "{{status}}"
+      }],
+      "fieldConfig": {
+        "defaults": {
+          "unit": "ops",
+          "custom": {"drawStyle": "line", "lineInterpolation": "smooth", "fillOpacity": 10, "stacking": {"mode": "normal"}}
+        },
+        "overrides": [
+          {"matcher": {"id": "byName", "options": "success"}, "properties": [{"id": "color", "value": {"mode": "fixed", "fixedColor": "green"}}]},
+          {"matcher": {"id": "byName", "options": "failed"}, "properties": [{"id": "color", "value": {"mode": "fixed", "fixedColor": "red"}}]}
+        ]
+      }
+    },
+    {
+      "type": "timeseries",
+      "title": "任务耗时 P50 / P95 / P99",
+      "gridPos": {"h": 8, "w": 12, "x": 12, "y": 4},
+      "datasource": {"type": "prometheus", "uid": "${DS_PROMETHEUS}"},
+      "targets": [
+        {"expr": "histogram_quantile(0.50, sum(rate(backupx_task_run_duration_seconds_bucket[10m])) by (le, task_type))", "refId": "A", "legendFormat": "P50 {{task_type}}"},
+        {"expr": "histogram_quantile(0.95, sum(rate(backupx_task_run_duration_seconds_bucket[10m])) by (le, task_type))", "refId": "B", "legendFormat": "P95 {{task_type}}"},
+        {"expr": "histogram_quantile(0.99, sum(rate(backupx_task_run_duration_seconds_bucket[10m])) by (le, task_type))", "refId": "C", "legendFormat": "P99 {{task_type}}"}
+      ],
+      "fieldConfig": {"defaults": {"unit": "s"}}
+    },
+    {
+      "type": "timeseries",
+      "title": "任务产出字节速率",
+      "gridPos": {"h": 8, "w": 12, "x": 0, "y": 12},
+      "datasource": {"type": "prometheus", "uid": "${DS_PROMETHEUS}"},
+      "targets": [{"expr": "sum by (task_type) (rate(backupx_task_bytes_total[5m]))", "refId": "A", "legendFormat": "{{task_type}}"}],
+      "fieldConfig": {"defaults": {"unit": "Bps"}}
+    },
+    {
+      "type": "bargauge",
+      "title": "存储目标用量 TopN",
+      "gridPos": {"h": 8, "w": 12, "x": 12, "y": 12},
+      "datasource": {"type": "prometheus", "uid": "${DS_PROMETHEUS}"},
+      "targets": [{"expr": "topk(10, backupx_storage_used_bytes)", "refId": "A", "legendFormat": "{{target_name}} ({{target_type}})"}],
+      "fieldConfig": {"defaults": {"unit": "bytes"}},
+      "options": {"orientation": "horizontal", "displayMode": "gradient"}
+    },
+    {
+      "type": "table",
+      "title": "节点在线状态",
+      "gridPos": {"h": 8, "w": 12, "x": 0, "y": 20},
+      "datasource": {"type": "prometheus", "uid": "${DS_PROMETHEUS}"},
+      "targets": [{"expr": "backupx_node_online", "refId": "A", "format": "table", "instant": true}],
+      "transformations": [
+        {"id": "organize", "options": {"excludeByName": {"Time": true, "__name__": true, "job": true, "instance": true}, "indexByName": {"node_name": 0, "role": 1, "Value": 2}, "renameByName": {"Value": "online"}}}
+      ],
+      "fieldConfig": {
+        "overrides": [{
+          "matcher": {"id": "byName", "options": "online"},
+          "properties": [{"id": "mappings", "value": [{"type": "value", "options": {"0": {"text": "离线", "color": "red"}, "1": {"text": "在线", "color": "green"}}}]}]
+        }]
+      }
+    },
+    {
+      "type": "timeseries",
+      "title": "验证 / 恢复 / 复制成功率",
+      "gridPos": {"h": 8, "w": 12, "x": 12, "y": 20},
+      "datasource": {"type": "prometheus", "uid": "${DS_PROMETHEUS}"},
+      "targets": [
+        {"expr": "sum by (status) (rate(backupx_verify_run_total[15m]))", "refId": "A", "legendFormat": "verify {{status}}"},
+        {"expr": "sum by (status) (rate(backupx_restore_run_total[15m]))", "refId": "B", "legendFormat": "restore {{status}}"},
+        {"expr": "sum by (status) (rate(backupx_replication_run_total[15m]))", "refId": "C", "legendFormat": "replication {{status}}"}
+      ],
+      "fieldConfig": {"defaults": {"unit": "ops"}}
+    }
+  ],
+  "refresh": "30s",
+  "schemaVersion": 39,
+  "tags": ["backupx", "backup", "sre"],
+  "templating": {
+    "list": [
+      {
+        "current": {"selected": false, "text": "Prometheus", "value": "Prometheus"},
+        "label": "Datasource",
+        "name": "DS_PROMETHEUS",
+        "query": "prometheus",
+        "refresh": 1,
+        "regex": "",
+        "type": "datasource"
+      }
+    ]
+  },
+  "time": {"from": "now-6h", "to": "now"},
+  "timepicker": {},
+  "timezone": "",
+  "title": "BackupX Overview",
+  "uid": "backupx-overview",
+  "version": 1,
+  "weekStart": ""
+}
--- a/deploy/install.sh
+++ b/deploy/install.sh
@@ -1,35 +1,94 @@
 #!/bin/sh
 set -eu

-PROJECT_ROOT=$(CDPATH= cd -- "$(dirname -- "$0")/.." && pwd)
+SCRIPT_DIR=$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)
+PROJECT_ROOT=$(CDPATH= cd -- "$SCRIPT_DIR/.." && pwd)
 PREFIX="${PREFIX:-/opt/backupx}"
 ETC_DIR="${ETC_DIR:-/etc/backupx}"
 SERVICE_NAME="backupx"
 APP_USER="backupx"
 APP_GROUP="backupx"
-BIN_SOURCE="${BIN_SOURCE:-$PROJECT_ROOT/server/backupx}"
-WEB_SOURCE="${WEB_SOURCE:-$PROJECT_ROOT/web/dist}"
-CONFIG_TEMPLATE="${CONFIG_TEMPLATE:-$PROJECT_ROOT/server/config.example.yaml}"
-SERVICE_SOURCE="${SERVICE_SOURCE:-$PROJECT_ROOT/deploy/backupx.service}"
-NGINX_SOURCE="${NGINX_SOURCE:-$PROJECT_ROOT/deploy/nginx.conf}"
+if [ -f "$SCRIPT_DIR/backupx" ] && [ -d "$SCRIPT_DIR/web" ]; then
+    BIN_SOURCE="${BIN_SOURCE:-$SCRIPT_DIR/backupx}"
+    WEB_SOURCE="${WEB_SOURCE:-$SCRIPT_DIR/web}"
+    CONFIG_TEMPLATE="${CONFIG_TEMPLATE:-$SCRIPT_DIR/config.example.yaml}"
+    NGINX_SOURCE="${NGINX_SOURCE:-$SCRIPT_DIR/nginx.conf}"
+    SERVICE_SOURCE_DEFAULT="$SCRIPT_DIR/backupx.service"
+else
+    SOURCE_BIN_DEFAULT="$PROJECT_ROOT/server/bin/backupx"
+    # Keep compatibility with contributors who built the historical path by
+    # hand, while matching the canonical `make build` output first.
+    if [ ! -f "$SOURCE_BIN_DEFAULT" ] && [ -f "$PROJECT_ROOT/server/backupx" ]; then
+        SOURCE_BIN_DEFAULT="$PROJECT_ROOT/server/backupx"
+    fi
+    BIN_SOURCE="${BIN_SOURCE:-$SOURCE_BIN_DEFAULT}"
+    WEB_SOURCE="${WEB_SOURCE:-$PROJECT_ROOT/web/dist}"
+    CONFIG_TEMPLATE="${CONFIG_TEMPLATE:-$PROJECT_ROOT/server/config.example.yaml}"
+    NGINX_SOURCE="${NGINX_SOURCE:-$PROJECT_ROOT/deploy/nginx.conf}"
+    SERVICE_SOURCE_DEFAULT="$PROJECT_ROOT/deploy/backupx.service"
+fi
+SERVICE_SOURCE_EXPLICIT=0
+if [ -n "${SERVICE_SOURCE:-}" ]; then
+    SERVICE_SOURCE_EXPLICIT=1
+fi
+SERVICE_SOURCE="${SERVICE_SOURCE:-$SERVICE_SOURCE_DEFAULT}"
+INSTALL_NGINX="${INSTALL_NGINX:-0}"

 if [ "$(id -u)" -ne 0 ]; then
    echo "请使用 root 或 sudo 执行安装脚本。" >&2
    exit 1
 fi

+validate_install_path() {
+    path_name="$1"
+    path_value="$2"
+    case "$path_value" in
+        /*) ;;
+        *) echo "$path_name 必须是绝对路径: $path_value" >&2; exit 1 ;;
+    esac
+    case "$path_value" in
+        /|*"//"*|*"/./"*|*"/."|*"/../"*|*"/.."|*[!A-Za-z0-9_./+-]*)
+            echo "$path_name 必须是规范、安全且非根目录的绝对路径: $path_value" >&2
+            exit 1
+            ;;
+    esac
+}
+
+validate_install_path PREFIX "$PREFIX"
+validate_install_path ETC_DIR "$ETC_DIR"
+
 if [ ! -f "$BIN_SOURCE" ]; then
-    echo "未找到后端二进制：$BIN_SOURCE" >&2
-    echo "请先执行：cd \"$PROJECT_ROOT/server\" && go build -o backupx ./cmd/backupx" >&2
+    echo "Backend binary not found / 未找到后端二进制：$BIN_SOURCE" >&2
+    echo "源码树安装请先在仓库根目录执行 make build（产物：server/bin/backupx）。" >&2
+    echo "For a source install, run 'make build' in the repository root first." >&2
+    echo "发布包安装请确认当前目录包含 ./backupx、./web 和 ./install.sh。" >&2
    exit 1
 fi

 if [ ! -d "$WEB_SOURCE" ]; then
    echo "未找到前端构建产物：$WEB_SOURCE" >&2
-    echo "请先执行：cd \"$PROJECT_ROOT/web\" && npm run build" >&2
+    echo "源码树安装请先执行：cd \"$PROJECT_ROOT/web\" && npm run build" >&2
+    echo "发布包安装请确认当前目录包含 ./web。" >&2
    exit 1
 fi

+if [ ! -f "$CONFIG_TEMPLATE" ]; then
+    echo "未找到配置模板：$CONFIG_TEMPLATE" >&2
+    exit 1
+fi
+
+if [ "$SERVICE_SOURCE_EXPLICIT" = "1" ] && [ ! -f "$SERVICE_SOURCE" ]; then
+    echo "指定的 systemd unit 不存在：$SERVICE_SOURCE" >&2
+    exit 1
+fi
+
+for managed_path in "$PREFIX" "$PREFIX/bin" "$PREFIX/web" "$PREFIX/data" "$ETC_DIR"; do
+    if [ -L "$managed_path" ]; then
+        echo "拒绝通过符号链接写入受管目录：$managed_path" >&2
+        exit 1
+    fi
+done
+
 if ! getent group "$APP_GROUP" >/dev/null 2>&1; then
    groupadd --system "$APP_GROUP"
 fi
@@ -38,25 +97,103 @@ if ! id "$APP_USER" >/dev/null 2>&1; then
    useradd --system --gid "$APP_GROUP" --home-dir "$PREFIX" --shell /usr/sbin/nologin "$APP_USER"
 fi

-install -d -o "$APP_USER" -g "$APP_GROUP" "$PREFIX" "$PREFIX/bin" "$PREFIX/web" "$PREFIX/data" "$ETC_DIR"
-install -m 0755 "$BIN_SOURCE" "$PREFIX/bin/backupx"
+install -d -o root -g root -m 0755 "$PREFIX" "$PREFIX/bin" "$PREFIX/web"
+install -d -o "$APP_USER" -g "$APP_GROUP" -m 0750 "$PREFIX/data"
+install -d -o root -g "$APP_GROUP" -m 0750 "$ETC_DIR"
+install -o root -g root -m 0755 "$BIN_SOURCE" "$PREFIX/bin/backupx.new"
+mv -f "$PREFIX/bin/backupx.new" "$PREFIX/bin/backupx"
 cp -R "$WEB_SOURCE/." "$PREFIX/web/"
-chown -R "$APP_USER:$APP_GROUP" "$PREFIX"
+chown -R root:root "$PREFIX/bin" "$PREFIX/web"
+find "$PREFIX/web" -type d -exec chmod 0755 {} \;
+find "$PREFIX/web" -type f -exec chmod 0644 {} \;
+chown -R "$APP_USER:$APP_GROUP" "$PREFIX/data"

 if [ ! -f "$ETC_DIR/config.yaml" ]; then
-    install -m 0640 "$CONFIG_TEMPLATE" "$ETC_DIR/config.yaml"
+    install -o root -g "$APP_GROUP" -m 0640 "$CONFIG_TEMPLATE" "$ETC_DIR/config.yaml"
+fi
+# 服务账户只需读取配置，不应拥有修改 /etc 配置或可执行文件的权限。
+chown root:"$APP_GROUP" "$ETC_DIR/config.yaml"
+chmod 0640 "$ETC_DIR/config.yaml"
+
+# 仓库 unit 使用标准路径；自定义 PREFIX/ETC_DIR 时动态生成以保持路径一致。
+# 显式传入 SERVICE_SOURCE 表示调用方已经审核其中的路径，始终优先使用。
+if [ -f "$SERVICE_SOURCE" ] && { [ "$SERVICE_SOURCE_EXPLICIT" = "1" ] || { [ "$PREFIX" = "/opt/backupx" ] && [ "$ETC_DIR" = "/etc/backupx" ]; }; }; then
+    install -m 0644 "$SERVICE_SOURCE" "/etc/systemd/system/$SERVICE_NAME.service"
+else
+    cat > "/etc/systemd/system/$SERVICE_NAME.service" <<UNIT
+[Unit]
+Description=BackupX API Service
+After=network-online.target
+Wants=network-online.target
+
+[Service]
+Type=simple
+User=$APP_USER
+Group=$APP_GROUP
+WorkingDirectory=$PREFIX
+ExecStart=$PREFIX/bin/backupx -config $ETC_DIR/config.yaml
+Restart=on-failure
+RestartSec=5
+NoNewPrivileges=true
+UMask=0027
+LimitNOFILE=65535
+
+[Install]
+WantedBy=multi-user.target
+UNIT
+fi
+systemctl daemon-reload
+if ! systemctl enable "$SERVICE_NAME" || ! systemctl restart "$SERVICE_NAME"; then
+    echo "BackupX systemd 服务启动失败。" >&2
+    systemctl status "$SERVICE_NAME" --no-pager >&2 || true
+    journalctl -u "$SERVICE_NAME" -n 50 --no-pager >&2 || true
+    exit 1
 fi

-install -m 0644 "$SERVICE_SOURCE" "/etc/systemd/system/$SERVICE_NAME.service"
-systemctl daemon-reload
-systemctl enable --now "$SERVICE_NAME"
-
-if [ -d "/etc/nginx/conf.d" ]; then
-    install -m 0644 "$NGINX_SOURCE" "/etc/nginx/conf.d/$SERVICE_NAME.conf"
-    if command -v nginx >/dev/null 2>&1; then
-        nginx -t
-        systemctl reload nginx || true
+# systemctl may return before the process has opened its HTTP listener. Verify
+# the same unauthenticated endpoint used by the first-administrator screen so a
+# broken bare-metal install cannot print a false success message.
+HEALTH_URL="${HEALTH_URL:-http://127.0.0.1:8340/api/auth/setup/status}"
+READY=0
+ATTEMPT=1
+while [ "$ATTEMPT" -le 30 ]; do
+    if systemctl is-active --quiet "$SERVICE_NAME"; then
+        if command -v curl >/dev/null 2>&1; then
+            if curl -fsS --max-time 2 "$HEALTH_URL" >/dev/null 2>&1; then
+                READY=1
+                break
+            fi
+        elif command -v wget >/dev/null 2>&1; then
+            if wget -q -T 2 -O /dev/null "$HEALTH_URL"; then
+                READY=1
+                break
+            fi
+        else
+            echo "Warning / 警告：未找到 curl 或 wget，仅验证 systemd 服务状态。" >&2
+            READY=1
+            break
+        fi
    fi
+    ATTEMPT=$((ATTEMPT + 1))
+    sleep 1
+done
+
+if [ "$READY" -ne 1 ]; then
+    echo "BackupX did not become ready at $HEALTH_URL / 服务未通过就绪检查。" >&2
+    systemctl status "$SERVICE_NAME" --no-pager >&2 || true
+    journalctl -u "$SERVICE_NAME" -n 50 --no-pager >&2 || true
+    exit 1
+fi
+
+if [ "$INSTALL_NGINX" = "1" ]; then
+    if [ ! -d "/etc/nginx/conf.d" ] || [ ! -f "$NGINX_SOURCE" ]; then
+        echo "已请求安装 Nginx 配置，但未找到 /etc/nginx/conf.d 或配置模板。" >&2
+        exit 1
+    fi
+    install -o root -g root -m 0644 "$NGINX_SOURCE" "/etc/nginx/conf.d/$SERVICE_NAME.conf"
+    command -v nginx >/dev/null 2>&1 || { echo "未找到 nginx 命令。" >&2; exit 1; }
+    nginx -t
+    systemctl reload nginx
 fi

 cat <<MESSAGE
@@ -67,6 +204,20 @@ cat <<MESSAGE
 - 配置文件：$ETC_DIR/config.yaml
 - systemd 服务：/etc/systemd/system/$SERVICE_NAME.service

+Web 控制台已由后端直接托管，无需额外的 nginx 反向代理即可访问：
+  http://<本机IP>:8340
+
+首次访问 / First sign-in:
+  1. 打开上面的地址，并可在登录页右上角选择 中文 或 English。
+  2. 页面显示“系统初始化 / System setup”时，创建首个管理员用户名和密码。
+  3. 如果未显示初始化表单，请先检查：$HEALTH_URL
+
+如需安装仓库提供的 Nginx 模板，请审核域名与 TLS 配置后重新执行：
+  sudo INSTALL_NGINX=1 ./install.sh
+
+排查：若服务未监听端口，请查看日志：
+  journalctl -u "$SERVICE_NAME" -n 50 --no-pager
+
 如需修改监听地址、数据库路径或日志级别，请编辑 "$ETC_DIR/config.yaml" 后执行：
  systemctl restart "$SERVICE_NAME"
 MESSAGE
--- a/deploy/nginx.conf
+++ b/deploy/nginx.conf
@@ -8,16 +8,38 @@ server {
    location /api/ {
        proxy_pass http://127.0.0.1:8340/api/;
        proxy_http_version 1.1;
-        proxy_set_header Host $host;
+        proxy_set_header Host $http_host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
+        proxy_set_header X-Forwarded-Host $http_host;
+        proxy_set_header X-Forwarded-Port $server_port;
        proxy_set_header Connection "";
+        client_max_body_size 0;
+        proxy_request_buffering off;
        proxy_buffering off;
        proxy_cache off;
        proxy_read_timeout 3600s;
    }

+    # Agent 一键安装脚本路径（兼容 v2.0 及之前生成的命令）。
+    # v2.1+ 新生成的命令走 /api/install/... 自动命中上面的 /api/ 代理。
+    location /install/ {
+        proxy_pass http://127.0.0.1:8340/install/;
+        proxy_http_version 1.1;
+        proxy_set_header Host $http_host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+        proxy_set_header X-Forwarded-Host $http_host;
+        proxy_set_header X-Forwarded-Port $server_port;
+    }
+
+    # 健康检查端点同样不走 SPA fallback。
+    location = /health { proxy_pass http://127.0.0.1:8340/health; }
+    location = /ready  { proxy_pass http://127.0.0.1:8340/ready; }
+    location = /metrics { proxy_pass http://127.0.0.1:8340/metrics; }
+
    location / {
        try_files $uri $uri/ /index.html;
    }
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -0,0 +1,48 @@
+# BackupX Docker Compose
+#
+# 快速启动：docker compose up -d
+# 访问地址：http://localhost:8340
+#
+# 生产环境建议在 .env 中固定 BACKUPX_IMAGE 版本，并通过 HTTPS 反向代理暴露服务。
+
+services:
+  backupx:
+    image: ${BACKUPX_IMAGE:-awuqing/backupx:latest}
+    # build: .
+    container_name: backupx
+    restart: unless-stopped
+    init: true
+    stop_grace_period: 30s
+    ports:
+      - "${BACKUPX_BIND_ADDRESS:-0.0.0.0}:${BACKUPX_PORT:-8340}:8340"
+    volumes:
+      - backupx-data:/app/data
+      # 挂载需要备份的宿主机目录（按需添加，:ro 表示只读）：
+      # - /var/www:/mnt/www:ro
+      # - /etc/nginx:/mnt/nginx-conf:ro
+      # - /home/user/data:/mnt/data:ro
+    security_opt:
+      - no-new-privileges:true
+    cap_drop:
+      - ALL
+    cap_add:
+      # 仅用于旧数据卷迁移与降权；应用进程随后以 backupx 运行。
+      - CHOWN
+      - DAC_OVERRIDE
+      - SETGID
+      - SETUID
+    environment:
+      TZ: ${TZ:-Asia/Shanghai}
+      # 远程 Agent 连接 Master 时，配置为所有节点可达的稳定 HTTPS URL：
+      # BACKUPX_SERVER_EXTERNAL_URL: https://backup.example.com
+      # BACKUPX_LOG_LEVEL: debug
+      # BACKUPX_BACKUP_MAX_CONCURRENT: "4"
+    healthcheck:
+      test: ["CMD", "su-exec", "backupx:backupx", "wget", "-q", "-T", "3", "-O", "/dev/null", "http://127.0.0.1:8340/ready"]
+      interval: 30s
+      timeout: 5s
+      retries: 3
+      start_period: 10s
+
+volumes:
+  backupx-data:
--- a/docs-site/.gitignore
+++ b/docs-site/.gitignore
@@ -0,0 +1,20 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
--- a/docs-site/README.md
+++ b/docs-site/README.md
@@ -0,0 +1,28 @@
+# BackupX documentation site
+
+The public documentation is a Docusaurus site with English source documents and a complete Simplified Chinese translation.
+
+## Local development
+
+```bash
+npm ci
+npm start
+```
+
+Use `npm start -- --locale zh-Hans` to preview the Chinese site. The public Chinese URL remains `/zh-Hans/`; its source files live under `i18n/zh-CN/` through the locale `path` mapping in `docusaurus.config.ts`.
+
+## Verification
+
+```bash
+npm run typecheck
+npm run build
+```
+
+The production build renders both locales and fails on broken document links. GitHub Actions publishes `build/` to GitHub Pages after changes reach `main`; do not deploy the site manually from a feature branch.
+
+When adding, renaming, or removing a document:
+
+1. Apply the same change under `docs/` and `i18n/zh-CN/docusaurus-plugin-content-docs/current/`.
+2. Update `sidebars.ts` and the translated sidebar labels when a category changes.
+3. Use relative links for links between documents so both locale prefixes resolve correctly.
+4. Run the full verification commands before opening a pull request.
--- a/docs-site/docs/deployment/bare-metal.md
+++ b/docs-site/docs/deployment/bare-metal.md
@@ -0,0 +1,121 @@
+---
+sidebar_position: 2
+title: Bare-metal Deployment
+description: Hardened systemd deployment from the prebuilt release tarball or source, with opt-in Nginx.
+---
+
+# Bare-metal Deployment
+
+## From prebuilt release
+
+```bash
+# Download the matching tarball
+curl -LO https://github.com/Awuqing/BackupX/releases/latest/download/backupx-linux-amd64.tar.gz
+curl -LO https://github.com/Awuqing/BackupX/releases/latest/download/backupx-linux-amd64.tar.gz.sha256
+sha256sum -c backupx-linux-amd64.tar.gz.sha256
+
+# Extract and install
+tar xzf backupx-linux-amd64.tar.gz && cd backupx-*-linux-amd64
+sudo ./install.sh
+```
+
+The installer performs these steps automatically:
+
+1. Creates a system user `backupx`
+2. Copies the binary to `/opt/backupx/bin/backupx` and the web console to `/opt/backupx/web`
+3. Installs the default configuration at `/etc/backupx/config.yaml`
+4. Installs `backupx.service` (systemd), enabled at boot
+5. Leaves Nginx unchanged unless `INSTALL_NGINX=1` is explicitly requested
+6. Verifies the first-setup API before reporting success
+
+The executable and web assets are owned by root; only `/opt/backupx/data` is writable by the `backupx` service account. `/etc/backupx/config.yaml` is installed as `root:backupx` with mode `0640`.
+
+The bundled Nginx template is a starting point and may conflict with an existing default server. Review its hostname and TLS policy first, then opt in:
+
+```bash
+sudo INSTALL_NGINX=1 ./install.sh
+```
+
+For multi-node clusters, edit `/etc/backupx/config.yaml` after installation and set the Master URL that remote Agents can reach:
+
+```yaml
+server:
+  external_url: "https://backup.example.com"
+```
+
+Restart BackupX after changing it:
+
+```bash
+sudo systemctl restart backupx
+```
+
+## From source
+
+```bash
+git clone https://github.com/Awuqing/BackupX.git && cd BackupX
+make build
+sudo ./deploy/install.sh
+```
+
+`make build` compiles:
+
+- `server/bin/backupx` (Go backend, no CGO)
+- `web/dist/` (React frontend, `npm run build`)
+
+## systemd
+
+The installed unit:
+
+```ini title="/etc/systemd/system/backupx.service"
+[Unit]
+Description=BackupX API Service
+After=network-online.target
+Wants=network-online.target
+
+[Service]
+Type=simple
+User=backupx
+Group=backupx
+WorkingDirectory=/opt/backupx
+ExecStart=/opt/backupx/bin/backupx -config /etc/backupx/config.yaml
+Restart=on-failure
+RestartSec=5
+NoNewPrivileges=true
+UMask=0027
+LimitNOFILE=65535
+
+[Install]
+WantedBy=multi-user.target
+```
+
+Typical operations:
+
+```bash
+sudo systemctl status backupx
+sudo journalctl -u backupx -f    # live logs
+sudo systemctl restart backupx
+curl -fsS http://127.0.0.1:8340/api/auth/setup/status
+```
+
+Open `http://your-server:8340`, switch to English if desired, and create the first administrator on the **System setup** screen. For a custom listen port, run the installer with a matching `HEALTH_URL`.
+
+For production, expose BackupX through HTTPS or restrict port `8340` at the firewall. The installer does not make firewall changes.
+
+Before replacing a release, snapshot `/etc/backupx`, `/opt/backupx/data`, the installed binary, and web assets while the service is stopped. Follow the versioned procedure in [Upgrade and Recovery](../operations/upgrade-recovery); running an older binary against a database already migrated by a newer release is not a safe rollback.
+
+## Password reset
+
+If the admin password is lost:
+
+```bash
+/opt/backupx/bin/backupx reset-password \
+  --username admin \
+  --password 'newpass123' \
+  --config /etc/backupx/config.yaml
+```
+
+Docker equivalent:
+
+```bash
+docker exec -it backupx /app/bin/backupx reset-password --username admin --password 'newpass123'
+```
--- a/docs-site/docs/deployment/configuration.md
+++ b/docs-site/docs/deployment/configuration.md
@@ -0,0 +1,97 @@
+---
+sidebar_position: 4
+title: Configuration Reference
+description: All config.yaml server keys with defaults and matching environment variables.
+---
+
+# Configuration Reference
+
+BackupX loads `./config.yaml` from the working directory by default. You can override the path with `--config`. Every key can also be set via a `BACKUPX_` prefixed environment variable.
+
+## Full config reference
+
+```yaml title="config.yaml"
+server:
+  host: "0.0.0.0"             # BACKUPX_SERVER_HOST
+  port: 8340                  # BACKUPX_SERVER_PORT
+  mode: "release"             # release | debug
+  external_url: ""            # BACKUPX_SERVER_EXTERNAL_URL — stable public Master URL
+  trusted_proxies:             # BACKUPX_SERVER_TRUSTED_PROXIES — exact proxy IPs/CIDRs
+    - "127.0.0.1"
+    - "::1"
+  web_root: ""                # BACKUPX_SERVER_WEB_ROOT — built frontend directory
+
+database:
+  path: "./data/backupx.db"   # BACKUPX_DATABASE_PATH — embedded SQLite
+
+security:
+  jwt_secret: ""              # BACKUPX_SECURITY_JWT_SECRET — auto-generated if empty
+  jwt_expire: "24h"           # BACKUPX_SECURITY_JWT_EXPIRE
+  encryption_key: ""          # AES-256-GCM key for storage config encryption
+
+backup:
+  temp_dir: "/tmp/backupx"    # BACKUPX_BACKUP_TEMP_DIR
+  max_concurrent: 2           # BACKUPX_BACKUP_MAX_CONCURRENT
+  retries: 10                 # Per-upload rclone low-level retries
+  bandwidth_limit: ""         # e.g. "10M" to cap transfers at 10 MB/s
+
+log:
+  level: "info"               # debug | info | warn | error
+  file: "./data/backupx.log"
+  max_size: 100               # MB per log file
+  max_backups: 3              # rotated files retained
+  max_age: 30                 # retention in days
+```
+
+## Secret generation
+
+If `jwt_secret` or `encryption_key` is empty on first start, BackupX generates a random value and persists it to the `system_configs` table. Keep a backup of `data/backupx.db` — losing it invalidates all existing encrypted storage configurations.
+
+## Environment variables
+
+The environment wins when both file and env are set. All dot-paths become underscores and uppercase:
+
+| Config key | Env variable |
+|------------|--------------|
+| `server.port` | `BACKUPX_SERVER_PORT` |
+| `server.external_url` | `BACKUPX_SERVER_EXTERNAL_URL` |
+| `server.trusted_proxies` | `BACKUPX_SERVER_TRUSTED_PROXIES` (comma-separated for env) |
+| `security.jwt_secret` | `BACKUPX_SECURITY_JWT_SECRET` |
+| `security.jwt_expire` | `BACKUPX_SECURITY_JWT_EXPIRE` |
+| `security.encryption_key` | `BACKUPX_SECURITY_ENCRYPTION_KEY` |
+| `log.level` | `BACKUPX_LOG_LEVEL` |
+| `backup.max_concurrent` | `BACKUPX_BACKUP_MAX_CONCURRENT` |
+| `backup.temp_dir` | `BACKUPX_BACKUP_TEMP_DIR` |
+| `backup.retries` | `BACKUPX_BACKUP_RETRIES` |
+| `backup.bandwidth_limit` | `BACKUPX_BACKUP_BANDWIDTH_LIMIT` |
+| `log.max_size` | `BACKUPX_LOG_MAX_SIZE` |
+| `log.max_backups` | `BACKUPX_LOG_MAX_BACKUPS` |
+| `log.max_age` | `BACKUPX_LOG_MAX_AGE` |
+
+## Master external URL
+
+Set `server.external_url` when BackupX is behind Docker, Nginx, a load balancer, or any reverse proxy whose internal Host is not reachable by remote Agents:
+
+```yaml
+server:
+  external_url: "https://backup.example.com"
+```
+
+This value is used when BackupX renders one-click Agent install scripts and docker-compose snippets. It must be reachable from every Agent host. Leave it empty only when `X-Forwarded-Proto` / `X-Forwarded-Host` are reliable and point to the same URL that Agents can access.
+
+The install wizard can set an Agent-specific URL for a proxy or SSH-bastion node. That override is used by both the target-side one-time install URL and the generated Agent runtime configuration, while the browser continues to use the normal public address.
+
+## Trusted reverse proxies
+
+BackupX trusts forwarded client-address headers only from `server.trusted_proxies`. The default permits loopback Nginx only. If a reverse proxy runs in another container or host, add its exact IP or subnet:
+
+```yaml
+server:
+  trusted_proxies:
+    - "127.0.0.1"
+    - "172.18.0.0/16"
+```
+
+Do not configure `0.0.0.0/0`: client addresses feed authentication throttling, install-token throttling, and audit records. Set an empty list when BackupX is exposed directly and should trust no forwarded headers.
+
+Back up the complete data directory and configuration before changing security keys or database paths. See [Upgrade and Recovery](../operations/upgrade-recovery) for a tested snapshot and rollback sequence.
--- a/docs-site/docs/deployment/docker.md
+++ b/docs-site/docs/deployment/docker.md
@@ -0,0 +1,98 @@
+---
+sidebar_position: 1
+title: Docker Deployment
+description: Hardened single-process Docker deployment with health checks and persistent data.
+---
+
+# Docker Deployment
+
+The official [`awuqing/backupx`](https://hub.docker.com/r/awuqing/backupx) image supports `linux/amd64` and `linux/arm64`.
+
+## Compose file
+
+```yaml title="docker-compose.yml"
+services:
+  backupx:
+    image: ${BACKUPX_IMAGE:-awuqing/backupx:latest}
+    container_name: backupx
+    restart: unless-stopped
+    init: true
+    stop_grace_period: 30s
+    ports:
+      - "${BACKUPX_BIND_ADDRESS:-0.0.0.0}:${BACKUPX_PORT:-8340}:8340"
+    volumes:
+      - backupx-data:/app/data
+      # - /var/www:/mnt/www:ro
+      # - /etc/nginx:/mnt/nginx-conf:ro
+    security_opt:
+      - no-new-privileges:true
+    cap_drop:
+      - ALL
+    cap_add:
+      - CHOWN
+      - DAC_OVERRIDE
+      - SETGID
+      - SETUID
+    environment:
+      TZ: Asia/Shanghai
+      # BACKUPX_SERVER_EXTERNAL_URL: https://backup.example.com
+      BACKUPX_LOG_LEVEL: info
+      BACKUPX_BACKUP_MAX_CONCURRENT: "2"
+    healthcheck:
+      test: ["CMD", "su-exec", "backupx:backupx", "wget", "-q", "-T", "3", "-O", "/dev/null", "http://127.0.0.1:8340/ready"]
+      interval: 30s
+      timeout: 5s
+      retries: 3
+      start_period: 10s
+
+volumes:
+  backupx-data:
+```
+
+```bash
+docker compose up -d
+docker compose ps
+```
+
+The entrypoint uses root only to migrate ownership of data written by older images, then starts one unprivileged `backupx` process. Compose retains only the ownership and UID/GID transition capabilities needed for that initialization. The backend serves both the API and built web assets; the image neither mounts the Docker socket nor bundles a Docker CLI. Pin `BACKUPX_IMAGE` to a release tag in production.
+
+## Host-directory backups
+
+Mount each source directory and use its container path in the task. The container's `backupx` user must be able to read it; restore destinations need a separate, narrowly scoped writable mount. Prefer a remote Agent for privileged host paths. If a Master-side task truly requires root, make that exception explicit with `user: "0:0"` and review every mount.
+
+## Multi-node cluster
+
+Set the stable URL that Agents can reach:
+
+```yaml
+environment:
+  BACKUPX_SERVER_EXTERNAL_URL: https://backup.example.com
+```
+
+Use HTTPS across untrusted networks. Proxy, private-CA, and SSH-bastion deployments are covered in [Multi-Node Cluster](../features/multi-node).
+
+If an external reverse proxy is in another container, add only its bridge subnet to `BACKUPX_SERVER_TRUSTED_PROXIES`, for example `172.18.0.0/16`. Do not trust every address.
+
+## Environment overrides
+
+```yaml
+environment:
+  TZ: Asia/Shanghai
+  BACKUPX_LOG_LEVEL: debug
+  BACKUPX_BACKUP_MAX_CONCURRENT: "4"
+  BACKUPX_BACKUP_TEMP_DIR: /tmp/backupx
+```
+
+The image's internal port is fixed at `8340`; change only the published host port with `BACKUPX_PORT`.
+
+## Upgrade prerequisites
+
+```bash
+docker compose pull
+docker compose up -d
+docker compose ps
+```
+
+Wait for `healthy` before switching traffic or removing an old deployment. Before upgrades, stop the Master for a file-level copy or take an atomic snapshot of the entire `backupx-data` volume. Keep exactly one active Master for a data volume; SQLite does not support multiple Master containers sharing `/app/data`.
+
+Use a release tag or digest instead of `latest`, and keep the matching pre-upgrade data snapshot. The complete upgrade, rollback, and disaster-recovery procedure is in [Upgrade and Recovery](../operations/upgrade-recovery).
--- a/docs-site/docs/deployment/nginx.md
+++ b/docs-site/docs/deployment/nginx.md
@@ -0,0 +1,82 @@
+---
+sidebar_position: 3
+title: Nginx Reverse Proxy
+description: Expose BackupX behind Nginx with HTTPS and SSE-friendly buffering disabled.
+---
+
+# Nginx Reverse Proxy
+
+A minimal production-ready Nginx site for BackupX:
+
+```nginx title="/etc/nginx/sites-available/backupx"
+server {
+    listen 80;
+    server_name backup.example.com;
+
+    # Static UI (served from /opt/backupx/web)
+    location / {
+        root /opt/backupx/web;
+        try_files $uri $uri/ /index.html;
+    }
+
+    # API reverse proxy
+    location /api/ {
+        proxy_pass http://127.0.0.1:8340;
+        proxy_http_version 1.1;
+        proxy_set_header Host $http_host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+        proxy_set_header X-Forwarded-Host $http_host;
+        proxy_set_header X-Forwarded-Port $server_port;
+        proxy_set_header Connection "";
+
+        # Large uploads (restore flow)
+        client_max_body_size 0;
+        proxy_request_buffering off;
+
+        # Live log stream uses SSE — buffering must be off
+        proxy_buffering off;
+        proxy_cache off;
+        proxy_read_timeout 3600s;
+        proxy_send_timeout 3600s;
+    }
+
+    # Compatibility route for installers generated by older releases.
+    # Current installers use /api/install/ through the API block above.
+    location /install/ {
+        proxy_pass http://127.0.0.1:8340/install/;
+        proxy_http_version 1.1;
+        proxy_set_header Host $http_host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+        proxy_set_header X-Forwarded-Host $http_host;
+        proxy_set_header X-Forwarded-Port $server_port;
+    }
+
+    # Keep probes and metrics out of the SPA fallback.
+    location = /health { proxy_pass http://127.0.0.1:8340/health; }
+    location = /ready  { proxy_pass http://127.0.0.1:8340/ready; }
+    location = /metrics { proxy_pass http://127.0.0.1:8340/metrics; }
+}
+```
+
+`proxy_request_buffering off` is required for Master-relay cluster backups. Without it, Nginx writes the complete Agent upload to its temporary storage before BackupX receives it, defeating streaming and potentially filling the proxy disk.
+
+If Nginx runs on another host or in another container, add only that proxy IP or subnet to `server.trusted_proxies`. Do not use `0.0.0.0/0`; BackupX uses the trusted client address for login throttling, install-token throttling, and audit records.
+
+`/health`, `/ready`, and `/metrics` do not require BackupX authentication. Allow probe and Prometheus source networks explicitly, or keep these locations on an internal listener instead of exposing them to the Internet.
+
+## HTTPS with certbot
+
+```bash
+sudo apt install certbot python3-certbot-nginx
+sudo certbot --nginx -d backup.example.com
+```
+
+Certbot rewrites the config to listen on 443 with auto-renewal.
+
+:::caution Agent needs a stable URL
+If Master is behind HTTPS, remote Agent deployments must use the final HTTPS URL for `--master`; redirects are not followed. For a private CA, pre-provision its PEM certificate and use `--ca-cert /path/to/ca.pem`. Reserve `--insecure-tls` for short-lived testing.
+:::
--- a/docs-site/docs/development/contributing.md
+++ b/docs-site/docs/development/contributing.md
@@ -0,0 +1,41 @@
+---
+sidebar_position: 2
+title: Contributing
+description: How to report issues, propose changes, and submit PRs.
+---
+
+# Contributing
+
+BackupX is open-source under Apache License 2.0. Issues and pull requests are welcome.
+
+## Reporting bugs
+
+Open an issue at [github.com/Awuqing/BackupX/issues](https://github.com/Awuqing/BackupX/issues). Please include:
+
+- BackupX version (`backupx --version`)
+- Your deployment mode (Docker / bare metal / from source)
+- Relevant backup task type and storage backend
+- Steps to reproduce
+- Stdout / `backupx.log` excerpt for the window around the problem
+
+## Proposing changes
+
+For significant features or refactors, open an issue first to align on scope before investing in a PR.
+
+## Pull requests
+
+1. Fork and create a topic branch (e.g. `fix/windows-path-escape`)
+2. Run `make test` and make sure everything passes
+3. Keep changes focused — one concern per PR
+4. Write commit messages in Chinese following `类型: 简要描述` — examples:
+   - `功能: 新增审计日志模块`
+   - `修复: 目录浏览器无法进入子目录`
+   - `重构: 简化存储目标解密逻辑`
+   - Types: `功能` / `修复` / `重构` / `文档` / `构建` / `测试`
+5. PR title and body in Chinese too. Describe the why and how, not just the what.
+
+## Coding guidelines
+
+- **Go** — handle every error (no `_ = err`); use the existing logger (`zap`); no `fmt.Println` in production paths
+- **TypeScript** — strict mode, no implicit any, follow existing ESLint/Prettier configs
+- **Commit scope** — one logical change per commit; don't mix drive-by cleanups with feature work
--- a/docs-site/docs/development/setup.md
+++ b/docs-site/docs/development/setup.md
@@ -0,0 +1,83 @@
+---
+sidebar_position: 1
+title: Development Setup
+description: Get a BackupX dev environment running — backend, frontend, tests.
+---
+
+# Development Setup
+
+**Requirements:** Go ≥ 1.25, Node.js 24 LTS, npm 11 or later.
+
+## Clone & install
+
+```bash
+git clone https://github.com/Awuqing/BackupX.git && cd BackupX
+cd web && npm install && cd ..
+```
+
+## Dev servers
+
+Run the backend and the Vite dev server in two terminals:
+
+```bash
+# Terminal 1: backend on :8340
+make dev-server
+
+# Terminal 2: Vite with HMR on :5173
+make dev-web
+```
+
+The Vite config proxies `/api` to `http://127.0.0.1:8340` so you can open the UI at `http://localhost:5173`.
+
+## Tests
+
+```bash
+make test           # runs Go + Web test suites
+make test-server    # Go only
+make test-web       # Vitest only
+```
+
+## Production build
+
+```bash
+make build          # server/bin/backupx + web/dist
+make docker         # Docker image
+make docker-cn      # Docker image with mainland China mirrors
+```
+
+## Tech stack
+
+| Component | Stack |
+|-----------|-------|
+| **Backend** | Go · Gin · GORM · SQLite · robfig/cron · rclone |
+| **Frontend** | React 18 · TypeScript · ArcoDesign · Vite · Zustand · ECharts |
+| **Storage** | rclone (70+ backends) · AWS SDK v2 · Google Drive API v3 |
+| **Security** | JWT · bcrypt · AES-256-GCM |
+
+## Project layout
+
+```
+BackupX/
+├── server/             # Go backend
+│   ├── cmd/backupx/    # Entry point + subcommands (agent, backint, reset-password)
+│   ├── internal/
+│   │   ├── agent/      # Agent CLI logic
+│   │   ├── app/        # Wiring (repositories → services → handlers)
+│   │   ├── backup/     # Backup runners (file / mysql / postgres / sqlite / saphana)
+│   │   ├── backint/    # SAP HANA Backint protocol
+│   │   ├── http/       # HTTP handlers + router
+│   │   ├── model/      # GORM models
+│   │   ├── repository/ # DB access
+│   │   ├── service/    # Business logic
+│   │   └── storage/    # Storage providers (rclone + direct SDKs)
+│   └── pkg/            # Generic utilities
+├── web/                # React frontend (Vite)
+│   └── src/
+│       ├── components/
+│       ├── pages/
+│       ├── services/
+│       └── types/
+├── docs-site/          # This documentation site (Docusaurus)
+├── deploy/             # install.sh, systemd unit, nginx config
+└── Makefile
+```
--- a/docs-site/docs/features/backup-types.md
+++ b/docs-site/docs/features/backup-types.md
@@ -0,0 +1,54 @@
+---
+sidebar_position: 1
+title: Backup Types
+description: File, MySQL, PostgreSQL, SQLite and SAP HANA — what they back up and what to configure.
+---
+
+# Backup Types
+
+BackupX supports five built-in backup types. Type determines which runner executes the job.
+
+When a task is routed to a remote Agent, the source tools and paths are resolved on that Agent host. Multi-target uploads are still tracked per storage target; if at least one target succeeds, the backup record is marked successful and the per-target result table shows partial failures.
+
+## File / Directory
+
+File tasks offer three backup modes:
+
+- **Full archive** — writes a self-contained tar artifact on every run
+- **Differential archive** — writes only changes since the current full baseline and periodically refreshes that baseline
+- **CDC repository** — splits content with stable 512 KiB / 1 MiB / 4 MiB boundaries, stores new chunks in immutable 32 MiB packs, and writes a small snapshot manifest for each run
+
+The CDC repository deduplicates identical content across files and snapshots. Restore, selective restore, verification, download-as-tar, retention, and garbage collection all resolve data through the repository index. Compression and encryption are applied per chunk; encrypted repositories use keyed chunk IDs so plaintext hashes are not exposed.
+
+Repository mode currently uses a single-writer index and therefore runs on the Master only. To keep repository copies on multiple backends, select multiple primary storage targets on the task. Object-level replication is intentionally disabled because a snapshot manifest without its shared packs and indexes is not a complete backup.
+
+Common file-task options:
+
+- **Source** accepts multiple paths — one per line in the UI
+- **Exclude patterns** accept gitignore-style globs
+- Supports following symlinks, preserving permissions
+- Full and differential modes output `.tar`, `.tar.gz`, or `.tar.zst` artifacts
+
+## MySQL
+
+Uses `mysqldump` under the hood. Requires `mysqldump` to be on `$PATH` of the host running the task (Master or Agent).
+
+- **Host / port / user / password / database** — multi-database allowed (comma-separated)
+- Output: `.sql` or `.sql.gz`
+- Default flags: `--single-transaction --routines --triggers --events`
+
+## PostgreSQL
+
+Uses `pg_dump`. Same connection fields as MySQL plus database name.
+
+## SQLite
+
+Copies the database file directly (with a consistency snapshot). No external tool required.
+
+## SAP HANA
+
+Two modes are supported — see the dedicated [SAP HANA](./sap-hana) page.
+
+## Deletion behavior
+
+When a task is deleted, BackupX removes backup artifacts from every storage target but preserves backup records for audit. Task deletion also tears down the cron schedule entry.
--- a/docs-site/docs/features/multi-node.md
+++ b/docs-site/docs/features/multi-node.md
@@ -0,0 +1,229 @@
+---
+sidebar_position: 4
+title: Multi-Node Cluster
+description: Deploy BackupX Agents through direct HTTPS, forward proxies, or SSH bastions.
+---
+
+# Multi-Node Cluster
+
+BackupX uses a single active Master as the control plane and an Agent on each source server. Agents initiate every connection, report a heartbeat every 15 seconds, and poll for commands every 5 seconds. No inbound Agent port is required.
+
+## Architecture and boundaries
+
+```text
+[Web console] ────────> [Active Master + SQLite]
+                              ^
+                              | outbound HTTP(S) polling
+                    +---------+---------+
+                    |         |         |
+                 [Agent B] [Agent C] [Agent D]
+                    |         |         |
+                    +----> storage targets
+```
+
+- Each node has an independent Agent Token. The Agent never receives the Master's JWT or encryption key.
+- A node is marked offline after 45 seconds without a heartbeat.
+- The Master persists commands; an Agent claims and executes them locally.
+- Network storage is normally written directly by the Agent. A Master-local target can opt into authenticated streaming relay.
+
+:::warning Single-active Master
+The embedded SQLite database is not a shared multi-writer database. Run exactly one active Master against a data directory. For control-plane recovery, use an active/passive host, persistent-volume snapshots, and a stable DNS name or virtual IP. Never scale multiple Master replicas over the same `/app/data` or `backupx.db`.
+:::
+
+BackupX applies a five-second SQLite busy timeout and command-queue indexes to reduce contention from concurrent Agent polls and task updates. Keep the database on a local or block-backed filesystem. For a file-level control-plane backup, stop the Master before copying the whole data directory; do not copy only `backupx.db` while it is running.
+
+## Choose a network path
+
+| Scenario | Agent Master URL | Agent proxy URL | Notes |
+| --- | --- | --- | --- |
+| Routed network or public service | `https://backup.example.com` | empty | Recommended; allow only outbound TCP 443 |
+| Corporate forward proxy | `https://backup.example.com` | `http://proxy.internal:3128` | HTTP(S) and SOCKS5(H) are supported |
+| SSH dynamic tunnel through a bastion | `https://backup.internal` | `socks5h://127.0.0.1:1080` | Preserves TLS hostname and resolves internal DNS through the tunnel |
+| SSH fixed local forward | `http://127.0.0.1:18340` | empty | The HTTP hop is protected by SSH; bind the forward to loopback only |
+
+For private PKI, provide the absolute path of a pre-provisioned PEM CA certificate. Do not use `--insecure-tls` in production.
+
+When no explicit proxy is configured, Agent-to-Master HTTP traffic follows `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY`. A system service does not normally inherit an interactive shell's environment, so set the proxy in the install wizard or Agent YAML for systemd deployments.
+
+## Prepare the Master
+
+Set a stable URL before generating commands:
+
+```yaml title="/etc/backupx/config.yaml"
+server:
+  external_url: "https://backup.example.com"
+  trusted_proxies:
+    - "127.0.0.1"
+    - "::1"
+    # Add the exact reverse-proxy IP or subnet when it is not local.
+    # - "172.18.0.0/16"
+```
+
+`external_url` is the default install and Agent runtime address. A restricted node can override both generated target-side URLs with its tunnel or internal address while the browser continues to use the public address.
+
+Use HTTPS across untrusted networks. For Master-relay uploads, configure the reverse proxy with unlimited request body size and request buffering disabled; see [Nginx Reverse Proxy](../deployment/nginx).
+
+Configure the Agent with the final API URL, not an HTTP-to-HTTPS redirect. The Agent deliberately does not follow redirects so its authentication Token cannot be forwarded to an unintended host.
+
+## Deploy an Agent
+
+Open **Node Management → Add Node**:
+
+1. Enter one node name, or up to 50 names in batch mode.
+2. Select systemd, Docker, or foreground mode; architecture; Agent release; command TTL; and download source.
+3. Select **Direct** or **Proxy or bastion**. For the restricted path, set an Agent-specific Master URL, proxy URL, or private CA path.
+4. Copy the generated command to the target host and run it with root privileges.
+
+Systemd is recommended for host-file backup and restore because the Agent needs access to arbitrary local paths. A Docker Agent sees only explicitly mounted paths; recreate it with read-only backup-source mounts and separately scoped writable restore destinations before assigning file tasks.
+
+The URL-based command downloads a one-time installer and verifies its marker before execution. The wizard binds the selected Agent URL, explicit proxy, and private CA to that download command as well as to the installed Agent configuration. If the install endpoint is still unreachable, use the separately displayed embedded command. The embedded command contains the long-lived node Token and must be handled as a secret.
+
+The installer:
+
+1. Detects `linux/amd64` or `linux/arm64`.
+2. Downloads the selected Release archive through the explicit proxy when configured, otherwise using the host's normal direct/environment-proxy route, and verifies its SHA-256 sidecar when the release provides one.
+3. Writes `/etc/backupx-agent/config.yaml` and `/etc/backupx-agent/agent.token` with mode `0600`.
+4. Keeps the Token out of the systemd unit and Docker environment metadata.
+5. Starts the Agent and checks `/api/v1/agent/self` for up to 30 seconds.
+6. Returns non-zero with systemd or Docker diagnostics when the node does not become online.
+
+Older releases without checksum sidecars remain installable with a warning. New releases should always publish and verify the sidecar.
+
+### Installed systemd configuration
+
+```yaml title="/etc/backupx-agent/config.yaml"
+master: "https://backup.example.com"
+tokenFile: "/etc/backupx-agent/agent.token"
+heartbeatInterval: "15s"
+pollInterval: "5s"
+tempDir: "/var/lib/backupx-agent/tmp"
+proxyUrl: ""
+caCertFile: ""
+```
+
+```ini title="/etc/systemd/system/backupx-agent.service"
+[Unit]
+Description=BackupX Agent
+After=network-online.target
+Wants=network-online.target
+StartLimitIntervalSec=300
+StartLimitBurst=10
+
+[Service]
+Type=simple
+ExecStart=/opt/backupx-agent/backupx agent --config /etc/backupx-agent/config.yaml
+Restart=on-failure
+RestartSec=10s
+TimeoutStopSec=30s
+UMask=0077
+LimitNOFILE=65535
+
+[Install]
+WantedBy=multi-user.target
+```
+
+The Agent runs as root because file backup and restore paths may belong to arbitrary system users. Restrict who can create tasks and who can modify the root-owned Agent configuration.
+
+## SSH bastion example
+
+Prefer a SOCKS tunnel when the internal Master uses HTTPS: its hostname and certificate validation remain unchanged.
+
+Create a dedicated SSH account and pre-provision its private key plus a verified `known_hosts` file. Then create:
+
+```sshconfig title="/etc/backupx-agent/ssh_config"
+Host backupx-bastion
+    HostName bastion.example.com
+    User backupx-tunnel
+    IdentityFile /etc/backupx-agent/tunnel_ed25519
+    IdentitiesOnly yes
+    BatchMode yes
+    UserKnownHostsFile /etc/backupx-agent/known_hosts
+    StrictHostKeyChecking yes
+    DynamicForward 127.0.0.1:1080
+    ExitOnForwardFailure yes
+    ServerAliveInterval 30
+    ServerAliveCountMax 3
+```
+
+```ini title="/etc/systemd/system/backupx-agent-tunnel.service"
+[Unit]
+Description=BackupX Agent SSH tunnel
+After=network-online.target
+Wants=network-online.target
+Before=backupx-agent.service
+
+[Service]
+Type=simple
+ExecStart=/usr/bin/ssh -NT -F /etc/backupx-agent/ssh_config backupx-bastion
+Restart=always
+RestartSec=5s
+
+[Install]
+WantedBy=multi-user.target
+```
+
+Add a drop-in so the Agent fails closed when the tunnel is unavailable:
+
+```ini title="/etc/systemd/system/backupx-agent.service.d/tunnel.conf"
+[Unit]
+Requires=backupx-agent-tunnel.service
+After=backupx-agent-tunnel.service
+```
+
+Reload and start both units:
+
+```bash
+sudo systemctl daemon-reload
+sudo systemctl enable --now backupx-agent-tunnel backupx-agent
+```
+
+In the wizard, keep the internal HTTPS Master URL and set the proxy to `socks5h://127.0.0.1:1080`. Verify the bastion host key out-of-band before enabling the service.
+
+## Central storage data paths
+
+| Destination | Data path |
+| --- | --- |
+| S3, WebDAV, FTP, cloud drive, or another network backend | Agent streams directly to the destination |
+| `local_disk` with **Relay remote backups through Master** enabled | Agent streams through the authenticated Master API; Master writes to its local mount |
+
+The relay does not create a second complete temporary copy on the Master. Restore uses the reverse streaming path. Nginx request buffering must be disabled for this behavior to remain streaming.
+
+## Operations
+
+```bash
+sudo systemctl status backupx-agent
+sudo journalctl -u backupx-agent -n 100 --no-pager
+sudo /opt/backupx-agent/backupx agent --config /etc/backupx-agent/config.yaml
+```
+
+Rotate a node Token from its action menu. Update `/etc/backupx-agent/agent.token` on the node and restart the service during the 24-hour overlap window.
+
+Monitor these Prometheus metrics:
+
+- `backupx_agent_command_queue_depth`
+- `backupx_agent_command_running`
+- `backupx_agent_command_timeout_total`
+- `backupx_node_online`
+
+## CLI reference
+
+```text
+backupx agent --help
+  -master string       Master URL
+  -token string        Agent authentication token
+  -token-file string   Read the Agent Token from a file
+  -config string       YAML configuration path
+  -temp-dir string     Local temporary directory
+  -proxy-url string    HTTP(S) or SOCKS5(H) proxy
+  -ca-cert string      PEM CA certificate used to verify the Master
+  -insecure-tls        Skip TLS verification (testing only)
+```
+
+Environment variables: `BACKUPX_AGENT_MASTER`, `BACKUPX_AGENT_TOKEN`, `BACKUPX_AGENT_TOKEN_FILE`, `BACKUPX_AGENT_HEARTBEAT`, `BACKUPX_AGENT_POLL`, `BACKUPX_AGENT_TEMP_DIR`, `BACKUPX_AGENT_PROXY_URL`, `BACKUPX_AGENT_CA_CERT_FILE`, and `BACKUPX_AGENT_INSECURE_TLS`.
+
+## Known limitations
+
+- The Master is single-active because it uses embedded SQLite.
+- Encrypted backups are Master-only because Agents do not hold the Master encryption key.
+- Remote directory browsing is a synchronous queue RPC with a 15-second timeout.
+- Claimed commands that stop reporting progress are timed out according to the Master command monitor.
--- a/docs-site/docs/features/notifications.md
+++ b/docs-site/docs/features/notifications.md
@@ -0,0 +1,49 @@
+---
+sidebar_position: 5
+title: Notifications
+description: Email, webhook, and Telegram notifications on backup success or failure.
+---
+
+# Notifications
+
+BackupX supports three notification channels. Configure per-channel rules for success-only, failure-only, or both.
+
+## Email (SMTP)
+
+| Field | Notes |
+|-------|-------|
+| SMTP host / port | e.g. `smtp.gmail.com:587` |
+| Username / password | App-specific password recommended |
+| From address | Used in `From:` header |
+| Recipients | Comma-separated list |
+| Use TLS / StartTLS | Match your SMTP provider |
+
+## Webhook
+
+Send a JSON POST to an arbitrary URL. Body shape:
+
+```json
+{
+  "event": "backup_result",
+  "task": {"id": 1, "name": "web-files", "type": "file"},
+  "record": {"id": 42, "status": "success", "fileSize": 1048576, "durationSeconds": 12},
+  "error": ""
+}
+```
+
+Useful for custom workflows: Slack incoming webhook, PagerDuty, your own API, etc.
+
+## Telegram
+
+| Field | Notes |
+|-------|-------|
+| Bot token | From [@BotFather](https://t.me/BotFather) |
+| Chat ID | Numeric — obtain via `/start` + bot's `getUpdates` |
+
+## Event rules
+
+Each notification configuration can be scoped to:
+
+- **Success only** — quiet during normal runs, pings on first failure
+- **Failure only** — recommended for loud channels
+- **Both** — useful during initial setup to verify notifications flow
--- a/docs-site/docs/features/sap-hana.md
+++ b/docs-site/docs/features/sap-hana.md
@@ -0,0 +1,79 @@
+---
+sidebar_position: 3
+title: SAP HANA Support
+description: Two SAP HANA backup modes — managed hdbsql runner and native Backint protocol agent.
+---
+
+# SAP HANA Support
+
+BackupX provides two SAP HANA backup modes. Pick whichever fits your operations workflow.
+
+## Mode 1: hdbsql Runner (console-managed)
+
+Create a SAP HANA backup task in the Web console. The backend invokes `hdbsql` to execute the backup. Use this when BackupX should own the schedule.
+
+**Source configuration supports:**
+
+| Field | Options | Description |
+|-------|---------|-------------|
+| Backup type | `data` / `log` | Data or log backup |
+| Backup level | `full` / `incremental` / `differential` | Auto-disabled for log backups |
+| Parallel channels | `1 ~ 32` | Multi-path SQL (`BACKUP DATA USING FILE ('c1', 'c2', ...)`) |
+| Retry count | `1 ~ 10` | Exponential backoff (`5s × attempt²`) |
+| Instance number | Optional | Inferred from port or specified manually |
+
+## Mode 2: Backint Protocol Agent (HANA native)
+
+BackupX ships a built-in Backint Agent. SAP HANA calls it via the native `BACKUP DATA USING BACKINT` syntax, and data is routed automatically to any BackupX storage target (S3 / OSS / COS / WebDAV / 70+ backends).
+
+### 1. Parameter file
+
+```ini title="/opt/backupx/backint_params.ini"
+#STORAGE_TYPE = s3
+#STORAGE_CONFIG_JSON = /opt/backupx/storage.json
+#PARALLEL_FACTOR = 4
+#COMPRESS = true
+#KEY_PREFIX = hana-backup
+#CATALOG_DB = /opt/backupx/backint_catalog.db
+#LOG_FILE = /var/log/backupx/backint.log
+```
+
+### 2. Storage config (same schema as storage targets)
+
+```json title="/opt/backupx/storage.json"
+{
+  "endpoint": "https://s3.amazonaws.com",
+  "region": "us-east-1",
+  "bucket": "hana-prod",
+  "accessKeyId": "AKIA...",
+  "secretAccessKey": "..."
+}
+```
+
+### 3. Create the hdbbackint symlink
+
+```bash
+ln -s /opt/backupx/backupx /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint
+```
+
+### 4. Enable Backint in HANA `global.ini`
+
+```ini
+[backup]
+data_backup_using_backint = true
+catalog_backup_using_backint = true
+log_backup_using_backint = true
+data_backup_parameter_file = /opt/backupx/backint_params.ini
+log_backup_parameter_file = /opt/backupx/backint_params.ini
+```
+
+### 5. Manual CLI invocation (troubleshooting)
+
+```bash
+backupx backint -f backup  -i input.txt -o output.txt -p backint_params.ini
+backupx backint -f restore -i input.txt -o output.txt -p backint_params.ini
+backupx backint -f inquire -i input.txt -o output.txt -p backint_params.ini
+backupx backint -f delete  -i input.txt -o output.txt -p backint_params.ini
+```
+
+The Backint Agent maintains an `EBID ↔ object-key` catalog in a local SQLite DB. All operations follow the SAP HANA Backint protocol (`#PIPE` / `#SAVED` / `#RESTORED` / `#BACKUP` / `#NOTFOUND` / `#DELETED` / `#ERROR`).
--- a/docs-site/docs/features/storage-backends.md
+++ b/docs-site/docs/features/storage-backends.md
@@ -0,0 +1,40 @@
+---
+sidebar_position: 2
+title: Storage Backends
+description: 70+ storage backends — built-in cloud providers plus any rclone backend.
+---
+
+# Storage Backends
+
+BackupX aims to accept any place you'd want to drop a backup file.
+
+## Built-in providers
+
+| Type | Required fields |
+|------|-----------------|
+| **Alibaba OSS** | Region + AccessKey ID/Secret + Bucket (endpoint auto-assembled) |
+| **Tencent COS** | Region + SecretId/SecretKey + Bucket (format `name-appid`) |
+| **Qiniu Kodo** | Region + AccessKey/SecretKey + Bucket |
+| **S3-compatible** | Endpoint + AccessKey + Bucket |
+| **Google Drive** | Client ID/Secret + OAuth authorization |
+| **WebDAV** | URL + username/password |
+| **FTP / FTPS** | Host + port + username/password |
+| **Local disk** | Target directory (absolute path) + optional Master relay for remote Agents |
+
+New local-disk targets enable **Relay remote backups through Master** by default. This makes the configured path belong to the Master, so a storage server mounted there can collect backups from many source Agents. Turn the switch off when the path intentionally belongs to each Agent. Existing targets retain their previous Agent-local behavior until explicitly changed.
+
+## Rclone backends
+
+Every [rclone backend](https://rclone.org/overview/) is exposed as a first-class storage type — SFTP, Azure Blob, Dropbox, OneDrive, Backblaze B2, Wasabi, pCloud, HDFS, and many more.
+
+- The form groups fields into **required** and **advanced** (advanced collapsed by default)
+- Validation and connection tests reuse rclone's built-in probe
+
+## Multiple targets per task
+
+A backup task can fan out to multiple targets in parallel. All targets receive the same artifact; a per-target status is recorded:
+
+- Success: storage path + size
+- Failed: error message
+
+If any target fails after retries, the record status is `failed` but successful targets are preserved (no rollback).
--- a/docs-site/docs/getting-started/installation.md
+++ b/docs-site/docs/getting-started/installation.md
@@ -0,0 +1,74 @@
+---
+sidebar_position: 1
+title: Installation
+description: Install BackupX via Docker, prebuilt archive, or from source.
+---
+
+# Installation
+
+BackupX ships as a single static binary. Three ways to install, pick the one that matches your environment.
+
+## Docker (recommended)
+
+Download the canonical hardened Compose file and start the service:
+
+```bash
+curl -fLO https://raw.githubusercontent.com/Awuqing/BackupX/main/docker-compose.yml
+docker compose up -d
+docker compose ps
+```
+
+The Compose definition enables init and graceful shutdown, persists `/app/data`, runs the application as an unprivileged user, drops unnecessary capabilities, and checks `/ready`. Images at [`awuqing/backupx`](https://hub.docker.com/r/awuqing/backupx) support `linux/amd64` and `linux/arm64`.
+
+For production, create a protected `.env` and pin a release instead of relying on `latest`:
+
+```dotenv
+BACKUPX_IMAGE=awuqing/backupx:vX.Y.Z
+BACKUPX_BIND_ADDRESS=127.0.0.1
+TZ=Asia/Shanghai
+```
+
+Use the loopback binding when a reverse proxy runs on the same host. For direct access, choose the intended interface and enforce a firewall. Mount host backup sources read-only or deploy an Agent on the source host. See [Docker Deployment](../deployment/docker) for the full configuration.
+
+## Prebuilt archive (bare metal)
+
+Download from the [Releases page](https://github.com/Awuqing/BackupX/releases) and run the installer:
+
+```bash
+sha256sum -c backupx-v*-linux-amd64.tar.gz.sha256
+tar xzf backupx-v*-linux-amd64.tar.gz && cd backupx-*
+sudo ./install.sh        # creates system user, installs to /opt/backupx, sets up systemd
+```
+
+The installer:
+
+1. Creates a `backupx` system user
+2. Installs the binary to `/opt/backupx/bin/backupx` and the web console to `/opt/backupx/web`
+3. Creates `/etc/backupx/config.yaml` with safe defaults
+4. Installs and enables the `backupx.service` systemd unit
+5. Leaves Nginx unchanged unless `INSTALL_NGINX=1` is explicitly requested
+6. Waits for `/api/auth/setup/status`; if startup fails, prints systemd diagnostics and exits non-zero
+
+## From source
+
+Requires Go ≥ 1.25, Node.js 24 LTS, and npm 11 or later.
+
+```bash
+git clone https://github.com/Awuqing/BackupX.git && cd BackupX
+make build
+sudo ./deploy/install.sh
+```
+
+After `make build`, the binary is at `server/bin/backupx` and the built web UI is at `web/dist/`.
+The installer consumes those exact paths, so no Docker runtime is required. If an existing configuration uses a non-default port, set `HEALTH_URL` for the readiness check, for example `sudo HEALTH_URL=http://127.0.0.1:9000/api/auth/setup/status ./deploy/install.sh`.
+
+The Nginx template is opt-in because automatically installing a catch-all virtual host can intercept existing sites. Review `deploy/nginx.conf`, then use `sudo INSTALL_NGINX=1 ./deploy/install.sh` only when it matches the host.
+
+## Verify the install
+
+```bash
+/opt/backupx/bin/backupx --version
+curl -fsS http://127.0.0.1:8340/api/auth/setup/status
+```
+
+Then open `http://your-server:8340`. Choose **English** or **中文** in the upper-right corner. A fresh database shows **System setup**, where you create the first administrator username and password. If that form does not appear, retry the status request above before attempting to sign in.
--- a/docs-site/docs/getting-started/quick-start.md
+++ b/docs-site/docs/getting-started/quick-start.md
@@ -0,0 +1,62 @@
+---
+sidebar_position: 2
+title: Quick Start
+description: Set up BackupX, add a storage target, create your first backup task.
+---
+
+# Quick Start
+
+After [installation](./installation), get a first backup running in five minutes.
+
+## 1. Open the console
+
+Browse to `http://your-server:8340`. The first time, you'll be guided through creating an admin account.
+
+## 2. Add a storage target
+
+Navigate to **Storage Targets → Add**. Pick a type and fill the required fields:
+
+| Type | Fields |
+|------|--------|
+| Alibaba OSS | Region + AccessKey ID/Secret + Bucket |
+| Tencent COS | Region + SecretId/SecretKey + Bucket (format `name-appid`) |
+| Qiniu Kodo | Region + AccessKey/SecretKey + Bucket |
+| S3-compatible | Endpoint + AccessKey + Bucket |
+| Google Drive | Client ID/Secret → click "Authorize" for OAuth flow |
+| WebDAV | URL + username/password |
+| FTP | Host + port + username/password |
+| Local disk | Target directory |
+| SFTP / Azure / Dropbox / OneDrive | Type-specific required fields; advanced options collapsed |
+
+:::tip
+For mainland China cloud vendors you only fill Region and AccessKey — BackupX assembles the endpoint automatically. Rclone-style providers separate required fields from advanced ones, with advanced collapsed by default.
+:::
+
+Click **Test Connection** to verify.
+
+## 3. Create a backup task
+
+Go to **Backup Tasks → New**. Three steps:
+
+1. **Basic info** — name, type, cron expression (leave empty for manual-only)
+2. **Source** — paths for file backup (multi-source supported), or connection info for databases
+3. **Storage & policy** — pick target(s), compression, retention days, encryption on/off
+
+For Agent-routed tasks, encryption must stay off because the Agent never receives the Master's encryption key. BackupX rejects remote-node or node-pool tasks with encryption enabled during create/update.
+
+Save, then click **Run Now** to trigger a test. Live logs stream on the **Backup Records** page.
+
+:::note
+Deleting a task also removes remote backup files to prevent orphans, but records are kept for audit.
+:::
+
+## 4. Configure notifications (optional)
+
+**Notifications** page supports email, webhook, and Telegram. Configure per-channel rules for success/failure events.
+
+## Next up
+
+- Explore [backup types](/docs/features/backup-types) and [storage backends](/docs/features/storage-backends)
+- Before production, review [Security Hardening](/docs/operations/security), [Monitoring and Alerts](/docs/operations/monitoring), and [Upgrade and Recovery](/docs/operations/upgrade-recovery)
+- Running SAP HANA? See [SAP HANA Support](/docs/features/sap-hana)
+- Managing many servers? See [Multi-Node Cluster](/docs/features/multi-node)
--- a/docs-site/docs/intro.md
+++ b/docs-site/docs/intro.md
@@ -0,0 +1,42 @@
+---
+id: intro
+slug: /intro
+sidebar_position: 1
+title: Introduction
+description: Overview of BackupX — a self-hosted server backup management platform.
+---
+
+# BackupX
+
+**BackupX** is a self-hosted server backup management platform. One static binary, one command, and every backup job for every server is under control.
+
+- **Single binary + embedded SQLite** — no external database or orchestrator required
+- **Files, databases, SAP HANA** — in one place, with a visual scheduler
+- **70+ storage backends** — Alibaba OSS, Tencent COS, Qiniu, S3, Google Drive, WebDAV, FTP, plus SFTP / Azure Blob / Dropbox / OneDrive and dozens more via rclone
+- **Multi-node cluster** — Master-Agent mode manages backups across servers, agents run tasks locally and upload straight to storage
+- **Secure by default** — JWT auth, bcrypt, AES-256-GCM encrypted config, optional backup encryption, full audit log
+
+## Architecture at a Glance
+
+```
+[Web Console] ─── JWT ──→ [Master (backupx)]
+                             │
+                             │ outbound HTTP polling (token auth)
+                             ▼
+                         [Agent (backupx agent)]
+                             │
+                             ▼
+                     [70+ Storage Backends]
+```
+
+Tasks routed to the local Master run in-process; tasks assigned to remote nodes are dispatched through a command queue and executed by the Agent locally. Agents only ever initiate outbound HTTP — no reverse connectivity required.
+
+## Where to Next
+
+- **New to BackupX?** Read the [Quick Start](/docs/getting-started/quick-start) first.
+- **Deploying to production?** See the [Deployment Guide](/docs/deployment/docker).
+- **Planning upgrades or recovery?** Follow [Upgrade and Recovery](/docs/operations/upgrade-recovery).
+- **Operating production?** Start with [Security Hardening](/docs/operations/security) and [Monitoring and Alerts](/docs/operations/monitoring).
+- **SAP HANA operator?** Both `hdbsql` Runner and native Backint are supported — see [SAP HANA](/docs/features/sap-hana).
+- **Managing multiple servers?** See [Multi-Node Cluster](/docs/features/multi-node).
+- **Integrating programmatically?** See the [API Reference](/docs/reference/api).
--- a/docs-site/docs/operations/monitoring.md
+++ b/docs-site/docs/operations/monitoring.md
@@ -0,0 +1,149 @@
+---
+sidebar_position: 3
+title: Monitoring and Alerts
+description: Health probes, Prometheus metrics, initial alert rules, and operational validation.
+---
+
+# Monitoring and Alerts
+
+BackupX exposes low-cost health endpoints and a dedicated Prometheus registry. Monitor both the control plane and the outcome of backup, restore, verification, and replication work.
+
+## Probes
+
+| Endpoint | Meaning | Expected response |
+| --- | --- | --- |
+| `/health` | Liveness: the HTTP process can respond | HTTP 200 with `status: live` |
+| `/ready` | Readiness: the process can reach SQLite | HTTP 200 with `status: ready`; HTTP 503 on database failure |
+| `/api/health` | API-prefixed alias for liveness | Same as `/health` |
+| `/api/ready` | API-prefixed alias for readiness | Same as `/ready` |
+| `/metrics` | Prometheus exposition | HTTP 200 when metrics are enabled |
+
+Use `/health` for a liveness probe and `/ready` for readiness or load-balancer traffic decisions. Do not restart a process only because an external storage provider is unavailable; storage health belongs in task and target alerts.
+
+~~~bash
+curl -fsS http://127.0.0.1:8340/health
+curl -fsS http://127.0.0.1:8340/ready
+curl -fsS http://127.0.0.1:8340/metrics | head
+~~~
+
+These endpoints are unauthenticated. Restrict them to orchestrator and monitoring networks.
+
+## Prometheus scrape
+
+~~~yaml
+scrape_configs:
+  - job_name: backupx
+    scheme: https
+    metrics_path: /metrics
+    static_configs:
+      - targets: [backup.example.com]
+~~~
+
+When Nginx terminates TLS, allow the Prometheus source address to reach `/metrics` and deny other public clients. The internal collector refreshes storage, node, command-queue, and SLA gauges every 30 seconds.
+
+## BackupX metrics
+
+| Metric | Type | Labels | Purpose |
+| --- | --- | --- | --- |
+| `backupx_app_info` | gauge | `version` | Running release metadata |
+| `backupx_task_run_total` | counter | `status`, `task_type` | Backup outcomes |
+| `backupx_task_run_duration_seconds` | histogram | `task_type` | Backup duration distribution |
+| `backupx_task_bytes_total` | counter | `task_type` | Produced backup bytes |
+| `backupx_task_running` | gauge | none | Current backup concurrency |
+| `backupx_storage_used_bytes` | gauge | `target_name`, `target_type` | Recorded usage per target |
+| `backupx_node_online` | gauge | `node_name`, `role` | Node online state, 1 or 0 |
+| `backupx_agent_command_queue_depth` | gauge | `node_name`, `role` | Pending and dispatched commands |
+| `backupx_agent_command_running` | gauge | `node_name`, `role` | Long-running Agent commands |
+| `backupx_agent_command_timeout_total` | gauge | `node_name`, `role` | Snapshot of timed-out commands |
+| `backupx_verify_run_total` | counter | `status` | Verification outcomes |
+| `backupx_restore_run_total` | counter | `status` | Restore outcomes |
+| `backupx_replication_run_total` | counter | `status` | Replication outcomes |
+| `backupx_sla_breach_tasks` | gauge | none | Enabled tasks outside their configured RPO |
+
+Standard Go runtime and process collectors are registered in the same endpoint.
+
+## Initial alert rules
+
+Tune windows and thresholds to the schedules and RPOs of each environment:
+
+~~~yaml
+groups:
+  - name: backupx
+    rules:
+      - alert: BackupXTargetDown
+        expr: up{job="backupx"} == 0
+        for: 2m
+        labels:
+          severity: critical
+        annotations:
+          summary: BackupX metrics endpoint is unreachable
+
+      - alert: BackupXNotReady
+        expr: probe_success{job="backupx-ready"} == 0
+        for: 2m
+        labels:
+          severity: critical
+        annotations:
+          summary: BackupX readiness check is failing
+
+      - alert: BackupXBackupFailure
+        expr: sum(increase(backupx_task_run_total{status="failed"}[15m])) > 0
+        labels:
+          severity: warning
+        annotations:
+          summary: A BackupX backup failed
+
+      - alert: BackupXSLABreach
+        expr: backupx_sla_breach_tasks > 0
+        for: 5m
+        labels:
+          severity: critical
+        annotations:
+          summary: One or more backup tasks are outside RPO
+
+      - alert: BackupXAgentOffline
+        expr: backupx_node_online{role="agent"} == 0
+        for: 2m
+        labels:
+          severity: warning
+        annotations:
+          summary: BackupX Agent is offline
+
+      - alert: BackupXAgentQueueBacklog
+        expr: backupx_agent_command_queue_depth > 20
+        for: 10m
+        labels:
+          severity: warning
+        annotations:
+          summary: BackupX Agent command queue is growing
+~~~
+
+The `BackupXNotReady` example assumes a blackbox probe job named `backupx-ready`. If no blackbox exporter is used, alert from the load balancer or orchestrator readiness signal instead.
+
+## Operational dashboard
+
+Track these views together:
+
+- Success and failure rate by task type.
+- P50, P95, and maximum run duration relative to the backup window.
+- Bytes produced compared with the expected data-change rate.
+- Current running tasks versus `backup.max_concurrent`.
+- Offline Agents, queue depth, running commands, and timeout-count changes.
+- Storage growth, free capacity from the storage provider, and retention cleanup.
+- SLA breach count and age of the most recent successful backup for critical tasks.
+- Verification, restore, and replication success rates.
+
+Prometheus storage usage is based on BackupX record metadata, not necessarily the provider's billable capacity. Monitor provider quota and filesystem free space separately.
+
+## Post-deployment validation
+
+After installation, upgrade, proxy changes, or recovery:
+
+1. Check liveness and readiness locally and through the public proxy.
+2. Confirm Prometheus sees one active Master and the expected version label.
+3. Verify every expected Agent reports `backupx_node_online == 1`.
+4. Run a small backup and confirm the success counter increases.
+5. Run a verification or isolated restore and confirm its counter increases.
+6. Trigger a test notification and verify the alert delivery path.
+
+Continue with [Troubleshooting](./troubleshooting) when a probe or metric is abnormal.
--- a/docs-site/docs/operations/security.md
+++ b/docs-site/docs/operations/security.md
@@ -0,0 +1,102 @@
+---
+sidebar_position: 2
+title: Security Hardening
+description: Production controls for network exposure, roles, secrets, Agents, containers, and public endpoints.
+---
+
+# Security Hardening
+
+BackupX coordinates access to source files, database credentials, storage credentials, and restore destinations. Deploy the Master as a security-sensitive control plane, not as a general public web application.
+
+## Recommended exposure model
+
+| Component | Inbound access | Outbound access |
+| --- | --- | --- |
+| Master | HTTPS from administrators and Agents; metrics only from monitoring networks | Storage providers, notification endpoints, release checks |
+| Agent | No inbound port required | Master HTTPS endpoint and assigned storage targets |
+| SQLite data | Local or block-backed filesystem only | None |
+
+Bind Docker to `127.0.0.1` when a reverse proxy runs on the same host:
+
+~~~dotenv
+BACKUPX_BIND_ADDRESS=127.0.0.1
+~~~
+
+For bare metal, set `server.host` to loopback when only a local proxy should reach BackupX. Otherwise restrict TCP 8340 with the host or network firewall.
+
+## TLS and reverse proxies
+
+- Use HTTPS across every untrusted network segment.
+- Set `server.external_url` to the stable URL that Agents can reach.
+- Add only the exact proxy IP or subnet to `server.trusted_proxies`. Never trust `0.0.0.0/0`.
+- Send the final HTTPS URL to Agents; the Agent does not follow redirects.
+- For private PKI, install a PEM CA on the Agent and configure `caCertFile` or `--ca-cert`.
+- Use `--insecure-tls` only for temporary testing.
+- Keep Nginx request and response buffering disabled for relay uploads and SSE logs.
+
+When an SSH bastion is required, bind tunnels to loopback, verify host keys, use a dedicated account and key, and make the Agent service depend on the tunnel. See [Multi-Node Cluster](../features/multi-node).
+
+## Roles and API keys
+
+| Role | Intended access |
+| --- | --- |
+| `viewer` | Read dashboards, tasks, records, reports, and audit data; cannot browse node filesystems or mutate resources |
+| `operator` | Viewer access plus task, storage, notification, backup, restore, verification, and file-browse operations |
+| `admin` | Operator access plus users, API keys, settings, node lifecycle, install tokens, and token rotation |
+
+Create separate named users instead of sharing the initial administrator. Enable two-factor authentication or passkeys for privileged accounts. Review trusted devices and recovery codes periodically.
+
+User JWTs are stateless. Logout removes the client copy but does not revoke a token that was already copied elsewhere. Set `security.jwt_expire` to the shortest practical lifetime, protect Bearer tokens, and rotate the JWT secret when all active sessions must be invalidated.
+
+API keys use the same role checks as interactive users. Their plaintext is shown only once; the database stores a keyed hash. Give automation the lowest role it needs, set an expiry, keep the key in a secret manager, and revoke unused keys. Avoid administrator API keys for monitoring.
+
+## Protect control-plane secrets
+
+- Restrict `/etc/backupx/config.yaml` to `root:backupx` mode `0640` and the data directory to the service account.
+- If `jwt_secret` and `encryption_key` are empty, generated values are persisted in the SQLite database. Back up the complete data directory.
+- Losing or replacing the encryption key makes saved storage credentials unreadable.
+- The database includes password hashes, configuration secrets, Agent tokens, API-key hashes, trusted-device state, and audit data. Encrypt snapshots and control their retention.
+- Do not put tokens in shell history, issue text, screenshots, or support bundles.
+
+Each node has an independent long-lived Agent token. The systemd installer stores it in `/etc/backupx-agent/agent.token` with mode `0600`. Rotate a token after personnel changes, host compromise, or accidental disclosure, update the token file during the overlap window, then restart the Agent.
+
+One-time install URLs are valid for 5 minutes to 24 hours and are consumed after use. Treat the URL and the embedded fallback command as secrets: the generated installation material provisions the long-lived node token.
+
+## Container and host permissions
+
+The canonical Compose deployment drops all capabilities and adds back only those needed to repair legacy volume ownership and switch to the unprivileged `backupx` user. Keep `no-new-privileges` enabled and do not mount the Docker socket.
+
+Mount backup sources read-only. Add a separate, narrowly scoped writable mount only when a restore destination requires it. Prefer a host Agent over running the Master container as root for privileged filesystem access.
+
+The systemd Master runs as `backupx`. The Agent normally runs as root because it may back up or restore files belonging to arbitrary system users. Limit who can create tasks and protect the root-owned Agent configuration.
+
+## Public endpoints
+
+The following endpoints intentionally do not use BackupX JWT or API-key authentication:
+
+- `/health` and `/api/health`
+- `/ready` and `/api/ready`
+- `/metrics`
+- one-time `/install/:token` and `/api/install/:token` routes
+
+Health responses expose status, version, uptime, timestamp, and readiness checks; a failed readiness check can include database error detail. `/metrics` also includes node and storage-target labels. Restrict metrics and probes to monitoring networks at the firewall or reverse proxy. Do not cache or log full install-token URLs.
+
+## Backup encryption boundary
+
+Encrypted backup tasks run on the Master because remote Agents never receive the Master's encryption key. Do not work around this boundary by copying the Master key to Agents. For Agent-routed tasks, rely on transport encryption and the destination provider's server-side encryption when required.
+
+Test restores for encrypted backups after every key-management change. A backup whose key is unavailable is not recoverable.
+
+## Audit and incident response
+
+BackupX records privileged actions in the audit log and can forward signed audit events to an external webhook. Send high-value audit records to a separately administered SIEM or append-only store so a compromised Master cannot erase the only copy.
+
+After suspected compromise:
+
+1. Isolate the Master without deleting evidence.
+2. Revoke exposed API keys and rotate affected Agent tokens and storage credentials.
+3. Replace JWT and encryption keys only with a planned migration; changing the encryption key invalidates saved encrypted configuration.
+4. Review user, trusted-device, API-key, node, settings, restore, and deletion events.
+5. Recover from a known-good control-plane snapshot when integrity cannot be established.
+
+Use [Upgrade and Recovery](./upgrade-recovery) for the paired application-and-database recovery procedure.
--- a/docs-site/docs/operations/troubleshooting.md
+++ b/docs-site/docs/operations/troubleshooting.md
@@ -0,0 +1,160 @@
+---
+sidebar_position: 4
+title: Troubleshooting
+description: A safe diagnostic sequence for the Master, reverse proxy, Agents, backup tools, and SQLite.
+---
+
+# Troubleshooting
+
+Start with the first failing boundary and preserve evidence. Avoid deleting the database, recreating volumes, rotating every token, or reinstalling until the failure is understood.
+
+## Fast triage
+
+| Symptom | First check | Likely boundary |
+| --- | --- | --- |
+| Web console unavailable | Local `/health`, then proxy `/health` | Process, listener, firewall, proxy, or static assets |
+| `/health` works but `/ready` is 503 | Service logs, database path, disk space, ownership | SQLite or data filesystem |
+| Login loops or client IP is wrong | Forwarded headers and `trusted_proxies` | Reverse-proxy trust |
+| Live logs stop updating | Nginx response buffering and timeout | SSE proxy path |
+| Relay upload stalls or proxy disk fills | Request buffering and body-size limit | Reverse proxy |
+| Agent offline | Agent service logs, final Master URL, proxy, DNS, CA | Agent-to-Master path |
+| Backup starts but fails | Record log, source path, native database tool | Task runner or permissions |
+| Restore fails | Record log, destination mount and write access | Storage read or destination permissions |
+
+## Collect status without secrets
+
+Docker Master:
+
+~~~bash
+docker compose ps
+docker compose logs --tail=200 backupx
+curl -i http://127.0.0.1:8340/health
+curl -i http://127.0.0.1:8340/ready
+~~~
+
+Bare-metal Master:
+
+~~~bash
+sudo systemctl status backupx --no-pager
+sudo journalctl -u backupx -n 200 --no-pager
+sudo ss -lntp | grep 8340
+curl -i http://127.0.0.1:8340/health
+curl -i http://127.0.0.1:8340/ready
+~~~
+
+Systemd Agent:
+
+~~~bash
+sudo systemctl status backupx-agent --no-pager
+sudo journalctl -u backupx-agent -n 200 --no-pager
+sudo systemctl status backupx-agent-tunnel --no-pager
+~~~
+
+The tunnel command is relevant only to bastion deployments. Before sharing output, remove Authorization headers, API keys, Agent tokens, install URLs, database passwords, storage credentials, proxy credentials, and private paths that reveal sensitive topology.
+
+## Web console or first setup
+
+Check the unauthenticated setup endpoint:
+
+~~~bash
+curl -fsS http://127.0.0.1:8340/api/auth/setup/status
+~~~
+
+If the API works but the browser receives a blank page or JSON:
+
+- Confirm the release contains web assets.
+- Bare metal: verify `/opt/backupx/web` is readable and `server.web_root` is correct when explicitly set.
+- Docker: confirm the official image is running and no custom mount hides the packaged web directory.
+- Nginx static mode: confirm `root /opt/backupx/web` and SPA fallback are present.
+- Clear an old service-worker or browser cache after a release change.
+
+For authentication failures, verify system time before diagnosing TOTP or passkeys. Confirm the browser origin matches the final HTTPS host, and inspect the audit log for throttling, disabled users, or revoked trusted devices.
+
+## Reverse proxy
+
+Validate and reload Nginx:
+
+~~~bash
+sudo nginx -t
+sudo systemctl reload nginx
+curl -i https://backup.example.com/health
+curl -i https://backup.example.com/ready
+~~~
+
+Common corrections:
+
+- HTTP 413: set `client_max_body_size 0` for the API route.
+- Relay uploads fill proxy temporary storage: set `proxy_request_buffering off`.
+- SSE logs arrive in bursts or disconnect: set `proxy_buffering off`, disable proxy cache, and increase read timeout.
+- One-click installer returns HTML: proxy `/api/` and retain the legacy `/install/` route.
+- Agent receives a redirect: configure the final HTTPS Master URL instead of an HTTP URL.
+- Audit shows the proxy address for every user: add only the real proxy IP or subnet to `server.trusted_proxies`.
+
+Use the complete [Nginx configuration](../deployment/nginx) as the comparison baseline.
+
+## Agent offline
+
+An Agent normally heartbeats every 15 seconds and is marked offline after 45 seconds.
+
+1. Confirm the Agent and optional tunnel services are active.
+2. Verify the configured Master URL has no trailing redirect and resolves from the Agent host.
+3. Check the explicit `proxyUrl`. Use `socks5h://` when DNS must resolve through an SSH dynamic tunnel.
+4. Confirm the private CA path exists and is readable. Do not switch permanently to insecure TLS.
+5. Check outbound firewall access to the Master and assigned storage backends.
+6. Verify `/etc/backupx-agent/agent.token` exists with mode `0600`.
+7. If a token was rotated, install the new value during the overlap window and restart the Agent.
+
+Do not paste the token into a diagnostic command that will be saved in shell history. A 401 in Agent logs usually indicates a missing, expired-overlap, or mismatched node token; repeated connection errors indicate URL, DNS, proxy, tunnel, firewall, or CA problems.
+
+## Backup task failures
+
+Open the backup record and inspect its complete log before changing the task.
+
+- File tasks resolve paths on the selected Master or Agent. Confirm the path exists in that host's namespace.
+- Docker sees only mounted paths. Backup mounts should normally be read-only.
+- MySQL requires `mysqldump` on the execution host's `PATH`.
+- PostgreSQL requires `pg_dump` on the execution host's `PATH`.
+- SAP HANA runner mode requires its configured client tools and environment.
+- Confirm the service account can read sources and write the temporary directory.
+- Test the selected storage target from the console.
+- Check DNS, egress policy, provider quota, clock skew, and proxy settings for remote storage.
+
+If multiple targets are configured, inspect the per-target result instead of assuming every copy failed. Preserve successful remote artifacts while correcting the failing target.
+
+## Restore, download, or verification failures
+
+- Confirm the remote artifact still exists and the storage credentials can read it.
+- Check that the destination is mounted on the host that performs the restore.
+- Use a separate writable restore path; do not make every backup-source mount writable.
+- Check free space in the destination and Agent temporary directory.
+- For encrypted backups, confirm the original Master encryption key is available.
+- For CDC repositories, keep manifests, indexes, and shared packs together; a manifest alone is not a complete backup.
+
+Prefer an isolated restore destination during diagnosis. Do not repeatedly restore over the production source.
+
+## SQLite and readiness failures
+
+When `/health` is 200 but `/ready` is 503:
+
+1. Read the exact database error from service logs.
+2. Check free disk space, inode availability, path ownership, and mount state.
+3. Confirm only one Master process or container uses the data directory.
+4. Keep SQLite on a local or block-backed filesystem, not a shared multi-writer or unreliable network filesystem.
+5. Check whether an external backup or antivirus process is holding files for long periods.
+
+BackupX uses a five-second SQLite busy timeout, but that does not make SQLite a clustered database. Do not fix lock errors by starting another Master. For a file-level copy, stop the service and copy the whole data directory.
+
+## Escalation package
+
+When opening an issue, include:
+
+- BackupX version, installation method, operating system, and architecture.
+- Whether the failure affects the Master, Agent, proxy, storage target, or one task.
+- Redacted service logs covering the first failure.
+- HTTP status and response body from `/health` and `/ready`.
+- A minimal reproduction and whether it began after an upgrade or configuration change.
+- Relevant proxy configuration with hostnames, credentials, and private addresses redacted.
+
+Never attach `backupx.db`, `.env`, full configuration files, Agent token files, API keys, install commands, or storage credentials to a public issue.
+
+If integrity or rollback is involved, stop making destructive changes and follow [Upgrade and Recovery](./upgrade-recovery).
--- a/docs-site/docs/operations/upgrade-recovery.md
+++ b/docs-site/docs/operations/upgrade-recovery.md
@@ -0,0 +1,153 @@
+---
+sidebar_position: 1
+title: Upgrade and Recovery
+description: Back up the control plane, upgrade safely, roll back as a unit, and recover a failed Master.
+---
+
+# Upgrade and Recovery
+
+Backup artifacts and the BackupX control plane are different recovery domains. Object storage may still contain every archive while a lost Master database removes users, encrypted storage credentials, schedules, records, node tokens, and audit history. Protect both.
+
+## Non-negotiable rules
+
+1. Run exactly one active Master against a data directory or SQLite database.
+2. Snapshot the complete data directory and configuration while the Master is stopped, or use a storage-level atomic snapshot.
+3. Keep the old application version and its pre-upgrade data snapshot together. Schema migration happens at startup, so switching only the binary or image back is not a safe rollback.
+4. Store control-plane snapshots outside the Master host and test restoring them.
+5. Let active backup and restore jobs finish before stopping the Master.
+
+| Deployment | Persistent control-plane data | Configuration and release state |
+| --- | --- | --- |
+| Docker | `/app/data` in the `backupx-data` volume | Compose file, protected `.env`, pinned image tag or digest |
+| Bare metal | `/opt/backupx/data` | `/etc/backupx`, `/opt/backupx/bin`, `/opt/backupx/web`, systemd unit |
+
+The SQLite database contains generated JWT and encryption keys when they are not supplied in configuration. Treat every control-plane snapshot as a secret.
+
+## Change checklist
+
+Before an upgrade, host migration, or security-key change:
+
+- Record the current BackupX version and the exact image digest or release checksum.
+- Confirm `/ready` returns HTTP 200 and review recent failures.
+- Wait for running backup, restore, verification, and replication work to finish.
+- Test at least one storage target and confirm Agents are online.
+- Create a full control-plane snapshot and copy it off-host.
+- Optionally export task definitions for human review. Task export excludes database passwords and storage credentials, so it is not a replacement for the database snapshot.
+- Define the rollback decision and maintenance-window deadline before starting.
+
+## Snapshot a Docker deployment
+
+This example creates a consistent file-level copy without requiring access to Docker's volume directory:
+
+~~~bash
+snapshot="backupx-control-plane-$(date -u +%Y%m%dT%H%M%SZ)"
+install -d -m 0700 "$snapshot"
+
+docker compose stop backupx
+docker cp backupx:/app/data "$snapshot/data"
+cp docker-compose.yml "$snapshot/"
+if [ -f .env ]; then cp .env "$snapshot/"; fi
+docker compose start backupx
+
+tar -czf "$snapshot.tar.gz" "$snapshot"
+sha256sum "$snapshot.tar.gz" > "$snapshot.tar.gz.sha256"
+curl -fsS http://127.0.0.1:8340/ready
+~~~
+
+If copying fails, start the stopped service before investigating. Protect the archive because `.env` and the database can contain credentials. A block-volume or storage-provider snapshot is also valid when it is atomic across the whole volume.
+
+## Snapshot a bare-metal deployment
+
+~~~bash
+snapshot="/var/backups/backupx/backupx-control-plane-$(date -u +%Y%m%dT%H%M%SZ).tar.gz"
+sudo install -d -m 0700 /var/backups/backupx
+
+sudo systemctl stop backupx
+sudo tar --acls --xattrs -C / -czf "$snapshot" \
+  etc/backupx \
+  etc/systemd/system/backupx.service \
+  opt/backupx/bin \
+  opt/backupx/web \
+  opt/backupx/data
+sudo systemctl start backupx
+
+sudo sha256sum "$snapshot" | sudo tee "$snapshot.sha256"
+curl -fsS http://127.0.0.1:8340/ready
+~~~
+
+Copy the archive and checksum to protected off-host storage. Do not copy only `backupx.db` while the service is running.
+
+## Upgrade Docker
+
+1. Put a release tag or immutable digest in `BACKUPX_IMAGE`. Do not use `latest` for a controlled production upgrade.
+2. Create and verify the pre-upgrade snapshot.
+3. Pull and recreate the service:
+
+~~~bash
+docker compose pull backupx
+docker compose up -d backupx
+docker compose ps
+docker compose logs --tail=100 backupx
+curl -fsS http://127.0.0.1:8340/ready
+~~~
+
+4. Sign in, test a storage target, confirm Agent heartbeats, and run one small backup plus a restore or verification drill.
+5. Keep the old image reference and snapshot until the observation window ends.
+
+Upgrade Agents after the Master, in small batches. Keep the node-specific proxy, private-CA, token-file, and bastion configuration unchanged unless that configuration is the purpose of the change.
+
+## Upgrade bare metal
+
+Download the target release and checksum, verify them, then extract the archive. The installer preserves an existing `/etc/backupx/config.yaml`, replaces the binary, web assets, and systemd unit, and restarts the service.
+
+~~~bash
+sha256sum -c backupx-vX.Y.Z-linux-amd64.tar.gz.sha256
+tar xzf backupx-vX.Y.Z-linux-amd64.tar.gz
+cd backupx-vX.Y.Z-linux-amd64
+sudo ./install.sh
+
+sudo systemctl status backupx --no-pager
+curl -fsS http://127.0.0.1:8340/ready
+~~~
+
+Create the stopped-service snapshot before running the installer. Use the same post-upgrade application checks as Docker.
+
+## Roll back
+
+Rollback is a paired operation: restore both the previous application release and the snapshot created immediately before the upgrade.
+
+For Docker, preserve the failed volume for analysis and restore the snapshot into a new empty volume. Point Compose at that volume and the previous image tag, then start exactly one Master. For bare metal, stop the service, preserve the failed state, restore the old configuration, binary, web assets, data directory, and unit from the same archive, reload systemd, and start the service.
+
+After rollback:
+
+~~~bash
+curl -fsS http://127.0.0.1:8340/health
+curl -fsS http://127.0.0.1:8340/ready
+~~~
+
+Then verify login, storage access, schedules, Agent heartbeats, a backup, and a non-destructive restore drill. Do not delete the failed state until the incident is understood.
+
+## Recover a lost Master
+
+1. Provision a replacement host with the same architecture and the exact application version recorded with the snapshot.
+2. Keep the replacement isolated from production traffic and ensure the old Master cannot start.
+3. Restore configuration and the complete data directory with their original permissions.
+4. Start one Master and check `/ready` locally.
+5. Move the stable DNS name or virtual IP only after local validation.
+6. Confirm users, storage targets, tasks, records, notifications, and audit history.
+7. Existing Agents reconnect automatically when the restored database contains their matching tokens. Investigate and rotate tokens that may have been exposed.
+8. Run a small backup and a restore or verification drill before ending the incident.
+
+External backup artifacts are not recreated by restoring the control plane; they remain on their configured storage targets. Conversely, task JSON export is useful for rebuilding schedules but omits secrets, storage definitions, and some node bindings. Use it only as an additional recovery aid.
+
+## Test the recovery plan
+
+At least quarterly, restore a recent snapshot into an isolated network, start the recorded BackupX version, and verify:
+
+- `/ready` becomes healthy without contacting the production Master.
+- An administrator can sign in and encrypted storage configurations can be read.
+- Task, node, record, and audit counts are plausible.
+- A storage target can be tested without writing production data.
+- A selected backup can be verified or restored to an isolated destination.
+
+Record restore duration and the newest recoverable snapshot time. Those measured values are the real control-plane RTO and RPO.
--- a/docs-site/docs/reference/api.md
+++ b/docs-site/docs/reference/api.md
@@ -0,0 +1,268 @@
+---
+sidebar_position: 1
+title: API Reference
+description: BackupX REST endpoints, authentication methods, role boundaries, streaming responses, and public probes.
+---
+
+# API Reference
+
+The interactive API is rooted at `/api`. Most endpoints accept either a user JWT or an API key; Agent protocol endpoints use a node-specific token. Public probes and one-time installers are listed separately.
+
+## Authentication
+
+### User JWT
+
+Obtain a JWT through `POST /api/auth/login` and send it as a Bearer token:
+
+~~~bash
+curl -H "Authorization: Bearer $BACKUPX_TOKEN" \
+  https://backup.example.com/api/backup/tasks
+~~~
+
+The login flow may require OTP, TOTP, recovery code, a trusted-device token, or WebAuthn depending on account and system settings.
+
+### API key
+
+An administrator creates API keys in the console or through `POST /api/api-keys`. The plaintext `bax_...` value is returned only once.
+
+~~~bash
+curl -H "X-Api-Key: $BACKUPX_API_KEY" \
+  https://backup.example.com/api/dashboard/stats
+~~~
+
+`Authorization: Bearer bax_...` is also accepted. API keys carry an `admin`, `operator`, or `viewer` role and can be disabled or given an expiry.
+
+### Agent token
+
+Agent protocol handlers authenticate the node token supplied in `X-Agent-Token`. This token is not a user credential and must not be used with the interactive resource API.
+
+### Access labels
+
+The tables use these labels:
+
+| Label | Required access |
+| --- | --- |
+| Public | No JWT or API key; an install route still requires its one-time token |
+| Auth | Any authenticated `viewer`, `operator`, or `admin` |
+| Operator | `operator` or `admin` |
+| Admin | `admin` only |
+| Agent | Valid node-specific Agent token |
+
+Viewers can use read endpoints except node filesystem browsing. Operators can run and mutate backup resources. Administrators additionally manage users, API keys, settings, nodes, install tokens, and node-token rotation. A rejected role returns HTTP 403.
+
+## Authentication and account security
+
+| Method | Endpoint | Access | Description |
+| --- | --- | --- | --- |
+| `GET` | `/api/auth/setup/status` | Public | Check whether first-admin setup is required |
+| `POST` | `/api/auth/setup` | Public | Create the first administrator when no user exists |
+| `POST` | `/api/auth/login` | Public | Complete password or MFA login and obtain a JWT |
+| `POST` | `/api/auth/otp/send` | Public | Send a configured login OTP |
+| `POST` | `/api/auth/webauthn/login/options` | Public | Begin passkey login |
+| `POST` | `/api/auth/logout` | Auth | Acknowledge logout; the client must discard its stateless JWT |
+| `GET` | `/api/auth/profile` | Auth | Read the current account |
+| `PUT` | `/api/auth/password` | Auth | Change the current account password |
+| `POST` | `/api/auth/2fa/setup` | Auth | Prepare TOTP enrollment |
+| `POST` | `/api/auth/2fa/enable` | Auth | Enable TOTP after verification |
+| `POST` | `/api/auth/2fa/recovery-codes` | Auth | Regenerate recovery codes |
+| `DELETE` | `/api/auth/2fa` | Auth | Disable TOTP |
+| `PUT` | `/api/auth/otp/config` | Auth | Update OTP login configuration |
+| `POST` | `/api/auth/webauthn/register/options` | Auth | Begin passkey registration |
+| `POST` | `/api/auth/webauthn/register/finish` | Auth | Finish passkey registration |
+| `GET` | `/api/auth/webauthn/credentials` | Auth | List passkeys |
+| `DELETE` | `/api/auth/webauthn/credentials/:id` | Auth | Delete a passkey |
+| `GET` | `/api/auth/trusted-devices` | Auth | List trusted devices |
+| `DELETE` | `/api/auth/trusted-devices/:id` | Auth | Revoke a trusted device |
+
+Use an interactive JWT, not an automation API key, for account-security endpoints.
+
+## System and storage targets
+
+| Method | Endpoint | Access | Description |
+| --- | --- | --- | --- |
+| `GET` | `/api/system/info` | Auth | Version and system information |
+| `GET` | `/api/system/update-check` | Auth | Check available releases |
+| `GET` | `/api/storage-targets` | Auth | List storage targets |
+| `POST` | `/api/storage-targets` | Operator | Create a target |
+| `POST` | `/api/storage-targets/test` | Operator | Test an unsaved configuration |
+| `GET` | `/api/storage-targets/rclone/backends` | Auth | List available rclone backends |
+| `POST` | `/api/storage-targets/google-drive/auth-url` | Operator | Start Google Drive authorization |
+| `POST` | `/api/storage-targets/google-drive/complete` | Operator | Complete Google Drive authorization |
+| `GET` | `/api/storage-targets/google-drive/callback` | Auth | Handle the OAuth callback |
+| `GET` | `/api/storage-targets/:id` | Auth | Read a target |
+| `PUT` | `/api/storage-targets/:id` | Operator | Update a target |
+| `DELETE` | `/api/storage-targets/:id` | Operator | Delete a target |
+| `PUT` | `/api/storage-targets/:id/star` | Operator | Toggle favorite state |
+| `POST` | `/api/storage-targets/:id/test` | Operator | Test a saved target |
+| `GET` | `/api/storage-targets/:id/usage` | Auth | Read recorded usage |
+| `GET` | `/api/storage-targets/:id/google-drive/profile` | Auth | Read the connected Google Drive profile |
+
+## Backup tasks
+
+| Method | Endpoint | Access | Description |
+| --- | --- | --- | --- |
+| `GET` | `/api/backup/tasks` | Auth | List tasks |
+| `GET` | `/api/backup/tasks/tags` | Auth | List task tags |
+| `GET` | `/api/backup/tasks/export` | Auth | Download all task definitions, or select them with `?ids=1,2` |
+| `POST` | `/api/backup/tasks/import` | Operator | Import task definitions, up to 1 MiB |
+| `POST` | `/api/backup/tasks/batch/toggle` | Operator | Enable or disable tasks in bulk |
+| `POST` | `/api/backup/tasks/batch/delete` | Operator | Delete tasks in bulk |
+| `POST` | `/api/backup/tasks/batch/run` | Operator | Run tasks in bulk |
+| `GET` | `/api/backup/tasks/:id` | Auth | Read a task |
+| `POST` | `/api/backup/tasks` | Operator | Create a task |
+| `PUT` | `/api/backup/tasks/:id` | Operator | Update a task |
+| `DELETE` | `/api/backup/tasks/:id` | Operator | Delete a task |
+| `PUT` | `/api/backup/tasks/:id/toggle` | Operator | Enable or disable a task |
+| `POST` | `/api/backup/tasks/:id/run` | Operator | Trigger a backup |
+| `POST` | `/api/backup/tasks/:id/verify` | Operator | Trigger verification from a task |
+
+Task export intentionally excludes database passwords and storage credentials. It is useful for migration and review, not a complete control-plane backup.
+
+## Backup and restore records
+
+| Method | Endpoint | Access | Description |
+| --- | --- | --- | --- |
+| `GET` | `/api/backup/records` | Auth | List and filter backup records |
+| `POST` | `/api/backup/records/batch-delete` | Operator | Delete records in bulk |
+| `GET` | `/api/backup/records/:id` | Auth | Read a backup record |
+| `GET` | `/api/backup/records/:id/logs/stream` | Auth | Stream logs with server-sent events |
+| `GET` | `/api/backup/records/:id/download` | Auth | Download an artifact |
+| `GET` | `/api/backup/records/:id/contents` | Auth | Browse artifact contents where supported |
+| `POST` | `/api/backup/records/:id/restore` | Operator | Start a restore |
+| `POST` | `/api/backup/records/:id/replicate` | Operator | Replicate an existing artifact |
+| `POST` | `/api/backup/records/:id/verify` | Operator | Verify an existing artifact |
+| `PUT` | `/api/backup/records/:id/lock` | Operator | Set retention lock state |
+| `DELETE` | `/api/backup/records/:id` | Operator | Delete a record and its managed artifact |
+| `GET` | `/api/restore/records` | Auth | List restore records |
+| `GET` | `/api/restore/records/:id` | Auth | Read a restore record |
+| `GET` | `/api/restore/records/:id/logs/stream` | Auth | Stream restore logs |
+| `GET` | `/api/replication/records` | Auth | List replication records |
+| `GET` | `/api/replication/records/:id` | Auth | Read a replication record |
+| `GET` | `/api/verify/records` | Auth | List verification records |
+| `GET` | `/api/verify/records/:id` | Auth | Read a verification record |
+| `GET` | `/api/verify/records/:id/logs/stream` | Auth | Stream verification logs |
+
+## Templates, reports, and dashboard
+
+| Method | Endpoint | Access | Description |
+| --- | --- | --- | --- |
+| `GET` | `/api/task-templates` | Auth | List task templates |
+| `GET` | `/api/task-templates/:id` | Auth | Read a task template |
+| `POST` | `/api/task-templates` | Operator | Create a template |
+| `PUT` | `/api/task-templates/:id` | Operator | Update a template |
+| `DELETE` | `/api/task-templates/:id` | Operator | Delete a template |
+| `POST` | `/api/task-templates/:id/apply` | Operator | Create tasks from a template |
+| `GET` | `/api/reports/compliance` | Auth | Read compliance evidence |
+| `GET` | `/api/reports/compliance/export` | Auth | Export compliance evidence as CSV |
+| `GET` | `/api/dashboard/stats` | Auth | Summary statistics |
+| `GET` | `/api/dashboard/timeline` | Auth | Recent activity |
+| `GET` | `/api/dashboard/sla` | Auth | RPO and SLA status |
+| `GET` | `/api/dashboard/cluster` | Auth | Cluster summary |
+| `GET` | `/api/dashboard/breakdown` | Auth | Task and record breakdown |
+| `GET` | `/api/dashboard/node-performance` | Auth | Per-node performance |
+
+## Notifications, settings, and administration
+
+| Method | Endpoint | Access | Description |
+| --- | --- | --- | --- |
+| `GET` | `/api/notifications` | Auth | List notification channels |
+| `GET` | `/api/notifications/:id` | Auth | Read a channel |
+| `POST` | `/api/notifications` | Operator | Create a channel |
+| `PUT` | `/api/notifications/:id` | Operator | Update a channel |
+| `DELETE` | `/api/notifications/:id` | Operator | Delete a channel |
+| `POST` | `/api/notifications/test` | Operator | Test an unsaved configuration |
+| `POST` | `/api/notifications/:id/test` | Operator | Test a saved channel |
+| `GET` | `/api/settings` | Auth | Read system settings |
+| `PUT` | `/api/settings` | Admin | Update system settings |
+| `GET` | `/api/users` | Admin | List users |
+| `POST` | `/api/users` | Admin | Create a user |
+| `PUT` | `/api/users/:id` | Admin | Update a user |
+| `POST` | `/api/users/:id/2fa/reset` | Admin | Reset a user's second factor |
+| `DELETE` | `/api/users/:id` | Admin | Delete a user |
+| `GET` | `/api/api-keys` | Admin | List API keys without plaintext values |
+| `POST` | `/api/api-keys` | Admin | Create an API key and return its plaintext once |
+| `PUT` | `/api/api-keys/:id/toggle` | Admin | Enable or disable an API key |
+| `DELETE` | `/api/api-keys/:id` | Admin | Revoke an API key |
+
+## Audit, events, search, and discovery
+
+| Method | Endpoint | Access | Description |
+| --- | --- | --- | --- |
+| `GET` | `/api/audit-logs` | Auth | List and filter audit records |
+| `GET` | `/api/audit-logs/export` | Auth | Export audit records |
+| `GET` | `/api/events/stream` | Auth | Stream real-time application events with SSE |
+| `GET` | `/api/search` | Auth | Search supported resources |
+| `POST` | `/api/database/discover` | Auth | Discover databases from supplied connection details |
+
+## Nodes
+
+| Method | Endpoint | Access | Description |
+| --- | --- | --- | --- |
+| `GET` | `/api/nodes` | Auth | List nodes |
+| `GET` | `/api/nodes/:id` | Auth | Read a node |
+| `GET` | `/api/nodes/:id/fs/list` | Operator | Browse the selected node filesystem |
+| `POST` | `/api/nodes` | Admin | Create a node |
+| `POST` | `/api/nodes/batch` | Admin | Create up to 50 nodes |
+| `PUT` | `/api/nodes/:id` | Admin | Update a node |
+| `DELETE` | `/api/nodes/:id` | Admin | Delete an unreferenced node |
+| `POST` | `/api/nodes/:id/install-tokens` | Admin | Create a one-time installer |
+| `GET` | `/api/nodes/:id/install-script-preview` | Admin | Preview generated install material |
+| `POST` | `/api/nodes/:id/rotate-token` | Admin | Rotate the long-lived node token |
+
+## Agent protocol
+
+These routes are for the `backupx agent` process and authenticate inside the handler with the node token.
+
+| Method | Endpoint | Access | Description |
+| --- | --- | --- | --- |
+| `POST` | `/api/agent/heartbeat` | Agent | Report liveness and node state |
+| `POST` | `/api/agent/commands/poll` | Agent | Claim a pending command |
+| `POST` | `/api/agent/commands/:id/result` | Agent | Report a command result |
+| `GET` | `/api/agent/tasks/:id` | Agent | Fetch a runnable task specification |
+| `POST` | `/api/agent/records/:id` | Agent | Append logs or update backup state |
+| `PUT` | `/api/agent/records/:id/artifacts/:targetId` | Agent | Stream a relayed artifact to the Master |
+| `GET` | `/api/agent/restores/:id/spec` | Agent | Fetch restore instructions |
+| `GET` | `/api/agent/restores/:id/artifact` | Agent | Stream a restore artifact |
+| `POST` | `/api/agent/restores/:id` | Agent | Update restore state |
+| `GET` | `/api/v1/agent/self` | Agent | Validate node identity during installation |
+
+## Public operational and install routes
+
+| Method | Endpoint | Access | Description |
+| --- | --- | --- | --- |
+| `GET` | `/health` | Public | Liveness |
+| `GET` | `/api/health` | Public | API-prefixed liveness alias |
+| `GET` | `/ready` | Public | SQLite readiness |
+| `GET` | `/api/ready` | Public | API-prefixed readiness alias |
+| `GET` | `/metrics` | Public | Prometheus metrics |
+| `GET` | `/install/:token` | Public | Consume a one-time Agent installer token |
+| `GET` | `/api/install/:token` | Public | API-prefixed installer route |
+| `GET` | `/install/:token/compose.yml` | Public | Render a Docker Agent Compose file |
+| `GET` | `/api/install/:token/compose.yml` | Public | API-prefixed Docker Compose route |
+
+Restrict probes and metrics to monitoring networks. Install tokens are single-use, time-limited secrets and must not be written to public logs.
+
+## Response formats
+
+Most JSON successes use:
+
+~~~json
+{
+  "code": "OK",
+  "message": "success",
+  "data": {}
+}
+~~~
+
+Errors use an HTTP 4xx or 5xx status plus a stable application code:
+
+~~~json
+{
+  "code": "BACKUP_TASK_NOT_FOUND",
+  "message": "备份任务不存在"
+}
+~~~
+
+Clients should branch on the HTTP status and `code`, not the localized `message`.
+
+Artifact downloads, task JSON export, audit or compliance exports, installer responses, and `/metrics` return their native content types instead of the JSON envelope. Log and event streams use `text/event-stream`; reverse proxies must keep response buffering disabled.
--- a/docs-site/docs/reference/cli.md
+++ b/docs-site/docs/reference/cli.md
@@ -0,0 +1,80 @@
+---
+sidebar_position: 2
+title: CLI Reference
+description: backupx subcommands — server, agent, backint, reset-password.
+---
+
+# CLI Reference
+
+The `backupx` binary ships several subcommands. Running `backupx` with no subcommand starts the main server process.
+
+## `backupx` (default: server)
+
+```bash
+backupx --config /opt/backupx/config.yaml
+backupx --version
+```
+
+| Flag | Description |
+|------|-------------|
+| `--config <path>` | Explicit config YAML path; omitted uses the search paths below |
+| `--version` | Print version and exit |
+
+When `--config` is omitted, the server searches `./config.yaml`, `./server/config.yaml`, and `/etc/backupx/config.yaml`. `BACKUPX_*` environment variables override matching server configuration keys. See [Configuration Reference](../deployment/configuration).
+
+## `backupx agent`
+
+Run in Agent mode, connecting to a Master. See [Multi-Node Cluster](../features/multi-node).
+
+```bash
+backupx agent --master https://backup.example.com --token-file /etc/backupx-agent/agent.token
+```
+
+| Flag | Description |
+|------|-------------|
+| `--master <url>` | Master URL |
+| `--token <token>` | Agent auth token |
+| `--token-file <path>` | Read the Agent Token from a file; preferred for services and containers |
+| `--config <path>` | Load Agent YAML; when present, environment-based Agent config is not loaded |
+| `--temp-dir <path>` | Local temp directory (default `/var/lib/backupx-agent/tmp`) |
+| `--proxy-url <url>` | Explicit HTTP(S) or SOCKS5(H) proxy |
+| `--ca-cert <path>` | PEM CA certificate used to verify the Master |
+| `--insecure-tls` | Skip TLS verification (testing only) |
+
+Agent precedence is explicit CLI flags over a YAML file. If `--config` is not supplied, Agent settings are loaded from `BACKUPX_AGENT_MASTER`, `BACKUPX_AGENT_TOKEN`, `BACKUPX_AGENT_TOKEN_FILE`, `BACKUPX_AGENT_HEARTBEAT`, `BACKUPX_AGENT_POLL`, `BACKUPX_AGENT_TEMP_DIR`, `BACKUPX_AGENT_PROXY_URL`, `BACKUPX_AGENT_CA_CERT_FILE`, and `BACKUPX_AGENT_INSECURE_TLS`. When no explicit proxy URL is set, the Agent also honors `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY`.
+
+`--token` overrides `--token-file`. Keep long-lived tokens in a root-readable file rather than command history. A private CA and `--insecure-tls` cannot be enabled together.
+
+## `backupx backint`
+
+SAP HANA Backint protocol agent. See [SAP HANA Support](../features/sap-hana).
+
+```bash
+backupx backint -f <function> -i <input> -o <output> -p <params>
+```
+
+| Flag | Description |
+|------|-------------|
+| `-f <fn>` | `backup` / `restore` / `inquire` / `delete` |
+| `-i <path>` | Input file |
+| `-o <path>` | Output file |
+| `-p <path>` | Parameter file |
+| `-u / -c / -l / -v` | Accepted and ignored for SAP compatibility |
+
+The `-p` file must define `STORAGE_TYPE` and either `STORAGE_CONFIG_JSON` or `STORAGE_CONFIG`. Optional keys include `PARALLEL_FACTOR`, `COMPRESS`, `LOG_FILE`, `CATALOG_DB`, and `KEY_PREFIX`.
+
+## `backupx reset-password`
+
+Reset an admin password directly in the SQLite database. No server restart needed.
+
+```bash
+backupx reset-password --username admin --password 'newpass123' [--config /path/to/config.yaml]
+```
+
+| Flag | Description |
+|------|-------------|
+| `--username` | Target username (default: `admin`) |
+| `--password` | New password (min 8 chars, required) |
+| `--config` | Config path (used to locate the database file) |
+
+Run this command on the Master host with access to the configured SQLite path. Avoid placing the new password directly in retained shell history.
--- a/docs-site/docusaurus.config.ts
+++ b/docs-site/docusaurus.config.ts
@@ -0,0 +1,147 @@
+import {themes as prismThemes} from 'prism-react-renderer';
+import type {Config} from '@docusaurus/types';
+import type * as Preset from '@docusaurus/preset-classic';
+
+// BackupX 官方站点 — 托管在 GitHub Pages
+// https://awuqing.github.io/BackupX/
+const config: Config = {
+  title: 'BackupX',
+  tagline: 'Self-hosted backup orchestration for servers, databases, storage targets and remote agents',
+  favicon: 'img/favicon.ico',
+
+  future: {
+    v4: true,
+  },
+
+  url: 'https://awuqing.github.io',
+  baseUrl: '/BackupX/',
+
+  organizationName: 'Awuqing',
+  projectName: 'BackupX',
+  deploymentBranch: 'gh-pages',
+  trailingSlash: false,
+
+  onBrokenLinks: 'throw',
+  markdown: {
+    hooks: {
+      onBrokenMarkdownLinks: 'throw',
+    },
+  },
+
+  i18n: {
+    defaultLocale: 'en',
+    locales: ['en', 'zh-Hans'],
+    localeConfigs: {
+      en: {label: 'English', direction: 'ltr', htmlLang: 'en-US'},
+      // Keep the published /zh-Hans/ URL while loading the existing zh-CN
+      // translation tree. Without path, Docusaurus silently falls back to the
+      // English documents because i18n/zh-Hans does not exist.
+      'zh-Hans': {label: '简体中文', direction: 'ltr', htmlLang: 'zh-CN', path: 'zh-CN'},
+    },
+  },
+
+  presets: [
+    [
+      'classic',
+      {
+        docs: {
+          sidebarPath: './sidebars.ts',
+          editUrl: 'https://github.com/Awuqing/BackupX/edit/main/docs-site/',
+          editLocalizedFiles: true,
+        },
+        blog: false,
+        theme: {
+          customCss: './src/css/custom.css',
+        },
+      } satisfies Preset.Options,
+    ],
+  ],
+
+  themeConfig: {
+    image: 'img/social-card.png',
+    colorMode: {
+      respectPrefersColorScheme: true,
+    },
+    navbar: {
+      title: 'BackupX',
+      logo: {
+        alt: 'BackupX Logo',
+        src: 'img/logo.svg',
+      },
+      items: [
+        {
+          type: 'docSidebar',
+          sidebarId: 'docs',
+          position: 'left',
+          label: 'Docs',
+        },
+        {
+          to: '/docs/deployment/docker',
+          label: 'Deployment',
+          position: 'left',
+        },
+        {
+          to: '/docs/operations/monitoring',
+          label: 'Operations',
+          position: 'left',
+        },
+        {
+          to: '/docs/reference/api',
+          label: 'API',
+          position: 'left',
+        },
+        {
+          to: '/community',
+          label: 'Community',
+          position: 'right',
+        },
+        {
+          type: 'localeDropdown',
+          position: 'right',
+        },
+        {
+          href: 'https://github.com/Awuqing/BackupX',
+          label: 'GitHub',
+          position: 'right',
+        },
+      ],
+    },
+    footer: {
+      style: 'dark',
+      links: [
+        {
+          title: 'Documentation',
+          items: [
+            {label: 'Introduction', to: '/docs/intro'},
+            {label: 'Quick Start', to: '/docs/getting-started/quick-start'},
+            {label: 'Configuration', to: '/docs/deployment/configuration'},
+          ],
+        },
+        {
+          title: 'Operations',
+          items: [
+            {label: 'Monitoring', to: '/docs/operations/monitoring'},
+            {label: 'Security', to: '/docs/operations/security'},
+            {label: 'Troubleshooting', to: '/docs/operations/troubleshooting'},
+          ],
+        },
+        {
+          title: 'Project',
+          items: [
+            {label: 'GitHub', href: 'https://github.com/Awuqing/BackupX'},
+            {label: 'Releases', href: 'https://github.com/Awuqing/BackupX/releases'},
+            {label: 'Community', to: '/community'},
+          ],
+        },
+      ],
+      copyright: `Copyright © ${new Date().getFullYear()} BackupX · Apache License 2.0`,
+    },
+    prism: {
+      theme: prismThemes.github,
+      darkTheme: prismThemes.dracula,
+      additionalLanguages: ['bash', 'yaml', 'ini', 'json', 'go', 'sql', 'nginx'],
+    },
+  } satisfies Preset.ThemeConfig,
+};
+
+export default config;
--- a/docs-site/i18n/zh-CN/code.json
+++ b/docs-site/i18n/zh-CN/code.json
@@ -0,0 +1,115 @@
+{
+  "home.badge": {"message": "BackupX 文档 · v2.2.1"},
+  "home.title.part1": {"message": "可靠地运维 BackupX，"},
+  "home.title.part2": {"message": "每一步都有依据。"},
+  "home.tagline": {"message": "从部署控制平面、连接存储与远程 Agent，到持续观测和验证恢复，一套务实文档覆盖完整运维路径。"},
+  "home.pageTitle": {"message": "面向自托管服务器的备份编排"},
+  "home.getStarted": {"message": "使用 Docker 开始"},
+  "home.viewSource": {"message": "查看源码"},
+  "home.supported.label": {"message": "支持的运行环境"},
+  "home.supported.docker": {"message": "Docker"},
+  "home.supported.linux": {"message": "Linux"},
+  "home.supported.windows": {"message": "Windows Agent"},
+  "home.guide.label": {"message": "推荐文档路径"},
+  "home.guide.kicker": {"message": "从这里开始"},
+  "home.guide.hint": {"message": "为下一项工作选择指南"},
+  "home.guide.install.title": {"message": "安装 BackupX"},
+  "home.guide.install.desc": {"message": "Docker、Compose 或独立二进制"},
+  "home.guide.cluster.title": {"message": "连接远程节点"},
+  "home.guide.cluster.desc": {"message": "Agent、代理、私有 CA 与堡垒机"},
+  "home.guide.security.title": {"message": "加固运维环境"},
+  "home.guide.security.desc": {"message": "安全控制、监控与审计记录"},
+  "home.guide.recovery.title": {"message": "准备恢复方案"},
+  "home.guide.recovery.desc": {"message": "升级、回滚、恢复与故障排查"},
+
+  "section.features.tag": {"message": "文档路径"},
+  "section.features.title": {"message": "从部署到恢复，不依赖猜测"},
+  "section.features.subtitle": {"message": "每条路径都把产品能力与生产环境所需的配置、安全和运维决策直接关联。"},
+  "feat.install.title": {"message": "安装与升级"},
+  "feat.install.desc": {"message": "选择 Docker、Compose 或独立二进制，并保持部署过程可重复。"},
+  "feat.types.title": {"message": "保护文件与数据库"},
+  "feat.types.desc": {"message": "配置文件、MySQL、PostgreSQL、SQLite 和 SAP HANA 备份工作负载。"},
+  "feat.storage.title": {"message": "连接存储目标"},
+  "feat.storage.desc": {"message": "通过一致流程使用原生 Provider 或任意受支持的 rclone 后端。"},
+  "feat.cluster.title": {"message": "构建远程节点集群"},
+  "feat.cluster.desc": {"message": "通过代理、私有 CA 或 SSH 堡垒机部署仅出站连接的 Agent。"},
+  "feat.monitor.title": {"message": "监控日常运行"},
+  "feat.monitor.desc": {"message": "持续查看任务健康、存储容量、通知、日志和服务就绪状态。"},
+  "feat.recovery.title": {"message": "按验证过的方案恢复"},
+  "feat.recovery.desc": {"message": "预先准备升级、回滚点、恢复验证和事件故障排查。"},
+
+  "showcase.tag": {"message": "产品界面"},
+  "showcase.title": {"message": "部署前先了解完整操作流程"},
+  "showcase.subtitle": {"message": "每张产品截图都连接到对应指南，说明背后的任务、配置和运行模型。"},
+  "showcase.tabs.label": {"message": "BackupX 产品界面"},
+  "showcase.preview.label": {"message": "BackupX 控制台"},
+  "showcase.tab.dashboard": {"message": "仪表盘"},
+  "showcase.tab.tasks": {"message": "备份任务"},
+  "showcase.tab.storage": {"message": "存储目标"},
+  "showcase.tab.nodes": {"message": "多节点"},
+  "showcase.dashboard.alt": {"message": "BackupX 仪表盘，展示 30 天备份趋势、存储分布、任务规模和集群健康度"},
+  "showcase.dashboard.title": {"message": "一眼掌握运行态"},
+  "showcase.dashboard.desc": {"message": "在一个实时运维视图中掌握 30 天成功/失败趋势、存储分布、任务数量、数据量和最近执行记录。"},
+  "showcase.tasks.alt": {"message": "BackupX 任务列表，展示调度、存储目标、保留策略、标签、RPO 目标和验证状态"},
+  "showcase.tasks.title": {"message": "策略状态清晰可扫"},
+  "showcase.tasks.desc": {"message": "集中查看调度、多目标策略、保留规则、标签、RPO 目标和验证状态，并可一键操作任意任务。"},
+  "showcase.storage.alt": {"message": "BackupX 存储目标，展示连接状态、实时容量、收藏和冗余角色"},
+  "showcase.storage.title": {"message": "每个目标，统一视图"},
+  "showcase.storage.desc": {"message": "统一比较本地磁盘与 70+ 远程后端的连接状态、实时容量、收藏及冗余角色。"},
+  "showcase.nodes.alt": {"message": "BackupX 节点列表，展示健康度、Agent 版本、队列深度、标签和心跳时间"},
+  "showcase.nodes.title": {"message": "集群健康一屏掌握"},
+  "showcase.nodes.desc": {"message": "集中监控本地 Master 与每个远程节点的健康度、Agent 版本、队列深度、标签和心跳时间。"},
+  "showcase.cta": {"message": "开始阅读文档"},
+
+  "community.tag": {"message": "社区"},
+  "community.pageTitle": {"message": "社区、赞助与贡献者"},
+  "community.pageDescription": {"message": "反馈真实部署约束、完善文档，或为 BackupX 提交可验证的改进。"},
+  "community.title": {"message": "开放协作让运维知识持续完善"},
+  "community.subtitle": {"message": "反馈真实部署约束、完善运行手册，或通过可复现验证提交聚焦的改动。"},
+  "community.path.kicker": {"message": "贡献路径"},
+  "community.path.guide": {"message": "贡献指南"},
+  "community.path.issues.title": {"message": "反馈生产环境问题"},
+  "community.path.issues.desc": {"message": "提交日志、部署拓扑和恢复预期。"},
+  "community.path.docs.title": {"message": "完善文档与示例"},
+  "community.path.docs.desc": {"message": "贡献存储、Agent 和数据库部署指南。"},
+  "community.path.code.title": {"message": "提交聚焦的 Pull Request"},
+  "community.path.code.desc": {"message": "保持改动可测试、可审查，并贴合现有架构。"},
+  "community.contributor.kicker": {"message": "贡献者"},
+  "community.contributor.all": {"message": "查看全部"},
+  "community.contributor.source": {"message": "通过 GitHub contributors API 加载，并提供本地回退数据。"},
+  "community.contributor.botRole": {"message": "自动化贡献者"},
+  "community.contributor.githubRole": {"message": "GitHub 贡献者"},
+  "community.contributor.contributions": {"message": "{count} 次贡献"},
+  "community.sponsor.bandTitle": {"message": "支持长期维护"},
+  "community.sponsor.bandDesc": {"message": "支持兼容性测试、恢复工作和面向运维者的文档。"},
+  "community.sponsor.learnMore": {"message": "了解赞助方案"},
+  "community.sponsor.title": {"message": "支持可靠的备份基础设施"},
+  "community.sponsor.programDesc": {"message": "赞助将用于测试覆盖、恢复可信度、Provider 兼容性，以及运维人员可以直接应用的文档。"},
+  "community.sponsor.cta": {"message": "赞助 BackupX"},
+  "community.sponsor.infrastructure.label": {"message": "基础设施"},
+  "community.sponsor.infrastructure.title": {"message": "云与存储兼容性"},
+  "community.sponsor.infrastructure.desc": {"message": "支持对象存储、WebDAV、SFTP 和区域云平台的真实验证。"},
+  "community.sponsor.security.label": {"message": "可靠性"},
+  "community.sponsor.security.title": {"message": "安全与恢复工作"},
+  "community.sponsor.security.desc": {"message": "支持加密审查、恢复演练、发布签名和运维检查。"},
+  "community.sponsor.community.label": {"message": "社区"},
+  "community.sponsor.community.title": {"message": "文档与贡献者支持"},
+  "community.sponsor.community.desc": {"message": "改善指南、示例、平台测试和贡献者体验。"},
+  "community.sponsor.tier.title": {"message": "支持方式"},
+  "community.sponsor.tier.subtitle": {"message": "根据团队依赖 BackupX 的方式选择合适层级。"},
+  "community.sponsor.tier.backer.name": {"message": "Backer"},
+  "community.sponsor.tier.backer.amount": {"message": "适合个人与小团队"},
+  "community.sponsor.tier.backer.desc": {"message": "支持文档、Issue 分流、兼容性测试和聚焦的易用性改进。"},
+  "community.sponsor.tier.partner.name": {"message": "Partner"},
+  "community.sponsor.tier.partner.amount": {"message": "适合存储与基础设施厂商"},
+  "community.sponsor.tier.partner.desc": {"message": "支持 Provider 验证、部署示例、基准说明和集成指南。"},
+  "community.sponsor.tier.enterprise.name": {"message": "Enterprise"},
+  "community.sponsor.tier.enterprise.amount": {"message": "适合生产环境使用方"},
+  "community.sponsor.tier.enterprise.desc": {"message": "支持恢复演练、发布加固、审计和长期维护。"},
+
+  "sponsors.pageTitle": {"message": "赞助 BackupX"},
+  "sponsors.pageDescription": {"message": "支持 BackupX 的可靠性、文档、存储兼容性和长期维护。"},
+  "sponsors.tag": {"message": "赞助"},
+  "sponsors.title": {"message": "让关键维护工作持续进行"},
+  "sponsors.subtitle": {"message": "赞助用于真实 Provider 验证、可靠发布、恢复演练和更完善的运维文档。"}
+}
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current.json
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current.json
@@ -0,0 +1,9 @@
+{
+  "version.label": {"message": "Next"},
+  "sidebar.docs.category.Getting Started": {"message": "快速开始"},
+  "sidebar.docs.category.Deployment": {"message": "部署"},
+  "sidebar.docs.category.Operations": {"message": "运维"},
+  "sidebar.docs.category.Features": {"message": "功能特性"},
+  "sidebar.docs.category.Reference": {"message": "参考"},
+  "sidebar.docs.category.Development": {"message": "开发"}
+}
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/bare-metal.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/bare-metal.md
@@ -0,0 +1,121 @@
+---
+sidebar_position: 2
+title: 裸机部署
+description: 从预编译包或源码加固部署 BackupX，Nginx 改为显式启用。
+---
+
+# 裸机部署
+
+## 使用预编译包
+
+```bash
+# 下载对应平台的压缩包
+curl -LO https://github.com/Awuqing/BackupX/releases/latest/download/backupx-linux-amd64.tar.gz
+curl -LO https://github.com/Awuqing/BackupX/releases/latest/download/backupx-linux-amd64.tar.gz.sha256
+sha256sum -c backupx-linux-amd64.tar.gz.sha256
+
+# 解压并安装
+tar xzf backupx-linux-amd64.tar.gz && cd backupx-*-linux-amd64
+sudo ./install.sh
+```
+
+安装脚本自动完成以下步骤：
+
+1. 创建系统用户 `backupx`
+2. 复制二进制到 `/opt/backupx/bin/backupx`，并把 Web 控制台复制到 `/opt/backupx/web`
+3. 把默认配置安装到 `/etc/backupx/config.yaml`
+4. 安装并启用 `backupx.service` systemd 单元
+5. 默认不修改 Nginx；只有显式设置 `INSTALL_NGINX=1` 时才安装模板
+6. 验证首次初始化接口就绪后才报告安装成功
+
+可执行文件与前端资源由 root 所有，只有 `/opt/backupx/data` 允许 `backupx` 服务账户写入。`/etc/backupx/config.yaml` 以 `root:backupx`、`0640` 权限安装。
+
+仓库提供的 Nginx 模板只是起点，可能与现有默认站点冲突。先审核域名与 TLS 策略，再显式启用：
+
+```bash
+sudo INSTALL_NGINX=1 ./install.sh
+```
+
+如果要部署多节点集群，安装后请编辑 `/etc/backupx/config.yaml`，设置远程 Agent 可访问到的 Master URL：
+
+```yaml
+server:
+  external_url: "https://backup.example.com"
+```
+
+修改后重启 BackupX：
+
+```bash
+sudo systemctl restart backupx
+```
+
+## 从源码构建
+
+```bash
+git clone https://github.com/Awuqing/BackupX.git && cd BackupX
+make build
+sudo ./deploy/install.sh
+```
+
+`make build` 会产出：
+
+- `server/bin/backupx`（Go 后端，无 CGO）
+- `web/dist/`（React 前端，执行 `npm run build`）
+
+## systemd
+
+安装后的 service 文件：
+
+```ini title="/etc/systemd/system/backupx.service"
+[Unit]
+Description=BackupX API Service
+After=network-online.target
+Wants=network-online.target
+
+[Service]
+Type=simple
+User=backupx
+Group=backupx
+WorkingDirectory=/opt/backupx
+ExecStart=/opt/backupx/bin/backupx -config /etc/backupx/config.yaml
+Restart=on-failure
+RestartSec=5
+NoNewPrivileges=true
+UMask=0027
+LimitNOFILE=65535
+
+[Install]
+WantedBy=multi-user.target
+```
+
+常用命令：
+
+```bash
+sudo systemctl status backupx
+sudo journalctl -u backupx -f    # 实时日志
+sudo systemctl restart backupx
+curl -fsS http://127.0.0.1:8340/api/auth/setup/status
+```
+
+访问 `http://your-server:8340`，可按需切换到 English，然后在“系统初始化 / System setup”页面创建首个管理员。若监听端口不是默认值，请为安装脚本传入对应的 `HEALTH_URL`。
+
+生产环境应通过 HTTPS 暴露 BackupX，或在防火墙限制 `8340` 端口。安装器不会自动修改防火墙。
+
+替换版本前，应在服务停止时同时快照 `/etc/backupx`、`/opt/backupx/data`、已安装二进制和前端文件。请按[升级与恢复](../operations/upgrade-recovery)中的版本化流程操作；让旧版本二进制直接读取已由新版本迁移的数据库并不是安全回滚。
+
+## 密码重置
+
+忘记管理员密码时：
+
+```bash
+/opt/backupx/bin/backupx reset-password \
+  --username admin \
+  --password 'newpass123' \
+  --config /etc/backupx/config.yaml
+```
+
+Docker 等效命令：
+
+```bash
+docker exec -it backupx /app/bin/backupx reset-password --username admin --password 'newpass123'
+```
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/configuration.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/configuration.md
@@ -0,0 +1,97 @@
+---
+sidebar_position: 4
+title: 配置参考
+description: config.yaml 全部服务端配置项及对应的环境变量。
+---
+
+# 配置参考
+
+BackupX 默认从工作目录加载 `./config.yaml`，可通过 `--config` 指定其他路径。所有配置项都可通过 `BACKUPX_` 前缀环境变量覆盖。
+
+## 完整配置
+
+```yaml title="config.yaml"
+server:
+  host: "0.0.0.0"             # BACKUPX_SERVER_HOST
+  port: 8340                  # BACKUPX_SERVER_PORT
+  mode: "release"             # release | debug
+  external_url: ""            # BACKUPX_SERVER_EXTERNAL_URL — 稳定的 Master 对外 URL
+  trusted_proxies:             # BACKUPX_SERVER_TRUSTED_PROXIES — 准确的代理 IP/CIDR
+    - "127.0.0.1"
+    - "::1"
+  web_root: ""                # BACKUPX_SERVER_WEB_ROOT — 前端构建目录
+
+database:
+  path: "./data/backupx.db"   # BACKUPX_DATABASE_PATH — 内嵌 SQLite
+
+security:
+  jwt_secret: ""              # BACKUPX_SECURITY_JWT_SECRET — 留空自动生成
+  jwt_expire: "24h"           # BACKUPX_SECURITY_JWT_EXPIRE
+  encryption_key: ""          # 用于加密存储配置的 AES-256-GCM 密钥
+
+backup:
+  temp_dir: "/tmp/backupx"    # BACKUPX_BACKUP_TEMP_DIR
+  max_concurrent: 2           # BACKUPX_BACKUP_MAX_CONCURRENT
+  retries: 10                 # 单次上传的 rclone 底层重试次数
+  bandwidth_limit: ""         # 例如 "10M" 表示限速 10 MB/s
+
+log:
+  level: "info"               # debug | info | warn | error
+  file: "./data/backupx.log"
+  max_size: 100               # 单个日志文件上限，单位 MB
+  max_backups: 3              # 保留的轮转文件数
+  max_age: 30                 # 保留天数
+```
+
+## 密钥生成
+
+如果首次启动时 `jwt_secret` 或 `encryption_key` 为空，BackupX 会自动生成随机值并写入 `system_configs` 表。请妥善备份 `data/backupx.db`，一旦丢失将导致所有已加密的存储配置失效。
+
+## 环境变量
+
+文件和环境变量同时存在时，环境变量优先。配置路径转换规则：小写字母下划线 → 大写字母下划线：
+
+| 配置项 | 环境变量 |
+|--------|----------|
+| `server.port` | `BACKUPX_SERVER_PORT` |
+| `server.external_url` | `BACKUPX_SERVER_EXTERNAL_URL` |
+| `server.trusted_proxies` | `BACKUPX_SERVER_TRUSTED_PROXIES`（环境变量使用逗号分隔） |
+| `security.jwt_secret` | `BACKUPX_SECURITY_JWT_SECRET` |
+| `security.jwt_expire` | `BACKUPX_SECURITY_JWT_EXPIRE` |
+| `security.encryption_key` | `BACKUPX_SECURITY_ENCRYPTION_KEY` |
+| `log.level` | `BACKUPX_LOG_LEVEL` |
+| `backup.max_concurrent` | `BACKUPX_BACKUP_MAX_CONCURRENT` |
+| `backup.temp_dir` | `BACKUPX_BACKUP_TEMP_DIR` |
+| `backup.retries` | `BACKUPX_BACKUP_RETRIES` |
+| `backup.bandwidth_limit` | `BACKUPX_BACKUP_BANDWIDTH_LIMIT` |
+| `log.max_size` | `BACKUPX_LOG_MAX_SIZE` |
+| `log.max_backups` | `BACKUPX_LOG_MAX_BACKUPS` |
+| `log.max_age` | `BACKUPX_LOG_MAX_AGE` |
+
+## Master 对外 URL
+
+当 BackupX 部署在 Docker、Nginx、负载均衡或多层反向代理后面，且后端收到的内部 Host 不是远程 Agent 可访问地址时，请配置 `server.external_url`：
+
+```yaml
+server:
+  external_url: "https://backup.example.com"
+```
+
+BackupX 会用这个地址渲染一键 Agent 安装脚本和 docker-compose 片段。该地址必须能被所有 Agent 主机访问。只有在 `X-Forwarded-Proto` / `X-Forwarded-Host` 可靠且正好指向 Agent 可访问地址时，才建议留空。
+
+代理或 SSH 堡垒机场景可在安装向导中为单个 Agent 设置覆盖地址。目标侧的一次性安装链接与生成的 Agent 运行配置都会使用这个地址，浏览器仍使用正常的公开地址。
+
+## 可信反向代理
+
+BackupX 只接受 `server.trusted_proxies` 中来源提供的客户端转发头。默认仅允许本机 Nginx。代理运行在其他容器或主机时，加入准确 IP 或网段：
+
+```yaml
+server:
+  trusted_proxies:
+    - "127.0.0.1"
+    - "172.18.0.0/16"
+```
+
+不要配置 `0.0.0.0/0`，因为登录限流、安装令牌限流和审计日志都依赖客户端地址。BackupX 直接暴露且不应信任任何转发头时可设置空列表。
+
+修改安全密钥或数据库路径前，应同时备份完整数据目录和配置文件。经过验证的快照与回滚流程见[升级与恢复](../operations/upgrade-recovery)。
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/docker.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/docker.md
@@ -0,0 +1,98 @@
+---
+sidebar_position: 1
+title: Docker 部署
+description: 带健康检查和持久化数据的加固单进程 Docker 部署。
+---
+
+# Docker 部署
+
+官方镜像 [`awuqing/backupx`](https://hub.docker.com/r/awuqing/backupx) 支持 `linux/amd64` 和 `linux/arm64`。
+
+## Compose 文件
+
+```yaml title="docker-compose.yml"
+services:
+  backupx:
+    image: ${BACKUPX_IMAGE:-awuqing/backupx:latest}
+    container_name: backupx
+    restart: unless-stopped
+    init: true
+    stop_grace_period: 30s
+    ports:
+      - "${BACKUPX_BIND_ADDRESS:-0.0.0.0}:${BACKUPX_PORT:-8340}:8340"
+    volumes:
+      - backupx-data:/app/data
+      # - /var/www:/mnt/www:ro
+      # - /etc/nginx:/mnt/nginx-conf:ro
+    security_opt:
+      - no-new-privileges:true
+    cap_drop:
+      - ALL
+    cap_add:
+      - CHOWN
+      - DAC_OVERRIDE
+      - SETGID
+      - SETUID
+    environment:
+      TZ: Asia/Shanghai
+      # BACKUPX_SERVER_EXTERNAL_URL: https://backup.example.com
+      BACKUPX_LOG_LEVEL: info
+      BACKUPX_BACKUP_MAX_CONCURRENT: "2"
+    healthcheck:
+      test: ["CMD", "su-exec", "backupx:backupx", "wget", "-q", "-T", "3", "-O", "/dev/null", "http://127.0.0.1:8340/ready"]
+      interval: 30s
+      timeout: 5s
+      retries: 3
+      start_period: 10s
+
+volumes:
+  backupx-data:
+```
+
+```bash
+docker compose up -d
+docker compose ps
+```
+
+入口脚本仅以 root 完成旧镜像数据的所有权迁移，随后只运行一个非 root `backupx` 进程；Compose 仅保留初始化所需的所有权与 UID/GID 切换能力。后端同时提供 API 与前端静态文件，默认不挂载 Docker Socket，也不打包 Docker CLI。生产环境应把 `BACKUPX_IMAGE` 固定到明确 Release 标签。
+
+## 备份宿主机目录
+
+按需挂载源目录，并在任务中使用容器内路径。容器中的 `backupx` 用户必须拥有读取权限；恢复目标应使用单独且范围受限的可写挂载。特权路径优先通过远程 Agent 处理；确实需要 Master 以 root 读取时，应显式设置 `user: "0:0"` 并审核每一个挂载。
+
+## 多节点集群
+
+设置所有 Agent 可达的稳定地址：
+
+```yaml
+environment:
+  BACKUPX_SERVER_EXTERNAL_URL: https://backup.example.com
+```
+
+跨不可信网络必须使用 HTTPS。代理、私有 CA 和 SSH 堡垒机场景见 [多节点集群](../features/multi-node)。
+
+外部反向代理运行在其他容器时，只把准确的 Docker 网桥网段加入 `BACKUPX_SERVER_TRUSTED_PROXIES`，例如 `172.18.0.0/16`，不要信任所有地址。
+
+## 环境变量覆盖
+
+```yaml
+environment:
+  TZ: Asia/Shanghai
+  BACKUPX_LOG_LEVEL: debug
+  BACKUPX_BACKUP_MAX_CONCURRENT: "4"
+  BACKUPX_BACKUP_TEMP_DIR: /tmp/backupx
+```
+
+镜像内部端口固定为 `8340`，只通过 `BACKUPX_PORT` 修改宿主机发布端口。
+
+## 升级前提
+
+```bash
+docker compose pull
+docker compose up -d
+docker compose ps
+```
+
+等待状态变为 `healthy` 后再切换流量或移除旧部署。升级前应停止 Master 后做文件级复制，或对整个 `backupx-data` 卷创建原子快照。同一个数据卷必须只运行一个活动 Master；SQLite 不支持多个 Master 容器共享 `/app/data`。
+
+生产环境应使用发布标签或镜像摘要而不是 `latest`，并保留与旧版本匹配的升级前数据快照。完整的升级、回滚和灾难恢复流程见[升级与恢复](../operations/upgrade-recovery)。
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/nginx.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/nginx.md
@@ -0,0 +1,81 @@
+---
+sidebar_position: 3
+title: Nginx 反向代理
+description: 通过 Nginx 发布 BackupX（HTTPS + SSE 友好的缓冲配置）。
+---
+
+# Nginx 反向代理
+
+生产环境可用的 Nginx 站点模板：
+
+```nginx title="/etc/nginx/sites-available/backupx"
+server {
+    listen 80;
+    server_name backup.example.com;
+
+    # 静态 UI（由 /opt/backupx/web 提供）
+    location / {
+        root /opt/backupx/web;
+        try_files $uri $uri/ /index.html;
+    }
+
+    # API 反向代理
+    location /api/ {
+        proxy_pass http://127.0.0.1:8340;
+        proxy_http_version 1.1;
+        proxy_set_header Host $http_host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+        proxy_set_header X-Forwarded-Host $http_host;
+        proxy_set_header X-Forwarded-Port $server_port;
+        proxy_set_header Connection "";
+
+        # 大文件上传（用于恢复流程）
+        client_max_body_size 0;
+        proxy_request_buffering off;
+
+        # 实时日志使用 SSE，必须关闭缓冲
+        proxy_buffering off;
+        proxy_cache off;
+        proxy_read_timeout 3600s;
+        proxy_send_timeout 3600s;
+    }
+
+    # 兼容旧版本生成的安装地址；新版本通过上面的 /api/install/ 访问。
+    location /install/ {
+        proxy_pass http://127.0.0.1:8340/install/;
+        proxy_http_version 1.1;
+        proxy_set_header Host $http_host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+        proxy_set_header X-Forwarded-Host $http_host;
+        proxy_set_header X-Forwarded-Port $server_port;
+    }
+
+    # 避免探针和指标请求落入 SPA fallback。
+    location = /health { proxy_pass http://127.0.0.1:8340/health; }
+    location = /ready  { proxy_pass http://127.0.0.1:8340/ready; }
+    location = /metrics { proxy_pass http://127.0.0.1:8340/metrics; }
+}
+```
+
+集群使用 Master 中转备份时必须保留 `proxy_request_buffering off`。否则 Nginx 会先把 Agent 上传的完整备份写入代理临时目录，再交给 BackupX，既失去流式传输优势，也可能占满代理磁盘。
+
+如果 Nginx 运行在另一台主机或另一个容器，只把该代理的 IP 或网段加入 `server.trusted_proxies`，不要配置 `0.0.0.0/0`。登录限流、安装令牌限流和审计日志都依赖可信的客户端地址。
+
+`/health`、`/ready` 和 `/metrics` 不需要 BackupX 认证。应只放行探针与 Prometheus 来源网段，或把这些 location 放在内部监听端口，避免直接暴露到互联网。
+
+## certbot 配置 HTTPS
+
+```bash
+sudo apt install certbot python3-certbot-nginx
+sudo certbot --nginx -d backup.example.com
+```
+
+certbot 会自动改写配置监听 443 并设置续期。
+
+:::caution Agent 需要稳定的 URL
+如果 Master 部署在 HTTPS 后面，远程 Agent 的 `--master` 必须使用最终 HTTPS 地址，Agent 不会跟随重定向。私有 CA 应预先下发 PEM 证书并使用 `--ca-cert /path/to/ca.pem`；`--insecure-tls` 只用于短期测试。
+:::
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/contributing.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/contributing.md
@@ -0,0 +1,41 @@
+---
+sidebar_position: 2
+title: 贡献指南
+description: 如何反馈问题、提出改进、提交 PR。
+---
+
+# 贡献指南
+
+BackupX 使用 Apache License 2.0 开源，欢迎提交 Issue 与 Pull Request。
+
+## 报告 Bug
+
+在 [github.com/Awuqing/BackupX/issues](https://github.com/Awuqing/BackupX/issues) 提交 Issue，请附上：
+
+- BackupX 版本（`backupx --version`）
+- 部署方式（Docker / 裸机 / 源码）
+- 相关的备份任务类型和存储后端
+- 复现步骤
+- 问题发生时段的 stdout / `backupx.log` 片段
+
+## 提议改动
+
+对于重要功能或重构，建议先开 Issue 对齐方案，避免 PR 大改动后被 Review 回退。
+
+## 提交 PR
+
+1. Fork 仓库，创建主题分支（如 `fix/windows-path-escape`）
+2. 执行 `make test` 确认本地全通过
+3. 保持每个 PR 只做一件事
+4. Commit message 使用中文，格式 `类型: 简要描述`：
+   - `功能: 新增审计日志模块`
+   - `修复: 目录浏览器无法进入子目录`
+   - `重构: 简化存储目标解密逻辑`
+   - 类型：`功能` / `修复` / `重构` / `文档` / `构建` / `测试`
+5. PR 标题和正文同样使用中文，描述"为什么"和"怎么做"，而非仅仅"做了什么"
+
+## 代码规范
+
+- **Go** — 所有错误必须处理（禁止 `_ = err`），日志使用现有 `zap`，禁止生产路径中出现 `fmt.Println`
+- **TypeScript** — 严格模式，禁止隐式 any，遵循现有 ESLint/Prettier 配置
+- **Commit 粒度** — 每个 commit 一件事，不要把顺手的小修改和功能代码混在一起
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/setup.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/setup.md
@@ -0,0 +1,83 @@
+---
+sidebar_position: 1
+title: 开发环境
+description: 搭建 BackupX 本地开发环境 — 后端、前端、测试。
+---
+
+# 开发环境
+
+**环境要求：** Go ≥ 1.25、Node.js 24 LTS、npm 11 或更高版本。
+
+## 克隆与依赖
+
+```bash
+git clone https://github.com/Awuqing/BackupX.git && cd BackupX
+cd web && npm install && cd ..
+```
+
+## 开发服务
+
+开两个终端分别跑后端和前端：
+
+```bash
+# 终端 1：后端，监听 :8340
+make dev-server
+
+# 终端 2：Vite HMR，监听 :5173
+make dev-web
+```
+
+Vite 配置了 `/api` 代理到 `http://127.0.0.1:8340`，浏览器直接访问 `http://localhost:5173`。
+
+## 测试
+
+```bash
+make test           # 运行 Go + Web 全部测试
+make test-server    # 仅 Go
+make test-web       # 仅 Vitest
+```
+
+## 生产构建
+
+```bash
+make build          # server/bin/backupx + web/dist
+make docker         # Docker 镜像
+make docker-cn      # 国内镜像加速构建
+```
+
+## 技术栈
+
+| 组件 | 技术 |
+|------|------|
+| **后端** | Go · Gin · GORM · SQLite · robfig/cron · rclone |
+| **前端** | React 18 · TypeScript · ArcoDesign · Vite · Zustand · ECharts |
+| **存储** | rclone（70+ 后端）· AWS SDK v2 · Google Drive API v3 |
+| **安全** | JWT · bcrypt · AES-256-GCM |
+
+## 目录结构
+
+```
+BackupX/
+├── server/             # Go 后端
+│   ├── cmd/backupx/    # 入口 + 子命令（agent / backint / reset-password）
+│   ├── internal/
+│   │   ├── agent/      # Agent CLI 逻辑
+│   │   ├── app/        # 装配（repo → service → handler）
+│   │   ├── backup/     # 备份 runner（file / mysql / postgres / sqlite / saphana）
+│   │   ├── backint/    # SAP HANA Backint 协议
+│   │   ├── http/       # HTTP handler + router
+│   │   ├── model/      # GORM 模型
+│   │   ├── repository/ # 数据访问
+│   │   ├── service/    # 业务逻辑
+│   │   └── storage/    # 存储 provider（rclone + 直接 SDK）
+│   └── pkg/            # 通用工具
+├── web/                # React 前端（Vite）
+│   └── src/
+│       ├── components/
+│       ├── pages/
+│       ├── services/
+│       └── types/
+├── docs-site/          # 文档站（Docusaurus）
+├── deploy/             # install.sh / systemd unit / nginx config
+└── Makefile
+```
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/backup-types.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/backup-types.md
@@ -0,0 +1,54 @@
+---
+sidebar_position: 1
+title: 备份类型
+description: 文件、MySQL、PostgreSQL、SQLite 和 SAP HANA — 各自的能力与配置说明。
+---
+
+# 备份类型
+
+BackupX 支持五种内置备份类型，类型决定了用哪个 runner 执行。
+
+当任务路由到远程 Agent 时，源路径和外部工具都会在该 Agent 主机上解析。多存储目标上传仍会逐目标记录结果；只要至少一个目标上传成功，备份记录即为成功，详情中的目标结果表会展示部分失败。
+
+## 文件 / 目录
+
+文件任务提供三种备份模式：
+
+- **全量归档** — 每次生成一份可独立使用的 tar 产物
+- **差异归档** — 只保存相对当前全量基线的变化，并按周期刷新全量基线
+- **CDC 去重仓库** — 按稳定的 512 KiB / 1 MiB / 4 MiB 内容边界切块，将新块合并到不可变的 32 MiB pack，每次运行只新增一份小型快照清单
+
+CDC 仓库会在不同文件、不同快照之间复用相同内容。完整恢复、选择性恢复、完整性校验、下载为 tar、保留策略和垃圾回收都通过仓库索引定位分块。压缩与加密按块执行；启用加密时使用带密钥的块 ID，不暴露明文哈希。
+
+当前仓库索引采用单写者模型，因此 CDC 模式仅在 Master 本机执行。如需保存多份完整仓库，请在任务中直接多选主存储目标。对象级副本复制会被禁用，因为只有快照清单、没有共享 pack 与索引并不是完整备份。
+
+文件任务的通用选项：
+
+- **源路径** 支持多个（UI 中每行一个）
+- **排除模式** 支持 gitignore 风格的通配符
+- 可选跟随符号链接、保留权限
+- 全量与差异模式输出 `.tar`、`.tar.gz` 或 `.tar.zst`
+
+## MySQL
+
+底层使用 `mysqldump`，需要执行任务的主机（Master 或 Agent）的 `$PATH` 中有 `mysqldump`。
+
+- **主机 / 端口 / 用户 / 密码 / 数据库** — 支持多库（英文逗号分隔）
+- 输出：`.sql` 或 `.sql.gz`
+- 默认参数：`--single-transaction --routines --triggers --events`
+
+## PostgreSQL
+
+底层使用 `pg_dump`，连接字段与 MySQL 一致加数据库名。
+
+## SQLite
+
+直接复制数据库文件（使用一致性快照），无需外部工具。
+
+## SAP HANA
+
+支持两种模式 — 详见 [SAP HANA](./sap-hana) 专题页。
+
+## 删除行为
+
+删除备份任务时，BackupX 会从所有存储目标上移除备份产物，但保留备份记录以供审计。删除任务同时拆除其 Cron 定时调度。
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/multi-node.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/multi-node.md
@@ -0,0 +1,227 @@
+---
+sidebar_position: 4
+title: 多节点集群
+description: 通过直连 HTTPS、正向代理或 SSH 堡垒机部署 BackupX Agent。
+---
+
+# 多节点集群
+
+BackupX 使用一个单活 Master 作为控制面，在每台源服务器运行 Agent。所有连接都由 Agent 主动发起：每 15 秒上报心跳，每 5 秒轮询命令，不需要为 Agent 开放入站端口。
+
+## 架构与边界
+
+```text
+[Web 控制台] ────────> [单活 Master + SQLite]
+                              ^
+                              | Agent 主动 HTTP(S) 轮询
+                    +---------+---------+
+                    |         |         |
+                 [Agent B] [Agent C] [Agent D]
+                    |         |         |
+                    +----> 存储目标
+```
+
+- 每个节点有独立 Agent Token，Agent 不持有 Master 的 JWT 密钥或配置加密密钥。
+- Master 超过 45 秒未收到心跳即把节点标记为离线。
+- Master 持久化命令，Agent 领取后在本机执行。
+- 网络存储通常由 Agent 直传；Master 本地存储可显式启用认证流式中转。
+
+:::warning Master 只能单活
+内置 SQLite 不是共享多写数据库。同一个数据目录只能运行一个 Master。控制面高可用应采用主备主机、持久卷快照以及稳定 DNS 或虚拟 IP，故障时确保旧 Master 停止后再启动备用实例。不要让多个 Master 副本同时挂载 `/app/data` 或同一个 `backupx.db`。
+:::
+
+BackupX 会设置 5 秒 SQLite busy timeout，并为命令队列建立查询索引，降低 Agent 并发轮询及任务更新时的锁竞争。数据库应位于本地文件系统或块存储。采用文件复制备份控制面时，先停止 Master 再复制整个数据目录；运行期间不要只复制 `backupx.db`。
+
+## 选择网络路径
+
+| 场景 | Agent Master 地址 | Agent 代理 URL | 说明 |
+| --- | --- | --- | --- |
+| 可路由内网或公网服务 | `https://backup.example.com` | 留空 | 推荐，只需放行出站 TCP 443 |
+| 企业正向代理 | `https://backup.example.com` | `http://proxy.internal:3128` | 支持 HTTP(S) 与 SOCKS5(H) |
+| 通过堡垒机建立 SSH 动态转发 | `https://backup.internal` | `socks5h://127.0.0.1:1080` | 保留 TLS 主机名，并通过隧道解析内网 DNS |
+| SSH 固定本地转发 | `http://127.0.0.1:18340` | 留空 | HTTP 链路位于 SSH 内，只能绑定回环地址 |
+
+私有 PKI 场景请填写目标节点上预置的 PEM CA 证书绝对路径。生产环境不要使用 `--insecure-tls`。
+
+未配置显式代理时，Agent 到 Master 的 HTTP 流量会遵循 `HTTP_PROXY`、`HTTPS_PROXY` 和 `NO_PROXY`。systemd 服务通常不会继承交互式 Shell 环境，因此 systemd 部署应在安装向导或 Agent YAML 中明确配置代理。
+
+## 准备 Master
+
+生成命令前先设置稳定地址：
+
+```yaml title="/etc/backupx/config.yaml"
+server:
+  external_url: "https://backup.example.com"
+  trusted_proxies:
+    - "127.0.0.1"
+    - "::1"
+    # 代理不在本机时，只加入准确的代理 IP 或网段。
+    # - "172.18.0.0/16"
+```
+
+`external_url` 是默认安装入口和 Agent 运行地址。受限节点可以让目标机侧生成的安装 URL 与 Agent 运行地址同时改用隧道或内网地址，浏览器仍继续访问公网地址。
+
+跨不可信网络必须使用 HTTPS。Master 中转上传还要求反向代理关闭请求缓冲并允许大请求体，详见 [Nginx 反向代理](../deployment/nginx)。
+
+Agent 必须直接配置最终 API 地址，不能依赖 HTTP 跳转到 HTTPS。Agent 会主动拒绝重定向，避免认证 Token 被转发到非预期主机。
+
+## 部署 Agent
+
+打开 **节点管理 → 添加节点**：
+
+1. 输入单个节点名，或在批量模式输入最多 50 个名称。
+2. 选择 systemd、Docker 或前台模式，以及架构、Agent Release、命令有效期和下载源。
+3. 选择 **直连** 或 **代理或堡垒机**。受限网络可填写节点专用 Master 地址、代理 URL 或私有 CA 路径。
+4. 把生成的命令复制到目标机，以 root 权限执行。
+
+备份和恢复宿主机文件时推荐 systemd，因为 Agent 需要访问任意本地路径。Docker Agent 只能看到显式挂载的目录；分配文件任务前，应使用只读备份源 volume，并为恢复目标单独配置范围受限的可写挂载。
+
+主命令通过一次性入口下载安装器，并在执行前校验脚本标记。向导会把所选 Agent 地址、显式代理和私有 CA 同时绑定到下载命令与安装后的 Agent 配置。如果目标网络仍无法访问安装入口，使用页面单独展示的嵌入式备用命令。嵌入式命令包含长期节点 Token，必须按密钥管理。
+
+安装器会：
+
+1. 检测 `linux/amd64` 或 `linux/arm64`。
+2. 配置显式代理时始终通过该代理下载 Release；否则使用主机的正常直连或环境代理路径，并在该版本提供 SHA-256 旁车文件时进行校验。
+3. 以 `0600` 权限写入 `/etc/backupx-agent/config.yaml` 和 `/etc/backupx-agent/agent.token`。
+4. 不把 Token 写入 systemd unit 或 Docker 环境元数据。
+5. 启动 Agent，并在 30 秒内轮询 `/api/v1/agent/self`。
+6. 节点未上线时返回非零状态，并输出 systemd 或 Docker 排查命令。
+
+旧版本如果没有校验文件，会显示兼容性警告后继续安装；新版本应始终发布并校验该文件。
+
+### systemd 安装结果
+
+```yaml title="/etc/backupx-agent/config.yaml"
+master: "https://backup.example.com"
+tokenFile: "/etc/backupx-agent/agent.token"
+heartbeatInterval: "15s"
+pollInterval: "5s"
+tempDir: "/var/lib/backupx-agent/tmp"
+proxyUrl: ""
+caCertFile: ""
+```
+
+```ini title="/etc/systemd/system/backupx-agent.service"
+[Unit]
+Description=BackupX Agent
+After=network-online.target
+Wants=network-online.target
+StartLimitIntervalSec=300
+StartLimitBurst=10
+
+[Service]
+Type=simple
+ExecStart=/opt/backupx-agent/backupx agent --config /etc/backupx-agent/config.yaml
+Restart=on-failure
+RestartSec=10s
+TimeoutStopSec=30s
+UMask=0077
+LimitNOFILE=65535
+
+[Install]
+WantedBy=multi-user.target
+```
+
+Agent 以 root 运行，因为文件备份和恢复路径可能属于任意系统用户。应严格限制谁能创建任务，以及谁能修改 root 所有的 Agent 配置。
+
+## SSH 堡垒机示例
+
+内网 Master 使用 HTTPS 时优先采用 SOCKS 隧道，这样 Master 主机名与证书校验保持不变。
+
+先创建专用 SSH 账户，预置私钥和已经人工核对指纹的 `known_hosts`，再创建：
+
+```sshconfig title="/etc/backupx-agent/ssh_config"
+Host backupx-bastion
+    HostName bastion.example.com
+    User backupx-tunnel
+    IdentityFile /etc/backupx-agent/tunnel_ed25519
+    IdentitiesOnly yes
+    BatchMode yes
+    UserKnownHostsFile /etc/backupx-agent/known_hosts
+    StrictHostKeyChecking yes
+    DynamicForward 127.0.0.1:1080
+    ExitOnForwardFailure yes
+    ServerAliveInterval 30
+    ServerAliveCountMax 3
+```
+
+```ini title="/etc/systemd/system/backupx-agent-tunnel.service"
+[Unit]
+Description=BackupX Agent SSH tunnel
+After=network-online.target
+Wants=network-online.target
+Before=backupx-agent.service
+
+[Service]
+Type=simple
+ExecStart=/usr/bin/ssh -NT -F /etc/backupx-agent/ssh_config backupx-bastion
+Restart=always
+RestartSec=5s
+
+[Install]
+WantedBy=multi-user.target
+```
+
+再添加依赖覆写，让隧道不可用时 Agent 关闭失败而不是绕过堡垒机：
+
+```ini title="/etc/systemd/system/backupx-agent.service.d/tunnel.conf"
+[Unit]
+Requires=backupx-agent-tunnel.service
+After=backupx-agent-tunnel.service
+```
+
+```bash
+sudo systemctl daemon-reload
+sudo systemctl enable --now backupx-agent-tunnel backupx-agent
+```
+
+在安装向导中保留内网 HTTPS Master 地址，把代理填写为 `socks5h://127.0.0.1:1080`。启用服务前必须通过独立渠道核对堡垒机 Host Key。
+
+## 集中存储数据路径
+
+| 目标 | 数据路径 |
+| --- | --- |
+| S3、WebDAV、FTP、云盘或其他网络后端 | Agent 直接流式上传到目标 |
+| 启用 **远程备份经 Master 中转** 的 `local_disk` | Agent 通过认证 Master API 流式上传，Master 写入本地挂载 |
+
+中转不会在 Master 上额外创建一份完整临时副本，恢复时走反向流式通道。Nginx 必须关闭请求缓冲，才能保持该特性。
+
+## 运维
+
+```bash
+sudo systemctl status backupx-agent
+sudo journalctl -u backupx-agent -n 100 --no-pager
+sudo /opt/backupx-agent/backupx agent --config /etc/backupx-agent/config.yaml
+```
+
+从节点操作菜单轮换 Token 后，在 24 小时重叠窗口内更新 `/etc/backupx-agent/agent.token` 并重启服务。
+
+建议监控：
+
+- `backupx_agent_command_queue_depth`
+- `backupx_agent_command_running`
+- `backupx_agent_command_timeout_total`
+- `backupx_node_online`
+
+## CLI 参考
+
+```text
+backupx agent --help
+  -master string       Master 地址
+  -token string        Agent Token
+  -token-file string   从文件读取 Agent Token
+  -config string       YAML 配置文件路径
+  -temp-dir string     本地临时目录
+  -proxy-url string    HTTP(S) 或 SOCKS5(H) 代理
+  -ca-cert string      用于校验 Master 的 PEM CA 证书
+  -insecure-tls        跳过 TLS 校验（仅测试）
+```
+
+环境变量：`BACKUPX_AGENT_MASTER`、`BACKUPX_AGENT_TOKEN`、`BACKUPX_AGENT_TOKEN_FILE`、`BACKUPX_AGENT_HEARTBEAT`、`BACKUPX_AGENT_POLL`、`BACKUPX_AGENT_TEMP_DIR`、`BACKUPX_AGENT_PROXY_URL`、`BACKUPX_AGENT_CA_CERT_FILE`、`BACKUPX_AGENT_INSECURE_TLS`。
+
+## 已知限制
+
+- Master 使用内置 SQLite，只支持单活。
+- 加密备份仅支持 Master 本机执行，因为 Agent 不持有 Master 加密密钥。
+- 远程目录浏览是同步队列 RPC，默认超时 15 秒。
+- Agent 领取后长期不更新的命令会由 Master 超时监控处理。
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/notifications.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/notifications.md
@@ -0,0 +1,49 @@
+---
+sidebar_position: 5
+title: 通知
+description: 备份成功或失败时通过邮件、Webhook、Telegram 推送通知。
+---
+
+# 通知
+
+BackupX 支持三种通知渠道，可为每个渠道单独配置成功/失败事件是否推送。
+
+## 邮件（SMTP）
+
+| 字段 | 说明 |
+|------|------|
+| SMTP 主机 / 端口 | 如 `smtp.gmail.com:587` |
+| 用户名 / 密码 | 建议使用专用应用密码 |
+| 发件人地址 | 邮件 `From:` 头 |
+| 收件人列表 | 英文逗号分隔 |
+| 使用 TLS / StartTLS | 按 SMTP 提供方要求选择 |
+
+## Webhook
+
+向任意 URL 发送 JSON POST，请求体结构：
+
+```json
+{
+  "event": "backup_result",
+  "task": {"id": 1, "name": "web-files", "type": "file"},
+  "record": {"id": 42, "status": "success", "fileSize": 1048576, "durationSeconds": 12},
+  "error": ""
+}
+```
+
+适合自定义场景：Slack incoming webhook、PagerDuty、自建 API 等。
+
+## Telegram
+
+| 字段 | 说明 |
+|------|------|
+| Bot Token | 在 [@BotFather](https://t.me/BotFather) 创建 |
+| Chat ID | 数字型，可通过 `/start` 后调 Bot 的 `getUpdates` 获取 |
+
+## 事件规则
+
+每个通知配置可以指定触发范围：
+
+- **仅成功** — 正常运行时静默
+- **仅失败** — 适合高噪敏感通道
+- **全部** — 初始化配置时用于验证链路
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/sap-hana.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/sap-hana.md
@@ -0,0 +1,79 @@
+---
+sidebar_position: 3
+title: SAP HANA 支持
+description: 两种 SAP HANA 备份模式 — 控制台托管的 hdbsql Runner 和原生 Backint 协议代理。
+---
+
+# SAP HANA 支持
+
+BackupX 提供两种 SAP HANA 备份模式，按实际运维流程选择。
+
+## 模式一：hdbsql Runner（控制台托管）
+
+通过 Web 控制台创建 SAP HANA 备份任务，后端调用 `hdbsql` 执行备份。适合希望 BackupX 来管理调度的场景。
+
+**源配置支持：**
+
+| 字段 | 可选值 | 说明 |
+|------|--------|------|
+| 备份类型 | `data` / `log` | 数据备份或日志备份 |
+| 备份级别 | `full` / `incremental` / `differential` | 日志备份时自动禁用 |
+| 并行通道数 | `1 ~ 32` | 多路径 SQL（`BACKUP DATA USING FILE ('c1', 'c2', ...)`） |
+| 失败重试次数 | `1 ~ 10` | 指数退避（`5s × 尝试次数²`） |
+| 实例编号 | 可选 | 从端口推断或手动指定 |
+
+## 模式二：Backint 协议代理（HANA 原生接口）
+
+BackupX 内置 Backint Agent，SAP HANA 通过原生 `BACKUP DATA USING BACKINT` 语法调用，数据自动路由到任意 BackupX 存储目标（S3 / OSS / COS / WebDAV / 70+ 后端）。
+
+### 1. 参数文件
+
+```ini title="/opt/backupx/backint_params.ini"
+#STORAGE_TYPE = s3
+#STORAGE_CONFIG_JSON = /opt/backupx/storage.json
+#PARALLEL_FACTOR = 4
+#COMPRESS = true
+#KEY_PREFIX = hana-backup
+#CATALOG_DB = /opt/backupx/backint_catalog.db
+#LOG_FILE = /var/log/backupx/backint.log
+```
+
+### 2. 存储配置（与存储目标 schema 相同）
+
+```json title="/opt/backupx/storage.json"
+{
+  "endpoint": "https://s3.amazonaws.com",
+  "region": "us-east-1",
+  "bucket": "hana-prod",
+  "accessKeyId": "AKIA...",
+  "secretAccessKey": "..."
+}
+```
+
+### 3. 创建 hdbbackint 软链接
+
+```bash
+ln -s /opt/backupx/backupx /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint
+```
+
+### 4. 在 HANA `global.ini` 中启用
+
+```ini
+[backup]
+data_backup_using_backint = true
+catalog_backup_using_backint = true
+log_backup_using_backint = true
+data_backup_parameter_file = /opt/backupx/backint_params.ini
+log_backup_parameter_file = /opt/backupx/backint_params.ini
+```
+
+### 5. CLI 手动调用（用于排查）
+
+```bash
+backupx backint -f backup  -i input.txt -o output.txt -p backint_params.ini
+backupx backint -f restore -i input.txt -o output.txt -p backint_params.ini
+backupx backint -f inquire -i input.txt -o output.txt -p backint_params.ini
+backupx backint -f delete  -i input.txt -o output.txt -p backint_params.ini
+```
+
+Backint Agent 使用本地 SQLite 维护 `EBID ↔ 对象键` 目录，所有操作遵循 SAP HANA Backint 协议（`#PIPE` / `#SAVED` / `#RESTORED` / `#BACKUP` / `#NOTFOUND` / `#DELETED` / `#ERROR`）。
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/storage-backends.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/storage-backends.md
@@ -0,0 +1,40 @@
+---
+sidebar_position: 2
+title: 存储后端
+description: 70+ 存储后端 — 内置云服务商 + 任意 rclone 后端。
+---
+
+# 存储后端
+
+BackupX 的目标是接入任何你想放置备份文件的地方。
+
+## 内置后端
+
+| 类型 | 必填字段 |
+|------|---------|
+| **阿里云 OSS** | Region + AccessKey ID/Secret + Bucket（endpoint 自动组装） |
+| **腾讯云 COS** | Region + SecretId/SecretKey + Bucket（格式 `name-appid`） |
+| **七牛云 Kodo** | Region + AccessKey/SecretKey + Bucket |
+| **S3 兼容** | Endpoint + AccessKey + Bucket |
+| **Google Drive** | Client ID/Secret + OAuth 授权 |
+| **WebDAV** | 地址 + 用户名/密码 |
+| **FTP / FTPS** | 主机 + 端口 + 用户名/密码 |
+| **本地磁盘** | 目标目录（绝对路径）+ 可选的远程 Agent 经 Master 中转 |
+
+新建本地磁盘目标默认开启 **远程备份经 Master 中转**。开启时，配置目录属于 Master，挂载到 Master 的存储服务器可集中接收多台源 Agent 的备份；如果该路径本就属于各 Agent，请关闭此选项。升级前已有目标保持原来的 Agent 本机落盘行为，只有显式开启后才会切换。
+
+## Rclone 后端
+
+每一种 [rclone 后端](https://rclone.org/overview/) 都作为一等公民暴露 — SFTP、Azure Blob、Dropbox、OneDrive、Backblaze B2、Wasabi、pCloud、HDFS 等。
+
+- 表单字段分为 **必填** 和 **高级**（高级默认折叠）
+- 校验与连接测试复用 rclone 自带的探测
+
+## 一个任务多个目标
+
+一个备份任务可以并行上传到多个存储目标。每个目标获得相同的产物，每目标的状态会单独记录：
+
+- 成功：storage_path + 文件大小
+- 失败：错误信息
+
+如果任一目标在重试后仍失败，整条记录的状态为 `failed`，但已成功的目标产物会被保留（不回滚）。
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/getting-started/installation.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/getting-started/installation.md
@@ -0,0 +1,74 @@
+---
+sidebar_position: 1
+title: 安装
+description: 通过 Docker、预编译包或源码安装 BackupX。
+---
+
+# 安装
+
+BackupX 以单个静态二进制发布。三种安装方式，按实际环境选一种。
+
+## Docker（推荐）
+
+下载仓库中的正式加固 Compose 文件并启动：
+
+```bash
+curl -fLO https://raw.githubusercontent.com/Awuqing/BackupX/main/docker-compose.yml
+docker compose up -d
+docker compose ps
+```
+
+该 Compose 配置启用 init 与优雅停止，持久化 `/app/data`，以非特权用户运行应用，删除不必要能力，并通过 `/ready` 检查健康。[`awuqing/backupx`](https://hub.docker.com/r/awuqing/backupx) 镜像支持 `linux/amd64` 和 `linux/arm64`。
+
+生产环境应创建受保护的 `.env`，固定 Release 而不是依赖 `latest`：
+
+```dotenv
+BACKUPX_IMAGE=awuqing/backupx:vX.Y.Z
+BACKUPX_BIND_ADDRESS=127.0.0.1
+TZ=Asia/Shanghai
+```
+
+反向代理位于同一主机时使用回环绑定；需要直接访问时，应选择明确的监听接口并配置防火墙。宿主机备份源应只读挂载，或在源主机部署 Agent。完整配置见 [Docker 部署](../deployment/docker)。
+
+## 预编译包（裸机）
+
+从 [Releases 页面](https://github.com/Awuqing/BackupX/releases) 下载对应平台的压缩包，执行安装脚本：
+
+```bash
+sha256sum -c backupx-v*-linux-amd64.tar.gz.sha256
+tar xzf backupx-v*-linux-amd64.tar.gz && cd backupx-*
+sudo ./install.sh        # 创建系统用户、安装到 /opt/backupx、配置 systemd
+```
+
+安装脚本会自动：
+
+1. 创建 `backupx` 系统用户
+2. 安装二进制到 `/opt/backupx/bin/backupx`，并把 Web 控制台安装到 `/opt/backupx/web`
+3. 生成 `/etc/backupx/config.yaml`（含安全默认值）
+4. 注册并启用 `backupx.service` systemd 单元
+5. 默认不修改 Nginx；只有显式设置 `INSTALL_NGINX=1` 时才安装模板
+6. 等待 `/api/auth/setup/status` 就绪；启动失败时输出 systemd 诊断并返回非零状态
+
+## 从源码构建
+
+依赖：Go ≥ 1.25、Node.js 24 LTS、npm 11 或更高版本。
+
+```bash
+git clone https://github.com/Awuqing/BackupX.git && cd BackupX
+make build
+sudo ./deploy/install.sh
+```
+
+`make build` 完成后，二进制位于 `server/bin/backupx`，构建好的 Web UI 位于 `web/dist/`。
+安装脚本会直接使用这两个路径，不需要 Docker 运行时。如果已有配置修改了默认端口，可覆盖就绪检查地址，例如：`sudo HEALTH_URL=http://127.0.0.1:9000/api/auth/setup/status ./deploy/install.sh`。
+
+自动安装兜底虚拟主机可能接管现有站点，因此 Nginx 模板改为显式启用。请先审核 `deploy/nginx.conf`，确认适合当前主机后再执行 `sudo INSTALL_NGINX=1 ./deploy/install.sh`。
+
+## 验证安装
+
+```bash
+/opt/backupx/bin/backupx --version
+curl -fsS http://127.0.0.1:8340/api/auth/setup/status
+```
+
+打开浏览器访问 `http://your-server:8340`，可在右上角选择 **中文** 或 **English**。全新数据库会显示“系统初始化 / System setup”，在这里创建首个管理员用户名和密码。如果没有出现初始化表单，请先重试上面的状态接口，不要直接尝试登录。
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/getting-started/quick-start.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/getting-started/quick-start.md
@@ -0,0 +1,62 @@
+---
+sidebar_position: 2
+title: 快速开始
+description: 部署 BackupX、添加存储目标、创建第一个备份任务。
+---
+
+# 快速开始
+
+完成 [安装](./installation) 后，花五分钟跑通第一个备份。
+
+## 1. 打开控制台
+
+浏览器访问 `http://your-server:8340`。首次打开会引导创建管理员账户。
+
+## 2. 添加存储目标
+
+进入 **存储目标 → 添加**，选择类型并填写凭证：
+
+| 类型 | 需要填写 |
+|------|---------|
+| 阿里云 OSS | Region + AccessKey ID/Secret + Bucket |
+| 腾讯云 COS | Region + SecretId/SecretKey + Bucket（格式 `name-appid`） |
+| 七牛云 Kodo | Region + AccessKey/SecretKey + Bucket |
+| S3 兼容 | Endpoint + AccessKey + Bucket |
+| Google Drive | Client ID/Secret → 点击「授权」完成 OAuth |
+| WebDAV | 服务器地址 + 用户名/密码 |
+| FTP | 主机 + 端口 + 用户名/密码 |
+| 本地磁盘 | 目标目录路径 |
+| SFTP / Azure / Dropbox / OneDrive 等 | 选择对应类型后填写必填项，高级配置默认折叠 |
+
+:::tip
+国内云厂商只需填 Region 和 AccessKey，系统自动组装 Endpoint。Rclone 类型的配置项按"必填 / 可选"分层展示，高级选项默认折叠。
+:::
+
+添加后点击 **测试连接** 确认配置正确。
+
+## 3. 创建备份任务
+
+进入 **备份任务 → 新建**，三步完成：
+
+1. **基础信息** — 任务名称、备份类型、Cron 表达式（留空则仅手动执行）
+2. **源配置** — 文件备份选择源路径（支持多个），数据库备份填写连接信息
+3. **存储与策略** — 选择存储目标（支持多个）、压缩策略、保留天数、是否加密
+
+对于路由到 Agent 的任务，加密必须关闭，因为 Agent 不会拿到 Master 的加密密钥。BackupX 会在创建/更新阶段拒绝开启加密的远程节点或节点池任务。
+
+保存后可点击 **立即执行** 测试，**备份记录** 页面实时查看执行日志。
+
+:::note
+删除备份任务时会自动清理远端存储上的备份文件，但保留备份记录以供审计追溯。
+:::
+
+## 4. 配置通知（可选）
+
+**通知配置** 页面支持邮件、Webhook、Telegram 三种方式，可分别配置成功/失败时是否推送。
+
+## 继续阅读
+
+- 了解 [备份类型](/docs/features/backup-types) 和 [存储后端](/docs/features/storage-backends)
+- 上线生产前阅读[安全加固](/docs/operations/security)、[监控与告警](/docs/operations/monitoring)和[升级与恢复](/docs/operations/upgrade-recovery)
+- 使用 SAP HANA？参考 [SAP HANA 支持](/docs/features/sap-hana)
+- 管理多台服务器？参考 [多节点集群](/docs/features/multi-node)
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/intro.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/intro.md
@@ -0,0 +1,42 @@
+---
+id: intro
+slug: /intro
+sidebar_position: 1
+title: 项目简介
+description: BackupX——自托管服务器备份管理平台概览。
+---
+
+# BackupX
+
+**BackupX** 是一款自托管的服务器备份管理平台：一个二进制，一条命令，管好所有服务器的所有备份。
+
+- **单二进制 + 内嵌 SQLite** — 不依赖外部数据库或编排器
+- **文件、数据库、SAP HANA** — 统一管理，可视化调度
+- **70+ 存储后端** — 阿里云 OSS、腾讯云 COS、七牛、S3、Google Drive、WebDAV、FTP，以及通过 rclone 接入的 SFTP / Azure Blob / Dropbox / OneDrive 等数十种
+- **多节点集群** — Master-Agent 模式跨服务器管理备份，Agent 在本地执行并直接上传到存储
+- **默认安全** — JWT 认证、bcrypt、AES-256-GCM 加密配置、可选备份加密、完整审计日志
+
+## 架构概览
+
+```
+[Web 控制台] ─── JWT ──→ [Master (backupx)]
+                             │
+                             │ Agent 主动 HTTP 轮询（Token 认证）
+                             ▼
+                         [Agent (backupx agent)]
+                             │
+                             ▼
+                       [70+ 存储后端]
+```
+
+路由到本机的任务在 Master 进程内直接执行；派到远程节点的任务通过命令队列下发，由 Agent 在本地执行。Agent 只发起出站 HTTP 连接 — 不需要任何反向连通性。
+
+## 下一步
+
+- **第一次使用 BackupX？** 先看 [快速开始](/docs/getting-started/quick-start)
+- **生产部署？** 参考 [部署指南](/docs/deployment/docker)
+- **规划升级或灾备？** 按[升级与恢复](/docs/operations/upgrade-recovery)执行
+- **生产运维？** 先阅读[安全加固](/docs/operations/security)与[监控和告警](/docs/operations/monitoring)
+- **SAP HANA 用户？** 支持 `hdbsql` Runner 和原生 Backint 两种模式 — 详见 [SAP HANA](/docs/features/sap-hana)
+- **管理多台服务器？** 参考 [多节点集群](/docs/features/multi-node)
+- **程序化集成？** 参考 [API 参考](/docs/reference/api)
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/operations/monitoring.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/operations/monitoring.md
@@ -0,0 +1,149 @@
+---
+sidebar_position: 3
+title: 监控与告警
+description: 健康探针、Prometheus 指标、初始告警规则和运维验证。
+---
+
+# 监控与告警
+
+BackupX 提供低开销健康端点和独立 Prometheus Registry。监控既要覆盖控制面，也要覆盖备份、恢复、验证和复制的实际结果。
+
+## 探针
+
+| 端点 | 含义 | 预期响应 |
+| --- | --- | --- |
+| `/health` | 存活：HTTP 进程可响应 | HTTP 200，`status: live` |
+| `/ready` | 就绪：进程可访问 SQLite | 正常为 HTTP 200 与 `status: ready`；数据库故障为 HTTP 503 |
+| `/api/health` | 带 API 前缀的存活别名 | 与 `/health` 相同 |
+| `/api/ready` | 带 API 前缀的就绪别名 | 与 `/ready` 相同 |
+| `/metrics` | Prometheus 指标 | 指标启用时为 HTTP 200 |
+
+`/health` 用作 liveness，`/ready` 用作 readiness 或负载均衡流量判断。外部存储暂时不可用不应直接触发进程重启，应通过任务和存储目标告警处理。
+
+~~~bash
+curl -fsS http://127.0.0.1:8340/health
+curl -fsS http://127.0.0.1:8340/ready
+curl -fsS http://127.0.0.1:8340/metrics | head
+~~~
+
+这些端点不需要认证，只允许编排器和监控网段访问。
+
+## Prometheus 抓取
+
+~~~yaml
+scrape_configs:
+  - job_name: backupx
+    scheme: https
+    metrics_path: /metrics
+    static_configs:
+      - targets: [backup.example.com]
+~~~
+
+Nginx 终止 TLS 时，应只放行 Prometheus 源地址访问 `/metrics`。内部采集器每 30 秒刷新存储、节点、命令队列和 SLA Gauge。
+
+## BackupX 指标
+
+| 指标 | 类型 | 标签 | 用途 |
+| --- | --- | --- | --- |
+| `backupx_app_info` | gauge | `version` | 当前版本元数据 |
+| `backupx_task_run_total` | counter | `status`、`task_type` | 备份结果 |
+| `backupx_task_run_duration_seconds` | histogram | `task_type` | 备份耗时分布 |
+| `backupx_task_bytes_total` | counter | `task_type` | 备份产出字节数 |
+| `backupx_task_running` | gauge | 无 | 当前备份并发 |
+| `backupx_storage_used_bytes` | gauge | `target_name`、`target_type` | 按目标记录的使用量 |
+| `backupx_node_online` | gauge | `node_name`、`role` | 节点在线状态，1 或 0 |
+| `backupx_agent_command_queue_depth` | gauge | `node_name`、`role` | 待处理与已派发命令 |
+| `backupx_agent_command_running` | gauge | `node_name`、`role` | Agent 长任务数 |
+| `backupx_agent_command_timeout_total` | gauge | `node_name`、`role` | 超时命令数快照 |
+| `backupx_verify_run_total` | counter | `status` | 验证结果 |
+| `backupx_restore_run_total` | counter | `status` | 恢复结果 |
+| `backupx_replication_run_total` | counter | `status` | 复制结果 |
+| `backupx_sla_breach_tasks` | gauge | 无 | 超出已配置 RPO 的启用任务数 |
+
+同一端点还注册了标准 Go Runtime 与进程指标。
+
+## 初始告警规则
+
+应根据各环境计划与 RPO 调整窗口和阈值：
+
+~~~yaml
+groups:
+  - name: backupx
+    rules:
+      - alert: BackupXTargetDown
+        expr: up{job="backupx"} == 0
+        for: 2m
+        labels:
+          severity: critical
+        annotations:
+          summary: BackupX metrics endpoint is unreachable
+
+      - alert: BackupXNotReady
+        expr: probe_success{job="backupx-ready"} == 0
+        for: 2m
+        labels:
+          severity: critical
+        annotations:
+          summary: BackupX readiness check is failing
+
+      - alert: BackupXBackupFailure
+        expr: sum(increase(backupx_task_run_total{status="failed"}[15m])) > 0
+        labels:
+          severity: warning
+        annotations:
+          summary: A BackupX backup failed
+
+      - alert: BackupXSLABreach
+        expr: backupx_sla_breach_tasks > 0
+        for: 5m
+        labels:
+          severity: critical
+        annotations:
+          summary: One or more backup tasks are outside RPO
+
+      - alert: BackupXAgentOffline
+        expr: backupx_node_online{role="agent"} == 0
+        for: 2m
+        labels:
+          severity: warning
+        annotations:
+          summary: BackupX Agent is offline
+
+      - alert: BackupXAgentQueueBacklog
+        expr: backupx_agent_command_queue_depth > 20
+        for: 10m
+        labels:
+          severity: warning
+        annotations:
+          summary: BackupX Agent command queue is growing
+~~~
+
+`BackupXNotReady` 示例假定存在名为 `backupx-ready` 的 Blackbox 探针任务。未部署 Blackbox Exporter 时，应改用负载均衡或编排器的 readiness 信号。
+
+## 运维仪表盘
+
+建议同时展示：
+
+- 按任务类型统计成功率与失败率。
+- P50、P95、最大执行时长及其与备份窗口的关系。
+- 产出字节数与预期数据变化率。
+- 当前任务数与 `backup.max_concurrent`。
+- 离线 Agent、队列深度、运行命令和超时数变化。
+- 存储增长、提供商剩余容量和保留策略清理。
+- SLA 违约数及关键任务最近成功备份时间。
+- 验证、恢复和复制成功率。
+
+Prometheus 存储使用量来自 BackupX 记录元数据，不一定等同于提供商计费容量，应另行监控提供商配额和文件系统剩余空间。
+
+## 部署后验证
+
+安装、升级、代理变更或恢复后：
+
+1. 分别从本机和公开代理检查存活与就绪。
+2. 确认 Prometheus 只看到一个活动 Master，并带有预期版本标签。
+3. 确认所有预期 Agent 的 `backupx_node_online == 1`。
+4. 执行小型备份并确认成功 Counter 增长。
+5. 执行验证或隔离恢复并确认对应 Counter 增长。
+6. 触发测试通知并验证告警投递链路。
+
+探针或指标异常时继续参考[故障排查](./troubleshooting)。
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/operations/security.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/operations/security.md
@@ -0,0 +1,102 @@
+---
+sidebar_position: 2
+title: 安全加固
+description: 生产环境的网络暴露、角色、密钥、Agent、容器和公开端点控制。
+---
+
+# 安全加固
+
+BackupX 统一接触源文件、数据库凭据、存储凭据和恢复目标，应把 Master 作为安全敏感的控制面部署，而不是普通的公开 Web 应用。
+
+## 推荐暴露模型
+
+| 组件 | 入站访问 | 出站访问 |
+| --- | --- | --- |
+| Master | 管理员与 Agent 的 HTTPS；指标只对监控网段开放 | 存储提供商、通知端点、版本检查 |
+| Agent | 不需要入站端口 | Master HTTPS 与分配的存储目标 |
+| SQLite 数据 | 仅本地或块存储文件系统 | 无 |
+
+反向代理与 Docker 位于同一主机时，把 Docker 绑定到 `127.0.0.1`：
+
+~~~dotenv
+BACKUPX_BIND_ADDRESS=127.0.0.1
+~~~
+
+裸机仅允许本机代理访问时，把 `server.host` 设置为回环地址；其他情况应使用主机或网络防火墙限制 TCP 8340。
+
+## TLS 与反向代理
+
+- 所有不可信网络段都使用 HTTPS。
+- `server.external_url` 设置为 Agent 可访问的稳定地址。
+- `server.trusted_proxies` 只加入准确代理 IP 或网段，禁止信任 `0.0.0.0/0`。
+- Agent 使用最终 HTTPS 地址，不要依赖重定向。
+- 私有 PKI 应向 Agent 下发 PEM CA，并配置 `caCertFile` 或 `--ca-cert`。
+- `--insecure-tls` 只用于临时测试。
+- Master 中转上传和 SSE 日志需要关闭 Nginx 请求与响应缓冲。
+
+必须经过 SSH 堡垒机时，将隧道绑定到回环地址，严格校验主机密钥，使用专用账号与密钥，并让 Agent 服务依赖隧道。详见[多节点集群](../features/multi-node)。
+
+## 角色与 API Key
+
+| 角色 | 预期权限 |
+| --- | --- |
+| `viewer` | 读取仪表盘、任务、记录、报表与审计数据；不能浏览节点文件系统或修改资源 |
+| `operator` | viewer 权限，加上任务、存储、通知、备份、恢复、验证和文件浏览操作 |
+| `admin` | operator 权限，加上用户、API Key、设置、节点生命周期、安装令牌和 Token 轮换 |
+
+为每位人员创建独立命名账号，不共享初始管理员。特权账号应启用双因素认证或通行密钥，并定期检查可信设备与恢复码。
+
+用户 JWT 是无状态令牌。登出只会删除客户端副本，无法撤销已被复制到其他位置的 Token。应把 `security.jwt_expire` 设置为可接受的最短时长，保护 Bearer Token；必须使全部会话失效时轮换 JWT 密钥。
+
+API Key 与交互式用户使用相同的角色检查。明文只在创建时显示一次，数据库只保存带密钥哈希。自动化应使用最低必要角色、设置有效期、保存在密钥管理系统，并及时撤销闲置 Key。监控不应使用管理员 Key。
+
+## 保护控制面密钥
+
+- `/etc/backupx/config.yaml` 应为 `root:backupx`、模式 `0640`，数据目录只允许服务账号访问。
+- `jwt_secret` 和 `encryption_key` 留空时，自动生成值会写入 SQLite 数据库，因此必须备份完整数据目录。
+- 加密密钥丢失或替换后，已有存储凭据将无法解密。
+- 数据库包含密码哈希、配置密钥、Agent Token、API Key 哈希、可信设备状态和审计数据。快照应加密并设置保留策略。
+- 不要把 Token 写入 shell 历史、Issue、截图或支持包。
+
+每个节点有独立的长期 Agent Token。systemd 安装器把它保存到 `/etc/backupx-agent/agent.token`，模式为 `0600`。人员变更、主机入侵或意外泄露后应轮换 Token，在重叠窗口内更新文件并重启 Agent。
+
+一次性安装 URL 有效期为 5 分钟至 24 小时，使用后立即失效。URL 与内嵌备用命令都应视为秘密，因为生成的安装材料会配置长期节点 Token。
+
+## 容器与主机权限
+
+正式 Compose 会删除全部能力，只添加旧数据卷所有权迁移与切换到非特权 `backupx` 用户所需的能力。保留 `no-new-privileges`，不要挂载 Docker Socket。
+
+备份源应只读挂载；只有恢复目标确实需要时才添加独立、范围明确的可写挂载。需要高权限文件访问时，优先部署宿主机 Agent，而不是让 Master 容器以 root 运行。
+
+systemd Master 以 `backupx` 运行。Agent 通常以 root 运行，因为它可能备份或恢复属于任意系统用户的文件。应限制任务创建权限并保护 root 所有的 Agent 配置。
+
+## 公开端点
+
+以下端点有意不使用 BackupX JWT 或 API Key 认证：
+
+- `/health` 与 `/api/health`
+- `/ready` 与 `/api/ready`
+- `/metrics`
+- 一次性 `/install/:token` 与 `/api/install/:token` 路由
+
+健康响应包含状态、版本、运行时间、时间戳和就绪检查；就绪失败时可能带有数据库错误细节。`/metrics` 还会包含节点与存储目标标签。应在防火墙或反向代理只允许监控网段访问探针与指标，不要缓存或记录完整安装令牌 URL。
+
+## 备份加密边界
+
+加密备份任务只能在 Master 执行，因为远程 Agent 不会收到 Master 加密密钥。不要通过复制 Master 密钥到 Agent 来绕过这个边界。Agent 任务需要加密时，应根据要求使用传输层加密和存储提供商的服务端加密。
+
+每次调整密钥管理后都应验证加密备份恢复。缺少密钥的备份不可恢复。
+
+## 审计与事故响应
+
+BackupX 会记录特权操作，并可把签名审计事件转发到外部 Webhook。高价值审计记录应发送到独立管理的 SIEM 或追加写存储，避免受损 Master 删除唯一副本。
+
+怀疑入侵时：
+
+1. 隔离 Master，但不要删除证据。
+2. 撤销泄露的 API Key，轮换受影响的 Agent Token 与存储凭据。
+3. JWT 与加密密钥只能按计划迁移；直接更换加密密钥会使已保存加密配置失效。
+4. 审查用户、可信设备、API Key、节点、设置、恢复与删除事件。
+5. 无法确认完整性时，从已知可信的控制面快照恢复。
+
+应用与数据库配套恢复流程见[升级与恢复](./upgrade-recovery)。
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/operations/troubleshooting.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/operations/troubleshooting.md
@@ -0,0 +1,160 @@
+---
+sidebar_position: 4
+title: 故障排查
+description: Master、反向代理、Agent、备份工具和 SQLite 的安全诊断顺序。
+---
+
+# 故障排查
+
+从最先失败的边界开始并保留证据。在确认原因前，不要删除数据库、重建卷、一次性轮换所有 Token 或重新安装。
+
+## 快速分流
+
+| 现象 | 首项检查 | 可能边界 |
+| --- | --- | --- |
+| Web 控制台不可用 | 本机 `/health`，再检查代理 `/health` | 进程、监听、防火墙、代理或静态文件 |
+| `/health` 正常但 `/ready` 为 503 | 服务日志、数据库路径、磁盘、权限 | SQLite 或数据文件系统 |
+| 登录循环或客户端 IP 错误 | 转发头与 `trusted_proxies` | 反向代理信任 |
+| 实时日志停止更新 | Nginx 响应缓冲与超时 | SSE 代理路径 |
+| 中转上传停滞或代理磁盘占满 | 请求缓冲与 Body 上限 | 反向代理 |
+| Agent 离线 | Agent 日志、最终 Master URL、代理、DNS、CA | Agent 到 Master 网络 |
+| 备份启动后失败 | 记录日志、源路径、数据库原生工具 | Runner 或权限 |
+| 恢复失败 | 记录日志、目标挂载与写权限 | 存储读取或目标权限 |
+
+## 无敏感信息的状态采集
+
+Docker Master：
+
+~~~bash
+docker compose ps
+docker compose logs --tail=200 backupx
+curl -i http://127.0.0.1:8340/health
+curl -i http://127.0.0.1:8340/ready
+~~~
+
+裸机 Master：
+
+~~~bash
+sudo systemctl status backupx --no-pager
+sudo journalctl -u backupx -n 200 --no-pager
+sudo ss -lntp | grep 8340
+curl -i http://127.0.0.1:8340/health
+curl -i http://127.0.0.1:8340/ready
+~~~
+
+systemd Agent：
+
+~~~bash
+sudo systemctl status backupx-agent --no-pager
+sudo journalctl -u backupx-agent -n 200 --no-pager
+sudo systemctl status backupx-agent-tunnel --no-pager
+~~~
+
+最后一条只适用于堡垒机部署。共享输出前，移除 Authorization 头、API Key、Agent Token、安装 URL、数据库密码、存储凭据、代理凭据以及会暴露敏感拓扑的私有路径。
+
+## Web 控制台或首次初始化
+
+检查无需认证的初始化端点：
+
+~~~bash
+curl -fsS http://127.0.0.1:8340/api/auth/setup/status
+~~~
+
+API 正常但浏览器出现空白页或 JSON 时：
+
+- 确认 Release 包含前端文件。
+- 裸机检查 `/opt/backupx/web` 可读；显式配置时确认 `server.web_root` 正确。
+- Docker 确认运行正式镜像，且自定义挂载未覆盖镜像内前端目录。
+- Nginx 静态模式确认 `root /opt/backupx/web` 和 SPA fallback 存在。
+- 版本变更后清理旧 Service Worker 或浏览器缓存。
+
+认证失败先校验系统时间，再排查 TOTP 或通行密钥。确认浏览器 Origin 与最终 HTTPS 主机一致，并从审计日志检查限流、禁用用户或已撤销可信设备。
+
+## 反向代理
+
+验证并重载 Nginx：
+
+~~~bash
+sudo nginx -t
+sudo systemctl reload nginx
+curl -i https://backup.example.com/health
+curl -i https://backup.example.com/ready
+~~~
+
+常见修正：
+
+- HTTP 413：API 路由设置 `client_max_body_size 0`。
+- 中转上传占满代理临时目录：设置 `proxy_request_buffering off`。
+- SSE 日志批量到达或断开：设置 `proxy_buffering off`、关闭代理缓存并增加读取超时。
+- 一键安装返回 HTML：代理 `/api/` 并保留旧版 `/install/` 路由。
+- Agent 收到重定向：配置最终 HTTPS Master URL，不使用 HTTP 地址。
+- 审计中所有用户都是代理 IP：只把真实代理 IP 或网段加入 `server.trusted_proxies`。
+
+以完整的 [Nginx 配置](../deployment/nginx)作为对照基线。
+
+## Agent 离线
+
+Agent 通常每 15 秒发送一次心跳，45 秒无心跳后会被标记离线。
+
+1. 确认 Agent 与可选隧道服务运行。
+2. 确认 Master URL 没有重定向，且可在 Agent 主机解析。
+3. 检查显式 `proxyUrl`；DNS 必须经过 SSH 动态隧道时使用 `socks5h://`。
+4. 确认私有 CA 路径存在且可读，不要长期改为跳过 TLS。
+5. 检查到 Master 与分配存储后端的出站防火墙。
+6. 确认 `/etc/backupx-agent/agent.token` 存在且模式为 `0600`。
+7. Token 已轮换时，在重叠窗口内写入新值并重启 Agent。
+
+不要把 Token 直接放进会保存到 shell 历史的诊断命令。Agent 日志中的 401 通常表示 Token 缺失、重叠期已结束或节点不匹配；连续连接错误通常来自 URL、DNS、代理、隧道、防火墙或 CA。
+
+## 备份任务失败
+
+修改任务前先打开备份记录并阅读完整日志。
+
+- 文件任务路径在所选 Master 或 Agent 上解析，确认路径存在于该主机命名空间。
+- Docker 只能看到已挂载路径，备份源通常应只读。
+- MySQL 要求执行主机 `PATH` 中存在 `mysqldump`。
+- PostgreSQL 要求执行主机 `PATH` 中存在 `pg_dump`。
+- SAP HANA Runner 模式要求对应客户端工具与环境。
+- 确认服务账号可读源路径并可写临时目录。
+- 从控制台测试所选存储目标。
+- 远端存储应检查 DNS、出站策略、提供商配额、时钟偏差和代理。
+
+配置多个目标时，应查看逐目标结果，不要假定所有副本都失败。修复失败目标时保留已经成功的远端产物。
+
+## 恢复、下载或验证失败
+
+- 确认远端产物仍存在且存储凭据可读取。
+- 确认执行恢复的主机挂载了目标路径。
+- 使用独立可写恢复目录，不要把所有备份源都改为可写。
+- 检查目标与 Agent 临时目录剩余空间。
+- 加密备份必须能取得原 Master 加密密钥。
+- CDC 仓库的 Manifest、索引和共享 Pack 必须一起保留，单独 Manifest 不是完整备份。
+
+诊断时优先恢复到隔离目录，不要反复覆盖生产源。
+
+## SQLite 与就绪故障
+
+`/health` 为 200 而 `/ready` 为 503 时：
+
+1. 从服务日志读取准确数据库错误。
+2. 检查磁盘空间、inode、路径所有权和挂载状态。
+3. 确认数据目录只被一个 Master 进程或容器使用。
+4. SQLite 应位于本地或块存储文件系统，不放在共享多写或不可靠网络文件系统。
+5. 检查外部备份或防病毒进程是否长期占用文件。
+
+BackupX 使用 5 秒 SQLite busy timeout，但这不会把 SQLite 变成集群数据库。不能通过启动另一个 Master 解决锁冲突。文件级复制应先停服，再复制整个数据目录。
+
+## 升级问题材料
+
+提交 Issue 时提供：
+
+- BackupX 版本、安装方式、操作系统和架构。
+- 故障影响 Master、Agent、代理、存储目标还是单个任务。
+- 覆盖首次失败时段的脱敏日志。
+- `/health` 与 `/ready` 的 HTTP 状态和响应体。
+- 最小复现步骤，以及是否始于升级或配置变更。
+- 脱敏后的相关代理配置。
+
+不要向公开 Issue 附加 `backupx.db`、`.env`、完整配置、Agent Token 文件、API Key、安装命令或存储凭据。
+
+涉及完整性或回滚时，应停止破坏性变更并参考[升级与恢复](./upgrade-recovery)。
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/operations/upgrade-recovery.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/operations/upgrade-recovery.md
@@ -0,0 +1,153 @@
+---
+sidebar_position: 1
+title: 升级与恢复
+description: 备份控制面、安全升级、配套回滚并恢复故障 Master。
+---
+
+# 升级与恢复
+
+备份产物与 BackupX 控制面属于两个不同的恢复域。对象存储中可能仍保留全部归档，但 Master 数据库丢失会同时丢失用户、加密后的存储凭据、计划、记录、节点 Token 和审计历史，因此两者都必须保护。
+
+## 必须遵守的规则
+
+1. 同一个数据目录或 SQLite 数据库只能运行一个活动 Master。
+2. 停止 Master 后快照完整数据目录与配置，或使用覆盖整个存储卷的原子快照。
+3. 旧应用版本必须与其升级前数据快照配套保留。启动时会执行数据库迁移，只切回旧二进制或旧镜像不是安全回滚。
+4. 控制面快照应保存到 Master 主机之外，并定期验证恢复。
+5. 停止 Master 前，先等待正在运行的备份、恢复、验证和复制任务结束。
+
+| 部署方式 | 持久化控制面数据 | 配置与版本状态 |
+| --- | --- | --- |
+| Docker | `backupx-data` 卷中的 `/app/data` | Compose 文件、受保护的 `.env`、固定的镜像标签或摘要 |
+| 裸机 | `/opt/backupx/data` | `/etc/backupx`、`/opt/backupx/bin`、`/opt/backupx/web`、systemd unit |
+
+配置未显式提供 JWT 与加密密钥时，自动生成的值保存在 SQLite 数据库中。所有控制面快照都应按敏感数据管理。
+
+## 变更前检查
+
+升级、迁移主机或修改安全密钥前：
+
+- 记录当前 BackupX 版本以及准确的镜像摘要或 Release 校验和。
+- 确认 `/ready` 返回 HTTP 200，并检查近期失败记录。
+- 等待正在运行的备份、恢复、验证和复制结束。
+- 测试至少一个存储目标，并确认 Agent 在线。
+- 创建完整控制面快照，校验后复制到异机。
+- 可额外导出任务定义供人工审阅。任务导出不包含数据库密码与存储凭据，不能代替数据库快照。
+- 开始前确定回滚条件与维护窗口截止时间。
+
+## 快照 Docker 部署
+
+下面的示例无需直接访问 Docker 卷目录，即可生成一致的文件级副本：
+
+~~~bash
+snapshot="backupx-control-plane-$(date -u +%Y%m%dT%H%M%SZ)"
+install -d -m 0700 "$snapshot"
+
+docker compose stop backupx
+docker cp backupx:/app/data "$snapshot/data"
+cp docker-compose.yml "$snapshot/"
+if [ -f .env ]; then cp .env "$snapshot/"; fi
+docker compose start backupx
+
+tar -czf "$snapshot.tar.gz" "$snapshot"
+sha256sum "$snapshot.tar.gz" > "$snapshot.tar.gz.sha256"
+curl -fsS http://127.0.0.1:8340/ready
+~~~
+
+复制失败时，应先恢复已停止的服务，再继续排查。归档中的 `.env` 和数据库可能包含凭据，必须限制访问。如果块存储或云平台快照能原子覆盖整个卷，也可以直接使用。
+
+## 快照裸机部署
+
+~~~bash
+snapshot="/var/backups/backupx/backupx-control-plane-$(date -u +%Y%m%dT%H%M%SZ).tar.gz"
+sudo install -d -m 0700 /var/backups/backupx
+
+sudo systemctl stop backupx
+sudo tar --acls --xattrs -C / -czf "$snapshot" \
+  etc/backupx \
+  etc/systemd/system/backupx.service \
+  opt/backupx/bin \
+  opt/backupx/web \
+  opt/backupx/data
+sudo systemctl start backupx
+
+sudo sha256sum "$snapshot" | sudo tee "$snapshot.sha256"
+curl -fsS http://127.0.0.1:8340/ready
+~~~
+
+把归档及校验和复制到受保护的异机存储。不要在服务运行时只复制 `backupx.db`。
+
+## 升级 Docker
+
+1. 在 `BACKUPX_IMAGE` 中使用 Release 标签或不可变摘要，受控生产升级不要使用 `latest`。
+2. 创建并验证升级前快照。
+3. 拉取并重建服务：
+
+~~~bash
+docker compose pull backupx
+docker compose up -d backupx
+docker compose ps
+docker compose logs --tail=100 backupx
+curl -fsS http://127.0.0.1:8340/ready
+~~~
+
+4. 登录后测试存储目标，确认 Agent 心跳，并执行一个小型备份以及一次恢复或验证演练。
+5. 观察窗口结束前保留旧镜像引用与快照。
+
+Master 完成后再小批量升级 Agent。除非变更目标就是网络配置，否则不要改动节点专用代理、私有 CA、Token 文件和堡垒机参数。
+
+## 升级裸机
+
+下载目标 Release 与校验和，完成校验后解压。安装器会保留已有的 `/etc/backupx/config.yaml`，替换二进制、前端文件和 systemd unit，并重启服务。
+
+~~~bash
+sha256sum -c backupx-vX.Y.Z-linux-amd64.tar.gz.sha256
+tar xzf backupx-vX.Y.Z-linux-amd64.tar.gz
+cd backupx-vX.Y.Z-linux-amd64
+sudo ./install.sh
+
+sudo systemctl status backupx --no-pager
+curl -fsS http://127.0.0.1:8340/ready
+~~~
+
+运行安装器前必须先创建停服快照。升级后的业务检查与 Docker 相同。
+
+## 回滚
+
+回滚是配套操作：必须同时恢复旧应用版本和紧邻升级前创建的数据快照。
+
+Docker 应保留故障卷用于分析，把快照恢复到新的空卷，Compose 同时指向该卷与旧镜像标签，然后只启动一个 Master。裸机应停止服务并保留故障现场，从同一归档恢复旧配置、二进制、前端、数据目录和 unit，重新加载 systemd 后启动。
+
+回滚后检查：
+
+~~~bash
+curl -fsS http://127.0.0.1:8340/health
+curl -fsS http://127.0.0.1:8340/ready
+~~~
+
+随后验证登录、存储访问、计划、Agent 心跳、一次备份和一次非破坏性恢复演练。在事故原因明确前不要删除故障现场。
+
+## 恢复丢失的 Master
+
+1. 按快照记录准备同架构主机与完全相同的应用版本。
+2. 替代主机先与生产流量隔离，并确保旧 Master 无法再次启动。
+3. 按原权限恢复配置和完整数据目录。
+4. 只启动一个 Master，在本机检查 `/ready`。
+5. 本地验证完成后再切换稳定 DNS 名称或虚拟 IP。
+6. 检查用户、存储目标、任务、记录、通知和审计历史。
+7. 数据库内 Token 与节点一致时，已有 Agent 会自动重连；可能泄露的 Token 必须调查并轮换。
+8. 执行小型备份及恢复或验证演练后再结束事故处理。
+
+恢复控制面不会重新生成外部备份产物，它们仍位于原存储目标。反过来，任务 JSON 导出只适合辅助重建计划，不包含密钥、存储定义和部分节点绑定，不能作为完整灾备。
+
+## 验证恢复计划
+
+至少每季度把近期快照恢复到隔离网络，启动快照记录的 BackupX 版本并验证：
+
+- 不接触生产 Master 时，`/ready` 能恢复正常。
+- 管理员可登录，已加密的存储配置可读取。
+- 任务、节点、记录和审计数量合理。
+- 可以测试一个存储目标而不写入生产数据。
+- 选定备份可验证，或可恢复到隔离目录。
+
+记录恢复耗时和最新可恢复快照时间，这两个实测值才是控制面的真实 RTO 与 RPO。
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/reference/api.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/reference/api.md
@@ -0,0 +1,268 @@
+---
+sidebar_position: 1
+title: API 参考
+description: BackupX REST 端点、认证方式、角色边界、流式响应和公开探针。
+---
+
+# API 参考
+
+交互式 API 以 `/api` 为根路径。大多数端点接受用户 JWT 或 API Key；Agent 协议使用节点专用 Token。公开探针和一次性安装器在文末单列。
+
+## 认证
+
+### 用户 JWT
+
+通过 `POST /api/auth/login` 获取 JWT，并作为 Bearer Token 发送：
+
+~~~bash
+curl -H "Authorization: Bearer $BACKUPX_TOKEN" \
+  https://backup.example.com/api/backup/tasks
+~~~
+
+根据账号和系统设置，登录过程还可能要求邮件或短信 OTP、TOTP、恢复码、可信设备 Token 或 WebAuthn。
+
+### API Key
+
+管理员可在控制台或通过 `POST /api/api-keys` 创建 API Key。明文 `bax_...` 只返回一次。
+
+~~~bash
+curl -H "X-Api-Key: $BACKUPX_API_KEY" \
+  https://backup.example.com/api/dashboard/stats
+~~~
+
+也支持 `Authorization: Bearer bax_...`。API Key 带有 `admin`、`operator` 或 `viewer` 角色，可禁用并可设置有效期。
+
+### Agent Token
+
+Agent 协议 Handler 从 `X-Agent-Token` 验证节点 Token。它不是用户凭据，不能用于交互式资源 API。
+
+### 权限标记
+
+下表使用这些标记：
+
+| 标记 | 所需权限 |
+| --- | --- |
+| 公开 | 不需要 JWT 或 API Key；安装路由仍要求一次性 Token |
+| 已认证 | 任意 `viewer`、`operator` 或 `admin` |
+| 运维 | `operator` 或 `admin` |
+| 管理员 | 仅 `admin` |
+| Agent | 有效的节点专用 Agent Token |
+
+viewer 可使用读取端点，但不能浏览节点文件系统；operator 可以执行和修改备份资源；admin 还可管理用户、API Key、设置、节点、安装令牌和节点 Token 轮换。角色不满足时返回 HTTP 403。
+
+## 认证与账号安全
+
+| 方法 | 端点 | 权限 | 说明 |
+| --- | --- | --- | --- |
+| `GET` | `/api/auth/setup/status` | 公开 | 查询是否需要创建首个管理员 |
+| `POST` | `/api/auth/setup` | 公开 | 系统无用户时创建首个管理员 |
+| `POST` | `/api/auth/login` | 公开 | 完成密码或 MFA 登录并获取 JWT |
+| `POST` | `/api/auth/otp/send` | 公开 | 发送已配置的登录 OTP |
+| `POST` | `/api/auth/webauthn/login/options` | 公开 | 开始通行密钥登录 |
+| `POST` | `/api/auth/logout` | 已认证 | 确认登出；客户端必须丢弃无状态 JWT |
+| `GET` | `/api/auth/profile` | 已认证 | 读取当前账号 |
+| `PUT` | `/api/auth/password` | 已认证 | 修改当前账号密码 |
+| `POST` | `/api/auth/2fa/setup` | 已认证 | 准备 TOTP 注册 |
+| `POST` | `/api/auth/2fa/enable` | 已认证 | 验证后启用 TOTP |
+| `POST` | `/api/auth/2fa/recovery-codes` | 已认证 | 重新生成恢复码 |
+| `DELETE` | `/api/auth/2fa` | 已认证 | 停用 TOTP |
+| `PUT` | `/api/auth/otp/config` | 已认证 | 更新 OTP 登录配置 |
+| `POST` | `/api/auth/webauthn/register/options` | 已认证 | 开始注册通行密钥 |
+| `POST` | `/api/auth/webauthn/register/finish` | 已认证 | 完成通行密钥注册 |
+| `GET` | `/api/auth/webauthn/credentials` | 已认证 | 列出通行密钥 |
+| `DELETE` | `/api/auth/webauthn/credentials/:id` | 已认证 | 删除通行密钥 |
+| `GET` | `/api/auth/trusted-devices` | 已认证 | 列出可信设备 |
+| `DELETE` | `/api/auth/trusted-devices/:id` | 已认证 | 撤销可信设备 |
+
+账号安全端点应使用交互式 JWT，不应使用自动化 API Key。
+
+## 系统与存储目标
+
+| 方法 | 端点 | 权限 | 说明 |
+| --- | --- | --- | --- |
+| `GET` | `/api/system/info` | 已认证 | 版本与系统信息 |
+| `GET` | `/api/system/update-check` | 已认证 | 检查可用 Release |
+| `GET` | `/api/storage-targets` | 已认证 | 存储目标列表 |
+| `POST` | `/api/storage-targets` | 运维 | 创建目标 |
+| `POST` | `/api/storage-targets/test` | 运维 | 测试未保存配置 |
+| `GET` | `/api/storage-targets/rclone/backends` | 已认证 | 可用 rclone 后端 |
+| `POST` | `/api/storage-targets/google-drive/auth-url` | 运维 | 开始 Google Drive 授权 |
+| `POST` | `/api/storage-targets/google-drive/complete` | 运维 | 完成 Google Drive 授权 |
+| `GET` | `/api/storage-targets/google-drive/callback` | 已认证 | 处理 OAuth 回调 |
+| `GET` | `/api/storage-targets/:id` | 已认证 | 读取目标 |
+| `PUT` | `/api/storage-targets/:id` | 运维 | 更新目标 |
+| `DELETE` | `/api/storage-targets/:id` | 运维 | 删除目标 |
+| `PUT` | `/api/storage-targets/:id/star` | 运维 | 切换收藏 |
+| `POST` | `/api/storage-targets/:id/test` | 运维 | 测试已保存目标 |
+| `GET` | `/api/storage-targets/:id/usage` | 已认证 | 读取已记录用量 |
+| `GET` | `/api/storage-targets/:id/google-drive/profile` | 已认证 | 读取已连接 Google Drive 账号 |
+
+## 备份任务
+
+| 方法 | 端点 | 权限 | 说明 |
+| --- | --- | --- | --- |
+| `GET` | `/api/backup/tasks` | 已认证 | 任务列表 |
+| `GET` | `/api/backup/tasks/tags` | 已认证 | 任务标签 |
+| `GET` | `/api/backup/tasks/export` | 已认证 | 下载全部任务 JSON，或用 `?ids=1,2` 选择任务 |
+| `POST` | `/api/backup/tasks/import` | 运维 | 导入任务，最大 1 MiB |
+| `POST` | `/api/backup/tasks/batch/toggle` | 运维 | 批量启用或停用 |
+| `POST` | `/api/backup/tasks/batch/delete` | 运维 | 批量删除 |
+| `POST` | `/api/backup/tasks/batch/run` | 运维 | 批量执行 |
+| `GET` | `/api/backup/tasks/:id` | 已认证 | 读取任务 |
+| `POST` | `/api/backup/tasks` | 运维 | 创建任务 |
+| `PUT` | `/api/backup/tasks/:id` | 运维 | 更新任务 |
+| `DELETE` | `/api/backup/tasks/:id` | 运维 | 删除任务 |
+| `PUT` | `/api/backup/tasks/:id/toggle` | 运维 | 启用或停用 |
+| `POST` | `/api/backup/tasks/:id/run` | 运维 | 触发备份 |
+| `POST` | `/api/backup/tasks/:id/verify` | 运维 | 从任务触发验证 |
+
+任务导出会主动排除数据库密码与存储凭据，适合迁移和审阅，不是完整控制面备份。
+
+## 备份与恢复记录
+
+| 方法 | 端点 | 权限 | 说明 |
+| --- | --- | --- | --- |
+| `GET` | `/api/backup/records` | 已认证 | 列出并筛选备份记录 |
+| `POST` | `/api/backup/records/batch-delete` | 运维 | 批量删除记录 |
+| `GET` | `/api/backup/records/:id` | 已认证 | 读取备份记录 |
+| `GET` | `/api/backup/records/:id/logs/stream` | 已认证 | 通过 SSE 输出日志 |
+| `GET` | `/api/backup/records/:id/download` | 已认证 | 下载产物 |
+| `GET` | `/api/backup/records/:id/contents` | 已认证 | 浏览支持类型的产物内容 |
+| `POST` | `/api/backup/records/:id/restore` | 运维 | 启动恢复 |
+| `POST` | `/api/backup/records/:id/replicate` | 运维 | 复制已有产物 |
+| `POST` | `/api/backup/records/:id/verify` | 运维 | 验证已有产物 |
+| `PUT` | `/api/backup/records/:id/lock` | 运维 | 设置保留锁 |
+| `DELETE` | `/api/backup/records/:id` | 运维 | 删除记录及受管产物 |
+| `GET` | `/api/restore/records` | 已认证 | 恢复记录列表 |
+| `GET` | `/api/restore/records/:id` | 已认证 | 恢复记录详情 |
+| `GET` | `/api/restore/records/:id/logs/stream` | 已认证 | 恢复日志 SSE |
+| `GET` | `/api/replication/records` | 已认证 | 复制记录列表 |
+| `GET` | `/api/replication/records/:id` | 已认证 | 复制记录详情 |
+| `GET` | `/api/verify/records` | 已认证 | 验证记录列表 |
+| `GET` | `/api/verify/records/:id` | 已认证 | 验证记录详情 |
+| `GET` | `/api/verify/records/:id/logs/stream` | 已认证 | 验证日志 SSE |
+
+## 模板、报表与仪表盘
+
+| 方法 | 端点 | 权限 | 说明 |
+| --- | --- | --- | --- |
+| `GET` | `/api/task-templates` | 已认证 | 任务模板列表 |
+| `GET` | `/api/task-templates/:id` | 已认证 | 读取任务模板 |
+| `POST` | `/api/task-templates` | 运维 | 创建模板 |
+| `PUT` | `/api/task-templates/:id` | 运维 | 更新模板 |
+| `DELETE` | `/api/task-templates/:id` | 运维 | 删除模板 |
+| `POST` | `/api/task-templates/:id/apply` | 运维 | 从模板创建任务 |
+| `GET` | `/api/reports/compliance` | 已认证 | 合规证据 |
+| `GET` | `/api/reports/compliance/export` | 已认证 | 导出合规 CSV |
+| `GET` | `/api/dashboard/stats` | 已认证 | 汇总统计 |
+| `GET` | `/api/dashboard/timeline` | 已认证 | 最近活动 |
+| `GET` | `/api/dashboard/sla` | 已认证 | RPO 与 SLA 状态 |
+| `GET` | `/api/dashboard/cluster` | 已认证 | 集群概览 |
+| `GET` | `/api/dashboard/breakdown` | 已认证 | 任务与记录分布 |
+| `GET` | `/api/dashboard/node-performance` | 已认证 | 节点性能 |
+
+## 通知、设置与管理
+
+| 方法 | 端点 | 权限 | 说明 |
+| --- | --- | --- | --- |
+| `GET` | `/api/notifications` | 已认证 | 通知渠道列表 |
+| `GET` | `/api/notifications/:id` | 已认证 | 读取渠道 |
+| `POST` | `/api/notifications` | 运维 | 创建渠道 |
+| `PUT` | `/api/notifications/:id` | 运维 | 更新渠道 |
+| `DELETE` | `/api/notifications/:id` | 运维 | 删除渠道 |
+| `POST` | `/api/notifications/test` | 运维 | 测试未保存配置 |
+| `POST` | `/api/notifications/:id/test` | 运维 | 测试已保存渠道 |
+| `GET` | `/api/settings` | 已认证 | 读取系统设置 |
+| `PUT` | `/api/settings` | 管理员 | 更新系统设置 |
+| `GET` | `/api/users` | 管理员 | 用户列表 |
+| `POST` | `/api/users` | 管理员 | 创建用户 |
+| `PUT` | `/api/users/:id` | 管理员 | 更新用户 |
+| `POST` | `/api/users/:id/2fa/reset` | 管理员 | 重置用户第二因素 |
+| `DELETE` | `/api/users/:id` | 管理员 | 删除用户 |
+| `GET` | `/api/api-keys` | 管理员 | API Key 列表，不返回明文 |
+| `POST` | `/api/api-keys` | 管理员 | 创建 API Key，明文仅返回一次 |
+| `PUT` | `/api/api-keys/:id/toggle` | 管理员 | 启用或停用 API Key |
+| `DELETE` | `/api/api-keys/:id` | 管理员 | 撤销 API Key |
+
+## 审计、事件、搜索与发现
+
+| 方法 | 端点 | 权限 | 说明 |
+| --- | --- | --- | --- |
+| `GET` | `/api/audit-logs` | 已认证 | 列出并筛选审计记录 |
+| `GET` | `/api/audit-logs/export` | 已认证 | 导出审计记录 |
+| `GET` | `/api/events/stream` | 已认证 | 通过 SSE 输出实时应用事件 |
+| `GET` | `/api/search` | 已认证 | 搜索支持的资源 |
+| `POST` | `/api/database/discover` | 已认证 | 按提供的连接信息发现数据库 |
+
+## 节点
+
+| 方法 | 端点 | 权限 | 说明 |
+| --- | --- | --- | --- |
+| `GET` | `/api/nodes` | 已认证 | 节点列表 |
+| `GET` | `/api/nodes/:id` | 已认证 | 节点详情 |
+| `GET` | `/api/nodes/:id/fs/list` | 运维 | 浏览所选节点文件系统 |
+| `POST` | `/api/nodes` | 管理员 | 创建节点 |
+| `POST` | `/api/nodes/batch` | 管理员 | 批量创建最多 50 个节点 |
+| `PUT` | `/api/nodes/:id` | 管理员 | 更新节点 |
+| `DELETE` | `/api/nodes/:id` | 管理员 | 删除未被引用的节点 |
+| `POST` | `/api/nodes/:id/install-tokens` | 管理员 | 创建一次性安装器 |
+| `GET` | `/api/nodes/:id/install-script-preview` | 管理员 | 预览安装材料 |
+| `POST` | `/api/nodes/:id/rotate-token` | 管理员 | 轮换长期节点 Token |
+
+## Agent 协议
+
+这些路由供 `backupx agent` 使用，Handler 内部通过节点 Token 认证。
+
+| 方法 | 端点 | 权限 | 说明 |
+| --- | --- | --- | --- |
+| `POST` | `/api/agent/heartbeat` | Agent | 上报心跳与节点状态 |
+| `POST` | `/api/agent/commands/poll` | Agent | 领取待执行命令 |
+| `POST` | `/api/agent/commands/:id/result` | Agent | 上报命令结果 |
+| `GET` | `/api/agent/tasks/:id` | Agent | 获取可执行任务规格 |
+| `POST` | `/api/agent/records/:id` | Agent | 追加日志或更新备份状态 |
+| `PUT` | `/api/agent/records/:id/artifacts/:targetId` | Agent | 向 Master 流式中转产物 |
+| `GET` | `/api/agent/restores/:id/spec` | Agent | 获取恢复指令 |
+| `GET` | `/api/agent/restores/:id/artifact` | Agent | 流式读取恢复产物 |
+| `POST` | `/api/agent/restores/:id` | Agent | 更新恢复状态 |
+| `GET` | `/api/v1/agent/self` | Agent | 安装时校验节点身份 |
+
+## 公开运维与安装路由
+
+| 方法 | 端点 | 权限 | 说明 |
+| --- | --- | --- | --- |
+| `GET` | `/health` | 公开 | 存活检查 |
+| `GET` | `/api/health` | 公开 | 带 API 前缀的存活别名 |
+| `GET` | `/ready` | 公开 | SQLite 就绪检查 |
+| `GET` | `/api/ready` | 公开 | 带 API 前缀的就绪别名 |
+| `GET` | `/metrics` | 公开 | Prometheus 指标 |
+| `GET` | `/install/:token` | 公开 | 消费一次性 Agent 安装令牌 |
+| `GET` | `/api/install/:token` | 公开 | 带 API 前缀的安装路由 |
+| `GET` | `/install/:token/compose.yml` | 公开 | 生成 Docker Agent Compose |
+| `GET` | `/api/install/:token/compose.yml` | 公开 | 带 API 前缀的 Docker Compose 路由 |
+
+探针与指标应只对监控网段开放。安装 Token 是单次、限时秘密，不能写入公开日志。
+
+## 响应格式
+
+大多数 JSON 成功响应为：
+
+~~~json
+{
+  "code": "OK",
+  "message": "success",
+  "data": {}
+}
+~~~
+
+错误使用 HTTP 4xx 或 5xx，并带稳定业务码：
+
+~~~json
+{
+  "code": "BACKUP_TASK_NOT_FOUND",
+  "message": "备份任务不存在"
+}
+~~~
+
+客户端应按 HTTP 状态和 `code` 分支，不要依赖本地化的 `message`。
+
+产物下载、任务 JSON 导出、审计或合规导出、安装器响应和 `/metrics` 使用各自原生 Content-Type，不使用 JSON Envelope。日志与事件流使用 `text/event-stream`，反向代理必须关闭响应缓冲。
--- a/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/reference/cli.md
+++ b/docs-site/i18n/zh-CN/docusaurus-plugin-content-docs/current/reference/cli.md
@@ -0,0 +1,80 @@
+---
+sidebar_position: 2
+title: CLI 参考
+description: backupx 子命令 — server / agent / backint / reset-password。
+---
+
+# CLI 参考
+
+`backupx` 二进制内置多个子命令。无子命令时默认启动主服务进程。
+
+## `backupx`（默认：服务进程）
+
+```bash
+backupx --config /opt/backupx/config.yaml
+backupx --version
+```
+
+| 参数 | 说明 |
+|------|------|
+| `--config <path>` | 显式配置文件路径；省略时使用下方查找路径 |
+| `--version` | 打印版本后退出 |
+
+未提供 `--config` 时，服务端依次查找 `./config.yaml`、`./server/config.yaml` 和 `/etc/backupx/config.yaml`。`BACKUPX_*` 环境变量会覆盖对应服务端配置项，详见[配置参考](../deployment/configuration)。
+
+## `backupx agent`
+
+以 Agent 模式运行，连接到 Master。详见 [多节点集群](../features/multi-node)。
+
+```bash
+backupx agent --master https://backup.example.com --token-file /etc/backupx-agent/agent.token
+```
+
+| 参数 | 说明 |
+|------|------|
+| `--master <url>` | Master URL |
+| `--token <token>` | Agent 认证令牌 |
+| `--token-file <path>` | 从文件读取 Agent Token，服务与容器部署推荐使用 |
+| `--config <path>` | 加载 Agent YAML；提供后不再加载基于环境变量的 Agent 配置 |
+| `--temp-dir <path>` | 本地临时目录（默认 `/var/lib/backupx-agent/tmp`） |
+| `--proxy-url <url>` | 显式 HTTP(S) 或 SOCKS5(H) 代理 |
+| `--ca-cert <path>` | 用于校验 Master 的 PEM CA 证书 |
+| `--insecure-tls` | 跳过 TLS 校验（仅测试用） |
+
+Agent 配置优先级为显式 CLI 参数高于 YAML。未提供 `--config` 时，配置从 `BACKUPX_AGENT_MASTER`、`BACKUPX_AGENT_TOKEN`、`BACKUPX_AGENT_TOKEN_FILE`、`BACKUPX_AGENT_HEARTBEAT`、`BACKUPX_AGENT_POLL`、`BACKUPX_AGENT_TEMP_DIR`、`BACKUPX_AGENT_PROXY_URL`、`BACKUPX_AGENT_CA_CERT_FILE` 和 `BACKUPX_AGENT_INSECURE_TLS` 加载。未设置显式代理时，Agent 还会遵循 `HTTP_PROXY`、`HTTPS_PROXY` 和 `NO_PROXY`。
+
+`--token` 优先于 `--token-file`。长期 Token 应放在仅 root 可读的文件中，不要进入命令历史。私有 CA 与 `--insecure-tls` 不能同时启用。
+
+## `backupx backint`
+
+SAP HANA Backint 协议代理，详见 [SAP HANA 支持](../features/sap-hana)。
+
+```bash
+backupx backint -f <function> -i <input> -o <output> -p <params>
+```
+
+| 参数 | 说明 |
+|------|------|
+| `-f <fn>` | `backup` / `restore` / `inquire` / `delete` |
+| `-i <path>` | 输入文件 |
+| `-o <path>` | 输出文件 |
+| `-p <path>` | 参数文件 |
+| `-u / -c / -l / -v` | 接收但忽略（兼容 SAP 约定） |
+
+`-p` 参数文件必须定义 `STORAGE_TYPE`，并提供 `STORAGE_CONFIG_JSON` 或 `STORAGE_CONFIG`。可选项包括 `PARALLEL_FACTOR`、`COMPRESS`、`LOG_FILE`、`CATALOG_DB` 和 `KEY_PREFIX`。
+
+## `backupx reset-password`
+
+直接在 SQLite 中重置管理员密码，无需重启服务。
+
+```bash
+backupx reset-password --username admin --password 'newpass123' [--config /path/to/config.yaml]
+```
+
+| 参数 | 说明 |
+|------|------|
+| `--username` | 目标用户名（默认 `admin`） |
+| `--password` | 新密码（最少 8 字符，必填） |
+| `--config` | 配置文件路径（用于定位数据库文件） |
+
+该命令应在可访问配置中 SQLite 路径的 Master 主机执行。不要把新密码直接写入长期保留的 shell 历史。
--- a/docs-site/i18n/zh-CN/docusaurus-theme-classic/footer.json
+++ b/docs-site/i18n/zh-CN/docusaurus-theme-classic/footer.json
@@ -0,0 +1,14 @@
+{
+  "link.title.Documentation": {"message": "文档"},
+  "link.title.Operations": {"message": "运维"},
+  "link.title.Project": {"message": "项目"},
+  "link.item.label.Introduction": {"message": "简介"},
+  "link.item.label.Quick Start": {"message": "快速开始"},
+  "link.item.label.Configuration": {"message": "配置"},
+  "link.item.label.Monitoring": {"message": "监控"},
+  "link.item.label.Security": {"message": "安全"},
+  "link.item.label.Troubleshooting": {"message": "故障排查"},
+  "link.item.label.GitHub": {"message": "GitHub"},
+  "link.item.label.Releases": {"message": "发布版本"},
+  "link.item.label.Community": {"message": "社区"}
+}
--- a/docs-site/i18n/zh-CN/docusaurus-theme-classic/navbar.json
+++ b/docs-site/i18n/zh-CN/docusaurus-theme-classic/navbar.json
@@ -0,0 +1,8 @@
+{
+  "item.label.Docs": {"message": "文档"},
+  "item.label.Deployment": {"message": "部署"},
+  "item.label.Operations": {"message": "运维"},
+  "item.label.API": {"message": "API"},
+  "item.label.Community": {"message": "社区"},
+  "item.label.GitHub": {"message": "GitHub"}
+}
--- a/docs-site/package-lock.json
+++ b/docs-site/package-lock.json
--- a/docs-site/package.json
+++ b/docs-site/package.json
@@ -0,0 +1,49 @@
+{
+  "name": "backupx-docs",
+  "version": "1.0.0",
+  "private": true,
+  "scripts": {
+    "docusaurus": "docusaurus",
+    "start": "docusaurus start",
+    "build": "docusaurus build",
+    "swizzle": "docusaurus swizzle",
+    "deploy": "docusaurus deploy",
+    "clear": "docusaurus clear",
+    "serve": "docusaurus serve",
+    "write-translations": "docusaurus write-translations",
+    "write-heading-ids": "docusaurus write-heading-ids",
+    "typecheck": "tsc"
+  },
+  "dependencies": {
+    "@docusaurus/core": "3.10.2",
+    "@docusaurus/faster": "3.10.2",
+    "@docusaurus/preset-classic": "3.10.2",
+    "@mdx-js/react": "^3.0.0",
+    "clsx": "^2.0.0",
+    "prism-react-renderer": "^2.3.0",
+    "react": "^19.2.8",
+    "react-dom": "^19.2.8"
+  },
+  "devDependencies": {
+    "@docusaurus/module-type-aliases": "3.10.2",
+    "@docusaurus/tsconfig": "3.10.2",
+    "@docusaurus/types": "3.10.2",
+    "@types/react": "^19.2.18",
+    "typescript": "~6.0.2"
+  },
+  "browserslist": {
+    "production": [
+      ">0.5%",
+      "not dead",
+      "not op_mini all"
+    ],
+    "development": [
+      "last 3 chrome version",
+      "last 3 firefox version",
+      "last 5 safari version"
+    ]
+  },
+  "engines": {
+    "node": ">=24.0"
+  }
+}
--- a/docs-site/sidebars.ts
+++ b/docs-site/sidebars.ts
@@ -0,0 +1,65 @@
+import type {SidebarsConfig} from '@docusaurus/plugin-content-docs';
+
+const sidebars: SidebarsConfig = {
+  docs: [
+    'intro',
+    {
+      type: 'category',
+      label: 'Getting Started',
+      collapsed: false,
+      items: [
+        'getting-started/installation',
+        'getting-started/quick-start',
+      ],
+    },
+    {
+      type: 'category',
+      label: 'Deployment',
+      items: [
+        'deployment/docker',
+        'deployment/bare-metal',
+        'deployment/nginx',
+        'deployment/configuration',
+      ],
+    },
+    {
+      type: 'category',
+      label: 'Operations',
+      items: [
+        'operations/upgrade-recovery',
+        'operations/security',
+        'operations/monitoring',
+        'operations/troubleshooting',
+      ],
+    },
+    {
+      type: 'category',
+      label: 'Features',
+      items: [
+        'features/backup-types',
+        'features/storage-backends',
+        'features/sap-hana',
+        'features/multi-node',
+        'features/notifications',
+      ],
+    },
+    {
+      type: 'category',
+      label: 'Reference',
+      items: [
+        'reference/api',
+        'reference/cli',
+      ],
+    },
+    {
+      type: 'category',
+      label: 'Development',
+      items: [
+        'development/setup',
+        'development/contributing',
+      ],
+    },
+  ],
+};
+
+export default sidebars;
--- a/docs-site/src/components/DocIcon/index.tsx
+++ b/docs-site/src/components/DocIcon/index.tsx
@@ -0,0 +1,172 @@
+import type {ReactNode} from 'react';
+
+export type DocIconName =
+  | 'arrowRight'
+  | 'bookOpen'
+  | 'box'
+  | 'check'
+  | 'clock'
+  | 'cloud'
+  | 'database'
+  | 'download'
+  | 'external'
+  | 'github'
+  | 'heart'
+  | 'monitor'
+  | 'network'
+  | 'restore'
+  | 'server'
+  | 'shield'
+  | 'storage'
+  | 'terminal'
+  | 'users'
+  | 'wrench';
+
+type DocIconProps = {
+  name: DocIconName;
+  size?: number;
+  className?: string;
+};
+
+const ICON_PATHS: Record<Exclude<DocIconName, 'github'>, ReactNode> = {
+  arrowRight: (
+    <>
+      <path d="M5 12h14" />
+      <path d="m13 6 6 6-6 6" />
+    </>
+  ),
+  bookOpen: (
+    <>
+      <path d="M3 5.5A3.5 3.5 0 0 1 6.5 2H11v17H6.5A3.5 3.5 0 0 0 3 22Z" />
+      <path d="M21 5.5A3.5 3.5 0 0 0 17.5 2H13v17h4.5A3.5 3.5 0 0 1 21 22Z" />
+    </>
+  ),
+  box: (
+    <>
+      <path d="m12 3 8 4.5v9L12 21l-8-4.5v-9Z" />
+      <path d="m4.4 7.7 7.6 4.4 7.6-4.4" />
+      <path d="M12 12.1V21" />
+    </>
+  ),
+  check: <path d="m5 12 4 4L19 6" />,
+  clock: (
+    <>
+      <circle cx="12" cy="12" r="9" />
+      <path d="M12 7v5l3 2" />
+    </>
+  ),
+  cloud: <path d="M17.5 19H7a5 5 0 0 1-.6-9.96A6.5 6.5 0 0 1 18.7 8.2 5.5 5.5 0 0 1 17.5 19Z" />,
+  database: (
+    <>
+      <ellipse cx="12" cy="5" rx="8" ry="3" />
+      <path d="M4 5v6c0 1.7 3.6 3 8 3s8-1.3 8-3V5" />
+      <path d="M4 11v6c0 1.7 3.6 3 8 3s8-1.3 8-3v-6" />
+    </>
+  ),
+  download: (
+    <>
+      <path d="M12 3v12" />
+      <path d="m7 10 5 5 5-5" />
+      <path d="M4 20h16" />
+    </>
+  ),
+  external: (
+    <>
+      <path d="M14 4h6v6" />
+      <path d="m20 4-9 9" />
+      <path d="M19 13v6a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V6a1 1 0 0 1 1-1h6" />
+    </>
+  ),
+  heart: <path d="M20.8 4.6a5.5 5.5 0 0 0-7.8 0L12 5.7l-1.1-1.1a5.5 5.5 0 0 0-7.8 7.8l1.1 1.1L12 21l7.8-7.5 1.1-1.1a5.5 5.5 0 0 0-.1-7.8Z" />,
+  monitor: (
+    <>
+      <rect x="3" y="4" width="18" height="13" rx="1" />
+      <path d="M8 21h8" />
+      <path d="M12 17v4" />
+    </>
+  ),
+  network: (
+    <>
+      <rect x="9" y="3" width="6" height="5" rx="1" />
+      <rect x="3" y="16" width="6" height="5" rx="1" />
+      <rect x="15" y="16" width="6" height="5" rx="1" />
+      <path d="M12 8v4M6 16v-4h12v4" />
+    </>
+  ),
+  restore: (
+    <>
+      <path d="M4 7v5h5" />
+      <path d="M5.6 17a8 8 0 1 0 .4-10L4 9" />
+      <path d="M12 8v4l3 2" />
+    </>
+  ),
+  server: (
+    <>
+      <rect x="3" y="4" width="18" height="6" rx="1" />
+      <rect x="3" y="14" width="18" height="6" rx="1" />
+      <path d="M7 7h.01M7 17h.01M11 7h7M11 17h7" />
+    </>
+  ),
+  shield: (
+    <>
+      <path d="M12 3 20 6v6c0 5-3.3 8.2-8 9-4.7-.8-8-4-8-9V6Z" />
+      <path d="m8.5 12 2.2 2.2 4.8-5" />
+    </>
+  ),
+  storage: (
+    <>
+      <path d="M4 6h16v12H4z" />
+      <path d="M8 10h8M8 14h5" />
+    </>
+  ),
+  terminal: (
+    <>
+      <rect x="3" y="4" width="18" height="16" rx="1" />
+      <path d="m7 9 3 3-3 3M13 15h4" />
+    </>
+  ),
+  users: (
+    <>
+      <circle cx="9" cy="8" r="3" />
+      <path d="M3 20a6 6 0 0 1 12 0" />
+      <path d="M16 5.2a3 3 0 0 1 0 5.6M17 14a5 5 0 0 1 4 4.9" />
+    </>
+  ),
+  wrench: (
+    <>
+      <path d="M14.7 6.3a4 4 0 0 0-5-5L12 3.6 8.4 7.2 6.1 4.9a4 4 0 0 0 5 5L19 17.8a1.6 1.6 0 0 1-2.2 2.2l-7.9-7.9" />
+    </>
+  ),
+};
+
+export default function DocIcon({name, size = 20, className}: DocIconProps): ReactNode {
+  if (name === 'github') {
+    return (
+      <svg
+        aria-hidden="true"
+        className={className}
+        width={size}
+        height={size}
+        viewBox="0 0 24 24"
+        fill="currentColor">
+        <path d="M12 2C6.48 2 2 6.59 2 12.25c0 4.53 2.87 8.37 6.84 9.73.5.1.68-.22.68-.49v-1.92c-2.78.62-3.37-1.21-3.37-1.21-.45-1.18-1.11-1.49-1.11-1.49-.91-.64.07-.63.07-.63 1 .08 1.53 1.06 1.53 1.06.89 1.57 2.34 1.11 2.91.85.09-.67.35-1.11.63-1.37-2.22-.26-4.56-1.14-4.56-5.07 0-1.12.39-2.03 1.03-2.75-.1-.26-.45-1.3.1-2.71 0 0 .84-.28 2.75 1.05A9.3 9.3 0 0 1 12 6.95a9.3 9.3 0 0 1 2.5.35c1.91-1.33 2.75-1.05 2.75-1.05.55 1.41.2 2.45.1 2.71.64.72 1.03 1.63 1.03 2.75 0 3.94-2.34 4.8-4.57 5.06.36.32.68.94.68 1.9v2.82c0 .27.18.59.69.49A10.27 10.27 0 0 0 22 12.25C22 6.59 17.52 2 12 2Z" />
+      </svg>
+    );
+  }
+
+  return (
+    <svg
+      aria-hidden="true"
+      className={className}
+      width={size}
+      height={size}
+      viewBox="0 0 24 24"
+      fill="none"
+      stroke="currentColor"
+      strokeWidth="1.6"
+      strokeLinecap="round"
+      strokeLinejoin="round">
+      {ICON_PATHS[name]}
+    </svg>
+  );
+}
--- a/docs-site/src/components/HomepageCommunity/index.tsx
+++ b/docs-site/src/components/HomepageCommunity/index.tsx
@@ -0,0 +1,348 @@
+import type {ReactNode} from 'react';
+import {useEffect, useState} from 'react';
+import Heading from '@theme/Heading';
+import Translate from '@docusaurus/Translate';
+import Link from '@docusaurus/Link';
+import DocIcon, {type DocIconName} from '@site/src/components/DocIcon';
+import styles from './styles.module.css';
+
+type Contributor = {
+  login: string;
+  avatarUrl?: string;
+  contributions: number;
+  type: string;
+  href: string;
+};
+
+type GitHubContributor = {
+  login: string;
+  avatar_url?: string;
+  contributions?: number;
+  html_url?: string;
+  type?: string;
+};
+
+type CommunityPath = {
+  icon: DocIconName;
+  title: ReactNode;
+  description: ReactNode;
+  href: string;
+};
+
+type SponsorFocus = {
+  id: string;
+  icon: DocIconName;
+  label: ReactNode;
+  title: ReactNode;
+  description: ReactNode;
+};
+
+type SponsorTier = {
+  id: string;
+  name: ReactNode;
+  audience: ReactNode;
+  description: ReactNode;
+};
+
+const FALLBACK_CONTRIBUTORS: Contributor[] = [
+  {
+    login: 'Awuqing',
+    contributions: 0,
+    type: 'User',
+    href: 'https://github.com/Awuqing',
+  },
+  {
+    login: 'dependabot[bot]',
+    contributions: 0,
+    type: 'Bot',
+    href: 'https://github.com/dependabot',
+  },
+];
+
+const COMMUNITY_PATHS: CommunityPath[] = [
+  {
+    icon: 'wrench',
+    title: <Translate id="community.path.issues.title">Report production issues</Translate>,
+    description: <Translate id="community.path.issues.desc">Share logs, deployment topology, and restore expectations.</Translate>,
+    href: 'https://github.com/Awuqing/BackupX/issues',
+  },
+  {
+    icon: 'bookOpen',
+    title: <Translate id="community.path.docs.title">Improve docs and examples</Translate>,
+    description: <Translate id="community.path.docs.desc">Contribute deployment guides for storage, agents, and databases.</Translate>,
+    href: '/docs/development/contributing',
+  },
+  {
+    icon: 'github',
+    title: <Translate id="community.path.code.title">Ship focused pull requests</Translate>,
+    description: <Translate id="community.path.code.desc">Keep changes tested, reviewable, and aligned with the existing architecture.</Translate>,
+    href: 'https://github.com/Awuqing/BackupX/pulls',
+  },
+];
+
+const SPONSOR_FOCUS: SponsorFocus[] = [
+  {
+    id: 'infrastructure',
+    icon: 'cloud',
+    label: <Translate id="community.sponsor.infrastructure.label">Infrastructure</Translate>,
+    title: <Translate id="community.sponsor.infrastructure.title">Cloud and storage compatibility</Translate>,
+    description: <Translate id="community.sponsor.infrastructure.desc">Support validation across object storage, WebDAV, SFTP, and regional cloud providers.</Translate>,
+  },
+  {
+    id: 'reliability',
+    icon: 'shield',
+    label: <Translate id="community.sponsor.security.label">Reliability</Translate>,
+    title: <Translate id="community.sponsor.security.title">Security and recovery work</Translate>,
+    description: <Translate id="community.sponsor.security.desc">Fund encryption reviews, restore drills, release signing, and operational checks.</Translate>,
+  },
+  {
+    id: 'community',
+    icon: 'users',
+    label: <Translate id="community.sponsor.community.label">Community</Translate>,
+    title: <Translate id="community.sponsor.community.title">Documentation and contributor support</Translate>,
+    description: <Translate id="community.sponsor.community.desc">Improve guides, examples, platform testing, and the contributor experience.</Translate>,
+  },
+];
+
+const SPONSOR_TIERS: SponsorTier[] = [
+  {
+    id: 'backer',
+    name: <Translate id="community.sponsor.tier.backer.name">Backer</Translate>,
+    audience: <Translate id="community.sponsor.tier.backer.amount">For individuals and small teams</Translate>,
+    description: <Translate id="community.sponsor.tier.backer.desc">Supports documentation, issue triage, compatibility testing, and focused usability work.</Translate>,
+  },
+  {
+    id: 'partner',
+    name: <Translate id="community.sponsor.tier.partner.name">Partner</Translate>,
+    audience: <Translate id="community.sponsor.tier.partner.amount">For storage and infrastructure vendors</Translate>,
+    description: <Translate id="community.sponsor.tier.partner.desc">Supports provider validation, deployment examples, benchmarks, and integration guides.</Translate>,
+  },
+  {
+    id: 'enterprise',
+    name: <Translate id="community.sponsor.tier.enterprise.name">Enterprise</Translate>,
+    audience: <Translate id="community.sponsor.tier.enterprise.amount">For production BackupX operators</Translate>,
+    description: <Translate id="community.sponsor.tier.enterprise.desc">Funds recovery drills, release hardening, audits, and long-term maintenance.</Translate>,
+  },
+];
+
+function getInitials(login: string): string {
+  return login
+    .replace(/\[bot\]$/i, '')
+    .split(/[-_\s]/)
+    .filter(Boolean)
+    .slice(0, 2)
+    .map(part => part[0]?.toUpperCase())
+    .join('') || login.slice(0, 2).toUpperCase();
+}
+
+function normalizeContributor(contributor: GitHubContributor): Contributor | null {
+  if (!contributor.login) {
+    return null;
+  }
+  return {
+    login: contributor.login,
+    avatarUrl: contributor.avatar_url,
+    contributions: contributor.contributions ?? 0,
+    type: contributor.type ?? 'User',
+    href: contributor.html_url ?? `https://github.com/${contributor.login}`,
+  };
+}
+
+function useGitHubContributors(): Contributor[] {
+  const [contributors, setContributors] = useState<Contributor[]>(FALLBACK_CONTRIBUTORS);
+
+  useEffect(() => {
+    const controller = new AbortController();
+
+    fetch('https://api.github.com/repos/Awuqing/BackupX/contributors?per_page=8', {
+      signal: controller.signal,
+      headers: {Accept: 'application/vnd.github+json'},
+    })
+      .then(response => {
+        if (!response.ok) {
+          throw new Error(`GitHub contributors request failed: ${response.status}`);
+        }
+        return response.json() as Promise<GitHubContributor[]>;
+      })
+      .then(payload => {
+        const nextContributors = payload
+          .map(normalizeContributor)
+          .filter((contributor): contributor is Contributor => Boolean(contributor));
+
+        if (nextContributors.length > 0) {
+          setContributors(nextContributors);
+        }
+      })
+      .catch(error => {
+        if (error instanceof Error && error.name !== 'AbortError') {
+          console.warn(error.message);
+        }
+      });
+
+    return () => controller.abort();
+  }, []);
+
+  return contributors;
+}
+
+function ContributorRow({login, avatarUrl, contributions, type, href}: Contributor): ReactNode {
+  return (
+    <Link className={styles.contributorRow} to={href}>
+      {avatarUrl ? (
+        <img className={styles.avatarImage} src={avatarUrl} alt="" loading="lazy" />
+      ) : (
+        <span className={styles.avatar} aria-hidden="true">{getInitials(login)}</span>
+      )}
+      <span className={styles.contributorBody}>
+        <span className={styles.contributorName}>{login}</span>
+        <span className={styles.contributorRole}>
+          {type === 'Bot' ? (
+            <Translate id="community.contributor.botRole">Automation contributor</Translate>
+          ) : (
+            <Translate id="community.contributor.githubRole">GitHub contributor</Translate>
+          )}
+        </span>
+      </span>
+      <span className={styles.contributionCount}>
+        <Translate id="community.contributor.contributions" values={{count: contributions}}>
+          {'{count} contributions'}
+        </Translate>
+      </span>
+    </Link>
+  );
+}
+
+export function HomepageSponsors(): ReactNode {
+  return (
+    <div className={styles.sponsorProgram}>
+      <div className={styles.sponsorProgramHeader}>
+        <span className={styles.sponsorProgramIcon}><DocIcon name="heart" size={23} /></span>
+        <div className={styles.sponsorProgramCopy}>
+          <Heading as="h2" className={styles.sponsorProgramTitle}>
+            <Translate id="community.sponsor.title">Support reliable backup infrastructure</Translate>
+          </Heading>
+          <p>
+            <Translate id="community.sponsor.programDesc">
+              Sponsorship is directed toward test coverage, restore confidence, provider compatibility, and documentation that operators can apply directly.
+            </Translate>
+          </p>
+        </div>
+        <Link className={styles.sponsorAction} to="https://github.com/sponsors/Awuqing">
+          <DocIcon name="github" size={17} />
+          <Translate id="community.sponsor.cta">Sponsor BackupX</Translate>
+          <DocIcon name="external" size={15} />
+        </Link>
+      </div>
+
+      <div className={styles.sponsorFocusList}>
+        {SPONSOR_FOCUS.map(focus => (
+          <div key={focus.id} className={styles.sponsorFocusItem}>
+            <span className={styles.sponsorFocusIcon}><DocIcon name={focus.icon} size={20} /></span>
+            <span className={styles.sponsorFocusBody}>
+              <span className={styles.sponsorFocusLabel}>{focus.label}</span>
+              <span className={styles.sponsorFocusTitle}>{focus.title}</span>
+              <span className={styles.sponsorFocusDescription}>{focus.description}</span>
+            </span>
+          </div>
+        ))}
+      </div>
+
+      <div className={styles.tierSection}>
+        <div className={styles.tierSectionHeader}>
+          <Heading as="h3"><Translate id="community.sponsor.tier.title">Ways to support</Translate></Heading>
+          <p><Translate id="community.sponsor.tier.subtitle">Choose a level that matches how your team depends on BackupX.</Translate></p>
+        </div>
+        <div className={styles.tierGrid}>
+          {SPONSOR_TIERS.map(tier => (
+            <div key={tier.id} className={styles.tierItem}>
+              <span className={styles.tierName}>{tier.name}</span>
+              <span className={styles.tierAudience}>{tier.audience}</span>
+              <span className={styles.tierDescription}>{tier.description}</span>
+            </div>
+          ))}
+        </div>
+      </div>
+    </div>
+  );
+}
+
+export default function HomepageCommunity(): ReactNode {
+  const contributors = useGitHubContributors();
+
+  return (
+    <section id="community" className={styles.section}>
+      <div className="container">
+        <div className={styles.sectionHead}>
+          <div>
+            <div className={styles.sectionTag}>
+              <Translate id="community.tag">Community</Translate>
+            </div>
+            <Heading as="h2" className={styles.sectionTitle}>
+              <Translate id="community.title">Operational knowledge improves in the open</Translate>
+            </Heading>
+          </div>
+          <p className={styles.sectionSubtitle}>
+            <Translate id="community.subtitle">
+              Report real deployment constraints, improve the runbooks, or contribute a focused change with reproducible validation.
+            </Translate>
+          </p>
+        </div>
+
+        <div className={styles.communityShell}>
+          <div className={styles.pathPanel}>
+            <div className={styles.panelHeader}>
+              <span><Translate id="community.path.kicker">Contribution paths</Translate></span>
+              <Link to="/docs/development/contributing">
+                <Translate id="community.path.guide">Contribution guide</Translate>
+                <DocIcon name="arrowRight" size={15} />
+              </Link>
+            </div>
+            <div className={styles.pathList}>
+              {COMMUNITY_PATHS.map((path, index) => (
+                <Link key={path.href} className={styles.pathItem} to={path.href}>
+                  <span className={styles.pathIndex}>{String(index + 1).padStart(2, '0')}</span>
+                  <span className={styles.pathIcon}><DocIcon name={path.icon} size={19} /></span>
+                  <span className={styles.pathBody}>
+                    <span className={styles.pathTitle}>{path.title}</span>
+                    <span className={styles.pathDescription}>{path.description}</span>
+                  </span>
+                  <DocIcon name="arrowRight" size={17} className={styles.rowArrow} />
+                </Link>
+              ))}
+            </div>
+          </div>
+
+          <div className={styles.contributorPanel}>
+            <div className={styles.panelHeader}>
+              <span><Translate id="community.contributor.kicker">Contributors</Translate></span>
+              <Link to="https://github.com/Awuqing/BackupX/graphs/contributors">
+                <Translate id="community.contributor.all">View all</Translate>
+                <DocIcon name="external" size={14} />
+              </Link>
+            </div>
+            <p className={styles.panelNote}>
+              <Translate id="community.contributor.source">Loaded from the GitHub contributors API with a local fallback.</Translate>
+            </p>
+            <div className={styles.contributorList}>
+              {contributors.slice(0, 5).map(contributor => (
+                <ContributorRow key={contributor.login} {...contributor} />
+              ))}
+            </div>
+          </div>
+
+          <div className={styles.sponsorBand}>
+            <span className={styles.sponsorBandIcon}><DocIcon name="heart" size={20} /></span>
+            <span className={styles.sponsorBandBody}>
+              <span className={styles.sponsorBandTitle}><Translate id="community.sponsor.bandTitle">Support long-term maintenance</Translate></span>
+              <span className={styles.sponsorBandDescription}><Translate id="community.sponsor.bandDesc">Fund compatibility testing, recovery work, and operator-focused documentation.</Translate></span>
+            </span>
+            <Link to="/sponsors">
+              <Translate id="community.sponsor.learnMore">Sponsorship details</Translate>
+              <DocIcon name="arrowRight" size={16} />
+            </Link>
+          </div>
+        </div>
+      </div>
+    </section>
+  );
+}
--- a/docs-site/src/components/HomepageCommunity/styles.module.css
+++ b/docs-site/src/components/HomepageCommunity/styles.module.css
@@ -0,0 +1,509 @@
+.section {
+  background: var(--ifm-background-color);
+  padding: 5rem 0 5.5rem;
+}
+
+.sectionHead {
+  align-items: end;
+  display: grid;
+  gap: 3rem;
+  grid-template-columns: minmax(0, 1fr) minmax(320px, 0.7fr);
+  margin-bottom: 2.25rem;
+}
+
+.sectionTag {
+  color: var(--ifm-color-primary);
+  font-size: 12px;
+  font-weight: 500;
+  letter-spacing: 0.06em;
+  margin-bottom: 0.75rem;
+  text-transform: uppercase;
+}
+
+.sectionTitle {
+  color: var(--ifm-heading-color);
+  font-size: clamp(1.9rem, 4vw, 2.55rem);
+  font-weight: 500;
+  letter-spacing: -0.025em;
+  line-height: 1.18;
+  margin: 0;
+  max-width: 720px;
+}
+
+.sectionSubtitle {
+  color: var(--ifm-color-content-secondary);
+  font-size: 1rem;
+  line-height: 1.7;
+  margin: 0;
+}
+
+.communityShell,
+.sponsorProgram {
+  border: 1px solid var(--bx-border);
+  border-radius: 4px;
+  overflow: hidden;
+}
+
+.communityShell {
+  display: grid;
+  grid-template-columns: minmax(0, 1.35fr) minmax(310px, 0.8fr);
+}
+
+.pathPanel,
+.contributorPanel {
+  min-width: 0;
+}
+
+.pathPanel {
+  border-right: 1px solid var(--bx-border);
+}
+
+.panelHeader {
+  align-items: center;
+  background: var(--bx-surface-subtle);
+  border-bottom: 1px solid var(--bx-border);
+  display: flex;
+  gap: 1rem;
+  justify-content: space-between;
+  min-height: 50px;
+  padding: 10px 14px;
+}
+
+.panelHeader > span {
+  color: var(--ifm-heading-color);
+  font-size: 13px;
+  font-weight: 500;
+}
+
+.panelHeader a {
+  align-items: center;
+  color: var(--ifm-color-primary);
+  display: inline-flex;
+  font-size: 12px;
+  gap: 5px;
+  text-decoration: none !important;
+}
+
+.pathList,
+.contributorList {
+  display: grid;
+}
+
+.pathItem {
+  align-items: center;
+  border-bottom: 1px solid var(--bx-border);
+  color: inherit;
+  display: grid;
+  gap: 11px;
+  grid-template-columns: auto auto minmax(0, 1fr) auto;
+  min-height: 100px;
+  padding: 13px 14px;
+  text-decoration: none !important;
+}
+
+.pathItem:last-child {
+  border-bottom: 0;
+}
+
+.pathItem:hover,
+.pathItem:focus-visible,
+.contributorRow:hover,
+.contributorRow:focus-visible {
+  background: var(--bx-surface-selected);
+  color: inherit;
+}
+
+.pathIndex {
+  color: var(--ifm-color-content-secondary);
+  font-family: var(--ifm-font-family-monospace);
+  font-size: 11px;
+}
+
+.pathIcon,
+.sponsorBandIcon,
+.sponsorProgramIcon,
+.sponsorFocusIcon {
+  align-items: center;
+  background: var(--bx-surface-selected);
+  border: 1px solid color-mix(in srgb, var(--ifm-color-primary) 25%, var(--bx-border));
+  border-radius: 3px;
+  color: var(--ifm-color-primary);
+  display: inline-flex;
+  justify-content: center;
+}
+
+.pathIcon {
+  height: 36px;
+  width: 36px;
+}
+
+.pathBody,
+.contributorBody,
+.sponsorBandBody,
+.sponsorFocusBody {
+  display: grid;
+  min-width: 0;
+}
+
+.pathBody {
+  gap: 3px;
+}
+
+.pathTitle,
+.contributorName,
+.sponsorBandTitle,
+.sponsorFocusTitle,
+.tierName {
+  color: var(--ifm-heading-color);
+  font-weight: 500;
+}
+
+.pathTitle {
+  font-size: 14px;
+}
+
+.pathDescription {
+  color: var(--ifm-color-content-secondary);
+  font-size: 12px;
+  line-height: 1.55;
+}
+
+.rowArrow {
+  color: var(--ifm-color-content-secondary);
+}
+
+.pathItem:hover .rowArrow,
+.pathItem:focus-visible .rowArrow {
+  color: var(--ifm-color-primary);
+}
+
+.panelNote {
+  border-bottom: 1px solid var(--bx-border);
+  color: var(--ifm-color-content-secondary);
+  font-size: 12px;
+  line-height: 1.5;
+  margin: 0;
+  padding: 10px 14px;
+}
+
+.contributorRow {
+  align-items: center;
+  border-bottom: 1px solid var(--bx-border);
+  color: inherit;
+  display: grid;
+  gap: 10px;
+  grid-template-columns: auto minmax(0, 1fr) auto;
+  min-height: 62px;
+  padding: 9px 14px;
+  text-decoration: none !important;
+}
+
+.contributorRow:last-child {
+  border-bottom: 0;
+}
+
+.avatar,
+.avatarImage {
+  border-radius: 4px;
+  height: 34px;
+  width: 34px;
+}
+
+.avatar {
+  align-items: center;
+  background: var(--ifm-color-primary);
+  color: #ffffff;
+  display: inline-flex;
+  font-size: 11px;
+  justify-content: center;
+}
+
+.avatarImage {
+  border: 1px solid var(--bx-border);
+  object-fit: cover;
+}
+
+.contributorBody {
+  gap: 1px;
+}
+
+.contributorName {
+  font-size: 13px;
+  overflow: hidden;
+  text-overflow: ellipsis;
+  white-space: nowrap;
+}
+
+.contributorRole,
+.contributionCount {
+  color: var(--ifm-color-content-secondary);
+  font-size: 11px;
+}
+
+.contributionCount {
+  white-space: nowrap;
+}
+
+.sponsorBand {
+  align-items: center;
+  background: var(--bx-surface-subtle);
+  border-top: 1px solid var(--bx-border);
+  display: grid;
+  gap: 12px;
+  grid-column: 1 / -1;
+  grid-template-columns: auto minmax(0, 1fr) auto;
+  min-height: 82px;
+  padding: 13px 14px;
+}
+
+.sponsorBandIcon {
+  height: 38px;
+  width: 38px;
+}
+
+.sponsorBandBody {
+  gap: 2px;
+}
+
+.sponsorBandTitle {
+  font-size: 14px;
+}
+
+.sponsorBandDescription {
+  color: var(--ifm-color-content-secondary);
+  font-size: 12px;
+  line-height: 1.5;
+}
+
+.sponsorBand > a,
+.sponsorAction {
+  align-items: center;
+  border: 1px solid var(--bx-border-strong);
+  border-radius: 4px;
+  color: var(--ifm-color-primary);
+  display: inline-flex;
+  font-size: 13px;
+  gap: 6px;
+  min-height: 38px;
+  padding: 0 11px;
+  text-decoration: none !important;
+  white-space: nowrap;
+}
+
+.sponsorBand > a:hover,
+.sponsorBand > a:focus-visible,
+.sponsorAction:hover,
+.sponsorAction:focus-visible {
+  background: var(--bx-surface-selected);
+  border-color: var(--ifm-color-primary);
+  color: var(--ifm-color-primary);
+}
+
+.sponsorProgramHeader {
+  align-items: center;
+  background: var(--bx-surface-subtle);
+  border-bottom: 1px solid var(--bx-border);
+  display: grid;
+  gap: 14px;
+  grid-template-columns: auto minmax(0, 1fr) auto;
+  padding: 1.4rem;
+}
+
+.sponsorProgramIcon {
+  height: 44px;
+  width: 44px;
+}
+
+.sponsorProgramCopy {
+  min-width: 0;
+}
+
+.sponsorProgramTitle {
+  color: var(--ifm-heading-color);
+  font-size: 1.25rem;
+  font-weight: 500;
+  margin: 0 0 4px;
+}
+
+.sponsorProgramCopy p {
+  color: var(--ifm-color-content-secondary);
+  font-size: 0.9rem;
+  line-height: 1.55;
+  margin: 0;
+  max-width: 740px;
+}
+
+.sponsorFocusList {
+  display: grid;
+  grid-template-columns: repeat(3, minmax(0, 1fr));
+}
+
+.sponsorFocusItem {
+  display: grid;
+  gap: 11px;
+  grid-template-columns: auto minmax(0, 1fr);
+  min-height: 190px;
+  padding: 1.4rem;
+}
+
+.sponsorFocusItem + .sponsorFocusItem {
+  border-left: 1px solid var(--bx-border);
+}
+
+.sponsorFocusIcon {
+  height: 36px;
+  width: 36px;
+}
+
+.sponsorFocusBody {
+  align-content: start;
+  gap: 5px;
+}
+
+.sponsorFocusLabel {
+  color: var(--ifm-color-primary);
+  font-size: 11px;
+  font-weight: 500;
+  letter-spacing: 0.05em;
+  text-transform: uppercase;
+}
+
+.sponsorFocusTitle {
+  font-size: 14px;
+  line-height: 1.4;
+}
+
+.sponsorFocusDescription,
+.tierDescription {
+  color: var(--ifm-color-content-secondary);
+  font-size: 12px;
+  line-height: 1.6;
+}
+
+.tierSection {
+  border-top: 1px solid var(--bx-border);
+}
+
+.tierSectionHeader {
+  align-items: baseline;
+  background: var(--bx-surface-subtle);
+  border-bottom: 1px solid var(--bx-border);
+  display: flex;
+  gap: 14px;
+  justify-content: space-between;
+  padding: 14px;
+}
+
+.tierSectionHeader h3 {
+  color: var(--ifm-heading-color);
+  font-size: 14px;
+  font-weight: 500;
+  margin: 0;
+}
+
+.tierSectionHeader p {
+  color: var(--ifm-color-content-secondary);
+  font-size: 12px;
+  margin: 0;
+  text-align: right;
+}
+
+.tierGrid {
+  display: grid;
+  grid-template-columns: repeat(3, minmax(0, 1fr));
+}
+
+.tierItem {
+  display: grid;
+  gap: 5px;
+  min-height: 150px;
+  padding: 1.25rem;
+}
+
+.tierItem + .tierItem {
+  border-left: 1px solid var(--bx-border);
+}
+
+.tierName {
+  font-size: 15px;
+}
+
+.tierAudience {
+  color: var(--ifm-color-primary);
+  font-size: 12px;
+}
+
+@media (max-width: 996px) {
+  .section {
+    padding: 4rem 0;
+  }
+
+  .sectionHead {
+    align-items: start;
+    gap: 1rem;
+    grid-template-columns: 1fr;
+  }
+
+  .communityShell {
+    grid-template-columns: 1fr;
+  }
+
+  .pathPanel {
+    border-bottom: 1px solid var(--bx-border);
+    border-right: 0;
+  }
+
+  .sponsorFocusList,
+  .tierGrid {
+    grid-template-columns: 1fr;
+  }
+
+  .sponsorFocusItem,
+  .tierItem {
+    min-height: 0;
+  }
+
+  .sponsorFocusItem + .sponsorFocusItem,
+  .tierItem + .tierItem {
+    border-left: 0;
+    border-top: 1px solid var(--bx-border);
+  }
+}
+
+@media (max-width: 640px) {
+  .section {
+    padding: 3.25rem 0;
+  }
+
+  .pathItem {
+    grid-template-columns: auto minmax(0, 1fr) auto;
+  }
+
+  .pathIndex,
+  .contributionCount {
+    display: none;
+  }
+
+  .sponsorBand,
+  .sponsorProgramHeader {
+    align-items: start;
+    grid-template-columns: auto minmax(0, 1fr);
+  }
+
+  .sponsorBand > a,
+  .sponsorAction {
+    grid-column: 1 / -1;
+    justify-content: center;
+    width: 100%;
+  }
+
+  .tierSectionHeader {
+    align-items: flex-start;
+    flex-direction: column;
+    gap: 2px;
+  }
+
+  .tierSectionHeader p {
+    text-align: left;
+  }
+}
--- a/docs-site/src/components/HomepageFeatures/index.tsx
+++ b/docs-site/src/components/HomepageFeatures/index.tsx
@@ -0,0 +1,90 @@
+import type {ReactNode} from 'react';
+import Link from '@docusaurus/Link';
+import Translate from '@docusaurus/Translate';
+import Heading from '@theme/Heading';
+import DocIcon, {type DocIconName} from '@site/src/components/DocIcon';
+import styles from './styles.module.css';
+
+type DocumentationPath = {
+  icon: DocIconName;
+  title: ReactNode;
+  description: ReactNode;
+  to: string;
+};
+
+const DOCUMENTATION_PATHS: DocumentationPath[] = [
+  {
+    icon: 'box',
+    title: <Translate id="feat.install.title">Install and upgrade</Translate>,
+    description: <Translate id="feat.install.desc">Choose Docker, Compose, or a standalone binary and keep the deployment repeatable.</Translate>,
+    to: '/docs/getting-started/installation',
+  },
+  {
+    icon: 'database',
+    title: <Translate id="feat.types.title">Protect files and databases</Translate>,
+    description: <Translate id="feat.types.desc">Configure file, MySQL, PostgreSQL, SQLite, and SAP HANA backup workloads.</Translate>,
+    to: '/docs/features/backup-types',
+  },
+  {
+    icon: 'storage',
+    title: <Translate id="feat.storage.title">Connect storage targets</Translate>,
+    description: <Translate id="feat.storage.desc">Use native providers or any supported rclone backend through one consistent flow.</Translate>,
+    to: '/docs/features/storage-backends',
+  },
+  {
+    icon: 'network',
+    title: <Translate id="feat.cluster.title">Build a remote-node cluster</Translate>,
+    description: <Translate id="feat.cluster.desc">Deploy outbound-only agents through proxies, private CAs, or SSH bastion hosts.</Translate>,
+    to: '/docs/features/multi-node',
+  },
+  {
+    icon: 'monitor',
+    title: <Translate id="feat.monitor.title">Monitor daily operations</Translate>,
+    description: <Translate id="feat.monitor.desc">Track task health, storage capacity, notifications, logs, and service readiness.</Translate>,
+    to: '/docs/operations/monitoring',
+  },
+  {
+    icon: 'restore',
+    title: <Translate id="feat.recovery.title">Recover with a tested plan</Translate>,
+    description: <Translate id="feat.recovery.desc">Prepare upgrades, rollback points, restore validation, and incident troubleshooting.</Translate>,
+    to: '/docs/operations/upgrade-recovery',
+  },
+];
+
+export default function HomepageFeatures(): ReactNode {
+  return (
+    <section className={styles.section}>
+      <div className="container">
+        <div className={styles.sectionHead}>
+          <div>
+            <div className={styles.sectionTag}>
+              <Translate id="section.features.tag">Documentation paths</Translate>
+            </div>
+            <Heading as="h2" className={styles.sectionTitle}>
+              <Translate id="section.features.title">Move from deployment to recovery without guesswork</Translate>
+            </Heading>
+          </div>
+          <p className={styles.sectionSubtitle}>
+            <Translate id="section.features.subtitle">
+              Each path connects product capability to the configuration, security, and operational decisions required in production.
+            </Translate>
+          </p>
+        </div>
+
+        <div className={styles.pathGrid}>
+          {DOCUMENTATION_PATHS.map((path, index) => (
+            <Link key={path.to} to={path.to} className={styles.pathItem}>
+              <span className={styles.pathIndex}>{String(index + 1).padStart(2, '0')}</span>
+              <span className={styles.pathIcon}><DocIcon name={path.icon} size={21} /></span>
+              <span className={styles.pathBody}>
+                <span className={styles.pathTitle}>{path.title}</span>
+                <span className={styles.pathDescription}>{path.description}</span>
+              </span>
+              <DocIcon name="arrowRight" size={18} className={styles.pathArrow} />
+            </Link>
+          ))}
+        </div>
+      </div>
+    </section>
+  );
+}
--- a/docs-site/src/components/HomepageFeatures/styles.module.css
+++ b/docs-site/src/components/HomepageFeatures/styles.module.css
@@ -0,0 +1,171 @@
+.section {
+  background: var(--ifm-background-color);
+  padding: 5rem 0;
+}
+
+.sectionHead {
+  align-items: end;
+  display: grid;
+  gap: 3rem;
+  grid-template-columns: minmax(0, 1fr) minmax(320px, 0.7fr);
+  margin-bottom: 2.25rem;
+}
+
+.sectionTag {
+  color: var(--ifm-color-primary);
+  font-size: 12px;
+  font-weight: 500;
+  letter-spacing: 0.06em;
+  margin-bottom: 0.75rem;
+  text-transform: uppercase;
+}
+
+.sectionTitle {
+  color: var(--ifm-heading-color);
+  font-size: clamp(1.9rem, 4vw, 2.55rem);
+  font-weight: 500;
+  letter-spacing: -0.025em;
+  line-height: 1.18;
+  margin: 0;
+  max-width: 710px;
+}
+
+.sectionSubtitle {
+  color: var(--ifm-color-content-secondary);
+  font-size: 1rem;
+  line-height: 1.7;
+  margin: 0;
+}
+
+.pathGrid {
+  border: 1px solid var(--bx-border);
+  border-radius: 4px;
+  display: grid;
+  grid-template-columns: repeat(2, minmax(0, 1fr));
+  overflow: hidden;
+}
+
+.pathItem {
+  align-items: start;
+  border-bottom: 1px solid var(--bx-border);
+  color: inherit;
+  display: grid;
+  gap: 12px;
+  grid-template-columns: auto auto minmax(0, 1fr) auto;
+  min-height: 154px;
+  padding: 1.4rem;
+  text-decoration: none !important;
+}
+
+.pathItem:nth-child(odd) {
+  border-right: 1px solid var(--bx-border);
+}
+
+.pathItem:nth-last-child(-n + 2) {
+  border-bottom: 0;
+}
+
+.pathItem:hover,
+.pathItem:focus-visible {
+  background: var(--bx-surface-subtle);
+  color: inherit;
+}
+
+.pathIndex {
+  color: var(--ifm-color-content-secondary);
+  font-family: var(--ifm-font-family-monospace);
+  font-size: 11px;
+  line-height: 38px;
+}
+
+.pathIcon {
+  align-items: center;
+  background: var(--bx-surface-selected);
+  border: 1px solid color-mix(in srgb, var(--ifm-color-primary) 25%, var(--bx-border));
+  border-radius: 3px;
+  color: var(--ifm-color-primary);
+  display: inline-flex;
+  height: 38px;
+  justify-content: center;
+  width: 38px;
+}
+
+.pathBody {
+  display: grid;
+  gap: 7px;
+  min-width: 0;
+  padding-top: 7px;
+}
+
+.pathTitle {
+  color: var(--ifm-heading-color);
+  font-size: 1rem;
+  font-weight: 500;
+  line-height: 1.35;
+}
+
+.pathDescription {
+  color: var(--ifm-color-content-secondary);
+  font-size: 0.9rem;
+  line-height: 1.65;
+}
+
+.pathArrow {
+  color: var(--ifm-color-content-secondary);
+  margin-top: 10px;
+}
+
+.pathItem:hover .pathArrow,
+.pathItem:focus-visible .pathArrow {
+  color: var(--ifm-color-primary);
+}
+
+@media (max-width: 996px) {
+  .section {
+    padding: 4rem 0;
+  }
+
+  .sectionHead {
+    align-items: start;
+    gap: 1rem;
+    grid-template-columns: 1fr;
+  }
+}
+
+@media (max-width: 760px) {
+  .pathGrid {
+    grid-template-columns: 1fr;
+  }
+
+  .pathItem,
+  .pathItem:nth-child(odd),
+  .pathItem:nth-last-child(-n + 2) {
+    border-bottom: 1px solid var(--bx-border);
+    border-right: 0;
+  }
+
+  .pathItem:last-child {
+    border-bottom: 0;
+  }
+}
+
+@media (max-width: 520px) {
+  .section {
+    padding: 3.25rem 0;
+  }
+
+  .pathItem {
+    gap: 10px;
+    grid-template-columns: auto minmax(0, 1fr) auto;
+    min-height: 0;
+    padding: 1rem;
+  }
+
+  .pathIndex {
+    display: none;
+  }
+
+  .pathBody {
+    padding-top: 6px;
+  }
+}
--- a/docs-site/src/components/HomepageHero/index.tsx
+++ b/docs-site/src/components/HomepageHero/index.tsx
@@ -0,0 +1,103 @@
+import type {ReactNode} from 'react';
+import Link from '@docusaurus/Link';
+import Translate, {translate} from '@docusaurus/Translate';
+import Heading from '@theme/Heading';
+import DocIcon, {type DocIconName} from '@site/src/components/DocIcon';
+import styles from './styles.module.css';
+
+type GuideLink = {
+  icon: DocIconName;
+  title: ReactNode;
+  description: ReactNode;
+  to: string;
+};
+
+const GUIDE_LINKS: GuideLink[] = [
+  {
+    icon: 'box',
+    title: <Translate id="home.guide.install.title">Install BackupX</Translate>,
+    description: <Translate id="home.guide.install.desc">Docker, Compose, or a standalone binary</Translate>,
+    to: '/docs/getting-started/installation',
+  },
+  {
+    icon: 'network',
+    title: <Translate id="home.guide.cluster.title">Connect remote nodes</Translate>,
+    description: <Translate id="home.guide.cluster.desc">Agents, proxies, private CAs, and bastion hosts</Translate>,
+    to: '/docs/features/multi-node',
+  },
+  {
+    icon: 'shield',
+    title: <Translate id="home.guide.security.title">Harden operations</Translate>,
+    description: <Translate id="home.guide.security.desc">Security controls, monitoring, and audit trails</Translate>,
+    to: '/docs/operations/security',
+  },
+  {
+    icon: 'restore',
+    title: <Translate id="home.guide.recovery.title">Prepare recovery</Translate>,
+    description: <Translate id="home.guide.recovery.desc">Upgrade, rollback, restore, and troubleshoot</Translate>,
+    to: '/docs/operations/upgrade-recovery',
+  },
+];
+
+export default function HomepageHero(): ReactNode {
+  return (
+    <header className={styles.hero}>
+      <div className={`container ${styles.heroGrid}`}>
+        <div className={styles.heroContent}>
+          <div className={styles.badge}>
+            <DocIcon name="bookOpen" size={16} />
+            <Translate id="home.badge">BackupX documentation · v2.2.1</Translate>
+          </div>
+
+          <Heading as="h1" className={styles.heroTitle}>
+            <span className={styles.heroTitleLine}><Translate id="home.title.part1">Operate BackupX</Translate></span>
+            <span className={styles.heroTitleAccent}><Translate id="home.title.part2">with confidence.</Translate></span>
+          </Heading>
+
+          <p className={styles.heroSubtitle}>
+            <Translate id="home.tagline">
+              Deploy the control plane, connect storage and remote agents, then keep backups observable and recoverable with one practical guide set.
+            </Translate>
+          </p>
+
+          <div className={styles.actions}>
+            <Link className={styles.primaryAction} to="/docs/getting-started/quick-start">
+              <DocIcon name="terminal" size={18} />
+              <Translate id="home.getStarted">Start with Docker</Translate>
+              <DocIcon name="arrowRight" size={17} />
+            </Link>
+            <Link className={styles.secondaryAction} to="https://github.com/Awuqing/BackupX">
+              <DocIcon name="github" size={18} />
+              <Translate id="home.viewSource">View source</Translate>
+            </Link>
+          </div>
+
+          <div className={styles.supported} aria-label={translate({id: 'home.supported.label', message: 'Supported environments'})}>
+            <span><DocIcon name="check" size={16} /><Translate id="home.supported.docker">Docker</Translate></span>
+            <span><DocIcon name="check" size={16} /><Translate id="home.supported.linux">Linux</Translate></span>
+            <span><DocIcon name="check" size={16} /><Translate id="home.supported.windows">Windows agents</Translate></span>
+          </div>
+        </div>
+
+        <nav className={styles.guidePanel} aria-label={translate({id: 'home.guide.label', message: 'Recommended documentation paths'})}>
+          <div className={styles.guidePanelHeader}>
+            <span><Translate id="home.guide.kicker">Start here</Translate></span>
+            <span><Translate id="home.guide.hint">Choose a guide for the next task</Translate></span>
+          </div>
+          <div className={styles.guideList}>
+            {GUIDE_LINKS.map(guide => (
+              <Link key={guide.to} className={styles.guideLink} to={guide.to}>
+                <span className={styles.guideIcon}><DocIcon name={guide.icon} size={20} /></span>
+                <span className={styles.guideBody}>
+                  <span className={styles.guideTitle}>{guide.title}</span>
+                  <span className={styles.guideDescription}>{guide.description}</span>
+                </span>
+                <DocIcon name="arrowRight" size={17} className={styles.guideArrow} />
+              </Link>
+            ))}
+          </div>
+        </nav>
+      </div>
+    </header>
+  );
+}
--- a/docs-site/src/components/HomepageHero/styles.module.css
+++ b/docs-site/src/components/HomepageHero/styles.module.css
@@ -0,0 +1,273 @@
+.hero {
+  background: var(--bx-surface-subtle);
+  border-bottom: 1px solid var(--bx-border);
+  padding: 5.5rem 0 4.75rem;
+}
+
+.heroGrid {
+  align-items: center;
+  display: grid;
+  gap: 4.5rem;
+  grid-template-columns: minmax(0, 1fr) minmax(410px, 0.88fr);
+}
+
+.heroContent {
+  align-items: flex-start;
+  display: flex;
+  flex-direction: column;
+}
+
+.badge {
+  align-items: center;
+  background: var(--bx-surface-selected);
+  border: 1px solid color-mix(in srgb, var(--ifm-color-primary) 28%, var(--bx-border));
+  border-radius: 3px;
+  color: var(--ifm-color-primary);
+  display: inline-flex;
+  font-size: 13px;
+  font-weight: 400;
+  gap: 7px;
+  margin-bottom: 1.5rem;
+  min-height: 30px;
+  padding: 4px 9px;
+}
+
+.heroTitle {
+  color: var(--ifm-heading-color);
+  font-size: clamp(2.55rem, 5vw, 3.7rem);
+  font-weight: 500;
+  letter-spacing: -0.035em;
+  line-height: 1.06;
+  margin: 0;
+  max-width: 720px;
+}
+
+.heroTitleLine,
+.heroTitleAccent {
+  display: block;
+}
+
+.heroTitleLine {
+  color: var(--ifm-heading-color);
+}
+
+.heroTitleAccent {
+  color: var(--ifm-color-primary);
+}
+
+.heroSubtitle {
+  color: var(--ifm-color-content-secondary);
+  font-size: 1.08rem;
+  line-height: 1.72;
+  margin: 1.5rem 0 0;
+  max-width: 650px;
+}
+
+.actions {
+  display: flex;
+  flex-wrap: wrap;
+  gap: 10px;
+  margin-top: 1.75rem;
+}
+
+.primaryAction,
+.secondaryAction {
+  align-items: center;
+  border: 1px solid var(--ifm-color-primary);
+  border-radius: 4px;
+  display: inline-flex;
+  font-size: 14px;
+  font-weight: 400;
+  gap: 8px;
+  justify-content: center;
+  min-height: 44px;
+  padding: 0 15px;
+  text-decoration: none !important;
+}
+
+.primaryAction {
+  background: var(--ifm-color-primary);
+  color: #ffffff;
+}
+
+.primaryAction:hover,
+.primaryAction:focus-visible {
+  background: var(--ifm-color-primary-dark);
+  border-color: var(--ifm-color-primary-dark);
+  color: #ffffff;
+}
+
+.secondaryAction {
+  background: var(--ifm-background-color);
+  border-color: var(--bx-border-strong);
+  color: var(--ifm-color-content);
+}
+
+.secondaryAction:hover,
+.secondaryAction:focus-visible {
+  background: var(--bx-surface-selected);
+  border-color: var(--ifm-color-primary);
+  color: var(--ifm-color-primary);
+}
+
+.supported {
+  color: var(--ifm-color-content-secondary);
+  display: flex;
+  flex-wrap: wrap;
+  font-size: 13px;
+  gap: 10px 18px;
+  margin-top: 1.4rem;
+}
+
+.supported span {
+  align-items: center;
+  display: inline-flex;
+  gap: 5px;
+}
+
+.supported svg {
+  color: var(--bx-success);
+}
+
+.guidePanel {
+  background: var(--ifm-background-color);
+  border: 1px solid var(--bx-border-strong);
+  border-radius: 4px;
+  overflow: hidden;
+}
+
+.guidePanelHeader {
+  align-items: baseline;
+  border-bottom: 1px solid var(--bx-border);
+  display: flex;
+  gap: 12px;
+  justify-content: space-between;
+  padding: 14px 16px;
+}
+
+.guidePanelHeader span:first-child {
+  color: var(--ifm-heading-color);
+  font-size: 14px;
+  font-weight: 500;
+}
+
+.guidePanelHeader span:last-child {
+  color: var(--ifm-color-content-secondary);
+  font-size: 12px;
+  text-align: right;
+}
+
+.guideList {
+  display: grid;
+}
+
+.guideLink {
+  align-items: center;
+  border-bottom: 1px solid var(--bx-border);
+  color: inherit;
+  display: grid;
+  gap: 12px;
+  grid-template-columns: auto minmax(0, 1fr) auto;
+  min-height: 82px;
+  padding: 13px 16px;
+  text-decoration: none !important;
+}
+
+.guideLink:last-child {
+  border-bottom: 0;
+}
+
+.guideLink:hover,
+.guideLink:focus-visible {
+  background: var(--bx-surface-selected);
+  color: inherit;
+}
+
+.guideIcon {
+  align-items: center;
+  background: var(--bx-surface-subtle);
+  border: 1px solid var(--bx-border);
+  border-radius: 3px;
+  color: var(--ifm-color-primary);
+  display: inline-flex;
+  height: 38px;
+  justify-content: center;
+  width: 38px;
+}
+
+.guideBody {
+  display: grid;
+  gap: 2px;
+  min-width: 0;
+}
+
+.guideTitle {
+  color: var(--ifm-heading-color);
+  font-size: 14px;
+  font-weight: 500;
+}
+
+.guideDescription {
+  color: var(--ifm-color-content-secondary);
+  font-size: 12px;
+  line-height: 1.5;
+}
+
+.guideArrow {
+  color: var(--ifm-color-content-secondary);
+}
+
+.guideLink:hover .guideArrow,
+.guideLink:focus-visible .guideArrow {
+  color: var(--ifm-color-primary);
+}
+
+@media (max-width: 996px) {
+  .hero {
+    padding: 4.25rem 0 3.75rem;
+  }
+
+  .heroGrid {
+    gap: 2.75rem;
+    grid-template-columns: 1fr;
+  }
+
+  .heroContent {
+    max-width: 760px;
+  }
+}
+
+@media (max-width: 640px) {
+  .hero {
+    padding: 3.25rem 0 2.75rem;
+  }
+
+  .heroTitle {
+    font-size: 2.35rem;
+  }
+
+  .heroSubtitle {
+    font-size: 1rem;
+  }
+
+  .actions,
+  .primaryAction,
+  .secondaryAction {
+    width: 100%;
+  }
+
+  .guidePanelHeader {
+    align-items: flex-start;
+    flex-direction: column;
+    gap: 2px;
+  }
+
+  .guidePanelHeader span:last-child {
+    text-align: left;
+  }
+
+  .guideLink {
+    min-height: 78px;
+    padding: 12px;
+  }
+}
--- a/docs-site/src/components/HomepageShowcase/index.tsx
+++ b/docs-site/src/components/HomepageShowcase/index.tsx
@@ -0,0 +1,153 @@
+import type {ReactNode} from 'react';
+import {useState} from 'react';
+import clsx from 'clsx';
+import Heading from '@theme/Heading';
+import Translate, {translate} from '@docusaurus/Translate';
+import useBaseUrl from '@docusaurus/useBaseUrl';
+import Link from '@docusaurus/Link';
+import DocIcon, {type DocIconName} from '@site/src/components/DocIcon';
+import styles from './styles.module.css';
+
+type Tab = {
+  id: string;
+  label: ReactNode;
+  icon: DocIconName;
+  image: string;
+  imageAlt: string;
+  title: ReactNode;
+  description: ReactNode;
+};
+
+function useTabs(): Tab[] {
+  return [
+    {
+      id: 'dashboard',
+      label: <Translate id="showcase.tab.dashboard">Dashboard</Translate>,
+      icon: 'monitor',
+      image: useBaseUrl('/img/screenshots/dashboard.png'),
+      imageAlt: translate({
+        id: 'showcase.dashboard.alt',
+        message: 'BackupX dashboard showing 30-day backup trends, storage distribution, task volume and cluster health',
+      }),
+      title: <Translate id="showcase.dashboard.title">Operations at a glance</Translate>,
+      description: (
+        <Translate id="showcase.dashboard.desc">
+          Track 30-day success and failure trends, storage distribution, task counts, data volume and recent runs from one live operations view.
+        </Translate>
+      ),
+    },
+    {
+      id: 'tasks',
+      label: <Translate id="showcase.tab.tasks">Backup Tasks</Translate>,
+      icon: 'database',
+      image: useBaseUrl('/img/screenshots/backup-tasks.png'),
+      imageAlt: translate({
+        id: 'showcase.tasks.alt',
+        message: 'BackupX task list showing schedules, storage targets, retention, tags, RPO goals and verification status',
+      }),
+      title: <Translate id="showcase.tasks.title">Policies you can scan</Translate>,
+      description: (
+        <Translate id="showcase.tasks.desc">
+          Review schedules, multi-target policies, retention, tags, RPO goals and verification status together, then act on any task in one click.
+        </Translate>
+      ),
+    },
+    {
+      id: 'storage',
+      label: <Translate id="showcase.tab.storage">Storage Targets</Translate>,
+      icon: 'storage',
+      image: useBaseUrl('/img/screenshots/storage-targets.png'),
+      imageAlt: translate({
+        id: 'showcase.storage.alt',
+        message: 'BackupX storage targets showing connection health, live capacity, favourites and redundancy roles',
+      }),
+      title: <Translate id="showcase.storage.title">Every target, one view</Translate>,
+      description: (
+        <Translate id="showcase.storage.desc">
+          Compare connection health, live capacity, favourites and redundancy roles across local disks and 70+ remote backends.
+        </Translate>
+      ),
+    },
+    {
+      id: 'nodes',
+      label: <Translate id="showcase.tab.nodes">Multi-Node</Translate>,
+      icon: 'network',
+      image: useBaseUrl('/img/screenshots/nodes.png'),
+      imageAlt: translate({
+        id: 'showcase.nodes.alt',
+        message: 'BackupX node list showing health, Agent versions, queue depth, labels and heartbeat times',
+      }),
+      title: <Translate id="showcase.nodes.title">Cluster health in one view</Translate>,
+      description: (
+        <Translate id="showcase.nodes.desc">
+          Monitor health, Agent versions, queue depth, labels and heartbeat time across the local Master and every remote node.
+        </Translate>
+      ),
+    },
+  ];
+}
+
+export default function HomepageShowcase(): ReactNode {
+  const tabs = useTabs();
+  const [active, setActive] = useState(tabs[0].id);
+  const current = tabs.find(t => t.id === active) ?? tabs[0];
+  return (
+    <section className={styles.section}>
+      <div className="container">
+        <div className={styles.sectionHead}>
+          <div>
+            <div className={styles.sectionTag}>
+              <Translate id="showcase.tag">Product interface</Translate>
+            </div>
+            <Heading as="h2" className={styles.sectionTitle}>
+              <Translate id="showcase.title">See the workflow before you deploy</Translate>
+            </Heading>
+          </div>
+          <p className={styles.sectionSubtitle}>
+            <Translate id="showcase.subtitle">
+              Screenshots stay connected to the guide that explains the underlying task, configuration, and operating model.
+            </Translate>
+          </p>
+        </div>
+        <div className={styles.tabs} role="tablist" aria-label={translate({id: 'showcase.tabs.label', message: 'BackupX product screens'})}>
+          {tabs.map(tab => (
+            <button
+              key={tab.id}
+              id={`showcase-tab-${tab.id}`}
+              type="button"
+              role="tab"
+              aria-selected={active === tab.id}
+              aria-controls="showcase-panel"
+              className={clsx(styles.tabBtn, active === tab.id && styles.tabBtnActive)}
+              onClick={() => setActive(tab.id)}>
+              <DocIcon name={tab.icon} size={17} />
+              {tab.label}
+            </button>
+          ))}
+        </div>
+        <div
+          id="showcase-panel"
+          role="tabpanel"
+          aria-labelledby={`showcase-tab-${current.id}`}
+          className={styles.stage}>
+          <div className={styles.preview}>
+            <div className={styles.previewBar}>
+              <span><DocIcon name="monitor" size={16} /><Translate id="showcase.preview.label">BackupX console</Translate></span>
+              <code>backupx.local</code>
+            </div>
+            <img src={current.image} alt={current.imageAlt} className={styles.screenshot} />
+          </div>
+          <div className={styles.caption}>
+            <div className={styles.captionKicker}>{current.label}</div>
+            <Heading as="h3" className={styles.captionTitle}>{current.title}</Heading>
+            <p className={styles.captionDesc}>{current.description}</p>
+            <Link to="/docs/getting-started/quick-start" className={styles.captionLink}>
+              <Translate id="showcase.cta">Explore the docs</Translate>
+              <DocIcon name="arrowRight" size={17} />
+            </Link>
+          </div>
+        </div>
+      </div>
+    </section>
+  );
+}
--- a/docs-site/src/components/HomepageShowcase/styles.module.css
+++ b/docs-site/src/components/HomepageShowcase/styles.module.css
@@ -0,0 +1,224 @@
+.section {
+  background: var(--bx-surface-subtle);
+  border-bottom: 1px solid var(--bx-border);
+  border-top: 1px solid var(--bx-border);
+  padding: 5rem 0;
+}
+
+.sectionHead {
+  align-items: end;
+  display: grid;
+  gap: 3rem;
+  grid-template-columns: minmax(0, 1fr) minmax(320px, 0.7fr);
+  margin-bottom: 2.25rem;
+}
+
+.sectionTag {
+  color: var(--ifm-color-primary);
+  font-size: 12px;
+  font-weight: 500;
+  letter-spacing: 0.06em;
+  margin-bottom: 0.75rem;
+  text-transform: uppercase;
+}
+
+.sectionTitle {
+  color: var(--ifm-heading-color);
+  font-size: clamp(1.9rem, 4vw, 2.55rem);
+  font-weight: 500;
+  letter-spacing: -0.025em;
+  line-height: 1.18;
+  margin: 0;
+  max-width: 700px;
+}
+
+.sectionSubtitle {
+  color: var(--ifm-color-content-secondary);
+  font-size: 1rem;
+  line-height: 1.7;
+  margin: 0;
+}
+
+.tabs {
+  border: 1px solid var(--bx-border);
+  border-bottom: 0;
+  border-radius: 4px 4px 0 0;
+  display: flex;
+  gap: 4px;
+  overflow-x: auto;
+  padding: 6px;
+}
+
+.tabBtn {
+  align-items: center;
+  background: transparent;
+  border: 1px solid transparent;
+  border-radius: 3px;
+  color: var(--ifm-color-content-secondary);
+  cursor: pointer;
+  display: inline-flex;
+  flex: 1 0 auto;
+  font-size: 14px;
+  font-weight: 400;
+  gap: 7px;
+  justify-content: center;
+  min-height: 40px;
+  padding: 7px 14px;
+}
+
+.tabBtn:hover {
+  background: var(--ifm-background-color);
+  border-color: var(--bx-border);
+  color: var(--ifm-color-primary);
+}
+
+.tabBtnActive,
+.tabBtnActive:hover {
+  background: var(--bx-surface-selected);
+  border-color: color-mix(in srgb, var(--ifm-color-primary) 30%, var(--bx-border));
+  color: var(--ifm-color-primary);
+}
+
+.stage {
+  background: var(--ifm-background-color);
+  border: 1px solid var(--bx-border);
+  border-radius: 0 0 4px 4px;
+  display: grid;
+  grid-template-columns: minmax(0, 1.6fr) minmax(300px, 0.74fr);
+  overflow: hidden;
+}
+
+.preview {
+  border-right: 1px solid var(--bx-border);
+  min-width: 0;
+}
+
+.previewBar {
+  align-items: center;
+  background: var(--bx-surface-subtle);
+  border-bottom: 1px solid var(--bx-border);
+  color: var(--ifm-color-content-secondary);
+  display: flex;
+  font-size: 12px;
+  justify-content: space-between;
+  min-height: 42px;
+  padding: 8px 12px;
+}
+
+.previewBar span {
+  align-items: center;
+  display: inline-flex;
+  gap: 7px;
+}
+
+.previewBar code {
+  background: var(--ifm-background-color);
+  border: 1px solid var(--bx-border);
+  border-radius: 3px;
+  color: var(--ifm-color-content-secondary);
+  font-size: 11px;
+  padding: 2px 7px;
+}
+
+.screenshot {
+  background: var(--ifm-background-color);
+  display: block;
+  height: auto;
+  width: 100%;
+}
+
+.caption {
+  align-content: center;
+  display: grid;
+  padding: 2rem;
+}
+
+.captionKicker {
+  color: var(--ifm-color-primary);
+  font-size: 12px;
+  font-weight: 500;
+  letter-spacing: 0.05em;
+  margin-bottom: 0.75rem;
+  text-transform: uppercase;
+}
+
+.captionTitle {
+  color: var(--ifm-heading-color);
+  font-size: 1.65rem;
+  font-weight: 500;
+  letter-spacing: -0.02em;
+  line-height: 1.25;
+  margin: 0 0 0.9rem;
+}
+
+.captionDesc {
+  color: var(--ifm-color-content-secondary);
+  font-size: 0.96rem;
+  line-height: 1.7;
+  margin: 0 0 1.25rem;
+}
+
+.captionLink {
+  align-items: center;
+  color: var(--ifm-color-primary);
+  display: inline-flex;
+  font-size: 14px;
+  font-weight: 500;
+  gap: 6px;
+  justify-self: start;
+  text-decoration: none !important;
+}
+
+.captionLink:hover,
+.captionLink:focus-visible {
+  color: var(--ifm-color-primary-dark);
+}
+
+@media (max-width: 996px) {
+  .section {
+    padding: 4rem 0;
+  }
+
+  .sectionHead {
+    align-items: start;
+    gap: 1rem;
+    grid-template-columns: 1fr;
+  }
+
+  .stage {
+    grid-template-columns: 1fr;
+  }
+
+  .preview {
+    border-bottom: 1px solid var(--bx-border);
+    border-right: 0;
+  }
+
+  .caption {
+    padding: 1.5rem;
+  }
+}
+
+@media (max-width: 640px) {
+  .section {
+    padding: 3.25rem 0;
+  }
+
+  .tabs {
+    display: grid;
+    grid-template-columns: repeat(2, minmax(0, 1fr));
+  }
+
+  .tabBtn {
+    min-width: 0;
+    padding: 7px 8px;
+  }
+
+  .previewBar code {
+    display: none;
+  }
+
+  .caption {
+    padding: 1.25rem;
+  }
+}
--- a/docs-site/src/css/custom.css
+++ b/docs-site/src/css/custom.css
@@ -0,0 +1,501 @@
+/**
+ * BackupX documentation UI
+ * Flat, operational and consistent with the product interface.
+ */
+
+:root {
+  --ifm-color-primary: #175cd3;
+  --ifm-color-primary-dark: #1452bd;
+  --ifm-color-primary-darker: #124bad;
+  --ifm-color-primary-darkest: #0e3c8a;
+  --ifm-color-primary-light: #2a6bd7;
+  --ifm-color-primary-lighter: #3978dc;
+  --ifm-color-primary-lightest: #6d9be5;
+
+  --ifm-background-color: #ffffff;
+  --ifm-background-surface-color: #ffffff;
+  --ifm-color-emphasis-100: #f6f7f9;
+  --ifm-color-emphasis-200: #e4e7ec;
+  --ifm-color-emphasis-300: #d0d5dd;
+  --ifm-color-emphasis-400: #98a2b3;
+  --ifm-color-emphasis-600: #475467;
+  --ifm-color-content: #202939;
+  --ifm-color-content-secondary: #596579;
+  --ifm-heading-color: #111827;
+
+  --ifm-font-family-base: -apple-system, BlinkMacSystemFont, 'Segoe UI', 'PingFang SC', 'Hiragino Sans GB', 'Microsoft YaHei', sans-serif;
+  --ifm-font-family-monospace: ui-monospace, 'SFMono-Regular', Menlo, Monaco, Consolas, monospace;
+  --ifm-font-weight-bold: 500;
+  --ifm-heading-font-weight: 500;
+  --ifm-h1-font-size: 2.15rem;
+  --ifm-h2-font-size: 1.6rem;
+  --ifm-h3-font-size: 1.24rem;
+  --ifm-line-height-base: 1.72;
+  --ifm-code-font-size: 92%;
+  --ifm-global-radius: 4px;
+  --ifm-global-shadow-lw: none;
+  --ifm-global-shadow-md: none;
+  --ifm-global-shadow-tl: none;
+  --ifm-container-width: 1160px;
+  --ifm-container-width-xl: 1280px;
+
+  --ifm-navbar-height: 58px;
+  --ifm-navbar-background-color: #ffffff;
+  --ifm-navbar-link-color: #475467;
+  --ifm-navbar-link-hover-color: #175cd3;
+  --ifm-navbar-shadow: none;
+
+  --ifm-menu-color: #475467;
+  --ifm-menu-color-background-active: #eef4ff;
+  --ifm-menu-color-background-hover: #f6f7f9;
+  --ifm-toc-border-color: transparent;
+
+  --ifm-code-background: #f2f4f7;
+  --docusaurus-highlighted-code-line-bg: #eaf1fb;
+
+  --bx-border: #e4e7ec;
+  --bx-border-strong: #d0d5dd;
+  --bx-surface-subtle: #f8f9fb;
+  --bx-surface-selected: #eef4ff;
+  --bx-success: #168453;
+  --bx-warning: #b54708;
+}
+
+[data-theme='dark'] {
+  --ifm-color-primary: #84adff;
+  --ifm-color-primary-dark: #6f9df5;
+  --ifm-color-primary-darker: #5f8fe9;
+  --ifm-color-primary-darkest: #4776c9;
+  --ifm-color-primary-light: #98bbff;
+  --ifm-color-primary-lighter: #aac7ff;
+  --ifm-color-primary-lightest: #c7d8ff;
+
+  --ifm-background-color: #0f141c;
+  --ifm-background-surface-color: #151b24;
+  --ifm-color-emphasis-100: #1a222d;
+  --ifm-color-emphasis-200: #273240;
+  --ifm-color-emphasis-300: #344054;
+  --ifm-color-emphasis-400: #667085;
+  --ifm-color-emphasis-600: #98a2b3;
+  --ifm-color-content: #d0d5dd;
+  --ifm-color-content-secondary: #98a2b3;
+  --ifm-heading-color: #f2f4f7;
+
+  --ifm-navbar-background-color: #0f141c;
+  --ifm-navbar-link-color: #c7ced8;
+  --ifm-menu-color: #c7ced8;
+  --ifm-menu-color-background-active: #1c2c48;
+  --ifm-menu-color-background-hover: #1a222d;
+
+  --ifm-code-background: #1c2531;
+  --docusaurus-highlighted-code-line-bg: #213352;
+
+  --bx-border: #273240;
+  --bx-border-strong: #344054;
+  --bx-surface-subtle: #131a23;
+  --bx-surface-selected: #1c2c48;
+  --bx-success: #6ce9a6;
+  --bx-warning: #fec84b;
+}
+
+html {
+  scroll-padding-top: calc(var(--ifm-navbar-height) + 20px);
+}
+
+body {
+  text-rendering: optimizeLegibility;
+}
+
+strong,
+b {
+  font-weight: 500;
+}
+
+a,
+button,
+.button {
+  transition: color 160ms ease, background-color 160ms ease, border-color 160ms ease;
+}
+
+:focus-visible {
+  outline: 2px solid var(--ifm-color-primary);
+  outline-offset: 2px;
+}
+
+.button {
+  border-radius: 4px;
+  font-weight: 400;
+}
+
+.button--primary {
+  color: #ffffff;
+}
+
+.navbar {
+  border-bottom: 1px solid var(--bx-border);
+}
+
+.navbar__brand {
+  gap: 8px;
+  margin-right: 1.5rem;
+}
+
+.navbar__logo {
+  height: 28px;
+}
+
+.navbar__title {
+  font-size: 1rem;
+  font-weight: 500;
+  letter-spacing: 0;
+}
+
+.navbar__link {
+  font-size: 14px;
+  font-weight: 400;
+}
+
+.navbar__item.dropdown .navbar__link::after {
+  border-width: 0 1px 1px 0;
+  height: 6px;
+  margin-left: 7px;
+  transform: rotate(45deg) translateY(-2px);
+  width: 6px;
+}
+
+.dropdown__menu {
+  background: var(--ifm-background-surface-color);
+  border: 1px solid var(--bx-border);
+  border-radius: 4px;
+  padding: 4px;
+}
+
+.dropdown__link {
+  border-radius: 2px;
+  font-size: 14px;
+}
+
+.navbar-sidebar {
+  background: var(--ifm-background-color);
+}
+
+.navbar-sidebar__brand {
+  border-bottom: 1px solid var(--bx-border);
+}
+
+.theme-doc-sidebar-container {
+  border-right: 1px solid var(--bx-border) !important;
+}
+
+.theme-doc-sidebar-menu {
+  padding: 1rem 0.75rem 2rem;
+}
+
+.menu__list-item-collapsible {
+  border-radius: 4px;
+}
+
+.menu__link {
+  border-radius: 3px;
+  font-size: 14px;
+  font-weight: 400;
+  line-height: 1.45;
+  padding: 7px 10px;
+}
+
+.menu__link--active,
+.menu__link--active:hover {
+  color: var(--ifm-color-primary);
+  font-weight: 500;
+}
+
+.menu__caret::before,
+.menu__link--sublist-caret::after {
+  background-size: 1.15rem 1.15rem;
+}
+
+.breadcrumbs {
+  align-items: center;
+  font-size: 13px;
+  margin-bottom: 1.5rem;
+}
+
+.breadcrumbs__link {
+  background: transparent;
+  border-radius: 2px;
+  color: var(--ifm-color-content-secondary);
+  padding: 3px 5px;
+}
+
+.breadcrumbs__item--active .breadcrumbs__link {
+  color: var(--ifm-color-content);
+}
+
+.theme-doc-markdown {
+  max-width: 860px;
+}
+
+.theme-doc-markdown header + h1,
+.theme-doc-markdown > h1:first-child {
+  font-size: clamp(1.9rem, 4vw, 2.35rem);
+  line-height: 1.2;
+  margin-bottom: 1rem;
+}
+
+.markdown > p:first-of-type {
+  color: var(--ifm-color-content-secondary);
+  font-size: 1.04rem;
+}
+
+.markdown h2 {
+  border-top: 1px solid var(--bx-border);
+  margin-top: 2.75rem;
+  padding-top: 1.1rem;
+}
+
+.markdown h3 {
+  margin-top: 2rem;
+}
+
+.markdown h2,
+.markdown h3,
+.markdown h4 {
+  font-weight: 500;
+  letter-spacing: 0;
+}
+
+.markdown a:not(.hash-link) {
+  text-decoration-color: color-mix(in srgb, var(--ifm-color-primary) 45%, transparent);
+  text-underline-offset: 3px;
+}
+
+.markdown ul,
+.markdown ol {
+  padding-left: 1.35rem;
+}
+
+.markdown li + li {
+  margin-top: 0.35rem;
+}
+
+.markdown blockquote {
+  background: var(--bx-surface-subtle);
+  border: 1px solid var(--bx-border);
+  border-radius: 4px;
+  color: var(--ifm-color-content-secondary);
+  margin: 1.5rem 0;
+  padding: 0.9rem 1rem;
+}
+
+.markdown blockquote > :last-child {
+  margin-bottom: 0;
+}
+
+.markdown table {
+  border: 1px solid var(--bx-border);
+  border-collapse: separate;
+  border-radius: 4px;
+  border-spacing: 0;
+  display: table;
+  overflow: hidden;
+  width: 100%;
+}
+
+.markdown table thead tr {
+  background: var(--bx-surface-subtle);
+}
+
+.markdown table th,
+.markdown table td {
+  border: 0;
+  border-bottom: 1px solid var(--bx-border);
+  border-right: 1px solid var(--bx-border);
+  padding: 9px 12px;
+  text-align: left;
+}
+
+.markdown table th {
+  font-weight: 500;
+}
+
+.markdown table th:last-child,
+.markdown table td:last-child {
+  border-right: 0;
+}
+
+.markdown table tr:last-child td {
+  border-bottom: 0;
+}
+
+code {
+  background: var(--ifm-code-background);
+  border: 1px solid var(--bx-border);
+  border-radius: 3px;
+  font-size: 0.92em;
+  padding: 1px 5px;
+}
+
+pre code {
+  border: 0;
+  padding: 0;
+}
+
+.theme-code-block {
+  border: 1px solid var(--bx-border);
+  border-radius: 4px;
+  overflow: hidden;
+}
+
+.theme-code-block pre {
+  border-radius: 0;
+}
+
+.theme-admonition {
+  border: 1px solid var(--bx-border-strong) !important;
+  border-left-width: 1px !important;
+  border-radius: 4px;
+}
+
+.theme-admonition-heading h5 {
+  font-weight: 500;
+}
+
+details {
+  background: var(--bx-surface-subtle);
+  border: 1px solid var(--bx-border) !important;
+  border-radius: 4px;
+}
+
+details > summary {
+  font-weight: 500;
+}
+
+.table-of-contents {
+  border-left: 0;
+  border-top: 1px solid var(--bx-border);
+  font-size: 13px;
+  padding: 0.8rem 0 0;
+}
+
+.table-of-contents__link {
+  color: var(--ifm-color-content-secondary);
+}
+
+.table-of-contents__link--active {
+  color: var(--ifm-color-primary);
+  font-weight: 500;
+}
+
+.pagination-nav {
+  gap: 12px;
+}
+
+.pagination-nav__link {
+  border: 1px solid var(--bx-border);
+  border-radius: 4px;
+  padding: 0.9rem 1rem;
+}
+
+.pagination-nav__link:hover {
+  background: var(--bx-surface-subtle);
+  border-color: var(--ifm-color-primary);
+}
+
+.pagination-nav__sublabel {
+  color: var(--ifm-color-content-secondary);
+  font-size: 12px;
+  font-weight: 400;
+}
+
+.pagination-nav__label {
+  font-size: 14px;
+  font-weight: 500;
+}
+
+.theme-edit-this-page,
+.theme-last-updated {
+  font-size: 13px;
+}
+
+.footer {
+  --ifm-footer-background-color: #101828;
+  --ifm-footer-color: #98a2b3;
+  --ifm-footer-link-color: #d0d5dd;
+  --ifm-footer-link-hover-color: #ffffff;
+  --ifm-footer-title-color: #f2f4f7;
+  border-top: 1px solid #273240;
+  padding: 3rem 0 2rem;
+}
+
+.footer__title {
+  font-size: 13px;
+  font-weight: 500;
+  letter-spacing: 0;
+}
+
+.footer__link-item {
+  font-size: 14px;
+}
+
+.footer__bottom {
+  border-top: 1px solid #273240;
+  margin-top: 2rem;
+  padding-top: 1.5rem;
+}
+
+.footer__copyright {
+  color: #98a2b3;
+  font-size: 13px;
+}
+
+::-webkit-scrollbar {
+  height: 10px;
+  width: 10px;
+}
+
+::-webkit-scrollbar-thumb {
+  background: var(--ifm-color-emphasis-300);
+  border: 2px solid var(--ifm-background-color);
+  border-radius: 4px;
+}
+
+::-webkit-scrollbar-thumb:hover {
+  background: var(--ifm-color-emphasis-400);
+}
+
+@media (max-width: 996px) {
+  :root {
+    --ifm-navbar-height: 54px;
+  }
+
+  .theme-doc-markdown {
+    max-width: none;
+  }
+
+  .markdown table {
+    display: block;
+    overflow-x: auto;
+  }
+}
+
+@media (max-width: 576px) {
+  .pagination-nav {
+    display: grid;
+    grid-template-columns: 1fr;
+  }
+
+  .footer {
+    padding-top: 2.25rem;
+  }
+}
+
+@media (prefers-reduced-motion: reduce) {
+  *,
+  *::before,
+  *::after {
+    animation-duration: 0.01ms !important;
+    animation-iteration-count: 1 !important;
+    scroll-behavior: auto !important;
+    transition-duration: 0.01ms !important;
+  }
+}
--- a/docs-site/src/pages/community.tsx
+++ b/docs-site/src/pages/community.tsx
@@ -0,0 +1,19 @@
+import type {ReactNode} from 'react';
+import {translate} from '@docusaurus/Translate';
+import Layout from '@theme/Layout';
+import HomepageCommunity from '@site/src/components/HomepageCommunity';
+
+export default function Community(): ReactNode {
+  return (
+    <Layout
+      title={translate({id: 'community.pageTitle', message: 'Community, sponsors and contributors'})}
+      description={translate({
+        id: 'community.pageDescription',
+        message: 'Sponsor BackupX, meet contributors, and find practical ways to contribute.',
+      })}>
+      <main>
+        <HomepageCommunity />
+      </main>
+    </Layout>
+  );
+}
--- a/docs-site/src/pages/index.tsx
+++ b/docs-site/src/pages/index.tsx
@@ -0,0 +1,24 @@
+import type {ReactNode} from 'react';
+import {translate} from '@docusaurus/Translate';
+import useDocusaurusContext from '@docusaurus/useDocusaurusContext';
+import Layout from '@theme/Layout';
+import HomepageHero from '@site/src/components/HomepageHero';
+import HomepageFeatures from '@site/src/components/HomepageFeatures';
+import HomepageShowcase from '@site/src/components/HomepageShowcase';
+import HomepageCommunity from '@site/src/components/HomepageCommunity';
+
+export default function Home(): ReactNode {
+  const {siteConfig} = useDocusaurusContext();
+  return (
+    <Layout
+      title={translate({id: 'home.pageTitle', message: 'Backup orchestration for self-hosted servers'})}
+      description={siteConfig.tagline}>
+      <HomepageHero />
+      <main>
+        <HomepageFeatures />
+        <HomepageShowcase />
+        <HomepageCommunity />
+      </main>
+    </Layout>
+  );
+}
--- a/docs-site/src/pages/sponsors.tsx
+++ b/docs-site/src/pages/sponsors.tsx
@@ -0,0 +1,41 @@
+import type {ReactNode} from 'react';
+import {translate} from '@docusaurus/Translate';
+import Translate from '@docusaurus/Translate';
+import Layout from '@theme/Layout';
+import Heading from '@theme/Heading';
+import {HomepageSponsors} from '@site/src/components/HomepageCommunity';
+import styles from '@site/src/components/HomepageCommunity/styles.module.css';
+
+export default function Sponsors(): ReactNode {
+  return (
+    <Layout
+      title={translate({id: 'sponsors.pageTitle', message: 'Sponsors'})}
+      description={translate({
+        id: 'sponsors.pageDescription',
+        message: 'Sponsor BackupX reliability, documentation, storage compatibility and long-term maintenance.',
+      })}>
+      <main>
+        <section className={styles.section}>
+          <div className="container">
+            <div className={styles.sectionHead}>
+              <div>
+                <div className={styles.sectionTag}>
+                  <Translate id="sponsors.tag">Sponsorship</Translate>
+                </div>
+                <Heading as="h1" className={styles.sectionTitle}>
+                  <Translate id="sponsors.title">Keep critical maintenance moving</Translate>
+                </Heading>
+              </div>
+              <p className={styles.sectionSubtitle}>
+                <Translate id="sponsors.subtitle">
+                  Sponsorship funds real provider validation, reliable releases, recovery drills, and better operational documentation.
+                </Translate>
+              </p>
+            </div>
+            <HomepageSponsors />
+          </div>
+        </section>
+      </main>
+    </Layout>
+  );
+}
--- a/docs-site/static/.nojekyll
+++ b/docs-site/static/.nojekyll
--- a/docs-site/static/img/favicon.ico
+++ b/docs-site/static/img/favicon.ico
--- a/docs-site/static/img/logo.svg
+++ b/docs-site/static/img/logo.svg
@@ -0,0 +1,11 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 48 48" width="48" height="48">
+  <defs>
+    <linearGradient id="bxg" x1="0%" y1="0%" x2="100%" y2="100%">
+      <stop offset="0%" stop-color="#2f6cff"/>
+      <stop offset="100%" stop-color="#0b3eb3"/>
+    </linearGradient>
+  </defs>
+  <rect x="4" y="4" width="40" height="40" rx="8" fill="url(#bxg)"/>
+  <path d="M16 14h10a5 5 0 0 1 0 10H16V14z" fill="none" stroke="#fff" stroke-width="2.5" stroke-linecap="round" stroke-linejoin="round"/>
+  <path d="M16 24h12a5 5 0 0 1 0 10H16V24z" fill="none" stroke="#fff" stroke-width="2.5" stroke-linecap="round" stroke-linejoin="round"/>
+</svg>
--- a/docs-site/static/img/screenshots/backup-tasks.png
+++ b/docs-site/static/img/screenshots/backup-tasks.png
--- a/docs-site/static/img/screenshots/dashboard.png
+++ b/docs-site/static/img/screenshots/dashboard.png
--- a/docs-site/static/img/screenshots/nodes.png
+++ b/docs-site/static/img/screenshots/nodes.png
--- a/docs-site/static/img/screenshots/storage-targets.png
+++ b/docs-site/static/img/screenshots/storage-targets.png
--- a/docs-site/tsconfig.json
+++ b/docs-site/tsconfig.json
@@ -0,0 +1,12 @@
+// This file is not used by "docusaurus start/build" commands.
+// It is here to improve your IDE experience (type-checking, autocompletion...),
+// and can also run the package.json "typecheck" script manually.
+{
+  "extends": "@docusaurus/tsconfig",
+  "compilerOptions": {
+    "baseUrl": ".",
+    "ignoreDeprecations": "6.0",
+    "strict": true
+  },
+  "exclude": [".docusaurus", "build"]
+}
--- a/screenshots/backup-records.png
+++ b/screenshots/backup-records.png
--- a/screenshots/backup-tasks.png
+++ b/screenshots/backup-tasks.png
--- a/Show More
+++ b/Show More