Heroku Removing Gemfile.lock since it was created on Windows

Does anyone have any ideas about this? Attempt to deploy to the hero. I can make a successful launch in the hero, but I suspect that this warning is probably the reason that I get regret that something went wrong. Any input on this will be appreciated. By the way, I think this is a Windows problem. Honestly, this is my first crack in this, and it has been interesting so far, but if it's stupid, I'm going to deal with an attempt to develop on Windows, I could also hack the Linux machine setup. I know that there will be complications, but who knows. I installed and used it before, but not for development. Any suggestions? Thanks!

Ruby 2.0.0 Rails 4.0.0 Windows 7 64

ATTENTION: Removal Gemfile.lockbecause it was created on Windows. The bundler will do everything possible, so native stones are handled properly. This can lead to unexpected gem versions appearing in your application.

Just for reference, here is the whole push to the hero:

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
+4
source share
1 answer

your file Gemfile.lockprobably contains

PLATFORMS
  ruby
  x86-mingw32

You need to delete

  x86-mingw32

so that he plays well with the hero. Yours Gemfile.lockmay have lines that conflict with deleting this, for example. You could install a separate version of the gem mysql2for windows.

mysql2 (0.3.11-x86-mingw32)
mysql2 (0.3.14)

, , , Windows. Gemfile, bundler .

+6

All Articles