升级到Rails 3.2.11后,Capistrano部署失败

编程入门 行业动态 更新时间:2024-10-19 00:24:29
本文介绍了升级到Rails 3.2.11后,Capistrano部署失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧! 问题描述

我有生产Rails 3.2.3应用程序,可使用capistrano进行部署。当我决定将rails升级到3.2.11时,我执行了以下步骤:

I have production Rails 3.2.3 application which I use to deploy using capistrano. When I decided to upgrade rails to 3.2.11 i did following steps:

  • 在Gemfile中更改了rails版本
  • 运行捆绑更新轨道
  • 从供应商/缓存,Gemfile和Gemfile.lock中推送新的宝石
  • 运行盖帽生产部署
  • changed rails version in Gemfile
  • run "bundle update rails"
  • pushed new gems from vendor/cache, Gemfile and Gemfile.lock
  • run "cap production deploy"
  • Capistrano现在失败,并显示错误:

    Capistrano now fails with error:

    * 2013-01-11 15:58:25 executing `deploy:assets:precompile' triggering before callbacks for `deploy:assets:precompile' * 2013-01-11 15:58:25 executing `deploy:assets:update_asset_mtimes' * executing "[ -e /home/deploy/projects/otv/shared/assets/manifest.yml ] && cat /home/deploy/projects/otv/shared/assets/manifest.yml || echo" servers: ["xxx.xxx.99.51"] [xxx.xxx.99.51] executing command command finished in 28ms * executing "cd -- /home/deploy/projects/otv/releases/20130111095812 && export LANG=en_US.UTF-8 && /usr/local/bin/bundle exec rake RAILS_ENV=production RAILS_GROUPS=assets assets:precompile && cp -- /home/deploy/projects/otv/shared/assets/manifest.yml /home/deploy/projects/otv/releases/20130111095812/assets_manifest.yml" servers: ["xxx.xxx.99.51"] [xxx.xxx.99.51] executing command ** [out :: xxx.xxx.99.51] cp: cannot stat ‘/home/deploy/projects/otv/shared/assets/manifest.yml’: No such file or directory command finished in 18773ms

    我尝试执行这些操作

    我的 Gemfile和deploy.rb

    推荐答案

    FWIW,将Capistrano更新为> 2.14.0之后,我得到了这个:

    FWIW, I was getting this after updating Capistrano to > 2.14.0:

    *** [err :: ourapp] cp: cannot stat `/home/deploy/www/ourapp/shared/assets/manifest.yml' *** [err :: ourapp] : No such file or directory

    我认为将资产链接到共享dir可以解决此问题,但我没有搞乱(必须部署),我只是将上限降级到2.13.5。

    I think symlinking the assets to the shared dir would fix it, but instead of messing around (gotta get this deploy out), I just downgraded cap back to 2.13.5.

    更多推荐

    升级到Rails 3.2.11后,Capistrano部署失败

    本文发布于:2023-11-11 07:19:04,感谢您对本站的认可!
    本文链接:https://www.elefans.com/category/jswz/34/1577752.html
    版权声明:本站内容均来自互联网,仅供演示用,请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系,我们将在24小时内删除。
    本文标签:升级到   Rails   Capistrano

    发布评论

    评论列表 (有 0 条评论)
    草根站长

    >www.elefans.com

    编程频道|电子爱好者 - 技术资讯及电子产品介绍!