The Gemfile is where you specify which gems you want to use, and lets you specify which versions. The Gemfile.lock file is where Bundler records the exact versions that were installed. This way, when the same library/project is loaded on another machine, running bundle install will look at the Gemfile.lock and install the exact same … Read more
During your development in Rails, there will be times where you will want to provide some functionality which is required by you, but either you don’t know how to do or you don’t want to implement it on your own since a lot of work has been put into its development by talented developers. These … Read more
Update for 2022 from TrinitronX Fast-forward to 2021 and now Bundler docs [web archive] now say to commit the Gemfile.lock inside a gem… ¯_(ツ)_/¯ I guess it makes sense for developers and ease of use when starting on a project. However, now CI jobs need to be sure to remove any stray Gemfile.lock files to … Read more
Run gem install bundler or gem update bundler which may fix your problem. For all new installed versions of Ruby you should update or install a new bundler.
This means install the gem, but do not call require when you start Bundler. So you will need to manually call require “whenever” if you want to use the library. If you were to do gem “whenever”, require: “whereever” then bundler would download the gem named whenever, but would call require “whereever” This is often … Read more