dbbot Downloads and Release Notes
- GitHub Releases: https://github.com/fanderchan/dbbot/releases
- GitHub repository: https://github.com/fanderchan/dbbot
Release content description
dbbot uses single repository release. A distribution package will contain multiple types of capability directories at the same time, commonly including:
bin/dbbotctlmysql_ansibleclickhouse_ansiblemonitoring_prometheus_ansibleportable-ansible-v0.5.0-py3
If you only use one type of capability, it is also recommended to deploy it as a complete release package to facilitate subsequent version tracking and document correspondence.
dbbotctl in the release package
The curated release package includes /usr/local/dbbot/bin/dbbotctl for control-host lifecycle operations:
dbbotctl version: verify the installed dbbot release versiondbbotctl doctor: run local environment checks before deploymentdbbotctl release upgrade: replace the release package while preserving local statedbbotctl release rollback: return to a previous snapshot created by upgrade
Typical first checks after extracting the package:
/usr/local/dbbot/bin/dbbotctl version
/usr/local/dbbot/bin/dbbotctl doctor
For upgrade and rollback procedures, see dbbot Upgrade and Rollback.
Source Archive vs Release Package
On the GitHub Releases page you will usually see two kinds of archives:
| Type | Typical name | Use case |
|---|---|---|
| Release package (recommended) | dbbot-v0.1.0.tar.gz | Installation, deployment, offline distribution, and matching this documentation |
| Source archive | Source code (tar.gz) / Source code (zip) | Reading source code, secondary development, and contribution |
Key differences:
dbbot-vX.Y.Z.tar.gzis the curateddbbotrelease package. The download commands in this documentation point to this asset.Source codeis the tag snapshot generated by GitHub. It also contains repository maintenance and development content such as.github,assets, test files, and source directories likemysql_ansible/exporterregistrarandmysql_ansible/mysqlrouter_exporter.- The release package intentionally excludes those repository-maintenance files and source subprojects because its goal is a stable deployment input rather than a full development repository.
- If you want to install and run playbooks directly, download the release package. If you want to inspect the code, build binaries, follow unreleased changes, or contribute, use the source archive or clone the repository.
If the extracted tree contains .github, assets, or exporter source directories, you most likely downloaded GitHub’s Source code archive instead of the curated dbbot release package.