Skip to content

Erupt Cloud Server

Distributed node management center. Replaces traditional configuration center yml files with database tables; manages node configurations, service registration, and request scheduling through a visual interface.

Core Capabilities

Traditional microservice configuration centers (Nacos, Apollo, etc.) rely on yml/properties files for configuration management, and changes require re-publishing or restarting services. Erupt Cloud stores configurations in database tables, enabling visual editing through the admin interface. Nodes pull updates in real time with no additional configuration center infrastructure to maintain.

Traditional Config CenterErupt Cloud
yml / properties filesDatabase tables (visual management)
Requires deploying Nacos / ApolloReuses the existing database
Nodes must be notified to refresh after changesNodes pull actively; changes take effect immediately
Configurations scattered across project repositoriesCentrally maintained on the Server side

Usage

1. Create an Erupt Project

Refer to Quick Start

2. Add Maven Dependency

xml
<dependency>
  <groupId>xyz.erupt</groupId>
  <artifactId>erupt-cloud-server</artifactId>
  <version>${erupt.version}</version>
</dependency>

3. Add Redis Configuration and Enable redis-session

yaml
spring:
  data:
    redis:
      database: 0
      timeout: 10000
      host: 127.0.0.1
      port: 6379
      password:
erupt:
  redis-session: true

WARNING

Since Spring Boot 3, the Redis configuration prefix is spring.data.redis.*. The legacy spring.redis.* prefix no longer works.

4. Start the Project

After logging in, node management menus appear:

Deployment successful!

Optional Configuration

yaml
erupt:
  cloud-server:
    # Cloud key namespace (optional)
    cloud-name-space: 'erupt-cloud:'
    # Node persistence duration, in ms
    node-expire-time: 60000
    # Node liveness check interval, in ms
    node-survive-check-time: 120000
    # Whether to validate node access-token, default true (supported from 1.11.4+)
    validate-access-token: true

Docker Deployment

The Server side supports Docker deployment. New features only require developing Node instances:

bash
docker pull erupts/erupt:version

The image version matches the Erupt version number. Version information: https://hub.docker.com/repository/docker/erupts/erupt/general

Refer to the Changelog for the latest version number.

Contributors

The avatar of contributor named as YuePeng YuePeng
The avatar of contributor named as Claude Opus 5 (1M context) Claude Opus 5 (1M context)

Changelog

Released under the Apache-2.0 License.