Migration history. For the people on call.
Know whatchanged.
The open-source CLI that traces a production table back to the migration, the moment, and the person.
Then run ledgerlight init
One table.
The whole story.
A column appeared in production. Follow it back to the migration that put it there.
add_status.sql
ALTER TABLE orders
ADD COLUMN status text;The statement that changed the schema.
orders.status
- When (UTC)
- By
deploy-bot
The table tells you what. The record tells you who and when.
ledgerlight blame orders
| When (UTC) | Migration | By | Change |
|---|---|---|---|
20261008_add_status.sql | deploy-bot | ADD COLUMN status text | |
20261006_add_total.sql | backend-team | ADD COLUMN total numeric | |
20261001_create_orders.sql | ci-runner | CREATE TABLE orders |
Small commands.
Long memory.
Record the migrations your team runs. Ask a table where it came from. Read the history.
Start the record
Initialize Ledgerlight for your database.
ledgerlight initFollow a table’s trail
Find its migrations, timestamps, and actors.
ledgerlight blame <table>See the history
Read the migration timeline.
ledgerlight timeline
The optional hosted dashboard
For your team.
A dashboard.
The command line is free. The hosted Team dashboard is optional.
The CLI stays freeTeam
Hosted dashboard$12USD per user
per month
Example only. No account is created.
Next time,
leave a trail.
Install the free CLI. Start recording your database’s history.