UpgradeLink

English

简体中文

English

简体中文

Appearance

UpgradeLink-standalone Self-Build Image ​

This quick start guide helps you quickly deploy and use UpgradeLink in Docker containers by building your own Docker images.

  • The difference from the previous article is that, depending on your environment, you can configure your MySQL and Redis environments.

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 ​

Note: If you have independent MySQL and Redis environments, please adjust the configuration accordingly.

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

Adjust the following configuration files:

upgradelink-admin-core/server/api/etc/core-api.yaml

upgradelink-admin-core/server/rpc/etc/core-rpc.yaml 

upgradelink-admin-file/server/etc/fms.yaml

upgradelink-admin-message/server/etc/mcms.yaml

upgradelink-admin-upgrade/server/etc/upgrade.yaml

upgradelink-api/server/api/etc/api.yaml

4. Build Docker Images ​

4.1 Build the images ​

shell
cd development/docker-standalone

Package for both AMD and ARM architectures

shell
docker buildx build -t upgradelink-standalone:v2.1.0 --platform=linux/arm64 -f ./Dockerfile ../../ --load
shell
docker buildx build -t upgradelink-standalone:v2.1.0 --platform=linux/amd64 -f ./Dockerfile ../../ --load

5. Start UpgradeLink ​

When executing the command for the first time, it will automatically download the required Docker images. The waiting time depends on your network speed. You can also download the images in advance to shorten the waiting time for deployment commands.

shell
docker run -d -p 8081:8080 -p 8888:8888 upgradelink-standalone:v2.0.6

6. Verify if the UpgradeLink Service Started Successfully ​

Use the docker logs -f $container_id command to check the UpgradeLink service startup logs. If you see the following logs, the service has started successfully.

2025-09-26 15:10:26,284 INFO Set uid to user 0 succeeded
2025-09-26 15:10:26,302 INFO RPC interface 'supervisor' initialized
2025-09-26 15:10:26,303 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2025-09-26 15:10:26,303 INFO supervisord started with pid 9
2025-09-26 15:10:27,312 INFO spawned: 'core-rpc' with pid 11
2025-09-26 15:10:27,313 INFO spawned: 'file' with pid 12
2025-09-26 15:10:27,315 INFO spawned: 'message' with pid 13
2025-09-26 15:10:27,317 INFO spawned: 'upgrade' with pid 14
2025-09-26 15:10:27,322 INFO spawned: 'core-api' with pid 15
2025-09-26 15:10:27,325 INFO spawned: 'api' with pid 16
2025-09-26 15:10:27,336 INFO spawned: 'crond' with pid 25
2025-09-26 15:10:27,345 INFO spawned: 'nginx' with pid 41

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

6.1 UpgradeLink Console Page ​

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

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

6.2 api ​

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

toolsetlink@163.com