Does migratus acquire a db lock before applying changes? I'm setting up a deployment where multiple app instances start up at once. It would be easiest if they could all just try to run migrations on startup but only the one that gets a lock can run them. If they don't lock, I'll have to do something more complicated.
Great! Thanks. I should have thought to look through issues.