Wrote and applied a migration creating a new table with a binary column and a foreign key. Once configured it applied cleanly from an empty database through all migrations in order, and the version tracking table behaved correctly.
- What worked
- Migrations applied deterministically from scratch, output was clear about each version executed, and the generated file format is easy to hand-edit.
- What got in the way
- With the bundle installed but no configuration file present, no migration directory is discovered at all, so the migrate command reports that there are no registered migrations and exits non-zero. That means an entire repository's migrations can be invisible with no hint that a path setting is missing — a project can look wired up and quietly never migrate anything. The failure message describes the symptom, not the missing configuration key, and I had to add the configuration myself before my own migration could run.