Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How to Bundler (ROSSConf 2015)

André Arko
September 26, 2015

How to Bundler (ROSSConf 2015)

ROSSConf brings developers together to learn about open source projects, and then work on them together with help from project team members. This talk explains how Bundler works and highlights some upcoming plans that could use help from contributors, and was given at ROSSConf 2015 in Berlin, Germany.

André Arko

September 26, 2015

More Decks by André Arko

Other Decks in Programming


  1. $LOAD_PATH = [] def require(filename) full_path = $LOAD_PATH.first do |path|

    File.exist?(File.join(path, filename)) end eval File.read(full_path) end
  2. use ruby libraries 1. Find a cool library 2. Download

    the library 3. Untar the library 4. Run `ruby setup.rb all`
  3. “why is this broken in production?” “dunno, it works on

    every developer machine” 3 days of debugging later… “oh, look, one production server has frobnitz 1.1.3, but the others have 1.1.4” “welp. that explains those exceptions ”
  4. $ rails s Gem::LoadError: can't activate rack (~> 1.0.0., runtime)

    for ["actionpack-2.3.5"], already activated rack-1.1.0 for ["thin-1.2.7"] activation errors
  5. addressable (2.3.7) arel (6.0.0) bcrypt (3.1.10) binding_of_caller (0.7.2) debug_inspector (>=

    0.0.1) builder (3.2.2) byebug (3.5.1) columnize (~> 0.8) debugger-linecache (~> 1.2) slop (~> 3.6) celluloid (0.16.0) Gemfile.lock
  6. bundle install my old friend 1. Read the Gemfile (and

    lock, if it's there) 2. Ask RubyGems.org for a list of every gem we need 2. Find gems allowed by the Gemfile that work together 3. Write down those versions in the lock for future installs 4. Install gems until every locked gem is installed
  7. bundle exec everyone’s nemesis 1. Read the Gemfile (and lock,

    if it's there) 2a. Use locked gems if possible OR 2b. Find versions that work to put in the lock 3. Remove any existing gems the $LOAD_PATH 4. Add each gem in the lock to the $LOAD_PATH
  8. pro tip no more bundle exec! $ bundle binstubs rspec-core

    $ bin/rspec repeat as needed for other gems
  9. we have many plans • gathering gemfiles for a bundler

    benchmark • triaging github issues • add failing tests for bugs • improving our code! (check PullReview or
 Code Climate for ideas) • create a FAQ for bundler.io • build more librato graphs using our data • track how many projects a gem is used in • update the command docs on bundler.io • local gem server