Tweetegy On the edge of chaos with Ruby, Rails, JavaScript and AngularJS.

| About | Search | Archive | Github | RSS |

Dissecting (Smallest Rails App: Newsflash)

Since starting this series, the inevitable has happened – The Smallest Rails app has been refactored! In this post I want to cover the recfactorings to the first line which affects the first blog post in this series .

To recap the first line was as follows:

1 %w(action_controller/railtie coderay markaby).map &method(:require)

Now this has been changed to the following (2) lines (Note: since writing this post the first line has been removed (see conclusion below):

1 require "bundler/setup"
2 Bundler.require

For clarity, here is the commit diff in Github for this change.

Compare with Initial Commit

My first thought was that maybe this application was not using Bundler (before), but I can confirm that the first commit of this project was and even had the line require 'bundler/setup' so its been used all the time. For your information the initial commit of this project has a commit SHA of “2215c1a” and if you want to see how this looked just simply clone the project and checkout that commit to detach your code from HEAD, as follows:

git clone
git checkout 2215c1a63700f21d54d0d16466f5527932ac8df6

As you can see the application looks quite different from what it does now, but it does appear to be using Bundler. Perhaps another interesting series of posts would be to track the progress of changes to this app discussing the reason for each one, but maybe another day, for now let simply focus on the two lines that changed here.

By the way, if you want to get back to the HEAD for the repo, just run git checkout master

Bundler Setup

The first line require 'bundler/setup' simply runs: this code which, in turn, runs the Bundler.setup method. What does this do? According to the Bundler Docs it …configures the load path so all dependencies in your Gemfile can be required…. Essentially it means that once Bundler.setup has run, its then possible to require any gems as declared in the Gemfile using require and be certain that the correct bundled version of that gem will be loaded.

So Bundler.setup simply ensures that the load path is correctly set so that require xyz gem will load the very gem as defined in the Gemfile.lock file.


The next line does exactly what it says, it requires all the gems! In fact, this is a little known command that will require all the gems in the Gemfile. The alternative is to require each gem one by one, in this case ‘rails, ‘coderay’ and ‘markaby’. However, since this is the Smallest Rails app, we use Bundler.require to require all gems in one swoop!

Its also possible to execute the require method passing in a symbol representing the group that you desire to load. For example Bundle.require(:development) will require all declared gems in the development group of your Gemfile. Its possible to pass in multiple groups separated by comma too.

Bundler.setup and ‘bundle exec’

Its worth mentioning here that running ‘bundle exec’ on the command line before starting the Smallest Rails App ensures that the load path is setup correctly (essentially the same as require "bundler/setup") and thus means that its possible to run the Smallest Rails App without the require "bundler/setup" line. I have commented on this line of code to the author of the Smallest Rails App and he has since removed this line from the application!


The Smallest Rails app will still probably be able to get smaller as gems and approaches change. In the meantime, for our purpose, it serves as an interesting digest of new techniques to learn about Rails and its associated gems (in this case Bundler!).