Quickly Deploy Spring Cloud Blade on Rainbond: Step‑by‑Step Guide

This article explains how to quickly deploy the Spring Cloud Blade microservice platform using Rainbond.

About Spring Cloud Blade

Front‑end: two open‑source frameworks Sword (React, Ant Design) and Saber (Vue, Element‑UI).

Back‑end: built on the Spring Cloud suite, packaged as BladeTool (available on Maven Central).

Integrated Sentinel for flow control, circuit breaking, and system load protection.

Uses Nacos for service registry and configuration.

Provides lightweight multi‑tenant support and OAuth2‑based authentication with JWT.

Encapsulates security, tenant isolation, and clear module boundaries.

Module Overview

SpringBlade
├── blade-auth          -- Authorization service
├── blade-common        -- Common utilities
├── blade-gateway       -- Spring Cloud gateway
├── blade-ops
│   ├── blade-admin
│   ├── blade-develop
│   ├── blade-resource
│   ├── blade-seata-order
│   └── blade-seata-storage
├── blade-service
│   ├── blade-desk
│   ├── blade-log
│   ├── blade-system
│   └── blade-user
├── blade-service-api
│   ├── blade-desk-api
│   ├── blade-dict-api
│   ├── blade-system-api
│   └── blade-user-api

Deployment via Application Store

Search for “SpringBlade” in Rainbond’s Platform Management → Application Market → Open‑Source Application Store and click Install. After installation the service topology appears as shown.

Source‑Based Deployment Steps (Spring Cloud Blade v3.5.0)

1. Deploy Nacos

Install Nacos single‑node version 2.1.2 from the application store.

2. Deploy Redis

Install Redis version 5.0.7 from the application store.

3. Deploy Sentinel Dashboard

Install Sentinel‑Dashboard version 1.8.6 from the application store.

4. Initialize Database

Create a MySQL database named blade and run the Blade SQL scripts to create tables and seed data.

5. Deploy Blade Backend Services

Create a custom component with repository https://gitee.com/smallc/SpringBlade and tag v3.5.0. Set the startup commands for each module, for example:

web: java $JAVA_OPTS -jar blade-auth/target/blade-auth.jar

web: java $JAVA_OPTS -jar blade-gateway/target/blade-gateway.jar

web: java $JAVA_OPTS -jar blade-ops/blade-admin/target/blade-admin.jar

Arrange component dependencies in orchestration mode, linking each service to its required ports.

6. Deploy Blade Front‑end Saber

Create a custom component with repository https://gitee.com/zhangbigqi/Saber.git and tag v3.5.0. Change the default port to 8080 and expose it. Set Saber to depend on blade-gateway. Access the Saber UI via the default domain and log in.

Configuration Files

blade.yaml

# Server configuration
server:
  undertow:
    buffer-size: 1024
    direct-buffers: true
    threads:
      io: 16
      worker: 400

# Spring configuration
spring:
  cloud:
    sentinel:
      eager: true
  devtools:
    restart:
      log-condition-evaluation-delta: false
    livereload:
      port: 23333

# Feign configuration
feign:
  sentinel:
    enabled: true
  okhttp:
    enabled: true
  httpclient:
    enabled: false

# Management endpoints
management:
  endpoints:
    web:
      exposure:
        include: "*"
  endpoint:
    health:
      show-details: always

# Knife4j configuration
knife4j:
  enable: true
  basic:
    enable: false
    username: blade
    password: blade
  setting:
    enableSwaggerModels: true
    enableDocumentManage: true
    enableHost: false
    enableHostText: http://localhost
    enableRequestCache: true
    enableFilterMultipartApis: false
    enableFilterMultipartApiMethodType: POST
    language: zh-CN
    enableFooter: false
    enableFooterCustom: true
    footerCustomContent: Copyright © 2022 SpringBlade All Rights Reserved

# Blade configuration
blade:
  token:
    sign-key: Please configure a 32‑bit signature for security
  xss:
    enabled: true
    skip-url:
      - /weixin
  secure:
    skip-url:
      - /test/**
    client:
      - client-id: sword
        path-patterns:
          - /sword/**
      - client-id: saber
        path-patterns:
          - /saber/**
  tenant:
    column: tenant_id
    tables:
      - blade_notice

blade-dev.yaml

# Redis configuration
spring:
  redis:
    host: 127.0.0.1
    port: 6379
    password:
    database: 0
    ssl: false

# Project module datasource
blade:
  datasource:
    dev:
      url: jdbc:mysql://127.0.0.1:3306/blade?useSSL=false&useUnicode=true&characterEncoding=utf-8&zeroDateTimeBehavior=convertToNull&transformedBitIsBoolean=true&tinyInt1isBit=false&allowMultiQueries=true&serverTimezone=GMT+8
      username: root
      password: root

Final Steps

Restart all components except Nacos, MySQL, Redis, and Sentinel Dashboard to apply the new configurations. After deployment, the full service topology matches the diagram shown earlier.

About Rainbond

Rainbond is a cloud‑native application management platform that is 100 % open source, easy to use, and does not require deep knowledge of containers or Kubernetes. It supports multiple Kubernetes clusters and provides full lifecycle management for enterprise applications.