Having recently written a shell-based migration tool due to my frustration at trying to support the Python one we were using previously, this is an interesting topic to me.<p>As with the python tool we had been using, this doesn't appear to support SSL connections for mysql/postgresql?<p>I'm also dubious about the "format" used - the python tool we had been using, and the new shell tool I wrote to replace it, both just read regular SQL files in a series of directories (one called `up.sql` and one called `down.sql`). This meant that migrating from one tool to another was <i>ridiculously</i> easy, and if trying to debug, an entire SQL file can just be read into `mysql`/etc. Having the files separated (and without any special syntax required) also makes creating them much simpler - anything that can write out SQL can do it - even e.g. schema-change tools that record changes between two known states.<p>Anyway, good luck with it. Ultimately these tools usually come about to solve some problem or scratch some itch, so I hope your itch is scratched!