UpgradeLink

English

简体中文

English

简体中文

Appearance

UpgradeLink Docker Compose Quick Start ​

This guide helps you quickly deploy and use UpgradeLink in Docker containers through UpgradeLink project image examples.

Before you begin, we hope you have the following experience:

  • Familiar with Docker containerized deployment.
  • Familiar with MySQL database.
  • Familiar with Redis cache.
  • Familiar with backend project deployment.
  • Read the project module introduction to understand the functions of each module. Project Module Introduction

1. Environment Preparation ​

You need to install Docker.

2. Download the Project ​

2.1. Download the project from GitHub ​

shell
git clone https://github.com/toolsetlink/upgradelink

3. Modify MySQL and Redis configurations to replace them with your own database-related information. ​

Note: If you have independent MySQL and Redis environments, please adjust the configuration accordingly. No adjustment needed if using Docker-Compose configured environment

Note: The MySQL database file is located at development/upgrade-20250926.sql.

Adjust the following configuration files:

development/docker-compose/upgradelink-admin-core/core-api.yaml

development/docker-compose/upgradelink-admin-core/core-rpc.yaml

development/docker-compose/upgradelink-admin-file/fms.yaml

development/docker-compose/upgradelink-admin-message/mcms.yaml

development/docker-compose/upgradelink-admin-upgrade/upgrade.yaml

development/docker-compose/upgradelink-api/api.yaml

4. Start UpgradeLink ​

Project Module Introduction

Execute the following command in the development/docker-compose directory:

docker-compose up -d

5. Access the UpgradeLink Backend Management System ​

You can quickly test the functionality of UpgradeLink through the following services.

5.1 UpgradeLink Console Page ​

Open any browser and enter the address: http://127.0.0.1:80 to access the UpgradeLink console page.

Note: Default username and password are admin/simple-admin

5.2 API Interface ​

The API service address is http://127.0.0.1:8080. You can refer to the API documentation and replace the address for testing.

toolsetlink@163.com