Saturday, January 7, 2012

Capistrano and the frustating "run rake with --trace" problem

It's a pain to run a capistrano deployment just to find out something failed - perhaps in one of your migrations. At this point, you are getting upset because --trace wasn't run and you couldn't see where the actual issue was. Never fear. Open your Rakefile and add:

Rake.application.options.trace = true

After adding that and committing, run your cap deploy again and you will see that stack trace.

YAY!

No comments:

Post a Comment