Forums → Instiki →

Heroku hosting fails

Subscribe to Heroku hosting fails 8 posts, 2 voices

 
posted 3 years ago
bcs 11 posts

I followed the instructions on the instiki site to create and host a wiki on heroku. But there seems to be an error which is probably to do with the gemfile? Here is the build log

—–> Building on the Heroku-20 stack

—–> Determining which buildpack to use for this app

—–> Ruby app detected

—–> Installing bundler 1.17.3

—–> Removing BUNDLED WITH version in the Gemfile.lock

—–> Compiling Ruby/Rack

—–> Using Ruby version: ruby-2.7.1

—–> Installing dependencies using bundler 1.17.3

   Running: BUNDLE_WITHOUT='development:test' BUNDLE_PATH=vendor/bundle BUNDLE_BIN=vendor/bundle/bin BUNDLE_DEPLOYMENT=1 BUNDLE_GLOBAL_PATH_APPENDS_RUBY_SCOPE=1 bundle install -j4

   Fetching gem metadata from https://rubygems.org/...........

   Unable to use the platform-specific (x86_64-linux) version of nokogiri (1.11.4) because it has different dependencies from the ruby version. To use the platform-specific version of the gem, run `bundle config set specific_platform true` and install again.

   Fetching https://github.com/distler/maruku.git

   Fetching rake 12.3.2

   Installing rake 12.3.2

   Fetching RedCloth 4.3.2

   Using bundler 2.1.4

   Fetching abstract 1.0.0

   Fetching daemons 1.3.1

   Installing abstract 1.0.0

   Installing daemons 1.3.1

   Installing RedCloth 4.3.2 with native extensions

   Fetching erubis 2.7.0

   Installing erubis 2.7.0

   Fetching eventmachine 1.2.7

   Installing eventmachine 1.2.7 with native extensions

   Fetching file_signature 1.2.0

   Installing file_signature 1.2.0

   Fetching mime-types-data 3.2018.0812

   Installing mime-types-data 3.2018.0812

   Fetching multi_xml 0.6.0

   Installing multi_xml 0.6.0

   Fetching iconv 1.0.8

   Installing iconv 1.0.8 with native extensions

   Fetching itextomml 1.6.0

   Installing itextomml 1.6.0 with native extensions

   Fetching json 2.2.0

   Installing json 2.2.0 with native extensions

   Fetching mini_portile2 2.3.0

   Installing mini_portile2 2.3.0

   Fetching syntax 1.1.0

   Installing syntax 1.1.0

   Fetching pg 1.0.0

   Installing pg 1.0.0 with native extensions

   Fetching rack 2.2.3

   Installing rack 2.2.3

   Fetching rails_xss 0.4.0

   Installing rails_xss 0.4.0

   Fetching rdoc 4.3.0

   Installing rdoc 4.3.0

   Fetching rubyzip 0.9.9

   Installing rubyzip 0.9.9

   Fetching test-unit 2.5.5

   Installing test-unit 2.5.5

   Fetching mime-types 3.2.2

   Installing mime-types 3.2.2

   Fetching nokogiri 1.11.4

   Fetching thin 1.7.2

   Installing thin 1.7.2 with native extensions

   Fetching httparty 0.16.4

   Installing httparty 0.16.4

   Downloading nokogiri-1.11.4 revealed dependencies not in the API or the lockfile

   (racc (~> 1.4), mini_portile2 (~> 2.5.0)).

   Either installing with `--full-index` or running `bundle update nokogiri` should

   fix the problem.

   Bundler Output: Fetching gem metadata from https://rubygems.org/...........

   Unable to use the platform-specific (x86_64-linux) version of nokogiri (1.11.4) because it has different dependencies from the ruby version. To use the platform-specific version of the gem, run `bundle config set specific_platform true` and install again.

   Fetching https://github.com/distler/maruku.git

   Fetching rake 12.3.2

   Installing rake 12.3.2

   Fetching RedCloth 4.3.2

   Using bundler 2.1.4

   Fetching abstract 1.0.0

   Fetching daemons 1.3.1

   Installing abstract 1.0.0

   Installing daemons 1.3.1

   Installing RedCloth 4.3.2 with native extensions

   Fetching erubis 2.7.0

   Installing erubis 2.7.0

   Fetching eventmachine 1.2.7

   Installing eventmachine 1.2.7 with native extensions

   Fetching file_signature 1.2.0

   Installing file_signature 1.2.0

   Fetching mime-types-data 3.2018.0812

   Installing mime-types-data 3.2018.0812

   Fetching multi_xml 0.6.0

   Installing multi_xml 0.6.0

   Fetching iconv 1.0.8

   Installing iconv 1.0.8 with native extensions

   Fetching itextomml 1.6.0

   Installing itextomml 1.6.0 with native extensions

   Fetching json 2.2.0

   Installing json 2.2.0 with native extensions

   Fetching mini_portile2 2.3.0

   Installing mini_portile2 2.3.0

   Fetching syntax 1.1.0

   Installing syntax 1.1.0

   Fetching pg 1.0.0

   Installing pg 1.0.0 with native extensions

   Fetching rack 2.2.3

   Installing rack 2.2.3

   Fetching rails_xss 0.4.0

   Installing rails_xss 0.4.0

   Fetching rdoc 4.3.0

   Installing rdoc 4.3.0

   Fetching rubyzip 0.9.9

   Installing rubyzip 0.9.9

   Fetching test-unit 2.5.5

   Installing test-unit 2.5.5

   Fetching mime-types 3.2.2

   Installing mime-types 3.2.2

   Fetching nokogiri 1.11.4

   Fetching thin 1.7.2

   Installing thin 1.7.2 with native extensions

   Fetching httparty 0.16.4

   Installing httparty 0.16.4

   Downloading nokogiri-1.11.4 revealed dependencies not in the API or the lockfile

   (racc (~> 1.4), mini_portile2 (~> 2.5.0)).

   Either installing with `--full-index` or running `bundle update nokogiri` should

   fix the problem.

!

! Failed to install gems via Bundler.

!

! Push rejected, failed to compile Ruby app.

! Push failed

Could someone help with this issue?
 
posted 3 years ago
distler Moderator 123 posts

Hmm. Yes, it looks like the Gemfile.lock.heroku was out-of-sync with the Gemfile.heroku. I’ve updated both of them.
 
posted almost 3 years ago
bcs 11 posts

I tried it again and got this error:

—–> Building on the Heroku-20 stack

—–> Determining which buildpack to use for this app

—–> Ruby app detected

—–> Installing bundler 1.17.3

—–> Removing BUNDLED WITH version in the Gemfile.lock

—–> Compiling Ruby/Rack

—–> Using Ruby version: ruby-2.7.1

—–> Installing dependencies using bundler 1.17.3

   Running: BUNDLE_WITHOUT='development:test' BUNDLE_PATH=vendor/bundle BUNDLE_BIN=vendor/bundle/bin BUNDLE_DEPLOYMENT=1 BUNDLE_GLOBAL_PATH_APPENDS_RUBY_SCOPE=1 bundle install -j4

   You are trying to install in deployment mode after changing

   your Gemfile. Run `bundle install` elsewhere and add the

   updated Gemfile.lock to version control.

   

   If this is a development machine, remove the /tmp/build_34292e11/Gemfile freeze 

   by running `bundle install --no-deployment`.

   

   Bundler is unlocking ruby

   

   You have added to the Gemfile:

   * rubyzip (~> 2.3.0)

   

   You have deleted from the Gemfile:

   * rubyzip  (~> 2.3.0)

   Bundler Output: You are trying to install in deployment mode after changing

   your Gemfile. Run `bundle install` elsewhere and add the

   updated Gemfile.lock to version control.

   

   If this is a development machine, remove the /tmp/build_34292e11/Gemfile freeze 

   by running `bundle install --no-deployment`.

   

   Bundler is unlocking ruby

   

   You have added to the Gemfile:

   * rubyzip (~> 2.3.0)

   

   You have deleted from the Gemfile:

   * rubyzip  (~> 2.3.0)

!

! Failed to install gems via Bundler.

!

! Push rejected, failed to compile Ruby app.

! Push failed

I am not sure now if this was a problem from my side.
 
posted almost 3 years ago
distler Moderator 123 posts

Clearly you are trying to use the wrong Gemfile.lock. The correct one (which you are supposed to rename from Gemfile.lock.heroku) doesn’t have a “BUNDLED WITH” line in it.

Try following these instructions.
 
posted almost 3 years ago
bcs 11 posts

I followed the exact instructions on the site. The Gemfile.lock that I can see on my machine also doesn’t have the “BUNDLED WITH” line. The code seems to be running BUNDLED_WITHOUT :

remote: Running: BUNDLE_WITHOUT=‘development:test’ BUNDLE_PATH=vendor/bundle BUNDLE_BIN=vendor/bundle/bin BUNDLE_DEPLOYMENT=1 BUNDLE_GLOBAL_PATH_APPENDS_RUBY_SCOPE=1 bundle install -j4

But I do not know what BUNDLED_WITH version it is removing in a previous line. None of the files (Gemfile or Gemfile.lock) seem to have either BUNDLED_WITH or the BUNDLED_WITHOUT line. I found a dicussion on stackoverflow but the accepted answer says the same thing the log file says. I did not run bundle install at any point.
 
posted almost 3 years ago
distler Moderator 123 posts

Hmm. Looking more closely at your error message, I think this commit might fix your problem. Dunno what the source of the extra space is, but that seems to be the cause of Heroku’s complaints.
 
posted almost 3 years ago
bcs 11 posts

It works now! Thanks!
Forums → Instiki →