Heroku 是否预加载了一些特定的 gem?
在这些链接上提出了类似的问题,但答案并没有解决我的问题。
我有以下 Gemfile :
source 'http://rubygems.org'
gem 'rails'
gem 'daemons', '=1.0.10'
gem 'sqlite3'
gem 'locomotive_cms', :git => 'git://github.com/locomotivecms/engine.git', :require => 'locomotive/engine'
在我的 Gemfile.lock 中有这样:
daemons (1.0.10)
delayed_job (3.0.0.pre4)
activesupport (~> 3.0)
daemons (= 1.0.10)
但由于某些对我来说不明原因,我在 Heroku 上收到此错误:
You have already activated daemons 1.1.0, but your Gemfile requires daemons 1.0.10. Consider using bundle exec
这是否意味着 Heroku 以某种方式添加了此 gem 版本,或者...我对捆绑有什么误解?
Similar questions was asked on those links but the answer do not solve my problem.
why does heroku not list the same gems as i have locally?
I have the following Gemfile :
source 'http://rubygems.org'
gem 'rails'
gem 'daemons', '=1.0.10'
gem 'sqlite3'
gem 'locomotive_cms', :git => 'git://github.com/locomotivecms/engine.git', :require => 'locomotive/engine'
In my Gemfile.lock there so :
daemons (1.0.10)
delayed_job (3.0.0.pre4)
activesupport (~> 3.0)
daemons (= 1.0.10)
But for some obscure reason to me, I get this error on Heroku :
You have already activated daemons 1.1.0, but your Gemfile requires daemons 1.0.10. Consider using bundle exec
So does it means Heroku adds someway this gem version, or ... I misunderstood something about bundle ?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
Heroku 已经在你的堆栈中安装了守护进程 1.1.0,并且elasto_job gem 需要版本 1.0.10,因为他们说,他们在使用其他版本时遇到了问题。
我已经与 Heroku ruby 团队交谈过,他们说需要对依赖项进行太多更改才能解决此问题,所以他们不会。因此,您要么像此处所述解决它,然后更改您的堆栈(如果您正在运行严格的生产环境,我不建议这样做),或者您可以使用 我的延迟作业repo 并避免错误,风险由您自行承担。我所做的只是更改对守护程序版本的依赖关系。
Heroku already installs daemons 1.1.0 in your stack and the delayed_job gem requires the version 1.0.10 because, they said, they had problems with other versions.
I've talked with the Heroku ruby team and they said that it would require too many changes in their dependancies to fix this, so they won't. So you either solve it like described here and change your stack (which I would not suggest if you are running a serious production environment) or you can use the delayed job from my repo and avoid the error at your own risk. What I did was simply to change the dependency on the daemons version.