-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run diff -q #{release_path}/db/migrate #{current_path}/db/migrate
befo...
#71
Conversation
…efore running `rake db:migrate`
ping @kirs @leehambley @seenmyfate |
ping @leehambley I hope this can be merged so I can stop using my own fork. |
@kirs maintains this Gem, sure he'll be happy to merge it when he has time. |
Great idea! What do you think about making this thing optional? |
Yay for this! |
@umhan35 any updates concerning my comment? |
@kirs It sounds good. I have a rough idea and will try it if I have time tomorrow. My initial idea is to put a set statement (key name is probably conditionally_migrate, the value would be false) here: https://github.com/capistrano/rails/blob/master/lib/capistrano/tasks/migrations.rake#L22 I came back to China. Sorry for this late reply. |
@kirs I wrote some code making conditionally-migrate optional. Please check it out. |
run `diff -q #{release_path}/db/migrate #{current_path}/db/migrate` befo...
Awesome. Thanks! |
...re running
rake db:migrate
So it shorten the unnecessary time to run migrations.