0

Recently moved project to another server. Capistrano stoped working. How to find what is wrong?

 ** sftp upload #<StringIO:0x00000001b4b5d0> -> /home/xxx/production/TOUCH_ASSETS
    [yyy.xxx.lt] /home/xxx/production/TOUCH_ASSETS
    [yyy.xxx.lt] done
  * sftp upload complete
  * executing "cat /home/xxx/production/TOUCH_ASSETS | while read asset; do touch -cm -- \"$asset\"; done && rm -f -- /home/xxx/production/TOUCH_ASSETS"
    servers: ["yyy.xxx.lt"]
    [yyy.xxx.lt] executing command
    command finished in 593ms
*** [deploy:update_code] rolling back

Using RVM and Capistrano 2.14.1

Jonas
  • 4,683
  • 4
  • 45
  • 81
  • Maybe [this](http://stackoverflow.com/questions/14276278/capistrano-deployment-fails-after-upgrade-to-rails-3-2-11) can solve your problem. – Andrew Jan 12 '13 at 13:20

1 Answers1

3

I've got the same problem, just do set :rails_env, "production" instead of set :rails_env, :production.

Andrew
  • 46
  • 2