Docs/Commands/Overview
Commands
Every DBLift command, what it does, and which edition ships it. Flags listed here are global — they work with any command and are documented once.
$ dblift [global flags] <command> [command flags]Everyday commands
The migrate loop. Available in every edition.
migrateApply migrations.
infoShow migration information.
validateValidate migration scripts.
undoRoll back migrations.
configInspect DBLift configuration.
mcpServe a stdio MCP server for coding agents.
Adopting and repairing
Run once, or when something is out of step.
baselineMark an existing database as already at a given version.
repairBring the schema history table back in line with the scripts on disk.
import-flywayCopy a Flyway schema history into DBLift's own history table.
cleanDrop every object in the target schema, including the schema history table.destructive
Database utilities
Grouped under dblift db. Use these when a connection will not come up.
db list-driversList native Python drivers
db validate-configValidate configuration file
db diagnose-connectionPerform detailed diagnosis of native driver availability. --format text|json|pretty
db check-connectionTest database connection
Pro and Enterprise commands
These appear in --help on the open-source build and explain how to get them; running one without a licence exits with code 4.
Global flags
Accepted before any command. Command pages list only their own flags.
FlagDefaultDescription
--configautoPath to config file. Omit it and DBLift finds the file itself.--env NAME—Named environment from the config file's environments: section. Overrides DBLIFT_ENV.--scripts—Migration scripts directory. Repeatable; subdirectories are scanned by default.--no-recursiveoffDo not scan --scripts subdirectories. Same as migrations.recursive=false.--dry-runoffDry run mode — nothing is written to the database.--installed-bydb userValue recorded in the installed_by column.--log-levelinfoOne of debug, info, warn, error. Case-insensitive.--log-formattexttext, json or html.--log-dirlogsDirectory the run's log file is written to.--quiet, -qoffSuppress info and debug lines on the console. Success, warnings and errors still show; file logs are unaffected.--no-progressoffDisable progress bars and spinners. Useful in CI logs.