Trouble with Middleman installation in Ubuntu - ruby-on-rails

I installed middleman using gem install middleman, and I can see the gem listed in my local gem list
middleman (4.3.5)
middleman-cli (4.3.5)
middleman-core(4.3.5
but when I enter middleman -v I get
Unknown switches "-v"
If I enter middleman --version I get
Unknown switches "--version"
Did you mean? "--verbose"
which middleman returns home/.rbenv/shims/middleman
which ruby returns home/.rbenv/shims/ruby
I'm running ruby version 2.6.3 by default
on Ubuntu 18.04
I've been trying to install Middleman for two days and keep running into problems; it's turning into a nightmare!

What's the problem, exactly? middleman is successfully installed. It just doesn't support the switches you're trying to pass. Did you try middleman init project_name as defined in the README? Because the fact that you're getting the error messages you've shown indicates that middleman IS installed correctly and WILL work correctly. You just have to run it, like so:
foo:~|⇒ which middleman
/Users/foo/.rvm/gems/ruby-2.6.3/bin/middleman
foo:~|⇒ middleman
/Users/foo/.rvm/gems/ruby-2.6.3/gems/activesupport-4.2.11.1/lib/active_support/core_ext/object/duplicable.rb:111: warning: BigDecimal.new is deprecated; use BigDecimal() method instead.
== Could not find a Middleman project config.rb
foo:~|⇒ middleman --version
/Users/foo/.rvm/gems/ruby-2.6.3/gems/activesupport-4.2.11.1/lib/active_support/core_ext/object/duplicable.rb:111: warning: BigDecimal.new is deprecated; use BigDecimal() method instead.
Unknown switches "--version"
Did you mean? "--verbose"
foo:~|⇒ middleman init foo
/Users/foo/.rvm/gems/ruby-2.6.3/gems/activesupport-4.2.11.1/lib/active_support/core_ext/object/duplicable.rb:111: warning: BigDecimal.new is deprecated; use BigDecimal() method instead.
run git clone --depth 1 https://github.com/middleman/middleman-templates-default.git /var/folders/ts/qq2cd6pn42d15jrhc36cxbtw0000gn/T/d20191106-69912-29f30z from "."
Cloning into '/var/folders/ts/qq2cd6pn42d15jrhc36cxbtw0000gn/T/d20191106-69912-29f30z'...
remote: Enumerating objects: 19, done.
remote: Counting objects: 100% (19/19), done.
remote: Compressing objects: 100% (11/11), done.
remote: Total 19 (delta 0), reused 12 (delta 0), pack-reused 0
Unpacking objects: 100% (19/19), done.
exist
create .gitignore
create Gemfile
create config.rb
create source/images/.keep
create source/index.html.erb
create source/javascripts/site.js
create source/layouts/layout.erb
create source/stylesheets/site.css.scss
run bundle install from "./foo"
The dependency tzinfo-data (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mswin32, x86-mingw32, java, x64-mingw32. To add those platforms to the bundle, run `bundle lock --add-platform x86-mswin32 x86-mingw32 java x64-mingw32`.
The dependency wdm (~> 0.1) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mswin32, x86-mingw32, x64-mingw32. To add those platforms to the bundle, run `bundle lock --add-platform x86-mswin32 x86-mingw32 x64-mingw32`.
Fetching gem metadata from https://rubygems.org/...............
Fetching gem metadata from https://rubygems.org/..
Resolving dependencies...
Using concurrent-ruby 1.1.5
Using i18n 0.9.5
Fetching minitest 5.13.0
Installing minitest 5.13.0
Using thread_safe 0.3.6
Using tzinfo 1.2.5
Fetching activesupport 5.0.7.2
Installing activesupport 5.0.7.2
Fetching public_suffix 4.0.1
Installing public_suffix 4.0.1
Fetching addressable 2.7.0
Installing addressable 2.7.0
Using execjs 2.7.0
Fetching autoprefixer-rails 9.7.1
Installing autoprefixer-rails 9.7.1
Using backports 3.15.0
Using bundler 1.17.3
Using coffee-script-source 1.12.2
Using coffee-script 2.4.1
Using contracts 0.13.0
Using dotenv 2.7.5
Using erubis 2.7.0
Using fast_blank 1.0.0
Using fastimage 2.1.7
Using ffi 1.11.1
Using temple 0.8.2
Fetching tilt 2.0.10
Installing tilt 2.0.10
Using haml 5.1.2
Using hamster 3.0.0
Using hashie 3.6.0
Using kramdown 1.17.0
Using rb-fsevent 0.10.3
Using rb-inotify 0.10.0
Using listen 3.0.8
Using memoist 0.16.0
Using thor 0.20.3
Using middleman-cli 4.3.5
Using padrino-support 0.13.3.4
Using padrino-helpers 0.13.3.4
Fetching parallel 1.18.0
Installing parallel 1.18.0
Using rack 2.0.7
Using sassc 2.2.1
Using servolux 0.13.0
Using uglifier 3.2.0
Using middleman-core 4.3.5
Using middleman 4.3.5
Fetching middleman-autoprefixer 2.10.1
Installing middleman-autoprefixer 2.10.1
Bundle complete! 4 Gemfile dependencies, 42 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
foo:~|⇒

Related

Heroku Rails deployments are not using my latest javascript assets

My Production environment does not have recent additions to our javascript library, and I believe it's due to an issue with the build process on Heroku.
I noticed this because recent javascript additions were not working in Prod, but were working in local. I then added some console.logs to the javascript file and found that they would always work in local, but never in Prod.
I think the issue has to do with when I build in Heroku, as I consistently get a "Yarn executable was not detected in the system." error message. The build seems to still happen (precompiling takes 42 seconds), but I wonder if the javascript component might be breaking given the yarn error.
Here's a snippet of what I see in my logs when Heroku builds from master:
-----> Preparing app for Rails asset pipeline
Running: rake assets:precompile
Yarn executable was not detected in the system.
Download Yarn at https://yarnpkg.com/en/docs/install
Asset precompilation completed (42.77s)
Cleaning assets
Running: rake assets:clean
I don't believe I'm using Yarn anywhere in this project.
I then tried to precompile directly in the Heroku environment through the terminal, but I didn't have better luck there. Infact, I'm not even sure that it compiled anything given the reponse:
~ $ bundle exec rake assets:precompile
Yarn executable was not detected in the system.
Download Yarn at https://yarnpkg.com/en/docs/install
~ $ rails --version
Rails 5.2.3
The full log from Heroku deploy is below:
-----> Ruby app detected
-----> Compiling Ruby/Rails
-----> Using Ruby version: ruby-2.4.0
-----> Vendoring libpq 5.12.1
-----> Removing BUNDLED WITH version in the Gemfile.lock
-----> Installing dependencies using bundler 2.0.2
Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
The dependency tzinfo-data (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mingw32, x86-mswin32, x64-mingw32, java. To add those platforms to the bundle, run `bundle lock --add-platform x86-mingw32 x86-mswin32 x64-mingw32 java`.
Using rake 12.3.3
Using concurrent-ruby 1.1.5
Using i18n 1.6.0
Using minitest 5.11.3
Using thread_safe 0.3.6
Using tzinfo 1.2.5
Using activesupport 5.2.3
Using builder 3.2.3
Using erubi 1.8.0
Using mini_portile2 2.4.0
Using nokogiri 1.10.4
Using rails-dom-testing 2.0.3
Using crass 1.0.4
Using loofah 2.2.3
Using rails-html-sanitizer 1.2.0
Using actionview 5.2.3
Using rack 2.0.7
Using rack-test 1.1.0
Using actionpack 5.2.3
Using nio4r 2.4.0
Using websocket-extensions 0.1.4
Using websocket-driver 0.7.1
Using actioncable 5.2.3
Using globalid 0.4.2
Using activejob 5.2.3
Using mini_mime 1.0.2
Using mail 2.7.1
Using actionmailer 5.2.3
Using activemodel 5.2.3
Using arel 9.0.0
Using activerecord 5.2.3
Using mimemagic 0.3.3
Using marcel 0.3.3
Using activestorage 5.2.3
Using analytics-ruby 2.0.13
Using aws-eventstream 1.0.3
Using aws-partitions 1.217.0
Using aws-sigv4 1.1.0
Using jmespath 1.4.0
Using aws-sdk-core 3.68.0
Using aws-sdk-kms 1.24.0
Using aws-sdk-s3 1.48.0
Using bcrypt 3.1.12
Using msgpack 1.3.1
Using bootsnap 1.4.4
Using method_source 0.9.2
Using thor 0.20.3
Using railties 5.2.3
Using bootstrap-datepicker-rails 1.8.0.1
Using bundler 2.0.2
Using chart-js-rails 0.1.7
Using chartkick 3.3.0
Using coffee-script-source 1.12.2
Using execjs 2.7.0
Using coffee-script 2.4.1
Using coffee-rails 4.2.2
Using csv 3.1.2
Using orm_adapter 0.5.0
Using responders 2.4.0
Using warden 1.2.8
Using devise 4.5.0
Using unf_ext 0.0.7.6
Using unf 0.1.4
Using domain_name 0.5.20190701
Using dotenv 2.7.5
Using dotenv-rails 2.7.5
Using ffi 1.11.1
Using friendly_id 5.3.0
Using geocoder 1.5.2
Using groupdate 4.2.0
Using http-cookie 1.0.3
Using inline_svg 1.5.2
Using jbuilder 2.9.1
Using jquery-rails 4.3.5
Using mime-types-data 3.2019.0904
Using mime-types 3.3
Using netrc 0.11.0
Using rest-client 2.0.2
Using mailgun-ruby 1.2.0
Using mini_magick 4.9.5
Using pg 0.18.4
Using puma 3.12.1
Using sprockets 3.7.2
Using sprockets-rails 3.2.1
Using rails 5.2.3
Using rb-fsevent 0.10.3
Using rb-inotify 0.10.0
Using sass-listen 4.0.0
Using sass 3.7.4
Using tilt 2.0.9
Using sass-rails 5.1.0
Using social-share-button 1.2.1
Using turbolinks-source 5.2.0
Using turbolinks 5.2.0
Using uglifier 4.2.0
Bundle complete! 36 Gemfile dependencies, 95 gems now installed.
Gems in the groups development and test were not installed.
Bundled gems are installed into `./vendor/bundle`
Bundle completed (0.42s)
Cleaning up the bundler cache.
-----> Installing node-v10.15.3-linux-x64
-----> Detecting rake tasks
-----> Preparing app for Rails asset pipeline
Running: rake assets:precompile
Yarn executable was not detected in the system.
Download Yarn at https://yarnpkg.com/en/docs/install
Asset precompilation completed (42.77s)
Cleaning assets
Running: rake assets:clean
-----> Detecting rails configuration
###### WARNING:
You are deploying to a non-production environment: "staging".
This is not recommended.
See https://devcenter.heroku.com/articles/deploying-to-a-custom-rails-environment for more information.
###### WARNING:
We detected that some binary dependencies required to
use all the preview features of Active Storage are not
present on this system.
For more information please see:
https://devcenter.heroku.com/articles/active-storage-on-heroku
###### WARNING:
There is a more recent Ruby version available for you to use:
2.4.9
The latest version will include security and bug fixes, we always recommend
running the latest version of your minor release.
Please upgrade your Ruby version.
For all available Ruby versions see:
https://devcenter.heroku.com/articles/ruby-support#supported-runtimes
###### WARNING:
Potential EOL Ruby Version
You are using a Ruby version that has either reached its End of Life (EOL)
or will reach its End of Life on December 25th of this year.
We suggest you upgrade to Ruby 2.5.x or later
Once a Ruby version becomes EOL, it will no longer receive
security updates from Ruby core and may have serious vulnerabilities.
Please upgrade your Ruby version.
For a list of supported Ruby versions see:
https://devcenter.heroku.com/articles/ruby-support#supported-runtimes
###### WARNING:
No Procfile detected, using the default web server.
We recommend explicitly declaring how to boot your server process via a Procfile.
https://devcenter.heroku.com/articles/ruby-default-web-server
-----> Discovering process types
Procfile declares types -> (none)
Default types for buildpack -> console, rake, web
-----> Compressing...
Done: 119.6M
-----> Launching...
Released v119
https://zzzz.herokuapp.com/ deployed to Heroku

Rails deployment to Heroku build failure

I've been deploying my app regularly to Heroku during development with no problems until now.
This build failed after only a couple of minor HTML and CSS changes and still appears to be functioning normally locally. I've since reverted to a previous commit that built successfully but that too results in the same error.
I've only included the topmost section of the build log but can include the rest if it's relevant.
-----> Ruby app detected
-----> Compiling Ruby/Rails
-----> Using Ruby version: ruby-2.3.1
-----> Installing dependencies using bundler 1.15.2
Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.16.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
Fetching gem metadata from https://rubygems.org/.........
Fetching version metadata from https://rubygems.org/..
Fetching dependency metadata from https://rubygems.org/.
Using rake 12.3.1
Using concurrent-ruby 1.0.5
Using minitest 5.11.3
Using thread_safe 0.3.6
Using builder 3.2.3
Using erubi 1.7.1
Using mini_portile2 2.3.0
Using crass 1.0.4
Using rack 2.0.4
Using nio4r 2.3.0
Using websocket-extensions 0.1.3
Using mini_mime 1.0.0
Using arel 9.0.0
Using mimemagic 0.3.2
Using execjs 2.7.0
Using bcrypt 3.1.11
Using msgpack 1.2.4
Using popper_js 1.12.9
Using rb-fsevent 0.10.3
Using ffi 1.9.23
Using bundler 1.15.2
Using coffee-script-source 1.12.2
Using method_source 0.9.0
Using thor 0.20.0
Using orm_adapter 0.5.0
Using multi_json 1.13.1
Using pg 0.20.0
Using puma 3.11.4
Using tilt 2.0.8
Using i18n 1.0.1
Using tzinfo 1.2.5
Using rack-test 1.0.0
Using warden 1.2.7
Using sprockets 3.7.1
Using websocket-driver 0.7.0
Using mail 2.7.0
Using marcel 0.3.2
Using autoprefixer-rails 8.3.0
Using uglifier 4.1.9
Using bootsnap 1.3.0
Using rb-inotify 0.9.10
Using nokogiri 1.8.2
Using coffee-script 2.4.1
Using activesupport 5.2.0
Using sass-listen 4.0.0
Using globalid 0.4.1
Using activemodel 5.2.0
Using jbuilder 2.7.0
Using sass 3.5.6
Using activejob 5.2.0
Using activerecord 5.2.0
Using rails-dom-testing 2.0.3
Using loofah 2.2.2
Using bootstrap 4.1.0
Using rails-html-sanitizer 1.0.4
Using actionview 5.2.0
Using actionpack 5.2.0
Using actioncable 5.2.0
Using actionmailer 5.2.0
Using activestorage 5.2.0
Using railties 5.2.0
Using sprockets-rails 3.2.1
Using coffee-rails 4.2.2
Using responders 2.4.0
Using jquery-rails 4.3.3
Using rails 5.2.0
Using sass-rails 5.0.7
Using devise 4.4.3
Bundle complete! 24 Gemfile dependencies, 68 gems now installed.
Gems in the groups development and test were not installed.
Bundled gems are installed into ./vendor/bundle.
Bundle completed (10.65s)
Cleaning up the bundler cache.
Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.16.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
The latest bundler is 1.16.1, but you are currently running 1.15.2.
To update, run `gem install bundler`
-----> Installing node-v8.10.0-linux-x64
-----> Detecting rake tasks
-----> Preparing app for Rails asset pipeline
Running: rake assets:precompile
Yarn executable was not detected in the system.
Download Yarn at https://yarnpkg.com/en/docs/install
Asset precompilation completed (1.85s)
Cleaning assets
Running: rake assets:clean
sh: 1: Syntax error: word unexpected (expecting ")")
!
! Command: 'bin/rails runner "puts %Q{heroku_detecting_active_storage_config=#{Rails.application.config.active_storage.service}}"' failed unexpectedly:
! /tmp/build_51f3c3aeade1d66d2890531aa58b477d/vendor/bundle/ruby/2.3.0/gems/bundler-1.15.2/lib/bundler/rubygems_integration.rb:377:in `block (2 levels) in replace_gem': Error loading the 'sqlite3' Active Record adapter. Missing a gem it depends on? sqlite3 is not part of the bundle. Add it to your Gemfile. (Gem::LoadError)
! from /tmp/build_51f3c3aeade1d66d2890531aa58b477d/vendor/bundle/ruby/2.3.0/gems/activerecord-5.2.0/lib/active_record/connection_adapters/sqlite3_adapter.rb:12:in `<main>'
.
.
.
! Push rejected, failed to compile Ruby app.
! Push failed
This error seems to have been caused by a change to the Heroku Ruby buildpack as described here https://github.com/heroku/heroku-buildpack-ruby/issues/744 and is now fixed.

Ruby on rails app not deploying on Heroku

I am very new to development in general and am following Michael Hartl's rails book. My 'toy app' works perfectly on my local server but for some reason when I try to deploy it through Heroku, I get an error code H10 and the description is "app crashed".
I've got no idea what to do to fix this and have consulted many similar questions across forums but none of the answers seem to work for me. When trying to deploy initially I got a "push rejected" message but after running bundle update everything seemed to process perfectly, except I cannot view the app through heroku.
Any suggestions on how to fix this?
Here's the full build-log from the deployment:
-----> Ruby app detected
-----> Compiling Ruby/Rails
-----> Using Ruby version: ruby-2.3.4
-----> Installing dependencies using bundler 1.15.2
Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.16.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
Fetching gem metadata from https://rubygems.org/.........
Fetching version metadata from https://rubygems.org/..
Fetching dependency metadata from https://rubygems.org/.
Using rake 12.3.0
Using concurrent-ruby 1.0.5
Using minitest 5.10.3
Using thread_safe 0.3.6
Using builder 3.2.3
Using erubi 1.7.0
Using mini_portile2 2.3.0
Using crass 1.0.3
Using rack 2.0.3
Using nio4r 2.2.0
Using websocket-extensions 0.1.3
Using mini_mime 1.0.0
Using arel 8.0.0
Using bundler 1.15.2
Using coffee-script-source 1.12.2
Using execjs 2.7.0
Using method_source 0.9.0
Using thor 0.20.0
Using ffi 1.9.18
Using multi_json 1.12.2
Using pg 0.21.0
Using puma 3.11.0
Using rb-fsevent 0.10.2
Using tilt 2.0.8
Using turbolinks-source 5.0.3
Using i18n 0.9.1
Using tzinfo 1.2.4
Using nokogiri 1.8.1
Using websocket-driver 0.6.5
Using mail 2.7.0
Using coffee-script 2.4.1
Using uglifier 4.1.2
Using rb-inotify 0.9.10
Using turbolinks 5.0.1
Using activesupport 5.1.4
Using loofah 2.1.1
Using rack-test 0.8.2
Using sprockets 3.7.1
Using sass-listen 4.0.0
Using rails-html-sanitizer 1.0.3
Using sass 3.5.4
Using rails-dom-testing 2.0.3
Using globalid 0.4.1
Using activemodel 5.1.4
Using jbuilder 2.7.0
Using actionview 5.1.4
Using activejob 5.1.4
Using activerecord 5.1.4
Using actionpack 5.1.4
Using actioncable 5.1.4
Using actionmailer 5.1.4
Using railties 5.1.4
Using sprockets-rails 3.2.1
Using coffee-rails 4.2.2
Using jquery-rails 4.3.1
Using rails 5.1.4
Using sass-rails 5.0.7
Bundle complete! 18 Gemfile dependencies, 57 gems now installed.
Gems in the groups development and test were not installed.
Bundled gems are installed into ./vendor/bundle.
Bundle completed (2.73s)
Cleaning up the bundler cache.
Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.16.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
The latest bundler is 1.16.1, but you are currently running 1.15.2.
To update, run `gem install bundler`
-----> Installing node-v6.11.1-linux-x64
-----> Detecting rake tasks
-----> Preparing app for Rails asset pipeline
Running: rake assets:precompile
Yarn executable was not detected in the system.
Download Yarn at https://yarnpkg.com/en/docs/install
Asset precompilation completed (1.54s)
Cleaning assets
Running: rake assets:clean
###### WARNING:
You have not declared a Ruby version in your Gemfile.
To set your Ruby version add this line to your Gemfile:
ruby '2.3.4'
# See https://devcenter.heroku.com/articles/ruby-versions for more information.
###### WARNING:
No Procfile detected, using the default web server.
We recommend explicitly declaring how to boot your server process via a Procfile.
https://devcenter.heroku.com/articles/ruby-default-web-server
-----> Discovering process types
Procfile declares types -> (none)
Default types for buildpack -> console, rake, web, worker
-----> Compressing...
Done: 37.3M
-----> Launching...
Released v11
https://still-everglades-21863.herokuapp.com/ deployed to Heroku
SQLite stores data in a file. Heroku doesn't allow storing user's file so you can't use SQLite with Heroku. Instead you should to switch to another database like PostgreSQL or MySQL. Here you can find details.

Why doesn't "bundle exec" see that I have rake installed?

I've been reading StackOverflow and trying to deal with this error for 2 hours now:
bundle exec rake db:setup
Could not find rake-10.4.2 in any of the sources
Run `bundle install` to install missing gems.
I followed the advice here, to no avail:
rails s: Could not find rake-10.4.2 in any of the sources (Bundler::GemNotFound)
also:
Could not find rake with bundle exec
So I did:
gem uninstall rake
gem install rake
And, following the other StackOverflow articles I read, I tried:
rbenv install 2.3.1
Downloading ruby-2.3.1.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.3/ruby-2.3.1.tar.bz2
Installing ruby-2.3.1...
Installed ruby-2.3.1 to /Users/lkrubner/.rbenv/versions/2.3.1
rbenv global 2.3.1
ruby -v
ruby 2.0.0p645 (2015-04-13 revision 50299) [universal.x86_64-darwin15]
bundle exec rake db:setup
Could not find rake-10.4.2 in any of the sources
Run `bundle install` to install missing gems.
rbenv rehash
rbenv uninstall rake
rbenv: version `rake' not installed
At the command line, if I look for versions, I see:
rake -V
rake, version 11.2.2
rails -v
Rails 4.2.0
ruby -v
ruby 2.0.0p645 (2015-04-13 revision 50299) [universal.x86_64-darwin15]
but I still get this error:
bundle exec rake db:setup
Could not find rake-10.4.2 in any of the sources
Run `bundle install` to install missing gems.
What would fix this?
Update 1
This is even more confusing:
bundle update rake
Fetching gem metadata from https://rubygems.org/.............
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies...
Installing rake 11.2.2 (was 10.4.2)
Using i18n 0.7.0
Using json 1.8.3
Using minitest 5.8.3
Using thread_safe 0.3.5
Using tzinfo 1.2.2
Using activesupport 4.2.0
Using builder 3.2.2
Using erubis 2.7.0
Using mini_portile 0.6.2
Using nokogiri 1.6.6.4
Using rails-deprecated_sanitizer 1.0.3
Using rails-dom-testing 1.0.7
Using loofah 2.0.3
Using rails-html-sanitizer 1.0.2
Using actionview 4.2.0
Using rack 1.6.4
Using rack-test 0.6.3
Using actionpack 4.2.0
Using globalid 0.3.6
Using activejob 4.2.0
Using mime-types 2.99
Using mail 2.6.3
Using actionmailer 4.2.0
Using activemodel 4.2.0
Using arel 6.0.3
Using activerecord 4.2.0
Using addressable 2.3.8
Using multi_xml 0.5.5
Using httparty 0.13.7
Using uuidtools 2.1.5
Using aws-sdk 1.3.9
Using bcrypt 3.1.10
Using debug_inspector 0.0.2
Using binding_of_caller 0.7.2
Using bson 3.2.6
Using bson_ext 1.5.1
Using bundler 1.8.5
Using byebug 8.2.1
Using xpath 2.0.0
Using capybara 2.5.0
Using ffi 1.9.10
Using childprocess 0.5.8
Using climate_control 0.0.3
Using cocaine 0.5.8
Using coderay 1.1.0
Using coffee-script-source 1.10.0
Using execjs 2.6.0
Using coffee-script 2.4.1
Using thor 0.19.1
Using railties 4.2.0
Using coffee-rails 4.1.0
Using database_cleaner 1.5.1
Using orm_adapter 0.5.0
Using responders 2.1.0
Using warden 1.2.3
Using devise 3.5.2
Using diff-lcs 1.2.5
Using dotenv 2.1.0
Using dotenv-rails 2.1.0
Using factory_girl 4.5.0
Using factory_girl_rails 4.5.0
Using faker 1.4.3
Using multipart-post 2.0.0
Using faraday 0.9.2
Using sass 3.4.19
Using foundation-rails 5.5.3.2
Using geocoder 1.2.9
Using httpclient 2.6.0.1
Using icalendar 2.3.0
Using multi_json 1.11.2
Using jbuilder 2.3.2
Using jquery-rails 4.0.5
Using jwt 1.5.2
Using kgio 2.9.3
Using method_source 0.8.2
Using mimemagic 0.3.0
Using mongo 2.1.2
Using origin 2.1.1
Using mongoid 5.0.1
Using paperclip 4.3.2
Using mongoid-paperclip 0.0.10
Using oauth2 1.0.0
Using slop 3.6.0
Using pry 0.10.1
Using pry-rails 0.3.4
Using quiet_assets 1.1.0
Using sprockets 3.4.1
Using sprockets-rails 2.3.3
Using rails 4.2.0
Using rails_serve_static_assets 0.0.4
Using rails_stdout_logging 0.0.3
Using rails_12factor 0.0.3
Using raindrops 0.15.0
Using rdoc 4.2.0
Using rspec-support 3.3.0
Using rspec-core 3.3.1
Using rspec-expectations 3.3.0
Using rspec-mocks 3.3.1
Using rspec-rails 3.3.2
Using rspec_junit_formatter 0.2.2
Using rubyzip 1.1.7
Using tilt 2.0.1
Using sass-rails 5.0.4
Using sdoc 0.4.1
Using websocket 1.2.2
Using selenium-webdriver 2.48.1
Using shoulda-matchers 2.8.0
Using signet 0.7.2
Using simple_form 3.2.0
Using spring 1.4.4
Using timezone 0.5.0
Using turbolinks 2.5.3
Using uglifier 2.7.2
Using unicorn 4.9.0
Using web-console 2.2.1
Updating files in vendor/cache
* rake-11.2.2.gem
Removing outdated .gem files from vendor/cache
* rake-10.4.2.gem
Bundle updated!
bundle exec rake db:setup
Could not find rake-11.2.2 in any of the sources
Run `bundle install` to install missing gems.
bundle update rake
So one line says that rake is installed, and the next line says that it is not installed, and both lines are nominally being managed by Bundler, so in theory this can not be a cache problem.
Update 2
I added this to the Gem file:
gem 'rake', '10.5.0'
And then ran
bundle install
which gives me:
Updating files in vendor/cache
Bundle complete! 40 Gemfile dependencies, 116 gems now installed.
Bundled gems are installed into ./vendor/cache.
So then I try:
bundle exec rake db:setup
and I get:
Could not find rake-10.5.0 in any of the sources
Run `bundle install` to install missing gems.
You could try to run install command as sudo and specify rake's version like this:
sudo gem install rake -v '11.2.2'

not able to use gem even after bundle install

I am creating a dashing project, on a Linux machine.
When I do bundle install, it installs all the gems, but when I try to use the gem, it gives me an error and suggests to do bundle install again.
The commands and output follow:
saurabh#my-linux:~/beacon$ bundle install
Using addressable 2.3.8
Using execjs 2.0.2
Using json 1.8.3
Using autoprefixer-rails 6.0.3
Using backports 3.6.6
Using sass 3.2.19
Using bootstrap-sass 3.2.0.2
Using buftok 0.2.0
Using coffee-script-source 1.9.1.1
Using coffee-script 2.2.0
Using daemons 1.2.3
Using rack 1.5.5
Using thread_safe 0.3.5
Using tzinfo 1.2.2
Using rufus-scheduler 2.0.24
Using rack-protection 1.5.3
Using tilt 1.4.1
Using sinatra 1.4.6
Using multi_json 1.11.2
Using rack-test 0.6.3
Using sinatra-contrib 1.4.6
Using hike 1.2.3
Using sprockets 2.10.2
Using eventmachine 1.0.8
Using thin 1.6.4
Using thor 0.18.1
Using dashing 1.3.4
Using unf_ext 0.0.7.1
Using unf 0.1.4
Using domain_name 0.5.25
Using equalizer 0.0.10
Using multipart-post 2.0.0
Using faraday 0.9.2
Using http-cookie 1.0.2
Using http-form_data 1.0.1
Using http_parser.rb 0.6.0
Using http 0.9.8
Using memoizable 0.4.2
Using naught 1.1.0
Using netrc 0.7.9
Using rest_client 1.8.3
Using simple_oauth 0.3.1
Using twitter 5.15.0
Using bundler 1.10.6
Updating files in vendor/cache
Bundle complete! 5 Gemfile dependencies, 44 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.
saurabh#my-linux:~/beacon$ bundle show dashing
/usr/lib/lib/ruby/gems/2.1.0/gems/dashing-1.3.4
saurabh#my-linux:~/beacon$ /usr/lib/lib/ruby/gems/2.1.0/gems/dashing-1.3.4/bin/dashing start
/usr/lib/lib/ruby/gems/2.1.0/gems/dashing-1.3.4/lib/dashing/cli.rb:1:in `require': no such file to load -- thor (LoadError)
from /usr/lib/lib/ruby/gems/2.1.0/gems/dashing-1.3.4/lib/dashing/cli.rb:1
from /usr/lib/lib/ruby/gems/2.1.0/gems/dashing-1.3.4/bin/dashing:6:in `require'
from /usr/lib/lib/ruby/gems/2.1.0/gems/dashing-1.3.4/bin/dashing:6
saurabh#my-linux:~/beacon$ dashing start
Could not find addressable-2.3.8 in any of the sources
Run `bundle install` to install missing gems.
saurabh#my-linux:~/beacon$ /usr/lib/lib/ruby/gems/2.1.0/gems/dashing-1.3.4/bin/dashing start
Could not find addressable-2.3.8 in any of the sources
Run `bundle install` to install missing gems.
What am I doing wrong?
sound like 2 options:
you didn't restarted your server after bundle install, please do.
you used sudo to install the gems so they installed to all linux users as root so bottom line they really not in your source path, read more about it here:
Why do "gem" and "sudo gem" have different installation directories?

Resources