Edeliver Migrations on a Single Instance

I’m using Edeliver with a clustered Phoenix application. When I run mix edeliver migrate staging it seems like migrations are run on multiple instances at the same time. That’s unnecessary since all of the instances in a single environment point to the same database. In the best scenario it will run on one and error out on the other when it tries to make modifications that already exist. Is that not how other people are using multiple instances in one environment?

The only way I’ve found to run them one time is to use the --host option to specify a specific instance. It seems error prone and much slower to have to manually specify that. Is there a way to make that the default in my config?

1 Like