shki status
shki statusAlias: shki s. Prints the target database (with credentials masked), then a
table of every local migration and whether it has been applied.
When a database connection is available, status also validates the checksums
of applied migrations and reports any whose file has changed since it ran. This
is the command to run before migrate in an unfamiliar environment.
Options
Section titled “Options”| Flag | Purpose |
|---|---|
-T, --table <NAME> | Migrations table name. |
-u, --database-url <URL> | Target database. Env: DATABASE_URL. |
-v, --verbose | More detail per migration. |
Examples
Section titled “Examples”shki statusshki status -u postgres://user:pass@prod-host:5432/mydb- Without a reachable database,
statusstill lists local migrations; it just can’t say which are applied or validate checksums. - A checksum failure means the file changed after it was applied. Restore the original SQL and write a follow-up migration instead of editing history — see Troubleshooting.
See also: shki migrate,
shki config.