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:
rake db:migrate:up VERSION=20090408054532
Where VERSION= is set to whatever comes from your generation.