If you are not deploying the code, at the same time as running the migrations, you will get this error. You are not advised (opinionated software, remember) to run migrations out of band of a deploy, since with opinionated Rails, at least - you should do these things in parallel!
I would advise you bind the deploy migrations task to the standard deploy, and do as Rafa suggested, and check that the files are indeed there. It's interesting - this issue didn't come up in ~3 years now, and it's just had a ticket opened on the tracker for this to use the <latest_relese> rather than the current time. -- Lee Hambley Twitter: @leehambley | @capistranorb -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
