Heroku删除Gemfile.lock,因为它是在Windows上生成的 [英] Heroku Removing Gemfile.lock because it was generated on Windows
问题描述
有人对此有任何想法吗?试图部署到heroku。我能够成功启动到heroku,但我怀疑这个警告可能是我得到遗憾的原因出错的消息。任何对此的意见,将不胜感激。顺便说一下,我认为这是一个Windows问题。说实话,这是我在这方面的第一个破解,迄今为止它已经很有趣,但如果这是我试图在Windows上开发的废话,那么我可能会开始设置一台Linux机器。我知道会有复杂情况,但谁知道。我已经安装并使用过它,但从未用于开发。有什么想法吗?谢谢!
Ruby 2.0.0
Rails 4.0.0
Windows 7 64
警告:
删除 Gemfile.lock
,因为它是在Windows上生成的。
Bundler会做一个完整的解决方案,以便正确处理原生宝石。
这可能会导致您的应用程序使用意外的宝石版本。
仅供参考,此处全面推送至heroku:
c:\dev\project2> git push heroku master
为密钥'/c/Users/vern/.ssh/id_rsa输入密码':
计数对象:5,完成。
使用多达8个线程的增量压缩。
压缩对象:100%(3/3),完成。
写入对象:100%(3/3),315字节| 0字节/秒,完成。
总计3(增量2),重用0(增量0)
-----> Ruby应用检测到
----->编译Ruby / Rails
----->使用Ruby版本:ruby-2.0.0
----->使用Bundler版本1.3.2安装依赖关系
正在运行:bundle install --without development:test --path vendor / bundle --binstubs vendor / bundle / bin
从https:// rubygems中获取gem元数据。 org / ...........
从https://rubygems.org/获取gem元数据..
解析依赖关系...
使用rake(10.1.0 )
使用i18n(0.6.5)
使用minitest(4.7.5)
使用multi_json(1.8.2)
使用atomic(1.1.14)
使用thread_safe(0.1.3)
使用tzinfo(0.3.38)
使用activesupport(4.0.0)
使用构建器(3.1.4)
使用erubis(2.7.0)
使用rack(1.5.2)
使用rack-test(0.6.2)
使用actionpack(4.0.0)
使用MIME类型(1.25.1)
使用polyglot(0.3.3)
使用treetop(1.4.15)
使用邮件(2.5.4)
使用actionmailer(4.0.0)
使用activemodel(4 .0.0)
使用activerecord-deprecated_finders(1.0.3)
使用arel(4.0.1)
使用activerecord(4.0.0)
使用bundler(1.3.2)
使用coffee-script-source(1.6.3)
使用execjs(2.0.2)
使用coffee-script(2.2.0)
使用thor(0.18.1)
使用railties(4.0.0)
使用coffee-rails(4.0.1)
使用hike(1.2.3)
使用jbuilder(1.5.2)
使用jquery-rails(3.0.4)
使用json(1.8.1)
使用mysql2(0.3.14)
使用tilt(1.4.1)
使用链轮(2.10。 1)
使用sprockets-rails(2.0.1)
使用rails(4.0.0)
使用rails_serve_static_assets(0.0.1)
使用rails_stdout_logging(0.0.3)
使用rails_12factor(0.0.2)
使用rdoc(3.12.2)
使用sass(3.2.12)
使用sass-rails(4.0.1)
使用sdoc (0.3.20)
使用tur bolinks(1.3.1)
使用uglifier(2.3.1)
您的包已完成!它已安装到./vendor/bundle
捆绑完成(9.55s)
清理捆绑器缓存。
----->编写config / database.yml以从DATABASE_URL读取
----->为Rails资产管道准备应用程序
运行:rake资产:预编译
资产预编译完成(2.58s)
清理资产
----->
警告:
删除` Gemfile.lock`因为它是在Windows上生成的。
Bundler会做一个完整的解决方案,以便正确处理原生宝石。
这可能会导致应用程序使用意外的宝石版本。
----->发现过程类型
Procfile声明类型 - > (无)
Ruby的默认类型 - >控制台,耙,网络,工人
----->编译段塞大小:21.1MB
----->启动完成,v12
http://fast-lake-6950.herokuapp.com部署到Heroku
到git@heroku.com:fast-lake-6950.git
c81423c..01c6a2d master - > master
您的 Gemfile.lock
文件可能包含
平台
红宝石
x86-mingw32
您需要删除
x86-mingw32
可以很好地与heroku一起玩。您的 Gemfile.lock
中可能存在与删除相冲突的行。你可能已经安装了一个独立版本的 mysql2
gem for windows。
mysql2(0.3.11-x86-mingw32)
mysql2(0.3.14)
您可能需要删除引用仅限于宝石版本的行。为此,您可能需要删除导致bundler安装该宝石的 Gemfile
中的行。
Does anyone have any idea about this one? Trying to deploy to heroku. I am able to do a successful launch to heroku but I suspect this warning is probably the reason I get the sorry something went wrong message. Any input on this would be appreciated. By the way I am thinking this is a Windows issue. To be honest this is my first crack at this and it's been interesting so far but if this is the nonsense I am going to deal with trying to develop on Windows I might as well get cracking on setting up a linux machine. I know there will be complications as well but who knows. I have installed and used it before but never for development. Any thoughts? Thanks!
Ruby 2.0.0 Rails 4.0.0 Windows 7 64
WARNINGS:
Removing Gemfile.lock
because it was generated on Windows.
Bundler will do a full resolve so native gems are handled properly.
This may result in unexpected gem versions being used in your app.
Just for reference here is the whole push to heroku:
c:\dev\project2>git push heroku master
Enter passphrase for key '/c/Users/vern/.ssh/id_rsa':
Counting objects: 5, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 315 bytes | 0 bytes/s, done.
Total 3 (delta 2), reused 0 (delta 0)
-----> Ruby app detected
-----> Compiling Ruby/Rails
-----> Using Ruby version: ruby-2.0.0
-----> Installing dependencies using Bundler version 1.3.2
Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin
Fetching gem metadata from https://rubygems.org/...........
Fetching gem metadata from https://rubygems.org/..
Resolving dependencies...
Using rake (10.1.0)
Using i18n (0.6.5)
Using minitest (4.7.5)
Using multi_json (1.8.2)
Using atomic (1.1.14)
Using thread_safe (0.1.3)
Using tzinfo (0.3.38)
Using activesupport (4.0.0)
Using builder (3.1.4)
Using erubis (2.7.0)
Using rack (1.5.2)
Using rack-test (0.6.2)
Using actionpack (4.0.0)
Using mime-types (1.25.1)
Using polyglot (0.3.3)
Using treetop (1.4.15)
Using mail (2.5.4)
Using actionmailer (4.0.0)
Using activemodel (4.0.0)
Using activerecord-deprecated_finders (1.0.3)
Using arel (4.0.1)
Using activerecord (4.0.0)
Using bundler (1.3.2)
Using coffee-script-source (1.6.3)
Using execjs (2.0.2)
Using coffee-script (2.2.0)
Using thor (0.18.1)
Using railties (4.0.0)
Using coffee-rails (4.0.1)
Using hike (1.2.3)
Using jbuilder (1.5.2)
Using jquery-rails (3.0.4)
Using json (1.8.1)
Using mysql2 (0.3.14)
Using tilt (1.4.1)
Using sprockets (2.10.1)
Using sprockets-rails (2.0.1)
Using rails (4.0.0)
Using rails_serve_static_assets (0.0.1)
Using rails_stdout_logging (0.0.3)
Using rails_12factor (0.0.2)
Using rdoc (3.12.2)
Using sass (3.2.12)
Using sass-rails (4.0.1)
Using sdoc (0.3.20)
Using turbolinks (1.3.1)
Using uglifier (2.3.1)
Your bundle is complete! It was installed into ./vendor/bundle
Bundle completed (9.55s)
Cleaning up the bundler cache.
-----> Writing config/database.yml to read from DATABASE_URL
-----> Preparing app for Rails asset pipeline
Running: rake assets:precompile
Asset precompilation completed (2.58s)
Cleaning assets
----->
WARNINGS:
Removing `Gemfile.lock` because it was generated on Windows.
Bundler will do a full resolve so native gems are handled properly.
This may result in unexpected gem versions being used in your app.
-----> Discovering process types
Procfile declares types -> (none)
Default types for Ruby -> console, rake, web, worker
-----> Compiled slug size: 21.1MB
-----> Launching... done, v12
http://fast-lake-6950.herokuapp.com deployed to Heroku
To git@heroku.com:fast-lake-6950.git
c81423c..01c6a2d master -> master
your Gemfile.lock
file likely contains
PLATFORMS
ruby
x86-mingw32
You need to remove
x86-mingw32
for it to play nicely with heroku. There may be lines in your Gemfile.lock
that conflict with removing that, e.g. you might have installed a separate version of the mysql2
gem for windows.
mysql2 (0.3.11-x86-mingw32)
mysql2 (0.3.14)
you will likely need to remove the line that references the windows-only version of the gem. And for that to work, you may need to remove the line in your Gemfile
that causes bundler to install that gem.
这篇关于Heroku删除Gemfile.lock,因为它是在Windows上生成的的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!