abp-next-admin2

这是基于vue-vben-admin 模板适用于abp vNext的前端管理项目

26 KiB

Raw Blame History

现在我已经收集了足够的信息来创建部署指南文档。让我开始编写详细的部署指南：

# 部署指南 **本文档中引用的文件** - [deploy/README.md](file://deploy/README.md) - [deploy/deploy.ps1](file://deploy/deploy.ps1) - [docker-compose.yml](file://docker-compose.yml) - [docker-compose.override.yml](file://docker-compose.override.yml) - [docker-compose.middleware.yml](file://docker-compose.middleware.yml) - [docker-compose.override.configuration.yml](file://docker-compose.override.configuration.yml) - [docker-compose.override.agile.yml](file://docker-compose.override.agile.yml) - [tye.yaml](file://tye.yaml) - [starter/readme.md](file://starter/readme.md) - [apps/react-admin/docker-compose.yaml](file://apps/react-admin/docker-compose.yaml)

简介

本文档提供了ABP Next Admin项目的全面部署指南，涵盖从开发环境到生产环境的各种部署方案。该项目采用微服务架构，基于ABP框架构建，支持多种部署模式，包括Docker容器化部署、单体部署和微服务部署。

项目的主要特点：

基于ABP框架的微服务架构
支持多种数据库（MySQL、PostgreSQL、SQL Server）
完整的前后端分离架构
多种身份认证方式（OpenIddict、IdentityServer）
完善的中间件支持（Redis、RabbitMQ、Elasticsearch）

项目架构概览

graph TB
subgraph "前端层"
UI[Vben Admin UI]
Gateway[API网关]
end
subgraph "后端服务层"
AuthService[身份认证服务]
AdminService[管理后台服务]
PlatformService[平台服务]
LocalizationService[国际化服务]
MessageService[消息服务]
TaskService[任务管理服务]
WebhookService[Webhook服务]
WorkflowService[工作流服务]
WechatService[微信服务]
end
subgraph "基础设施层"
MySQL[(MySQL数据库)]
Redis[(Redis缓存)]
RabbitMQ[(RabbitMQ消息队列)]
ES[(Elasticsearch)]
Kibana[Kibana可视化]
end
UI --> Gateway
Gateway --> AuthService
Gateway --> AdminService
Gateway --> PlatformService
Gateway --> LocalizationService
Gateway --> MessageService
Gateway --> TaskService
Gateway --> WebhookService
Gateway --> WorkflowService
Gateway --> WechatService
AuthService -.-> MySQL
AdminService -.-> MySQL
PlatformService -.-> MySQL
LocalizationService -.-> MySQL
MessageService -.-> MySQL
TaskService -.-> MySQL
WebhookService -.-> MySQL
WorkflowService -.-> MySQL
WechatService -.-> MySQL
AuthService -.-> Redis
AdminService -.-> Redis
PlatformService -.-> Redis
LocalizationService -.-> Redis
MessageService -.-> Redis
TaskService -.-> Redis
WebhookService -.-> Redis
WorkflowService -.-> Redis
WechatService -.-> Redis
AuthService -.-> RabbitMQ
AdminService -.-> RabbitMQ
PlatformService -.-> RabbitMQ
LocalizationService -.-> RabbitMQ
MessageService -.-> RabbitMQ
TaskService -.-> RabbitMQ
WebhookService -.-> RabbitMQ
WorkflowService -.-> RabbitMQ
WechatService -.-> RabbitMQ
AuthService -.-> ES
AdminService -.-> ES
PlatformService -.-> ES
LocalizationService -.-> ES
MessageService -.-> ES
TaskService -.-> ES
WebhookService -.-> ES
WorkflowService -.-> ES
WechatService -.-> ES

图表来源

docker-compose.yml
docker-compose.middleware.yml

部署方案

部署模式对比

部署模式	适用场景	复杂度	维护成本	性能	可扩展性
Docker容器化	开发、测试、小型生产环境	中等	低	中等	高
单体部署	小型应用、原型开发	低	中等	中等	低
微服务部署	大型应用、企业级环境	高	高	高	最高

部署前准备

在开始部署之前，请确保满足以下要求：

系统要求
- Windows 10/11 或 Linux/MacOS
- Docker Desktop (Windows/Mac) 或 Docker Engine (Linux)
- PowerShell 5.1+ (Windows)
- Node.js 16+ (前端构建)
- .NET 6.0+ SDK
网络要求
- 端口开放：30000-30060（服务端口）
- 网络连接：能够访问外部镜像仓库
- DNS解析：正确配置主机名映射
硬件要求
- CPU：至少4核心
- 内存：8GB以上
- 存储：50GB以上可用空间

Docker容器化部署

快速开始

方法一：使用预置脚本

# 1. 自动配置Docker环境
.\00.auto-config-docker.cmd

# 2. 创建数据库
.\01.create database.cmd

# 3. 迁移数据库
.\02.migrate-db.cmd

# 4. 启动所有服务
.\80.start-host.cmd

# 5. 启动前端UI
.\99.start-ui.cmd

方法二：使用Docker Compose

# 启动中间件服务
docker-compose -f docker-compose.middleware.yml up -d --build

# 等待30秒让数据库初始化
Start-Sleep -Seconds 30

# 创建数据库
cd aspnet-core
cmd.exe /c create-database.bat

# 执行数据库迁移
cd build
foreach ($solution in $migrationArray) {  
    cd $solution.Path
    dotnet run --no-build
}

# 启动应用服务
docker-compose -f docker-compose.yml -f docker-compose.override.yml -f docker-compose.override.configuration.yml up -d --build

服务组件详解

graph LR
subgraph "身份认证服务"
STS[auth-server<br/>端口:44385]
STS_API[auth-server-api<br/>端口:30015]
end
subgraph "管理服务"
ADMIN[admin-api<br/>端口:30010]
PLATFORM[platform-api<br/>端口:30025]
LOCALIZATION[localization-api<br/>端口:30030]
end
subgraph "业务服务"
MESSAGES[messages-api<br/>端口:30020]
TASKS[task-api<br/>端口:30040]
WEBHOOKS[webhook-api<br/>端口:30045]
WORKFLOW[workflow-api<br/>端口:30050]
WECHAT[wechat-api<br/>端口:30060]
end
subgraph "网关服务"
INTERNAL[internal-apigateway<br/>端口:30000]
end
subgraph "前端服务"
UI[UI界面<br/>端口:40080]
end
STS --> ADMIN
STS_API --> ADMIN
ADMIN --> PLATFORM
PLATFORM --> MESSAGES
PLATFORM --> TASKS
PLATFORM --> WEBHOOKS
PLATFORM --> WORKFLOW
PLATFORM --> WECHAT
INTERNAL --> STS
INTERNAL --> STS_API
INTERNAL --> ADMIN
INTERNAL --> PLATFORM
INTERNAL --> LOCALIZATION
INTERNAL --> MESSAGES
INTERNAL --> TASKS
INTERNAL --> WEBHOOKS
INTERNAL --> WORKFLOW
INTERNAL --> WECHAT
UI --> INTERNAL

图表来源

docker-compose.yml

Docker Compose配置详解

核心服务配置

每个服务都包含以下关键配置：

环境变量配置

environment:
  - ASPNETCORE_ENVIRONMENT=Development
  - ASPNETCORE_HTTP_PORTS=80
  - TZ=Asia/Shanghai

健康检查

healthcheck:
  test: ["CMD-SHELL", "wget --spider http://localhost/healthz || exit"]
  interval: 10s
  timeout: 5s
  retries: 5

网络配置
```
networks:
  - abp-next-admin
```

主机名映射

extra_hosts:
  - "host.docker.internal:host-gateway"
  - "auth-server:host-gateway"

章节来源

docker-compose.yml
docker-compose.override.yml

单体部署

单体部署架构

单体部署将所有服务打包成一个单一的应用程序，适合小型项目或开发环境。

flowchart TD
Start([开始部署]) --> Config[配置环境变量]
Config --> Build[构建.NET应用程序]
Build --> Publish[发布应用程序]
Publish --> Database[初始化数据库]
Database --> Start[启动服务]
Start --> Health[健康检查]
Health --> Success([部署成功])
Config --> ConfigError{配置错误?}
ConfigError --> |是| FixConfig[修复配置]
FixConfig --> Config
Build --> BuildError{构建失败?}
BuildError --> |是| FixBuild[修复构建问题]
FixBuild --> Build
Database --> DBError{数据库错误?}
DBError --> |是| FixDB[修复数据库问题]
FixDB --> Database
Health --> HealthError{健康检查失败?}
HealthError --> |是| Restart[重启服务]
Restart --> Health

部署步骤

1. 准备工作

# 克隆项目
git clone https://github.com/your-repo/abp-next-admin.git
cd abp-next-admin

# 安装依赖
cd apps/vue
pnpm install

2. 配置环境

创建 .env 文件：

# 数据库连接
DB_CONNECTION_STRING=Server=localhost;Database=AbpNextAdmin;User Id=root;Password=yourpassword

# Redis配置
REDIS_CONNECTION=127.0.0.1:6379

# 身份认证
AUTH_SERVER_URL=http://localhost:44385
CLIENT_ID=vue-admin-client
CLIENT_SECRET=your-secret

# CORS配置
CORS_ORIGINS=http://localhost:3000,http://localhost:3100

3. 构建和启动

# 构建前端
cd apps/vue
pnpm build

# 启动后端
cd ../../aspnet-core
dotnet run --project services/LY.MicroService.BackendAdmin.HttpApi.Host

章节来源

starter/readme.md

微服务部署

微服务架构设计

微服务部署将每个功能模块独立部署，实现高内聚、低耦合的架构。

graph TB
subgraph "服务网格"
subgraph "认证服务集群"
Auth1[Auth Server 1]
Auth2[Auth Server 2]
AuthLB[负载均衡器]
end
subgraph "业务服务集群"
Admin1[Admin Service 1]
Admin2[Admin Service 2]
Platform1[Platform Service 1]
Platform2[Platform Service 2]
Message1[Message Service 1]
Message2[Message Service 2]
end
subgraph "数据服务集群"
MySQL1[(MySQL主节点)]
MySQL2[(MySQL从节点)]
Redis1[(Redis主节点)]
Redis2[(Redis从节点)]
end
subgraph "消息服务集群"
RabbitMQ1[(RabbitMQ 1)]
RabbitMQ2[(RabbitMQ 2)]
end
end
subgraph "客户端"
Browser[浏览器]
Mobile[移动应用]
end
Browser --> AuthLB
Mobile --> AuthLB
AuthLB --> Auth1
AuthLB --> Auth2
Auth1 --> MySQL1
Auth2 --> MySQL1
Auth1 --> Redis1
Auth2 --> Redis1
Admin1 --> MySQL1
Admin2 --> MySQL1
Platform1 --> MySQL1
Platform2 --> MySQL1
Message1 --> MySQL1
Message2 --> MySQL1
Admin1 --> RabbitMQ1
Admin2 --> RabbitMQ1
Platform1 --> RabbitMQ1
Platform2 --> RabbitMQ1
Message1 --> RabbitMQ1
Message2 --> RabbitMQ1

Kubernetes部署

1. 创建命名空间

apiVersion: v1
kind: Namespace
metadata:
  name: abp-next-admin
  labels:
    name: abp-next-admin

2. 部署配置

apiVersion: apps/v1
kind: Deployment
metadata:
  name: backend-admin-api
  namespace: abp-next-admin
  labels:
    app: backend-admin-api
spec:
  replicas: 3
  selector:
    matchLabels:
      app: backend-admin-api
  template:
    metadata:
      labels:
        app: backend-admin-api
    spec:
      containers:
      - name: backend-admin-api
        image: abp-next-admin/backend-admin:latest
        ports:
        - containerPort: 8080
        env:
        - name: ASPNETCORE_ENVIRONMENT
          value: Production
        - name: ConnectionStrings__Default
          valueFrom:
            secretKeyRef:
              name: db-secrets
              key: connection-string
        resources:
          requests:
            memory: "512Mi"
            cpu: "500m"
          limits:
            memory: "1Gi"
            cpu: "1000m"
        livenessProbe:
          httpGet:
            path: /healthz
            port: 8080
          initialDelaySeconds: 30
          periodSeconds: 10
        readinessProbe:
          httpGet:
            path: /healthz
            port: 8080
          initialDelaySeconds: 5
          periodSeconds: 5

3. 服务暴露

apiVersion: v1
kind: Service
metadata:
  name: backend-admin-api
  namespace: abp-next-admin
spec:
  selector:
    app: backend-admin-api
  ports:
  - port: 80
    targetPort: 8080
  type: LoadBalancer

4. Ingress配置

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: abp-next-admin-ingress
  namespace: abp-next-admin
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
spec:
  tls:
  - hosts:
    - api.example.com
    secretName: tls-secret
  rules:
  - host: api.example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: backend-admin-api
            port:
              number: 80

章节来源

aspnet-core/templates/micro/content/deploy/deployment.yaml

环境配置管理

开发环境配置

开发环境主要用于本地开发和调试，配置相对简单。

开发环境特点

数据库：使用本地MySQL实例
缓存：使用本地Redis实例
消息队列：使用本地RabbitMQ实例
日志：控制台输出和本地文件
监控：基本健康检查

开发环境配置示例

services:
  admin-api:
    environment:
      - ASPNETCORE_ENVIRONMENT=Development
      - ConnectionStrings__Default=Server=localhost;Database=AbpNextAdmin_Dev;User Id=root;Password=devpassword
      - Redis__Configuration=localhost:6379
      - CAP__RabbitMQ__HostName=localhost
      - Elasticsearch__NodeUris=http://localhost:9200

测试环境配置

测试环境模拟生产环境，但资源有限。

测试环境特点

数据库：独立的测试数据库实例
缓存：独立的Redis实例
消息队列：独立的消息队列实例
日志：集中式日志收集
监控：完整的监控体系

测试环境配置示例

services:
  admin-api:
    environment:
      - ASPNETCORE_ENVIRONMENT=Testing
      - ConnectionStrings__Default=Server=test-db;Database=AbpNextAdmin_Test;User Id=testuser;Password=testpass
      - Redis__Configuration=test-redis:6379
      - CAP__RabbitMQ__HostName=test-rabbitmq
      - Elasticsearch__NodeUris=http://test-es:9200
      - Serilog__WriteTo__1__Name=Elasticsearch
      - Serilog__WriteTo__1__Args__nodeUris=http://test-es:9200

生产环境配置

生产环境需要考虑高可用性、安全性和性能。

生产环境特点

数据库：主从复制、读写分离
缓存：集群模式、持久化
消息队列：集群模式、持久化
日志：分布式日志收集、分析
监控：APM监控、告警系统
安全：SSL/TLS加密、访问控制

生产环境配置示例

services:
  admin-api:
    environment:
      - ASPNETCORE_ENVIRONMENT=Production
      - ConnectionStrings__Default=Server=prod-db-cluster;Database=AbpNextAdmin_Prod;User Id=produser;Password=prodpass
      - Redis__Configuration=prod-redis-cluster:6379
      - CAP__RabbitMQ__HostName=prod-rabbitmq-cluster
      - Elasticsearch__NodeUris=https://prod-es-cluster:9200
      - Serilog__WriteTo__1__Name=Elasticsearch
      - Serilog__WriteTo__1__Args__nodeUris=https://prod-es-cluster:9200
      - AuthServer__RequireHttpsMetadata=true
      - App__SelfUrl=https://api.example.com

章节来源

docker-compose.override.configuration.yml

自动化部署脚本

部署脚本架构

flowchart TD
DeployScript[deploy.ps1] --> InitEnv[初始化环境]
InitEnv --> DeployMiddleware[部署中间件]
DeployMiddleware --> WaitDB[等待数据库初始化]
WaitDB --> CreateDB[创建数据库]
CreateDB --> MigrateDB[执行数据库迁移]
MigrateDB --> BuildDotNet[构建.NET项目]
BuildDotNet --> BuildFrontend[构建前端项目]
BuildFrontend --> StartServices[启动服务]
StartServices --> HealthCheck[健康检查]
HealthCheck --> Success[部署完成]
DeployMiddleware --> MWError{中间件错误?}
MWError --> |是| RetryMW[重试中间件部署]
RetryMW --> DeployMiddleware
CreateDB --> DBError{数据库错误?}
DBError --> |是| FixDB[修复数据库问题]
FixDB --> CreateDB
MigrateDB --> MigrationError{迁移错误?}
MigrationError --> |是| FixMigration[修复迁移问题]
FixMigration --> MigrateDB
HealthCheck --> HealthFail{健康检查失败?}
HealthFail --> |是| RestartServices[重启服务]
RestartServices --> HealthCheck

脚本功能详解

1. 环境初始化

# 设置根目录
$rootFolder = (Get-Item -Path "../" -Verbose).FullName
$deployPath = $rootFolder + "/deploy"
$buildPath = $rootFolder + "/build"
$aspnetcorePath = $rootFolder + "/aspnet-core"
$vuePath = $rootFolder + "/apps/vue"

2. 中间件部署

# 部署中间件服务
Write-host "deploy middleware..."
Set-Location $rootFolder
docker-compose -f .\docker-compose.middleware.yml up -d --build

3. 数据库初始化

# 等待30秒，数据库初始化完成
Write-host "initial database..."
Start-Sleep -Seconds 30

# 创建数据库
Write-host "create database..."
Set-Location $aspnetcorePath
cmd.exe /c create-database.bat

4. 应用程序构建

# 发布.NET项目
Write-host "release .net project..."
Set-Location $buildPath
foreach ($solution in $serviceArray) {  
    $publishPath = $rootFolder + "/aspnet-core/services/Publish/" + $solution.Service + "/"
    dotnet publish -c Release -o $publishPath $solution.Path --no-cache
    $dockerFile = Join-Path $solution.Path "Dockerfile"
    if ((Test-Path $dockerFile)) {
        Copy-Item $dockerFile -Destination $publishPath
    }
}

# 构建前端项目
Write-host "build front project..."
Set-Location $vuePath
pnpm install
pnpm build

5. 服务启动

# 运行应用程序
Write-host "running application..."
Set-Location $rootFolder
docker-compose -f .\docker-compose.yml -f .\docker-compose.override.yml -f .\docker-compose.override.configuration.yml up -d --build

章节来源

deploy/deploy.ps1

自定义部署选项

1. 指定部署环境

# 开发环境部署
.\deploy.ps1 -Environment Development

# 测试环境部署
.\deploy.ps1 -Environment Testing

# 生产环境部署
.\deploy.ps1 -Environment Production

2. 选择部署服务

# 只部署核心服务
.\deploy.ps1 -Services "admin,platform,auth"

# 排除某些服务
.\deploy.ps1 -ExcludeServices "wechat,workflow"

3. 自定义配置

# 使用自定义配置文件
.\deploy.ps1 -ConfigPath "./custom-config.yml"

# 指定镜像仓库
.\deploy.ps1 -Registry "myregistry.com"

高可用性部署

集群架构设计

graph TB
subgraph "负载均衡层"
LB1[Nginx LB 1]
LB2[Nginx LB 2]
VIP[虚拟IP<br/>192.168.1.100]
end
subgraph "应用服务集群"
subgraph "可用区A"
App1[App Server 1A]
App2[App Server 2A]
App3[App Server 3A]
end
subgraph "可用区B"
App4[App Server 1B]
App5[App Server 2B]
App6[App Server 3B]
end
subgraph "可用区C"
App7[App Server 1C]
App8[App Server 2C]
App9[App Server 3C]
end
end
subgraph "数据服务集群"
subgraph "数据库集群"
DBMaster[(MySQL Master)]
DBSlave1[(MySQL Slave 1)]
DBSlave2[(MySQL Slave 2)]
end
subgraph "缓存集群"
RedisCluster[(Redis Cluster)]
end
subgraph "消息队列集群"
RabbitMQCluster[(RabbitMQ Cluster)]
end
end
subgraph "监控告警"
Prometheus[Prometheus]
Grafana[Grafana]
AlertManager[Alert Manager]
end
VIP --> LB1
VIP --> LB2
LB1 --> App1
LB1 --> App2
LB1 --> App3
LB2 --> App4
LB2 --> App5
LB2 --> App6
LB1 --> App7
LB1 --> App8
LB1 --> App9
App1 --> DBMaster
App2 --> DBMaster
App3 --> DBMaster
App4 --> DBMaster
App5 --> DBMaster
App6 --> DBMaster
App7 --> DBMaster
App8 --> DBMaster
App9 --> DBMaster
App1 --> RedisCluster
App2 --> RedisCluster
App3 --> RedisCluster
App4 --> RedisCluster
App5 --> RedisCluster
App6 --> RedisCluster
App7 --> RedisCluster
App8 --> RedisCluster
App9 --> RedisCluster
App1 --> RabbitMQCluster
App2 --> RabbitMQCluster
App3 --> RabbitMQCluster
App4 --> RabbitMQCluster
App5 --> RabbitMQCluster
App6 --> RabbitMQCluster
App7 --> RabbitMQCluster
App8 --> RabbitMQCluster
App9 --> RabbitMQCluster
App1 --> Prometheus
App2 --> Prometheus
App3 --> Prometheus
App4 --> Prometheus
App5 --> Prometheus
App6 --> Prometheus
App7 --> Prometheus
App8 --> Prometheus
App9 --> Prometheus
Prometheus --> Grafana
Prometheus --> AlertManager

高可用配置

1. 负载均衡配置

upstream backend_admin {
    least_conn;
    server 192.168.1.10:30010 max_fails=3 fail_timeout=30s;
    server 192.168.1.11:30010 max_fails=3 fail_timeout=30s;
    server 192.168.1.12:30010 max_fails=3 fail_timeout=30s;
}

server {
    listen 80;
    server_name api.example.com;
    
    location / {
        proxy_pass http://backend_admin;
        proxy_set_header Host $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_connect_timeout 5s;
        proxy_send_timeout 60s;
        proxy_read_timeout 60s;
        
        # 错误处理
        error_page 500 502 503 504 @error;
    }
    
    location @error {
        return 502;
    }
}

2. 数据库高可用

# MySQL主从复制配置
master:
  image: mysql:8.0
  environment:
    - MYSQL_ROOT_PASSWORD=master_password
    - MYSQL_REPLICATION_MODE=master
    - MYSQL_REPLICATION_USER=repl_user
    - MYSQL_REPLICATION_PASSWORD=repl_password
  volumes:
    - mysql_master_data:/var/lib/mysql

slave1:
  image: mysql:8.0
  environment:
    - MYSQL_ROOT_PASSWORD=slave_password
    - MYSQL_REPLICATION_MODE=slave
    - MYSQL_MASTER_HOST=master
    - MYSQL_REPLICATION_USER=repl_user
    - MYSQL_REPLICATION_PASSWORD=repl_password
  depends_on:
    - master
  volumes:
    - mysql_slave_data:/var/lib/mysql

3. 缓存高可用

# Redis哨兵配置
redis-sentinel:
  image: redis:6-alpine
  command: >
    sh -c "
      echo 'sentinel monitor mymaster redis-master 6379 2' > /etc/redis/sentinel.conf &&
      echo 'sentinel down-after-milliseconds mymaster 5000' >> /etc/redis/sentinel.conf &&
      echo 'sentinel failover-timeout mymaster 10000' >> /etc/redis/sentinel.conf &&
      echo 'sentinel parallel-syncs mymaster 1' >> /etc/redis/sentinel.conf &&
      redis-sentinel /etc/redis/sentinel.conf
    "    
  depends_on:
    - redis-master
  volumes:
    - redis_sentinel_data:/var/lib/redis

4. 消息队列高可用

# RabbitMQ集群配置
rabbitmq-cluster:
  image: rabbitmq:3.9-management
  environment:
    - RABBITMQ_CLUSTER_NODES=rabbit@rabbitmq1,rabbit@rabbitmq2,rabbit@rabbitmq3
    - RABBITMQ_ERLANG_COOKIE=cluster_cookie
  volumes:
    - rabbitmq_data:/var/lib/rabbitmq
  ports:
    - "15672:15672"

灾难恢复

灾难恢复策略

flowchart TD
Disaster[灾难发生] --> Assess[评估影响]
Assess --> Priority{优先级评估}
Priority --> |高| Immediate[立即响应]
Priority --> |中| Standard[标准响应]
Priority --> |低| Deferred[延迟响应]
Immediate --> BackupRestore[备份恢复]
Standard --> BackupRestore
Deferred --> Plan[制定计划]
BackupRestore --> Verify[验证数据完整性]
Plan --> BackupRestore
Verify --> Test[功能测试]
Test --> Monitor[监控系统状态]
Monitor --> Success[恢复完成]
Verify --> RestoreFail{恢复失败?}
RestoreFail --> |是| AlternateBackup[使用备用备份]
AlternateBackup --> Verify
Monitor --> MonitorFail{监控异常?}
MonitorFail --> |是| Rollback[回滚操作]
Rollback --> Monitor

备份策略

1. 数据库备份

#!/bin/bash
# 数据库备份脚本

BACKUP_DIR="/backup/db"
DATE=$(date +%Y%m%d_%H%M%S)
DB_NAME="abp_next_admin"

# 创建备份目录
mkdir -p $BACKUP_DIR

# 执行备份
mysqldump -h localhost -u root -p$MYSQL_ROOT_PASSWORD \
  --single-transaction \
  --routines \
  --triggers \
  --events \
  $DB_NAME > $BACKUP_DIR/$DB_NAME-$DATE.sql

# 压缩备份文件
gzip $BACKUP_DIR/$DB_NAME-$DATE.sql

# 清理旧备份（保留7天）
find $BACKUP_DIR -name "*.sql.gz" -mtime +7 -delete

echo "Database backup completed: $DATE"

2. 文件备份

#!/bin/bash
# 文件备份脚本

SOURCE_DIR="/opt/abp-next-admin"
BACKUP_DIR="/backup/files"
DATE=$(date +%Y%m%d_%H%M%S)

# 创建备份目录
mkdir -p $BACKUP_DIR

# 备份配置文件和日志
tar -czf $BACKUP_DIR/config-$DATE.tar.gz \
  $SOURCE_DIR/config \
  $SOURCE_DIR/logs

# 清理旧备份
find $BACKUP_DIR -name "*.tar.gz" -mtime +30 -delete

echo "File backup completed: $DATE"

3. 容器镜像备份

#!/bin/bash
# 容器镜像备份脚本

IMAGE_NAME="abp-next-admin"
TAG="latest"
BACKUP_DIR="/backup/images"
DATE=$(date +%Y%m%d_%H%M%S)

# 导出镜像
docker save $IMAGE_NAME:$TAG | gzip > $BACKUP_DIR/$IMAGE_NAME-$DATE.tar.gz

# 验证导出的镜像
docker load < $BACKUP_DIR/$IMAGE_NAME-$DATE.tar.gz

echo "Image backup completed: $DATE"

恢复流程

1. 数据库恢复

#!/bin/bash
# 数据库恢复脚本

BACKUP_FILE=$1
DB_NAME="abp_next_admin"

if [ -z "$BACKUP_FILE" ]; then
    echo "Usage: $0 <backup_file>"
    exit 1
fi

# 解压备份文件
gunzip -c $BACKUP_FILE | mysql -u root -p$MYSQL_ROOT_PASSWORD $DB_NAME

echo "Database restored from: $BACKUP_FILE"

2. 应用服务恢复

#!/bin/bash
# 应用服务恢复脚本

SERVICE_NAME=$1
BACKUP_IMAGE=$2

if [ -z "$SERVICE_NAME" ] || [ -z "$BACKUP_IMAGE" ]; then
    echo "Usage: $0 <service_name> <backup_image>"
    exit 1
fi

# 停止当前服务
docker-compose stop $SERVICE_NAME

# 删除现有容器
docker-compose rm -f $SERVICE_NAME

# 启动备份镜像
docker-compose up -d $SERVICE_NAME

echo "$SERVICE_NAME restored from: $BACKUP_IMAGE"

3. 完整系统恢复

#!/bin/bash
# 完整系统恢复脚本

BACKUP_DATE=$1
RESTORE_DIR="/restore"

if [ -z "$BACKUP_DATE" ]; then
    echo "Usage: $0 <backup_date>"
    exit 1
fi

# 停止所有服务
docker-compose down

# 恢复数据库
./restore_db.sh $RESTORE_DIR/db/abp_next_admin-$BACKUP_DATE.sql.gz

# 恢复配置文件
tar -xzf $RESTORE_DIR/files/config-$BACKUP_DATE.tar.gz -C /

# 恢复应用服务
./restore_service.sh admin-api $RESTORE_DIR/images/admin-api-$BACKUP_DATE.tar.gz
./restore_service

26 KiB Raw Blame History

目录

简介

项目架构概览

部署方案

部署模式对比

部署前准备

Docker容器化部署

快速开始

方法一：使用预置脚本

方法二：使用Docker Compose

服务组件详解

Docker Compose配置详解

核心服务配置

单体部署

单体部署架构

部署步骤

1. 准备工作

2. 配置环境

3. 构建和启动

微服务部署

微服务架构设计

Kubernetes部署

1. 创建命名空间

2. 部署配置

3. 服务暴露

4. Ingress配置

环境配置管理

开发环境配置

开发环境特点

开发环境配置示例

测试环境配置

测试环境特点

测试环境配置示例

生产环境配置

生产环境特点

生产环境配置示例

自动化部署脚本

部署脚本架构

脚本功能详解

1. 环境初始化

2. 中间件部署

3. 数据库初始化

4. 应用程序构建

5. 服务启动

自定义部署选项

1. 指定部署环境

2. 选择部署服务

3. 自定义配置

高可用性部署

集群架构设计

高可用配置

1. 负载均衡配置

2. 数据库高可用

3. 缓存高可用

4. 消息队列高可用

灾难恢复

灾难恢复策略

备份策略

1. 数据库备份

2. 文件备份

3. 容器镜像备份

恢复流程

1. 数据库恢复

2. 应用服务恢复

3. 完整系统恢复

26 KiB

Raw Blame History