Question

I deployed a new feature to Engine Yard that had migrations. Of course I passed the migration flag and it worked successfully. But then I decided to take the feature out.

Note: These migrations removed some columns

I then rolled back on github and deployed again, but now I'm getting a postgres error that a column doesn't exist (this is a column removed in the migration from before)

How do you rollback migrations on Engine Yard?

Was it helpful?

Solution 2

I've discovered that when you ssh into your engineyard app you can go to the current deploy's directory and run bundle exec rake ... thus you can run probably run bundle exec rake db:rollback

OTHER TIPS

TMP,

While there is a rollback command built into the engineyard gem, it would be better to just deploy with a new migration that effectively adds the columns back in or update the code to not use the missing columns.

Evan

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top