bladepipe/cgdm-alone repository overview

⁠CloudDM Alone

CloudDM Alone is the standalone image of CloudDM. It combines the web console, execution capability, and metadata database runtime into a single container, which makes it suitable for local evaluation, PoC usage, individual users, small-team trials, and local integration testing.

[Website⁠] [Documentation⁠] [Blog⁠] [Gitee⁠ [Github⁠

⁠What Is CloudDM

CloudDM is a free and open-source database management platform for team collaboration. It provides access control, data masking, SQL auditing, CI/CD, and cross-region deployment capabilities.

It is not only a SQL query tool, and it is not only a database operations tool. It brings the following capabilities into one web product:

• Unified management for multiple databases and data sources
• Visual query, object management, and daily operations workflows
• Audit, risk validation, and approval before SQL execution
• Role-, resource-, and temporary-authorization-based access control
• Database access deployment closer to database networks through the Console + Sidecar architecture

If you need a database platform that can be adopted directly rather than just a lightweight command-line client, CloudDM is a better fit.

⁠Core Capabilities

⁠Query and Development

• Supports MySQL, Oracle, MariaDB, PostgreSQL, SQL Server, DB2, TiDB, ClickHouse, Doris, StarRocks, Redis, MongoDB, and more
• Provides a unified web console, SQL editor, result export, execution plans, transaction control, and syntax highlighting

⁠Database Management

• Supports management of catalogs, schemas, tables, columns, indexes, views, functions, stored procedures, triggers, users, and roles
• Suitable for unified management across multiple environments and instances

⁠Database CI/CD

• Supports Git Push, Web Hook, and HttpCall as CI/CD triggers
• Supports Gitee as a change repository

⁠Security and Permissions

• Supports both resource permissions and functional permissions
• Supports permission requests, grants, temporary authorization, and approval workflows
• Provides SQL auditing, risk interception, and data masking

⁠Workflow and Collaboration

• Supports SQL audit workflows, permission tickets, and change workflows
• Supports manual, immediate, and scheduled execution modes
• Supports OpenLDAP, OIDC, Windows AD, DingTalk, Feishu, and WeCom integrations for authentication and workflow engines
• Suitable as a shared database access entry point for teams

⁠License

CloudDM uses the business-friendly Apache 2.0 license.

⁠Usage

docker run -d --name cgdm-alone -p 8222:8222 bladepipe/cgdm-alone:3.0.7

For mainland China network environments:

docker run -d --name cgdm-alone -p 8222:8222 \
  cloudcanal-registry.cn-shanghai.cr.aliyuncs.com/clougence/cgdm-alone:3.0.7

After the container starts, open:

http://localhost:8222

To persist data to host directories:

mkdir -p /data/cgdm-alone/conf
mkdir -p /data/cgdm-alone/logs
mkdir -p /data/cgdm-alone/data
mkdir -p /data/cgdm-alone/mysql

docker run -d \
  --name cgdm-alone \
  -p 8222:8222 \
  -v /data/cgdm-alone/conf:/root/cgdm/alone/conf \
  -v /data/cgdm-alone/logs:/root/cgdm/alone/logs \
  -v /data/cgdm-alone/data:/root/cgdm/alone/data \
  -v /data/cgdm-alone/mysql:/var/lib/mysql \
  bladepipe/cgdm-alone:3.0.7

If you want to switch to an external MySQL instance, add MYSQL_EMBEDDED=false to the command and provide DB_HOST, DB_PORT, DB_DATABASE, DB_USERNAME, and DB_PASSWORD.

⁠Environment Variables

⁠General Startup Parameters

⁠Database Parameters

⁠Data Persistence

⁠Ports

For the minimal startup path, only 8222 needs to be mapped.

⁠Important Rule

This image generates configuration from environment variables only when /root/cgdm/alone/conf/alone.properties does not exist.