SQLE 3.0 Installation Guide: RPM and Docker Deployment
This article provides a step‑by‑step guide for installing the open‑source SQLE 3.0 SQL quality management platform using both RPM packages and Docker containers, covering environment preparation, configuration file adjustments, service startup, common issues, and troubleshooting tips.
1 SQLE Introduction
SQLE is an open‑source SQL quality management platform that supports multiple databases and offers lifecycle governance for development, testing, release, and production stages. It enforces standards, pre‑checks, post‑monitoring, and standard publishing to improve stability.
2 RPM Installation
2.1 Prepare Environment
The recommended OS is CentOS 7. Download the RPM package from https://github.com/actiontech/sqle/releases .
2.2 Execute Installation
rpm -ihv sqle-ce-3.2310.0.qa.el7.x86_64.rpm --prefix=/opt/sqle2.3 Install MySQL (Docker)
# Docker run MySQL
docker run -d --restart=always --name mysql \
--network=host \
-e MYSQL_ROOT_PASSWORD=sqle2023 \
-e LANG=C.UTF-8 \
-v /etc/timezone:/etc/timezone \
-v /etc/localtime:/etc/localtime \
mysql:5.7.41
# Enter container
docker exec -it mysql bash
mysql -uroot -psqle2023
# Create databases
CREATE DATABASE IF NOT EXISTS sqle default character set utf8mb4 collate utf8mb4_unicode_ci;
CREATE DATABASE IF NOT EXISTS dms default character set utf8mb4 collate utf8mb4_unicode_ci;2.4 Modify Configuration
Update database connection info and generate a secret_key (e.g., using uuidgen without hyphens).
dms:
id: 1
api:
addr: "0.0.0.0"
port: 10000
enable_https: false
cert_file_path: './etc/cert.pem'
key_file_path: './etc/key.pem'
secret_key: '7fa9af029350433daceb899710ee3a62'
service:
database:
host: "127.0.0.1"
port: 3306
username: "root"
password: "sqle2023"
database: "dms"
debug: true
... (additional YAML omitted for brevity)2.5 Start Services
cd /opt/sqle
chmod +x scripts/init_start.sh
./scripts/init_start.sh2.6 Verify Installation
Check the process, then access http://IP:10000 with default credentials admin/admin to log in.
3 Docker Installation
3.1 Prepare Environment
Docker image for SQLE 3.0 is available.
3.2 Install MySQL (Docker)
# Docker run MySQL (same as RPM section)3.3 Deploy SQLE Container
# Pull image
docker pull actiontech/sqle-ce:latest
# Save image (offline servers)
docker save actiontech/sqle-ce:latest > sqle.tar
# Load image on target server
docker load < sqle.tar
# Run SQLE container
docker run -d \
--name sqle-server \
-p 10000:10000 -p 10001:10001 \
-e MYSQL_HOST="IP" \
-e MYSQL_PORT=3306 \
-e MYSQL_USER="root" \
-e MYSQL_PASSWORD="sqle2023" \
-e MYSQL_DMS_SCHEMA="dms" \
-e MYSQL_SQLE_SCHEMA="sqle" \
actiontech/sqle-ce:latestAfter the container starts, open http://IP:10000 to see the SQLE UI.
4 Summary
4.1 Overall Process
RPM installation is straightforward but requires correct secret_key configuration; otherwise, reinstall after cleaning the database.
Docker installation is fast and hassle‑free, completing in minutes.
4.2 RPM Issues
Port Mismatch
Documentation states default port 10000, but actual default may be 7601.
Missing Semicolon
SQL statements sometimes lack a trailing semicolon and need manual addition.
Service Startup
RPM registers services with systemd, yet a custom script is used to start both dms and sqled together.
4.3 Docker Issues
Docker Run Flags
The -d (detached) flag is sufficient; -it is unnecessary for this use case.
Configuration File Editing
Since the config resides inside the container, modify it by copying out with docker cp , editing, then copying back, or mount a host directory using -v .
Multiple Processes in One Container
SQLE runs both dms and sqled in a single container; separating them into two containers is recommended for easier management.
Aikesheng Open Source Community
The Aikesheng Open Source Community provides stable, enterprise‑grade MySQL open‑source tools and services, releases a premium open‑source component each year (1024), and continuously operates and maintains them.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.