Question. about migrate HOT 3 CLOSED

You'll need to determine how and when you want to run migrations since that affects how you use the tool.

Personally, my workflow looks like this:

1. Create migrations using the CLI create command. This ensures that the name of the migration is compatible w/ migrate. Note, I'm using file sources for my migrations and package everything into a docker image for my API servers.
2. Use the CLI to test the up/down migration on a test DB instance. The force command is handy for "fixing" borked migrations.
3. Ship the API server docker image. The API server (go binary) is responsible for running migrations (up only) when starting. I rely on the db lock to prevent contention between migrations and manage migrations manually using the CLI if necessary.

from migrate.

Correct, the table used to track the currently applied migration is created by migrate, specifically, by the db driver.

from migrate.

Thanks for your comments. I assume that the cli will create the version table on first run? Because that is what I don't get 😀 .. Do I create it my self or does the migrate app do that?

from migrate.