You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
From James Eggers: The migration directory can be changed via the configuration file currently. Regardless, we'll see what it'll do in order to implement such a request.
This would actually be useful to us too - under certain circumstances (until we can properly feature branch - we're held up by other factors at the moment) we would love to have two sets of migrations for two related products which are sharing the same DB but are evolving at different rates. e.g. /migrations and /migrations-otherproject.
Again if no one else is working on this I could look at it?
And my usecase in addition: Our application has two databases, and each of them should be updated using deploy scripts. Deploy scripts should run on different servers with different migrate folders. And I realy don't want to support config files for each environment.
Looks like it's tricky to implement the plugin without touching core code
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be useful when writing batch files to be able to provide the path to the migration files from the command line.
As it is, it always looks for the path "migrate" from the current working directory.
The text was updated successfully, but these errors were encountered: