Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Somehow my test environment forgot to copy over several migrations. In order to troubleshoot, I want to call certain migration files by hand.
Is there a rake db:migrate option or trick that allows me to pass in a directory full of migrations that should be ran? Or even a specific migration file that will be ran?
These migrations are not present under db/migrate/, but rather in another gems’ migration folder (/home/ber/.rvm/gems/ruby-1.8.7-p302@xxx/gems/spree_auth-1.0.0/db/migrate/).
If you generate your migrations with a specific version then this post will help you with that.
From post:
Where
VERSION=is set to whatever comes from your generation.