├── Procfile ├── source ├── images │ ├── emocow.png │ ├── favicon.png │ ├── panda.jpg │ ├── gembundler.png │ ├── bundler-shirt.png │ ├── bundler-small.png │ ├── contributors │ │ ├── carl.jpg │ │ ├── smit.jpg │ │ ├── tim.jpg │ │ ├── andre.jpg │ │ ├── larry.jpg │ │ ├── yehuda.jpg │ │ ├── jessica.jpg │ │ ├── segiddins.jpg │ │ ├── terence.jpg │ │ └── andremedeiros.jpg │ └── sponsors │ │ ├── heroku.png │ │ ├── librato.png │ │ ├── rollbar.png │ │ ├── stripe.png │ │ ├── travis.png │ │ ├── appsignal.png │ │ ├── engineyard.png │ │ ├── globalsign.png │ │ ├── mavenlink.png │ │ ├── pagerduty.png │ │ ├── papertrail.png │ │ └── honeybadger.png ├── robots.txt ├── 404.haml ├── older_versions.haml ├── v1.1 │ ├── bundle_version.haml │ ├── bundle_open.haml │ ├── bundle_console.haml │ ├── bundle_cache.haml │ ├── bundle_clean.haml │ ├── bundle_gem.haml │ ├── bundle_exec.haml │ ├── bundle_show.haml │ ├── bundle_init.haml │ ├── bundle_package.haml │ ├── bundler_setup.haml │ ├── bundle_update.haml │ ├── bundle_config.haml │ ├── sinatra.haml │ ├── bundle_outdated.haml │ ├── bundle_check.haml │ ├── bundle_viz.haml │ ├── groups.haml │ ├── rubygems.haml │ └── rails3.haml ├── v1.2 │ ├── bundle_version.haml │ ├── bundle_open.haml │ ├── bundle_console.haml │ ├── bundle_clean.haml │ ├── bundle_gem.haml │ ├── bundle_exec.haml │ ├── bundle_show.haml │ ├── bundle_init.haml │ ├── bundler_setup.haml │ ├── sinatra.haml │ ├── bundle_outdated.haml │ ├── bundle_check.haml │ ├── bundle_viz.haml │ ├── rubymotion.haml │ ├── bundle_platform.haml │ ├── groups.haml │ ├── rubygems.haml │ ├── gemfile_ruby.haml │ ├── rails3.haml │ └── bundle_package.haml ├── v1.3 │ ├── bundle_version.haml │ ├── bundle_console.haml │ ├── bundle_help.haml │ ├── bundle_clean.haml │ ├── bundle_gem.haml │ ├── bundle_open.haml │ ├── bundle_exec.haml │ ├── bundle_show.haml │ ├── bundle_init.haml │ ├── sinatra.haml │ ├── bundle_outdated.haml │ ├── bundle_check.haml │ ├── bundle_viz.haml │ ├── rubymotion.haml │ ├── bundle_platform.haml │ ├── whats_new.haml │ ├── rubygems.haml │ ├── gemfile_ruby.haml │ └── rails3.haml ├── v1.5 │ ├── bundle_version.haml │ ├── bundle_console.haml │ ├── bundle_help.haml │ ├── bundle_clean.haml │ ├── bundle_gem.haml │ ├── bundle_open.haml │ ├── bundle_exec.haml │ ├── bundle_show.haml │ ├── bundle_init.haml │ ├── sinatra.haml │ ├── bundle_check.haml │ ├── bundle_viz.haml │ ├── bundle_outdated.haml │ ├── rubymotion.haml │ ├── bundle_platform.haml │ ├── rubygems.haml │ ├── rails3.haml │ └── gemfile_ruby.haml ├── v1.6 │ ├── bundle_version.haml │ ├── bundle_help.haml │ ├── bundle_open.haml │ ├── bundle_clean.haml │ ├── bundle_console.haml │ ├── bundle_inject.haml │ ├── bundle_show.haml │ ├── bundle_binstubs.haml │ ├── bundle_init.haml │ ├── bundle_exec.haml │ ├── sinatra.haml │ ├── bundle_gem.haml │ ├── bundle_viz.haml │ ├── bundle_outdated.haml │ ├── bundle_check.haml │ ├── rubymotion.haml │ ├── bundle_platform.haml │ ├── rubygems.haml │ ├── rails3.haml │ ├── whats_new.haml │ └── gemfile_ruby.haml ├── v1.7 │ ├── bundle_version.haml │ ├── bundle_help.haml │ ├── bundle_open.haml │ ├── bundle_clean.haml │ ├── bundle_console.haml │ ├── bundle_inject.haml │ ├── bundle_show.haml │ ├── bundle_binstubs.haml │ ├── bundle_init.haml │ ├── bundle_exec.haml │ ├── sinatra.haml │ ├── bundle_gem.haml │ ├── bundle_viz.haml │ ├── bundle_outdated.haml │ ├── bundle_check.haml │ ├── rubymotion.haml │ ├── bundle_platform.haml │ ├── rubygems.haml │ ├── rails3.haml │ └── gemfile_ruby.haml ├── v1.8 │ ├── bundle_version.haml │ ├── bundle_help.haml │ ├── bundle_open.haml │ ├── bundle_clean.haml │ ├── bundle_inject.haml │ ├── bundle_show.haml │ ├── bundle_binstubs.haml │ ├── bundle_console.haml │ ├── bundle_init.haml │ ├── sinatra.haml │ ├── bundle_gem.haml │ ├── bundle_outdated.haml │ ├── bundle_check.haml │ ├── rubymotion.haml │ ├── bundle_exec.haml │ ├── bundle_viz.haml │ ├── bundle_platform.haml │ ├── rubygems.haml │ ├── rails3.haml │ └── gemfile_ruby.haml ├── v1.9 │ ├── bundle_version.haml │ ├── bundle_help.haml │ ├── bundle_open.haml │ ├── bundle_clean.haml │ ├── bundle_inject.haml │ ├── bundle_show.haml │ ├── bundle_binstubs.haml │ ├── bundle_console.haml │ ├── bundle_init.haml │ ├── sinatra.haml │ ├── bundle_gem.haml │ ├── bundle_outdated.haml │ ├── bundle_check.haml │ ├── rubymotion.haml │ ├── bundle_exec.haml │ ├── bundle_viz.haml │ ├── bundle_platform.haml │ ├── whats_new.haml │ ├── rubygems.haml │ ├── rails3.haml │ └── gemfile_ruby.haml ├── blog │ ├── index.haml │ ├── calendar.haml │ ├── 2014-08-15-gem-not-found-error-on-1-7-0.html.markdown │ ├── feed.xml.builder │ ├── 2013-10-12-goodbye-bundler-14-hello-bundler-15.markdown │ ├── 2015-03-21-hello-bundler-19.md │ └── 2015-03-19-announcing-ruby-together.html.markdown ├── shared │ ├── _command.haml │ └── _whats_new.haml ├── sitemap.xml.builder ├── partials │ ├── _head.haml │ ├── _footer.haml │ └── _sidebar.haml ├── layouts │ ├── layout.haml │ └── blog_layout.haml ├── v0.9 │ ├── bundle_package.haml │ ├── bundle_lock.haml │ ├── bundler_setup.haml │ ├── sinatra.haml │ ├── deploying.haml │ ├── groups.haml │ ├── rubygems.haml │ ├── bundle_install.haml │ ├── git.haml │ └── gemfile.haml ├── v1.0 │ ├── bundle_package.haml │ ├── bundler_setup.haml │ ├── sinatra.haml │ ├── groups.haml │ ├── rubygems.haml │ ├── rails3.haml │ └── bundle_install.haml ├── compatibility.haml └── contributors.haml ├── Gemfile ├── bin └── middleman ├── helpers └── command_reference_helper.rb ├── .gitignore ├── README.md └── config.rb /Procfile: -------------------------------------------------------------------------------- 1 | web: bundle exec middleman server -p $PORT 2 | -------------------------------------------------------------------------------- /source/images/emocow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/emocow.png -------------------------------------------------------------------------------- /source/images/favicon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/favicon.png -------------------------------------------------------------------------------- /source/images/panda.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/panda.jpg -------------------------------------------------------------------------------- /source/robots.txt: -------------------------------------------------------------------------------- 1 | # www.robotstxt.org 2 | User-agent: * 3 | Allow: / 4 | Sitemap: http://bundler.io/sitemap.xml -------------------------------------------------------------------------------- /source/images/gembundler.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/gembundler.png -------------------------------------------------------------------------------- /source/images/bundler-shirt.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/bundler-shirt.png -------------------------------------------------------------------------------- /source/images/bundler-small.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/bundler-small.png -------------------------------------------------------------------------------- /source/images/contributors/carl.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/contributors/carl.jpg -------------------------------------------------------------------------------- /source/images/contributors/smit.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/contributors/smit.jpg -------------------------------------------------------------------------------- /source/images/contributors/tim.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/contributors/tim.jpg -------------------------------------------------------------------------------- /source/images/sponsors/heroku.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/sponsors/heroku.png -------------------------------------------------------------------------------- /source/images/sponsors/librato.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/sponsors/librato.png -------------------------------------------------------------------------------- /source/images/sponsors/rollbar.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/sponsors/rollbar.png -------------------------------------------------------------------------------- /source/images/sponsors/stripe.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/sponsors/stripe.png -------------------------------------------------------------------------------- /source/images/sponsors/travis.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/sponsors/travis.png -------------------------------------------------------------------------------- /source/images/contributors/andre.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/contributors/andre.jpg -------------------------------------------------------------------------------- /source/images/contributors/larry.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/contributors/larry.jpg -------------------------------------------------------------------------------- /source/images/contributors/yehuda.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/contributors/yehuda.jpg -------------------------------------------------------------------------------- /source/images/sponsors/appsignal.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/sponsors/appsignal.png -------------------------------------------------------------------------------- /source/images/sponsors/engineyard.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/sponsors/engineyard.png -------------------------------------------------------------------------------- /source/images/sponsors/globalsign.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/sponsors/globalsign.png -------------------------------------------------------------------------------- /source/images/sponsors/mavenlink.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/sponsors/mavenlink.png -------------------------------------------------------------------------------- /source/images/sponsors/pagerduty.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/sponsors/pagerduty.png -------------------------------------------------------------------------------- /source/images/sponsors/papertrail.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/sponsors/papertrail.png -------------------------------------------------------------------------------- /source/images/contributors/jessica.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/contributors/jessica.jpg -------------------------------------------------------------------------------- /source/images/contributors/segiddins.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/contributors/segiddins.jpg -------------------------------------------------------------------------------- /source/images/contributors/terence.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/contributors/terence.jpg -------------------------------------------------------------------------------- /source/images/sponsors/honeybadger.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/sponsors/honeybadger.png -------------------------------------------------------------------------------- /source/404.haml: -------------------------------------------------------------------------------- 1 | %h2 Page not found 2 | 3 | %p== Sorry, we couldn't find that page. Try heading #{link_to 'back to the home page', '/'}, I guess. 4 | -------------------------------------------------------------------------------- /source/images/contributors/andremedeiros.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mattbrictson/bundler-site/master/source/images/contributors/andremedeiros.jpg -------------------------------------------------------------------------------- /source/older_versions.haml: -------------------------------------------------------------------------------- 1 | %h2 Older Versions of Bundler 2 | .buttons 3 | - (versions - [current_version]).each do |version| 4 | = link_to(version, "/#{version}/index.html") 5 | 6 | -------------------------------------------------------------------------------- /source/v1.1/bundle_version.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Prints the bundler's version information 7 | :code 8 | $ bundle version 9 | -------------------------------------------------------------------------------- /source/v1.2/bundle_version.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Prints the bundler's version information 7 | :code 8 | $ bundle version 9 | -------------------------------------------------------------------------------- /source/v1.3/bundle_version.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Prints the bundler's version information 7 | :code 8 | $ bundle version 9 | -------------------------------------------------------------------------------- /source/v1.5/bundle_version.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Prints the bundler's version information 7 | :code 8 | $ bundle version 9 | -------------------------------------------------------------------------------- /source/v1.6/bundle_version.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Prints the bundler's version information 7 | :code 8 | $ bundle version 9 | -------------------------------------------------------------------------------- /source/v1.7/bundle_version.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Prints the bundler's version information 7 | :code 8 | $ bundle version 9 | -------------------------------------------------------------------------------- /source/v1.8/bundle_version.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Prints the bundler's version information 7 | :code 8 | $ bundle version 9 | -------------------------------------------------------------------------------- /source/v1.9/bundle_version.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Prints the bundler's version information 7 | :code 8 | $ bundle version 9 | -------------------------------------------------------------------------------- /source/v1.1/bundle_open.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle open 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens the source directory of the given bundled gem 7 | :code 8 | $ bundle open GEM 9 | -------------------------------------------------------------------------------- /source/v1.2/bundle_open.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle open 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens the source directory of the given bundled gem 7 | :code 8 | $ bundle open GEM 9 | -------------------------------------------------------------------------------- /source/v1.1/bundle_console.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle console 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens an IRB session with the bundle pre-loaded 7 | :code 8 | $ bundle console [GROUP] 9 | -------------------------------------------------------------------------------- /source/v1.2/bundle_console.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle console 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens an IRB session with the bundle pre-loaded 7 | :code 8 | $ bundle console [GROUP] 9 | -------------------------------------------------------------------------------- /source/v1.3/bundle_console.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle console 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens an IRB session with the bundle pre-loaded 7 | :code 8 | $ bundle console [GROUP] 9 | -------------------------------------------------------------------------------- /source/v1.5/bundle_console.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle console 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens an IRB session with the bundle pre-loaded 7 | :code 8 | $ bundle console [GROUP] 9 | -------------------------------------------------------------------------------- /source/blog/index.haml: -------------------------------------------------------------------------------- 1 | %h2 Bundler news and updates 2 | 3 | %ul.posts 4 | - blog.articles.each do |article| 5 | %li 6 | .date= article.date.to_date.strftime("%b %e, %Y") 7 | = link_to article.title, article.url 8 | -------------------------------------------------------------------------------- /source/v1.7/bundle_help.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle help 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Displays detailed help for each subcommand on your command line 7 | :code 8 | $ bundle help 9 | .notes 10 | #{ link_to 'View the same man pages here', './man/bundle.1.html'} 11 | -------------------------------------------------------------------------------- /source/v1.8/bundle_help.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle help 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Displays detailed help for each subcommand on your command line 7 | :code 8 | $ bundle help 9 | .notes 10 | #{ link_to 'View the same man pages here', './man/bundle.1.html'} 11 | -------------------------------------------------------------------------------- /source/v1.9/bundle_help.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle help 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Displays detailed help for each subcommand on your command line 7 | :code 8 | $ bundle help 9 | .notes 10 | #{ link_to 'View the same man pages here', './man/bundle.1.html'} 11 | -------------------------------------------------------------------------------- /source/shared/_command.haml: -------------------------------------------------------------------------------- 1 | %tr 2 | %td 3 | .cli_name 4 | = link_to "bundle #{name}", "./bundle_#{name}.html" 5 | .cli_desc 6 | = desc 7 | %td 8 | - opts.each do |opt| 9 | .cli_option 10 | = link_to "--#{opt}", "./bundle_#{name}.html##{slugize(opt)}" 11 | .clear 12 | -------------------------------------------------------------------------------- /source/v1.3/bundle_help.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle help 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Displays detailed help for each subcommand on your command line 7 | :code 8 | $ bundle help 9 | .notes 10 | #{ link_to 'View the same man pages here', '/v1.3/man/bundle.1.html'} 11 | -------------------------------------------------------------------------------- /source/v1.5/bundle_help.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle help 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Displays detailed help for each subcommand on your command line 7 | :code 8 | $ bundle help 9 | .notes 10 | #{ link_to 'View the same man pages here', '/v1.5/man/bundle.1.html'} 11 | -------------------------------------------------------------------------------- /source/v1.6/bundle_help.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle help 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Displays detailed help for each subcommand on your command line 7 | :code 8 | $ bundle help 9 | .notes 10 | #{ link_to 'View the same man pages here', '/v1.6/man/bundle.1.html'} 11 | -------------------------------------------------------------------------------- /source/v1.1/bundle_cache.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle cache 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Cache all the gems to vendor/cache 7 | :code 8 | $ bundle cache [--no-prune] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --no-prune: Don't remove stale gems from the cache. 14 | -------------------------------------------------------------------------------- /source/v1.1/bundle_clean.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle clean 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Cleans up unused gems in your bundler directory 7 | :code 8 | $ bundle clean [--force] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --force: forces clean even if --path is set 14 | -------------------------------------------------------------------------------- /source/v1.1/bundle_gem.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle gem 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Creates a skeleton for creating a rubygem 7 | :code 8 | $ bundle gem GEM [--bin or -b] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --bin or -b: Generate a binary for your library. 14 | -------------------------------------------------------------------------------- /source/v1.2/bundle_clean.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle clean 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Cleans up unused gems in your bundler directory 7 | :code 8 | $ bundle clean [--force] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --force: forces clean even if --path is set 14 | -------------------------------------------------------------------------------- /source/v1.2/bundle_gem.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle gem 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Creates a skeleton for creating a rubygem 7 | :code 8 | $ bundle gem GEM [--bin or -b] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --bin or -b: Generate a binary for your library. 14 | -------------------------------------------------------------------------------- /source/v1.3/bundle_clean.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle clean 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Cleans up unused gems in your bundler directory 7 | :code 8 | $ bundle clean [--force] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --force: forces clean even if --path is set 14 | -------------------------------------------------------------------------------- /source/v1.3/bundle_gem.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle gem 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Creates a skeleton for creating a rubygem 7 | :code 8 | $ bundle gem GEM [--bin or -b] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --bin or -b: Generate a binary for your library. 14 | -------------------------------------------------------------------------------- /source/v1.5/bundle_clean.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle clean 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Cleans up unused gems in your bundler directory 7 | :code 8 | $ bundle clean [--force] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --force: forces clean even if --path is set 14 | -------------------------------------------------------------------------------- /source/v1.5/bundle_gem.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle gem 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Creates a skeleton for creating a rubygem 7 | :code 8 | $ bundle gem GEM [--bin or -b] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --bin or -b: Generate a binary for your library. 14 | -------------------------------------------------------------------------------- /Gemfile: -------------------------------------------------------------------------------- 1 | # If you have OpenSSL installed, we recommend updating 2 | # the following line to use "https" 3 | source 'https://rubygems.org' 4 | 5 | gem 'middleman', '~> 3.2' 6 | gem 'middleman-livereload' 7 | gem 'middleman-syntax', github: 'middleman/middleman-syntax' 8 | gem 'middleman-blog' 9 | gem 'compass' 10 | gem 'rake' 11 | gem 'ronn' 12 | gem 'kramdown' 13 | gem 'builder' 14 | -------------------------------------------------------------------------------- /source/v1.3/bundle_open.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle open 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens the source directory of the given bundled gem 7 | :code 8 | $ bundle open GEM 9 | .description 10 | %p 11 | Opens the source directory of the provided GEM in your editor. For this to 12 | work the `EDITOR` or `BUNDLER_EDITOR` environment variable has to be set. 13 | -------------------------------------------------------------------------------- /source/v1.5/bundle_open.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle open 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens the source directory of the given bundled gem 7 | :code 8 | $ bundle open GEM 9 | .description 10 | %p 11 | Opens the source directory of the provided GEM in your editor. For this to 12 | work the `EDITOR` or `BUNDLER_EDITOR` environment variable has to be set. 13 | -------------------------------------------------------------------------------- /source/v1.6/bundle_open.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle open 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens the source directory of the given bundled gem 7 | :code 8 | $ bundle open GEM 9 | .description 10 | %p 11 | Opens the source directory of the provided GEM in your editor. For this to 12 | work the `EDITOR` or `BUNDLER_EDITOR` environment variable has to be set. 13 | -------------------------------------------------------------------------------- /source/v1.7/bundle_open.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle open 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens the source directory of the given bundled gem 7 | :code 8 | $ bundle open GEM 9 | .description 10 | %p 11 | Opens the source directory of the provided GEM in your editor. For this to 12 | work the `EDITOR` or `BUNDLER_EDITOR` environment variable has to be set. 13 | -------------------------------------------------------------------------------- /source/v1.8/bundle_open.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle open 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens the source directory of the given bundled gem 7 | :code 8 | $ bundle open GEM 9 | .description 10 | %p 11 | Opens the source directory of the provided GEM in your editor. For this to 12 | work the `EDITOR` or `BUNDLER_EDITOR` environment variable has to be set. 13 | -------------------------------------------------------------------------------- /source/v1.9/bundle_open.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle open 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens the source directory of the given bundled gem 7 | :code 8 | $ bundle open GEM 9 | .description 10 | %p 11 | Opens the source directory of the provided GEM in your editor. For this to 12 | work the `EDITOR` or `BUNDLER_EDITOR` environment variable has to be set. 13 | -------------------------------------------------------------------------------- /source/v1.1/bundle_exec.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle exec 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Run the command in context of the bundle 7 | :code 8 | $ bundle exec 9 | .description 10 | Exec runs a command, providing it access to the gems in the bundle. While 11 | using bundle exec you can require and call the bundled gems as if they 12 | were installed into the systemwide RubyGems repository. 13 | -------------------------------------------------------------------------------- /source/v1.2/bundle_exec.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle exec 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Run the command in context of the bundle 7 | :code 8 | $ bundle exec 9 | .description 10 | Exec runs a command, providing it access to the gems in the bundle. While using 11 | bundle exec you can require and call the bundled gems as if they were installed 12 | into the systemwide RubyGems repository. 13 | -------------------------------------------------------------------------------- /source/v1.3/bundle_exec.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle exec 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Run the command in context of the bundle 7 | :code 8 | $ bundle exec 9 | .description 10 | Exec runs a command, providing it access to the gems in the bundle. While using 11 | bundle exec you can require and call the bundled gems as if they were installed 12 | into the systemwide RubyGems repository. 13 | -------------------------------------------------------------------------------- /source/v1.5/bundle_exec.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle exec 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Run the command in context of the bundle 7 | :code 8 | $ bundle exec 9 | .description 10 | Exec runs a command, providing it access to the gems in the bundle. While using 11 | bundle exec you can require and call the bundled gems as if they were installed 12 | into the systemwide RubyGems repository. 13 | -------------------------------------------------------------------------------- /bin/middleman: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env ruby 2 | # 3 | # This file was generated by Bundler. 4 | # 5 | # The application 'middleman' is installed as part of a gem, and 6 | # this file is here to facilitate running it. 7 | # 8 | 9 | require 'pathname' 10 | ENV['BUNDLE_GEMFILE'] ||= File.expand_path("../../Gemfile", 11 | Pathname.new(__FILE__).realpath) 12 | 13 | require 'rubygems' 14 | require 'bundler/setup' 15 | 16 | load Gem.bin_path('middleman-core', 'middleman') 17 | -------------------------------------------------------------------------------- /source/blog/calendar.haml: -------------------------------------------------------------------------------- 1 | %h2 2 | Bundler news and updates from 3 | - case page_type 4 | - when 'day' 5 | = Date.new(year, month, day).strftime('%b %e, %Y') 6 | - when 'month' 7 | = Date.new(year, month, 1).strftime('%b, %Y') 8 | - when 'year' 9 | = year 10 | 11 | %ul.posts 12 | - page_articles.each do |article| 13 | %li 14 | .date= article.date.to_date.strftime("%b %e, %Y") 15 | = link_to article.title, article.url 16 | -------------------------------------------------------------------------------- /source/v1.6/bundle_clean.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle clean 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Cleans up unused gems in your bundler directory 7 | :code 8 | $ bundle clean [--dry-run] [--force] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --dry-run: Only print out changes, do not actually clean 14 | gems 15 | %p 16 | --force: Forces clean even if --path is set 17 | -------------------------------------------------------------------------------- /source/v1.7/bundle_clean.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle clean 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Cleans up unused gems in your bundler directory 7 | :code 8 | $ bundle clean [--dry-run] [--force] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --dry-run: Only print out changes, do not actually clean 14 | gems 15 | %p 16 | --force: Forces clean even if --path is set 17 | -------------------------------------------------------------------------------- /source/v1.8/bundle_clean.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle clean 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Cleans up unused gems in your bundler directory 7 | :code 8 | $ bundle clean [--dry-run] [--force] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --dry-run: Only print out changes, do not actually clean 14 | gems 15 | %p 16 | --force: Forces clean even if --path is set 17 | -------------------------------------------------------------------------------- /source/v1.9/bundle_clean.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle clean 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Cleans up unused gems in your bundler directory 7 | :code 8 | $ bundle clean [--dry-run] [--force] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --dry-run: Only print out changes, do not actually clean 14 | gems 15 | %p 16 | --force: Forces clean even if --path is set 17 | -------------------------------------------------------------------------------- /source/sitemap.xml.builder: -------------------------------------------------------------------------------- 1 | xml.instruct! 2 | xml.urlset 'xmlns' => 'http://www.sitemaps.org/schemas/sitemap/0.9' do 3 | xml.url do 4 | xml.loc 'http://bundler.io' 5 | xml.lastmod Time.now.utc.iso8601 6 | xml.changefreq 'weekly' 7 | xml.priority 1.0 8 | end 9 | sitemap.resources.select{ |resource| resource.ext.eql? '.html' }.each do |resource| 10 | xml.url do 11 | xml.loc URI.join('http://bundler.io', resource.url) 12 | end 13 | end 14 | end -------------------------------------------------------------------------------- /source/partials/_head.haml: -------------------------------------------------------------------------------- 1 | %title 2 | = "Bundler: #{current_page.data.title || "The best way to manage a Ruby application's gems"}" 3 | %meta{'http-equiv' => 'Content-Type', 'content' => 'text/html; charset=UTF-8'} 4 | %meta{'name' => 'globalsign-domain-verification', 'content' => '276VSYOko8B8vIu1i8i5qbj7_ql5PXo0dU69XQy-SL'} 5 | = favicon_tag 'images/favicon.png' 6 | = stylesheet_link_tag 'application' 7 | = feed_tag :atom, "#{blog.options.prefix.to_s}/feed.xml", title: "Atom Feed" 8 | -------------------------------------------------------------------------------- /source/v1.6/bundle_console.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle console 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens an IRB session with the bundle pre-loaded 7 | :code 8 | $ bundle console [GROUP] 9 | 10 | .description 11 | Alternatives like Pry and Ripl can be used with bundle console by adjusting the console Bundler setting. Also make sure that pry or ripl is in your Gemfile. 12 | :code 13 | $ bundle config console pry 14 | $ bundle console 15 | [1] pry(main)> 16 | -------------------------------------------------------------------------------- /source/v1.7/bundle_console.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle console 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Opens an IRB session with the bundle pre-loaded 7 | :code 8 | $ bundle console [GROUP] 9 | 10 | .description 11 | Alternatives like Pry and Ripl can be used with bundle console by adjusting the console Bundler setting. Also make sure that pry or ripl is in your Gemfile. 12 | :code 13 | $ bundle config console pry 14 | $ bundle console 15 | [1] pry(main)> 16 | -------------------------------------------------------------------------------- /source/layouts/layout.haml: -------------------------------------------------------------------------------- 1 | !!! 2 | - v = current_page.url.scan(/v\d\.\d/).first || current_version 3 | %html 4 | %head 5 | = partial 'partials/head' 6 | %body 7 | #body 8 | #header 9 | - logo_img = image_tag('gembundler.png', :width => 725, :alt => "The best way to manage your application's dependencies") 10 | = link_to logo_img, '/', :class => 'image' 11 | #container 12 | #contents 13 | = yield 14 | = partial 'partials/sidebar' if v == current_version 15 | = partial 'partials/footer', locals: { v: v } 16 | -------------------------------------------------------------------------------- /source/v1.6/bundle_inject.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle inject 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Add the named gem(s), with version requirements, to the resolved Gemfile 7 | :code 8 | $ bundle inject [GEM] [VERSION] 9 | 10 | .bullet 11 | .description 12 | When injecting a gem, it adds it to both your Gemfile and Gemfile.lock if 13 | it doesn't yet exist in them. Example below: 14 | :code 15 | $ bundle install 16 | 17 | $ bundle inject 'rack' '> 0' 18 | # Injects rack gem greater than version 0 in your Gemfile and Gemfile.lock 19 | -------------------------------------------------------------------------------- /source/v1.7/bundle_inject.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle inject 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Add the named gem(s), with version requirements, to the resolved Gemfile 7 | :code 8 | $ bundle inject [GEM] [VERSION] 9 | 10 | .bullet 11 | .description 12 | When injecting a gem, it adds it to both your Gemfile and Gemfile.lock if 13 | it doesn't yet exist in them. Example below: 14 | :code 15 | $ bundle install 16 | 17 | $ bundle inject 'rack' '> 0' 18 | # Injects rack gem greater than version 0 in your Gemfile and Gemfile.lock 19 | -------------------------------------------------------------------------------- /source/v1.8/bundle_inject.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle inject 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Add the named gem(s), with version requirements, to the resolved Gemfile 7 | :code 8 | $ bundle inject [GEM] [VERSION] 9 | 10 | .bullet 11 | .description 12 | When injecting a gem, it adds it to both your Gemfile and Gemfile.lock if 13 | it doesn't yet exist in them. Example below: 14 | :code 15 | $ bundle install 16 | 17 | $ bundle inject 'rack' '> 0' 18 | # Injects rack gem greater than version 0 in your Gemfile and Gemfile.lock 19 | -------------------------------------------------------------------------------- /source/v1.9/bundle_inject.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle inject 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Add the named gem(s), with version requirements, to the resolved Gemfile 7 | :code 8 | $ bundle inject [GEM] [VERSION] 9 | 10 | .bullet 11 | .description 12 | When injecting a gem, it adds it to both your Gemfile and Gemfile.lock if 13 | it doesn't yet exist in them. Example below: 14 | :code 15 | $ bundle install 16 | 17 | $ bundle inject 'rack' '> 0' 18 | # Injects rack gem greater than version 0 in your Gemfile and Gemfile.lock 19 | -------------------------------------------------------------------------------- /source/v1.1/bundle_show.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle show 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Shows all gems that are part of the bundle, or the path to a given gem 7 | :code 8 | $ bundle show [GEM] [--paths] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --paths: List the paths of all gems that are required by your Gemfile. 14 | .description 15 | Show lists the names and versions of all gems that are required by your Gemfile. 16 | Calling show with [GEM] will list the exact location of that gem on your machine. 17 | -------------------------------------------------------------------------------- /source/v1.2/bundle_show.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle show 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Shows all gems that are part of the bundle, or the path to a given gem 7 | :code 8 | $ bundle show [GEM] [--paths] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --paths: List the paths of all gems that are required by your Gemfile. 14 | .description 15 | Show lists the names and versions of all gems that are required by your Gemfile. 16 | Calling show with [GEM] will list the exact location of that gem on your machine. 17 | -------------------------------------------------------------------------------- /source/v1.3/bundle_show.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle show 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Shows all gems that are part of the bundle, or the path to a given gem 7 | :code 8 | $ bundle show [GEM] [--paths] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --paths: List the paths of all gems that are required by your Gemfile. 14 | .description 15 | Show lists the names and versions of all gems that are required by your Gemfile. 16 | Calling show with [GEM] will list the exact location of that gem on your machine. 17 | -------------------------------------------------------------------------------- /source/v1.5/bundle_show.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle show 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Shows all gems that are part of the bundle, or the path to a given gem 7 | :code 8 | $ bundle show [GEM] [--paths] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --paths: List the paths of all gems that are required by your Gemfile. 14 | .description 15 | Show lists the names and versions of all gems that are required by your Gemfile. 16 | Calling show with [GEM] will list the exact location of that gem on your machine. 17 | -------------------------------------------------------------------------------- /source/v1.6/bundle_show.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle show 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Shows all gems that are part of the bundle, or the path to a given gem 7 | :code 8 | $ bundle show [GEM] [--paths] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --paths: List the paths of all gems that are required by your Gemfile. 14 | .description 15 | Show lists the names and versions of all gems that are required by your Gemfile. 16 | Calling show with [GEM] will list the exact location of that gem on your machine. 17 | -------------------------------------------------------------------------------- /source/v1.7/bundle_show.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle show 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Shows all gems that are part of the bundle, or the path to a given gem 7 | :code 8 | $ bundle show [GEM] [--paths] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --paths: List the paths of all gems that are required by your Gemfile. 14 | .description 15 | Show lists the names and versions of all gems that are required by your Gemfile. 16 | Calling show with [GEM] will list the exact location of that gem on your machine. 17 | -------------------------------------------------------------------------------- /source/v1.8/bundle_show.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle show 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Shows all gems that are part of the bundle, or the path to a given gem 7 | :code 8 | $ bundle show [GEM] [--paths] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --paths: List the paths of all gems that are required by your Gemfile. 14 | .description 15 | Show lists the names and versions of all gems that are required by your Gemfile. 16 | Calling show with [GEM] will list the exact location of that gem on your machine. 17 | -------------------------------------------------------------------------------- /source/v1.9/bundle_show.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle show 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Shows all gems that are part of the bundle, or the path to a given gem 7 | :code 8 | $ bundle show [GEM] [--paths] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --paths: List the paths of all gems that are required by your Gemfile. 14 | .description 15 | Show lists the names and versions of all gems that are required by your Gemfile. 16 | Calling show with [GEM] will list the exact location of that gem on your machine. 17 | -------------------------------------------------------------------------------- /source/v0.9/bundle_package.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle install 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Package up all your .gem files in vendor/cache 7 | :code 8 | $ bundle package 9 | 10 | .bullet 11 | .description 12 | Running bundle install in an application with packaged gems will use the gems in the package and skip connecting to rubygems.org 13 | .how 14 | :code 15 | $ bundle install 16 | .notes 17 | You can use this to avoid a dependency on rubygems.org at deploy time, or if you have private gems that are not in a public repository 18 | -------------------------------------------------------------------------------- /helpers/command_reference_helper.rb: -------------------------------------------------------------------------------- 1 | class CommandInfo 2 | attr_accessor :name, :desc 3 | def option=(opt) 4 | opts << opt 5 | end 6 | def opts 7 | @opts ||= [] 8 | end 9 | end 10 | 11 | module CommandReferenceHelper 12 | def command_table_row 13 | command = CommandInfo.new 14 | yield command 15 | partial( 16 | 'shared/command', 17 | :locals => { 18 | :name => command.name, 19 | :desc => command.desc, 20 | :opts => command.opts 21 | } 22 | ) 23 | end 24 | 25 | def slugize(str) 26 | str.sub(/^([^\s]*).*/, "\\1") 27 | end 28 | end 29 | -------------------------------------------------------------------------------- /source/v1.6/bundle_binstubs.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle binstubs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Installs the binstubs of the listed gem 7 | :code 8 | $ bundle binstubs [GEM] [--force] [--path=PATH] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --force: Overwrite existing binstubs if they exist. 14 | %p 15 | --path: Binstub destination directory (default bin) 16 | .description 17 | Generate binstubs for executables in [GEM]. Binstubs are put into bin, 18 | or the --binstubs directory if one has been set. 19 | -------------------------------------------------------------------------------- /source/v1.7/bundle_binstubs.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle binstubs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Installs the binstubs of the listed gem 7 | :code 8 | $ bundle binstubs [GEM] [--force] [--path=PATH] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --force: Overwrite existing binstubs if they exist. 14 | %p 15 | --path: Binstub destination directory (default bin) 16 | .description 17 | Generate binstubs for executables in [GEM]. Binstubs are put into bin, 18 | or the --binstubs directory if one has been set. 19 | -------------------------------------------------------------------------------- /source/v1.8/bundle_binstubs.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle binstubs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Installs the binstubs of the listed gem 7 | :code 8 | $ bundle binstubs [GEM] [--force] [--path=PATH] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --force: Overwrite existing binstubs if they exist. 14 | %p 15 | --path: Binstub destination directory (default bin) 16 | .description 17 | Generate binstubs for executables in [GEM]. Binstubs are put into bin, 18 | or the --binstubs directory if one has been set. 19 | -------------------------------------------------------------------------------- /source/v1.9/bundle_binstubs.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle binstubs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Installs the binstubs of the listed gem 7 | :code 8 | $ bundle binstubs [GEM] [--force] [--path=PATH] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --force: Overwrite existing binstubs if they exist. 14 | %p 15 | --path: Binstub destination directory (default bin) 16 | .description 17 | Generate binstubs for executables in [GEM]. Binstubs are put into bin, 18 | or the --binstubs directory if one has been set. 19 | -------------------------------------------------------------------------------- /source/v1.8/bundle_console.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle console 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Start an interactive Ruby console session in the context of the current bundle 7 | :code 8 | $ bundle console [GROUP] 9 | 10 | .description 11 | bundle console uses irb by default. Alternatives like Pry and Ripl can be used with bundle console by adjusting the console Bundler setting. Also make sure that pry or ripl is in your Gemfile. 12 | :code 13 | $ bundle config console pry 14 | $ bundle console 15 | [1] pry(main)> 16 | -------------------------------------------------------------------------------- /source/v1.9/bundle_console.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle console 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Start an interactive Ruby console session in the context of the current bundle 7 | :code 8 | $ bundle console [GROUP] 9 | 10 | .description 11 | bundle console uses irb by default. Alternatives like Pry and Ripl can be used with bundle console by adjusting the console Bundler setting. Also make sure that pry or ripl is in your Gemfile. 12 | :code 13 | $ bundle config console pry 14 | $ bundle console 15 | [1] pry(main)> 16 | -------------------------------------------------------------------------------- /source/v1.2/bundle_init.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle init 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a Gemfile into the current working directory 7 | :code 8 | $ bundle init [--gemspec=FILE] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --gemspec: Use the specified .gemspec to create the Gemfile 14 | .description 15 | Init generates a default Gemfile in the current working directory. When adding a 16 | Gemfile to a gem with a gemspec, the --gemspec option will automatically add each 17 | dependency listed in the gemspec file to the newly created Gemfile. 18 | -------------------------------------------------------------------------------- /source/v1.3/bundle_init.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle init 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a Gemfile into the current working directory 7 | :code 8 | $ bundle init [--gemspec=FILE] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --gemspec: Use the specified .gemspec to create the Gemfile 14 | .description 15 | Init generates a default Gemfile in the current working directory. When adding a 16 | Gemfile to a gem with a gemspec, the --gemspec option will automatically add each 17 | dependency listed in the gemspec file to the newly created Gemfile. 18 | -------------------------------------------------------------------------------- /source/v1.5/bundle_init.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle init 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a Gemfile into the current working directory 7 | :code 8 | $ bundle init [--gemspec=FILE] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --gemspec: Use the specified .gemspec to create the Gemfile 14 | .description 15 | Init generates a default Gemfile in the current working directory. When adding a 16 | Gemfile to a gem with a gemspec, the --gemspec option will automatically add each 17 | dependency listed in the gemspec file to the newly created Gemfile. 18 | -------------------------------------------------------------------------------- /source/v1.6/bundle_init.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle init 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a Gemfile into the current working directory 7 | :code 8 | $ bundle init [--gemspec=FILE] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --gemspec: Use the specified .gemspec to create the Gemfile 14 | .description 15 | Init generates a default Gemfile in the current working directory. When adding a 16 | Gemfile to a gem with a gemspec, the --gemspec option will automatically add each 17 | dependency listed in the gemspec file to the newly created Gemfile. 18 | -------------------------------------------------------------------------------- /source/v1.7/bundle_init.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle init 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a Gemfile into the current working directory 7 | :code 8 | $ bundle init [--gemspec=FILE] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --gemspec: Use the specified .gemspec to create the Gemfile 14 | .description 15 | Init generates a default Gemfile in the current working directory. When adding a 16 | Gemfile to a gem with a gemspec, the --gemspec option will automatically add each 17 | dependency listed in the gemspec file to the newly created Gemfile. 18 | -------------------------------------------------------------------------------- /source/v1.8/bundle_init.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle init 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a Gemfile into the current working directory 7 | :code 8 | $ bundle init [--gemspec=FILE] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --gemspec: Use the specified .gemspec to create the Gemfile 14 | .description 15 | Init generates a default Gemfile in the current working directory. When adding a 16 | Gemfile to a gem with a gemspec, the --gemspec option will automatically add each 17 | dependency listed in the gemspec file to the newly created Gemfile. 18 | -------------------------------------------------------------------------------- /source/v1.9/bundle_init.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle init 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a Gemfile into the current working directory 7 | :code 8 | $ bundle init [--gemspec=FILE] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --gemspec: Use the specified .gemspec to create the Gemfile 14 | .description 15 | Init generates a default Gemfile in the current working directory. When adding a 16 | Gemfile to a gem with a gemspec, the --gemspec option will automatically add each 17 | dependency listed in the gemspec file to the newly created Gemfile. 18 | -------------------------------------------------------------------------------- /source/v1.1/bundle_init.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle init 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a Gemfile into the current working directory 7 | :code 8 | $ bundle init [--gemspec=FILE] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --gemspec: Use the specified .gemspec to create the Gemfile 14 | .description 15 | Init generates a default Gemfile in the current working directory. When 16 | adding a Gemfile to a gem with a gemspec, the --gemspec option will 17 | automatically add each dependency listed in the gemspec file to the newly 18 | created Gemfile. 19 | -------------------------------------------------------------------------------- /source/v0.9/bundle_lock.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle lock 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Calculate the entire dependency tree and store the results in Gemfile.lock. Check Gemfile.lock into version control 7 | :code 8 | $ bundle lock 9 | $ git add Gemfile.lock 10 | 11 | .bullet 12 | .description 13 | After you have locked your gems, you've updated your Gemfile and want to update Gemfile.lock 14 | :code 15 | $ bundle lock 16 | 17 | .bullet 18 | .description 19 | After you have locked your gems, you've updated your Gemfile and want to install the new gems 20 | :code 21 | $ bundle install --relock 22 | -------------------------------------------------------------------------------- /source/v1.0/bundle_package.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle package 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Package up all your .gem files in vendor/cache 7 | :code 8 | $ bundle package 9 | 10 | .bullet 11 | .description 12 | Running bundle install in an application with 13 | packaged gems will use the gems in the package 14 | and skip connecting to rubygems.org 15 | .how 16 | :code 17 | $ bundle install --local 18 | .notes 19 | You can use this to avoid a dependency on 20 | rubygems.org at deploy time, or if you 21 | have private gems that are not in a public 22 | repository 23 | -------------------------------------------------------------------------------- /source/v1.6/bundle_exec.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle exec 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Run the command in context of the bundle 7 | :code 8 | $ bundle exec [--keep-file-descriptors] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --keep-file-descriptors: For Ruby versions less than 2.0, 14 | keeps non-standard file descriptors on Kernel#exec 15 | 16 | .description 17 | Exec runs a command, providing it access to the gems in the bundle. While using 18 | bundle exec you can require and call the bundled gems as if they were installed 19 | into the systemwide RubyGems repository. 20 | -------------------------------------------------------------------------------- /source/v1.7/bundle_exec.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle exec 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Run the command in context of the bundle 7 | :code 8 | $ bundle exec [--keep-file-descriptors] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --keep-file-descriptors: For Ruby versions less than 2.0, 14 | keeps non-standard file descriptors on Kernel#exec 15 | 16 | .description 17 | Exec runs a command, providing it access to the gems in the bundle. While using 18 | bundle exec you can require and call the bundled gems as if they were installed 19 | into the systemwide RubyGems repository. 20 | -------------------------------------------------------------------------------- /source/shared/_whats_new.haml: -------------------------------------------------------------------------------- 1 | %h1 What's New in each Release 2 | .buttons 3 | = link_to 'Latest Version v1.9', '/v1.9/whats_new.html#version19' 4 | = link_to 'v1.8', '/v1.8/whats_new.html#version18' 5 | = link_to 'v1.7', '/v1.7/whats_new.html#version17' 6 | = link_to 'v1.6', '/v1.6/whats_new.html#version16' 7 | = link_to 'v1.5', '/v1.5/whats_new.html#version15' 8 | = link_to 'v1.3', '/v1.3/whats_new.html#version13' 9 | = link_to 'v1.2', '/v1.2/whats_new.html#version12' 10 | = link_to 'v1.1', 'https://github.com/bundler/bundler/blob/master/CHANGELOG.md#110-mar-7-2012' 11 | = link_to 'v1.0', 'https://github.com/bundler/bundler/blob/master/CHANGELOG.md#100-august-29-2010' 12 | -------------------------------------------------------------------------------- /source/v1.1/bundle_package.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle package 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Locks and then caches all of the gems into vendor/cache 7 | :code 8 | $ bundle package [--no-prune] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --no-prune: Don't remove stale gems from the cache. 14 | .description 15 | The package command will copy the .gem files for every gem in the bundle into the 16 | directory ./vendor/cache. If you then check that directory into your source 17 | control repository, others who check out your source will be able to install the 18 | bundle without having to download any additional gems. 19 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # See http://help.github.com/ignore-files/ for more about ignoring files. 2 | # 3 | # If you find yourself ignoring temporary files generated by your text editor 4 | # or operating system, you probably want to add a global ignore instead: 5 | # git config --global core.excludesfile ~/.gitignore_global 6 | 7 | # Ignore bundler config 8 | /.bundle 9 | 10 | # Ignore the build directory 11 | /build 12 | 13 | # Ignore Sass' cache 14 | /.sass-cache 15 | 16 | .DS_store 17 | 18 | # (optional) local gems, installed with 19 | # bundle install --path vendor/bundle 20 | # also a checkout of bundler for manpages and releases 21 | /vendor 22 | 23 | # Bundler binstubs 24 | /bin 25 | 26 | source/issues.md 27 | source/conduct.md -------------------------------------------------------------------------------- /source/v1.1/bundler_setup.haml: -------------------------------------------------------------------------------- 1 | %h2 Bundler.setup 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Configure the load path so all dependencies in your Gemfile can be required 7 | :code 8 | # lang: ruby 9 | require 'rubygems' 10 | require 'bundler/setup' 11 | require 'nokogiri' 12 | 13 | .bullet 14 | .description 15 | Only add gems from specified groups to the load path. If you want the gems 16 | in the default group, make sure to include it 17 | :code 18 | # lang: ruby 19 | require 'rubygems' 20 | require 'bundler' 21 | Bundler.setup(:default, :ci) 22 | require 'nokogiri' 23 | = link_to 'Learn More: Groups', './groups.html' 24 | -------------------------------------------------------------------------------- /source/v1.2/bundler_setup.haml: -------------------------------------------------------------------------------- 1 | %h2 Bundler.setup 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Configure the load path so all dependencies in your Gemfile can be required 7 | :code 8 | # lang: ruby 9 | require 'rubygems' 10 | require 'bundler/setup' 11 | require 'nokogiri' 12 | 13 | .bullet 14 | .description 15 | Only add gems from specified groups to the load path. If you want the gems 16 | in the default group, make sure to include it 17 | :code 18 | # lang: ruby 19 | require 'rubygems' 20 | require 'bundler' 21 | Bundler.setup(:default, :ci) 22 | require 'nokogiri' 23 | = link_to 'Learn More: Groups', './groups.html' 24 | -------------------------------------------------------------------------------- /source/v0.9/bundler_setup.haml: -------------------------------------------------------------------------------- 1 | %h2 Bundler.setup 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Configure the load path so all dependencies in your Gemfile can be required 7 | :code 8 | # lang: ruby 9 | require 'rubygems' 10 | require 'bundler' 11 | Bundler.setup 12 | require 'nokogiri' 13 | 14 | .bullet 15 | .description 16 | Only add gems from specified groups to the load path. If you want the gems in the default group, make sure to include it 17 | :code 18 | # lang: ruby 19 | require 'rubygems' 20 | require 'bundler' 21 | Bundler.setup(:default, :ci) 22 | require 'nokogiri' 23 | = link_to 'Learn More: Groups', 'groups.html' 24 | -------------------------------------------------------------------------------- /source/v1.1/bundle_update.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle update 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Update the current environment 7 | :code 8 | $ bundle update [GEM] [--local] [--source=SOURCE] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --local: Do not attempt to fetch gems remotely and use the gem cache instead 14 | %p 15 | --source: Update a specific source (and all gems associated with it) 16 | .description 17 | Update will install the newest versions of the gems listed in the Gemfile. Use 18 | update when you have changed the Gemfile, or if you want to get the newest 19 | possible versions of the gems in the bundle. 20 | -------------------------------------------------------------------------------- /source/v1.0/bundler_setup.haml: -------------------------------------------------------------------------------- 1 | %h2 Bundler.setup 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Configure the load path so all dependencies in 7 | your Gemfile can be required 8 | :code 9 | # lang: ruby 10 | require "rubygems" 11 | require "bundler/setup" 12 | require "nokogiri" 13 | 14 | .bullet 15 | .description 16 | Only add gems from specified groups to the 17 | load path. If you want the gems in the 18 | default group, make sure to include it 19 | :code 20 | # lang: ruby 21 | require "rubygems" 22 | require "bundler" 23 | Bundler.setup(:default, :ci) 24 | require "nokogiri" 25 | = link_to("Learn More: Groups", "./groups.html") 26 | -------------------------------------------------------------------------------- /source/v1.1/bundle_config.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle config 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Retrieve or set a configuration value 7 | :code 8 | $ bundle config NAME [VALUE] 9 | .description 10 | Retrieves or sets a configuration value. If only parameter is provided, 11 | retrieve the value. If two parameters are provided, replace the existing 12 | value with the newly provided one. 13 | 14 | By default, setting a configuration value sets it for all projects on the 15 | machine. 16 | 17 | If a global setting is superceded by local configuration, this command 18 | will show the current value, as well as any superceded values and where 19 | they were specified. 20 | -------------------------------------------------------------------------------- /source/v1.1/sinatra.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Sinatra 2 | 3 | .contents 4 | .bullet 5 | .description 6 | To use bundler with a Sinatra application, you only need to do two things. First, create a Gemfile. 7 | :code 8 | # lang: ruby 9 | gem 'sinatra' 10 | 11 | .bullet 12 | .description 13 | Then, set up your config.ru file to load the bundle before it loads your Sinatra app. 14 | :code 15 | # lang: ruby 16 | require 'rubygems' 17 | require 'bundler' 18 | 19 | Bundler.require 20 | 21 | require './my_sinatra_app' 22 | run MySinatraApp 23 | 24 | .bullet 25 | .description 26 | Start your development server with rackup, and Sinatra will be loaded via Bundler. 27 | :code 28 | $ rackup 29 | -------------------------------------------------------------------------------- /source/v1.2/sinatra.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Sinatra 2 | 3 | .contents 4 | .bullet 5 | .description 6 | To use bundler with a Sinatra application, you only need to do two things. First, create a Gemfile. 7 | :code 8 | # lang: ruby 9 | gem 'sinatra' 10 | 11 | .bullet 12 | .description 13 | Then, set up your config.ru file to load the bundle before it loads your Sinatra app. 14 | :code 15 | # lang: ruby 16 | require 'rubygems' 17 | require 'bundler' 18 | 19 | Bundler.require 20 | 21 | require './my_sinatra_app' 22 | run MySinatraApp 23 | 24 | .bullet 25 | .description 26 | Start your development server with rackup, and Sinatra will be loaded via Bundler. 27 | :code 28 | $ rackup 29 | -------------------------------------------------------------------------------- /source/v1.3/sinatra.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Sinatra 2 | 3 | .contents 4 | .bullet 5 | .description 6 | To use bundler with a Sinatra application, you only need to do two things. First, create a Gemfile. 7 | :code 8 | # lang: ruby 9 | gem 'sinatra' 10 | 11 | .bullet 12 | .description 13 | Then, set up your config.ru file to load the bundle before it loads your Sinatra app. 14 | :code 15 | # lang: ruby 16 | require 'rubygems' 17 | require 'bundler' 18 | 19 | Bundler.require 20 | 21 | require './my_sinatra_app' 22 | run MySinatraApp 23 | 24 | .bullet 25 | .description 26 | Start your development server with rackup, and Sinatra will be loaded via Bundler. 27 | :code 28 | $ rackup 29 | -------------------------------------------------------------------------------- /source/v1.5/sinatra.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Sinatra 2 | 3 | .contents 4 | .bullet 5 | .description 6 | To use bundler with a Sinatra application, you only need to do two things. First, create a Gemfile. 7 | :code 8 | # lang: ruby 9 | gem 'sinatra' 10 | 11 | .bullet 12 | .description 13 | Then, set up your config.ru file to load the bundle before it loads your Sinatra app. 14 | :code 15 | # lang: ruby 16 | require 'rubygems' 17 | require 'bundler' 18 | 19 | Bundler.require 20 | 21 | require './my_sinatra_app' 22 | run MySinatraApp 23 | 24 | .bullet 25 | .description 26 | Start your development server with rackup, and Sinatra will be loaded via Bundler. 27 | :code 28 | $ rackup 29 | -------------------------------------------------------------------------------- /source/v1.6/sinatra.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Sinatra 2 | 3 | .contents 4 | .bullet 5 | .description 6 | To use bundler with a Sinatra application, you only need to do two things. First, create a Gemfile. 7 | :code 8 | # lang: ruby 9 | gem 'sinatra' 10 | 11 | .bullet 12 | .description 13 | Then, set up your config.ru file to load the bundle before it loads your Sinatra app. 14 | :code 15 | # lang: ruby 16 | require 'rubygems' 17 | require 'bundler' 18 | 19 | Bundler.require 20 | 21 | require './my_sinatra_app' 22 | run MySinatraApp 23 | 24 | .bullet 25 | .description 26 | Start your development server with rackup, and Sinatra will be loaded via Bundler. 27 | :code 28 | $ rackup 29 | -------------------------------------------------------------------------------- /source/v1.7/sinatra.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Sinatra 2 | 3 | .contents 4 | .bullet 5 | .description 6 | To use bundler with a Sinatra application, you only need to do two things. First, create a Gemfile. 7 | :code 8 | # lang: ruby 9 | gem 'sinatra' 10 | 11 | .bullet 12 | .description 13 | Then, set up your config.ru file to load the bundle before it loads your Sinatra app. 14 | :code 15 | # lang: ruby 16 | require 'rubygems' 17 | require 'bundler' 18 | 19 | Bundler.require 20 | 21 | require './my_sinatra_app' 22 | run MySinatraApp 23 | 24 | .bullet 25 | .description 26 | Start your development server with rackup, and Sinatra will be loaded via Bundler. 27 | :code 28 | $ bundle exec rackup 29 | -------------------------------------------------------------------------------- /source/v1.8/sinatra.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Sinatra 2 | 3 | .contents 4 | .bullet 5 | .description 6 | To use bundler with a Sinatra application, you only need to do two things. First, create a Gemfile. 7 | :code 8 | # lang: ruby 9 | gem 'sinatra' 10 | 11 | .bullet 12 | .description 13 | Then, set up your config.ru file to load the bundle before it loads your Sinatra app. 14 | :code 15 | # lang: ruby 16 | require 'rubygems' 17 | require 'bundler' 18 | 19 | Bundler.require 20 | 21 | require './my_sinatra_app' 22 | run MySinatraApp 23 | 24 | .bullet 25 | .description 26 | Start your development server with rackup, and Sinatra will be loaded via Bundler. 27 | :code 28 | $ bundle exec rackup 29 | -------------------------------------------------------------------------------- /source/v1.9/sinatra.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Sinatra 2 | 3 | .contents 4 | .bullet 5 | .description 6 | To use bundler with a Sinatra application, you only need to do two things. First, create a Gemfile. 7 | :code 8 | # lang: ruby 9 | gem 'sinatra' 10 | 11 | .bullet 12 | .description 13 | Then, set up your config.ru file to load the bundle before it loads your Sinatra app. 14 | :code 15 | # lang: ruby 16 | require 'rubygems' 17 | require 'bundler' 18 | 19 | Bundler.require 20 | 21 | require './my_sinatra_app' 22 | run MySinatraApp 23 | 24 | .bullet 25 | .description 26 | Start your development server with rackup, and Sinatra will be loaded via Bundler. 27 | :code 28 | $ bundle exec rackup 29 | -------------------------------------------------------------------------------- /source/v0.9/sinatra.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Sinatra 2 | 3 | .contents 4 | .bullet 5 | .description 6 | To use bundler with a Sinatra application, you only need to do two things. First, create a Gemfile. 7 | :code 8 | # lang: ruby 9 | gem 'sinatra' 10 | 11 | .bullet 12 | .description 13 | Then, set up your config.ru file to load the bundle before it loads your Sinatra app. 14 | :code 15 | # lang: ruby 16 | require 'rubygems' 17 | require 'bundler' 18 | Bundler.setup 19 | 20 | require 'sinatra' 21 | require 'my_sinatra_app' 22 | run MySinatraApp 23 | 24 | .bullet 25 | .description 26 | Start your development server with rackup, and Sinatra will be loaded via Bundler. 27 | :code 28 | $ rackup 29 | -------------------------------------------------------------------------------- /source/v1.6/bundle_gem.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle gem 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Creates a skeleton for creating a rubygem 7 | :code 8 | $ bundle gem GEM [--bin or -b] [--test=TESTFRAMEWORK] [--edit=TEXTEDITOR] [--ext] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --bin or -b: Generate a binary for your library. 14 | %p 15 | --edit: Opens generated gemspec with specified or default 16 | text editor set BUNDLER_EDITOR, EDITOR or VISUAL env variables. 17 | %p 18 | --ext: Generate a skeleton for a C-extension. 19 | %p 20 | --test: Generate a test directory for your library: 21 | 'rspec' is the default, but 'minitest' is also supported. 22 | -------------------------------------------------------------------------------- /source/v1.7/bundle_gem.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle gem 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Creates a skeleton for creating a rubygem 7 | :code 8 | $ bundle gem GEM [--bin or -b] [--test=TESTFRAMEWORK] [--edit=TEXTEDITOR] [--ext] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --bin or -b: Generate a binary for your library. 14 | %p 15 | --edit: Opens generated gemspec with specified or default 16 | text editor set BUNDLER_EDITOR, EDITOR or VISUAL env variables. 17 | %p 18 | --ext: Generate a skeleton for a C-extension. 19 | %p 20 | --test: Generate a test directory for your library: 21 | 'rspec' is the default, but 'minitest' is also supported. 22 | -------------------------------------------------------------------------------- /source/v1.8/bundle_gem.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle gem 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Creates a skeleton for creating a rubygem 7 | :code 8 | $ bundle gem GEM [--bin or -b] [--test=TESTFRAMEWORK] [--edit=TEXTEDITOR] [--ext] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --bin or -b: Generate a binary for your library. 14 | %p 15 | --edit: Opens generated gemspec with specified or default 16 | text editor set BUNDLER_EDITOR, EDITOR or VISUAL env variables. 17 | %p 18 | --ext: Generate a skeleton for a C-extension. 19 | %p 20 | --test: Generate a test directory for your library: 21 | 'rspec' is the default, but 'minitest' is also supported. 22 | -------------------------------------------------------------------------------- /source/v1.9/bundle_gem.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle gem 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Creates a skeleton for creating a rubygem 7 | :code 8 | $ bundle gem GEM [--bin or -b] [--test=TESTFRAMEWORK] [--edit=TEXTEDITOR] [--ext] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --bin or -b: Generate a binary for your library. 14 | %p 15 | --edit: Opens generated gemspec with specified or default 16 | text editor set BUNDLER_EDITOR, EDITOR or VISUAL env variables. 17 | %p 18 | --ext: Generate a skeleton for a C-extension. 19 | %p 20 | --test: Generate a test directory for your library: 21 | 'rspec' is the default, but 'minitest' is also supported. 22 | -------------------------------------------------------------------------------- /source/v1.1/bundle_outdated.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle outdated 2 | 3 | .contents 4 | .bullet 5 | .description 6 | List installed gems with newer versions available 7 | :code 8 | $ bundle outdated [GEM] [--local] [--pre] [--source] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --local: Do not attempt to fetch gems remotely and use the gem cache instead 14 | %p 15 | --pre: Check for newer pre-release gems 16 | %p 17 | --source: Check against a specific source 18 | .description 19 | Outdated lists the names and versions of gems that have a newer version available 20 | in the given source. Calling outdated with [GEM [GEM]] will only check for newer 21 | versions of the given gems. By default, available prerelease gems will be ignored. 22 | -------------------------------------------------------------------------------- /source/v1.2/bundle_outdated.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle outdated 2 | 3 | .contents 4 | .bullet 5 | .description 6 | List installed gems with newer versions available 7 | :code 8 | $ bundle outdated [GEM] [--local] [--pre] [--source] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --local: Do not attempt to fetch gems remotely and use the gem cache instead 14 | %p 15 | --pre: Check for newer pre-release gems 16 | %p 17 | --source: Check against a specific source 18 | .description 19 | Outdated lists the names and versions of gems that have a newer version available 20 | in the given source. Calling outdated with [GEM [GEM]] will only check for newer 21 | versions of the given gems. By default, available prerelease gems will be ignored. 22 | -------------------------------------------------------------------------------- /source/v1.3/bundle_outdated.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle outdated 2 | 3 | .contents 4 | .bullet 5 | .description 6 | List installed gems with newer versions available 7 | :code 8 | $ bundle outdated [GEM] [--local] [--pre] [--source] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --local: Do not attempt to fetch gems remotely and use the gem cache instead 14 | %p 15 | --pre: Check for newer pre-release gems 16 | %p 17 | --source: Check against a specific source 18 | .description 19 | Outdated lists the names and versions of gems that have a newer version available 20 | in the given source. Calling outdated with [GEM [GEM]] will only check for newer 21 | versions of the given gems. By default, available prerelease gems will be ignored. 22 | -------------------------------------------------------------------------------- /source/v1.2/bundle_check.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle check 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Checks if the dependencies listed in Gemfile are satisfied by currently installed gems 7 | :code 8 | $ bundle check [--gemfile=FILE] [--path=PATH] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --gemfile: Use the specified gemfile instead of Gemfile. 14 | %p 15 | --path: Specify a different path than the system default ($BUNDLE_PATH or $GEM_HOME). Bundler will remember this value for future installs on this machine. 16 | .description 17 | Check searches the local machine for each of the gems requested in the Gemfile. If 18 | all gems are found, Bundler prints a success message and exits with a status of 0. 19 | If not, the first missing gem is listed and Bundler exits status 1. 20 | -------------------------------------------------------------------------------- /source/v1.3/bundle_check.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle check 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Checks if the dependencies listed in Gemfile are satisfied by currently installed gems 7 | :code 8 | $ bundle check [--gemfile=FILE] [--path=PATH] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --gemfile: Use the specified gemfile instead of Gemfile. 14 | %p 15 | --path: Specify a different path than the system default ($BUNDLE_PATH or $GEM_HOME). Bundler will remember this value for future installs on this machine. 16 | .description 17 | Check searches the local machine for each of the gems requested in the Gemfile. If 18 | all gems are found, Bundler prints a success message and exits with a status of 0. 19 | If not, the first missing gem is listed and Bundler exits status 1. 20 | -------------------------------------------------------------------------------- /source/v1.5/bundle_check.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle check 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Checks if the dependencies listed in Gemfile are satisfied by currently installed gems 7 | :code 8 | $ bundle check [--gemfile=FILE] [--path=PATH] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --gemfile: Use the specified gemfile instead of Gemfile. 14 | %p 15 | --path: Specify a different path than the system default ($BUNDLE_PATH or $GEM_HOME). Bundler will remember this value for future installs on this machine. 16 | .description 17 | Check searches the local machine for each of the gems requested in the Gemfile. If 18 | all gems are found, Bundler prints a success message and exits with a status of 0. 19 | If not, the first missing gem is listed and Bundler exits status 1. 20 | -------------------------------------------------------------------------------- /source/layouts/blog_layout.haml: -------------------------------------------------------------------------------- 1 | !!! 2 | - v = current_page.url.scan(/v\d\.\d/).first || current_version 3 | %html 4 | %head 5 | = partial 'partials/head' 6 | %body 7 | #body 8 | #header 9 | - logo_img = image_tag('gembundler.png', :width => 725, :alt => "The best way to manage your application's dependencies") 10 | = link_to logo_img, '/', :class => 'image' 11 | #container 12 | .contents.blog 13 | %h2.title 14 | = link_to current_article.title, current_article.url 15 | %h3.subtitle 16 | by 17 | = link_to current_article.data.author, current_article.data.author_url, :target => '_blank' 18 | on 19 | %time 20 | = current_article.date.strftime('%b %e %Y') 21 | %hr 22 | = find_and_preserve do 23 | = yield 24 | = partial 'partials/footer', locals: { v: v } 25 | -------------------------------------------------------------------------------- /source/v1.1/bundle_check.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle check 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Checks if the dependencies listed in Gemfile are satisfied by currently 7 | installed gems 8 | :code 9 | $ bundle check [--gemfile=FILE] [--path=PATH] 10 | .notes 11 | %p 12 | Options: 13 | %p 14 | --gemfile: Use the specified gemfile instead of Gemfile. 15 | %p 16 | --path: Specify a different path than the system default 17 | ($BUNDLE_PATH or $GEM_HOME). Bundler will remember this value for future 18 | installs on this machine. 19 | .description 20 | Check searches the local machine for each of the gems requested in the 21 | Gemfile. If all gems are found, Bundler prints a success message and exits 22 | with a status of 0. If not, the first missing gem is listed and Bundler 23 | exits status 1. 24 | -------------------------------------------------------------------------------- /source/v1.1/bundle_viz.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle viz 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a visual dependency graph 7 | :code 8 | $ bundle viz [--file=FILE] [--format=FORMAT] [--requirements] [--version] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --file or -f: The name to use for the generated file. see format option 14 | %p 15 | --format or -F: This is output format option. Supported format is png, jpg, svg, dot ... 16 | %p 17 | --requirements or -r: Set to show the version of each required dependency. 18 | %p 19 | --version or -v: Set to show each gem version. 20 | .description 21 | Viz generates a PNG file of the current Gemfile as a dependency graph. 22 | Viz requires the ruby-graphviz gem (and its dependencies). 23 | The associated gems must also be installed via 'bundle install'. 24 | -------------------------------------------------------------------------------- /source/v1.2/bundle_viz.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle viz 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a visual dependency graph 7 | :code 8 | $ bundle viz [--file=FILE] [--format=FORMAT] [--requirements] [--version] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --file or -f: The name to use for the generated file. see format option 14 | %p 15 | --format or -F: This is output format option. Supported format is png, jpg, svg, dot ... 16 | %p 17 | --requirements or -r: Set to show the version of each required dependency. 18 | %p 19 | --version or -v: Set to show each gem version. 20 | .description 21 | Viz generates a PNG file of the current Gemfile as a dependency graph. 22 | Viz requires the ruby-graphviz gem (and its dependencies). 23 | The associated gems must also be installed via 'bundle install'. 24 | -------------------------------------------------------------------------------- /source/v1.3/bundle_viz.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle viz 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a visual dependency graph 7 | :code 8 | $ bundle viz [--file=FILE] [--format=FORMAT] [--requirements] [--version] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --file or -f: The name to use for the generated file. see format option 14 | %p 15 | --format or -F: This is output format option. Supported format is png, jpg, svg, dot ... 16 | %p 17 | --requirements or -r: Set to show the version of each required dependency. 18 | %p 19 | --version or -v: Set to show each gem version. 20 | .description 21 | Viz generates a PNG file of the current Gemfile as a dependency graph. 22 | Viz requires the ruby-graphviz gem (and its dependencies). 23 | The associated gems must also be installed via 'bundle install'. 24 | -------------------------------------------------------------------------------- /source/v1.5/bundle_viz.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle viz 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a visual dependency graph 7 | :code 8 | $ bundle viz [--file=FILE] [--format=FORMAT] [--requirements] [--version] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --file or -f: The name to use for the generated file. see format option 14 | %p 15 | --format or -F: This is output format option. Supported format is png, jpg, svg, dot ... 16 | %p 17 | --requirements or -r: Set to show the version of each required dependency. 18 | %p 19 | --version or -v: Set to show each gem version. 20 | .description 21 | Viz generates a PNG file of the current Gemfile as a dependency graph. 22 | Viz requires the ruby-graphviz gem (and its dependencies). 23 | The associated gems must also be installed via 'bundle install'. 24 | -------------------------------------------------------------------------------- /source/v1.6/bundle_viz.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle viz 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a visual dependency graph 7 | :code 8 | $ bundle viz [--file=FILE] [--format=FORMAT] [--requirements] [--version] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --file or -f: The name to use for the generated file. see format option 14 | %p 15 | --format or -F: This is output format option. Supported format is png, jpg, svg, dot ... 16 | %p 17 | --requirements or -r: Set to show the version of each required dependency. 18 | %p 19 | --version or -v: Set to show each gem version. 20 | .description 21 | Viz generates a PNG file of the current Gemfile as a dependency graph. 22 | Viz requires the ruby-graphviz gem (and its dependencies). 23 | The associated gems must also be installed via 'bundle install'. 24 | -------------------------------------------------------------------------------- /source/v1.7/bundle_viz.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle viz 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a visual dependency graph 7 | :code 8 | $ bundle viz [--file=FILE] [--format=FORMAT] [--requirements] [--version] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --file or -f: The name to use for the generated file. see format option 14 | %p 15 | --format or -F: This is output format option. Supported format is png, jpg, svg, dot ... 16 | %p 17 | --requirements or -r: Set to show the version of each required dependency. 18 | %p 19 | --version or -v: Set to show each gem version. 20 | .description 21 | Viz generates a PNG file of the current Gemfile as a dependency graph. 22 | Viz requires the ruby-graphviz gem (and its dependencies). 23 | The associated gems must also be installed via 'bundle install'. 24 | -------------------------------------------------------------------------------- /source/v1.5/bundle_outdated.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle outdated 2 | 3 | .contents 4 | .bullet 5 | .description 6 | List installed gems with newer versions available 7 | :code 8 | $ bundle outdated [GEM] [--local] [--pre] [--source] [--strict] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --local: Do not attempt to fetch gems remotely and use the gem cache instead 14 | %p 15 | --pre: Check for newer pre-release gems 16 | %p 17 | --source: Check against a specific source 18 | %p 19 | --strict: Display outdated gems that match the dependency requirements. 20 | .description 21 | Outdated lists the names and versions of gems that have a newer version available 22 | in the given source. Calling outdated with [GEM [GEM]] will only check for newer 23 | versions of the given gems. By default, available prerelease gems will be ignored. 24 | -------------------------------------------------------------------------------- /source/v1.6/bundle_outdated.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle outdated 2 | 3 | .contents 4 | .bullet 5 | .description 6 | List installed gems with newer versions available 7 | :code 8 | $ bundle outdated [GEM] [--local] [--pre] [--source] [--strict] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --local: Do not attempt to fetch gems remotely and use the gem cache instead 14 | %p 15 | --pre: Check for newer pre-release gems 16 | %p 17 | --source: Check against a specific source 18 | %p 19 | --strict: Display outdated gems that match the dependency requirements. 20 | .description 21 | Outdated lists the names and versions of gems that have a newer version available 22 | in the given source. Calling outdated with [GEM [GEM]] will only check for newer 23 | versions of the given gems. By default, available prerelease gems will be ignored. 24 | -------------------------------------------------------------------------------- /source/v1.7/bundle_outdated.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle outdated 2 | 3 | .contents 4 | .bullet 5 | .description 6 | List installed gems with newer versions available 7 | :code 8 | $ bundle outdated [GEM] [--local] [--pre] [--source] [--strict] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --local: Do not attempt to fetch gems remotely and use the gem cache instead 14 | %p 15 | --pre: Check for newer pre-release gems 16 | %p 17 | --source: Check against a specific source 18 | %p 19 | --strict: Display outdated gems that match the dependency requirements. 20 | .description 21 | Outdated lists the names and versions of gems that have a newer version available 22 | in the given source. Calling outdated with [GEM [GEM]] will only check for newer 23 | versions of the given gems. By default, available prerelease gems will be ignored. 24 | -------------------------------------------------------------------------------- /source/v1.8/bundle_outdated.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle outdated 2 | 3 | .contents 4 | .bullet 5 | .description 6 | List installed gems with newer versions available 7 | :code 8 | $ bundle outdated [GEM] [--local] [--pre] [--source] [--strict] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --local: Do not attempt to fetch gems remotely and use the gem cache instead 14 | %p 15 | --pre: Check for newer pre-release gems 16 | %p 17 | --source: Check against a specific source 18 | %p 19 | --strict: Display outdated gems that match the dependency requirements. 20 | .description 21 | Outdated lists the names and versions of gems that have a newer version available 22 | in the given source. Calling outdated with [GEM [GEM]] will only check for newer 23 | versions of the given gems. By default, available prerelease gems will be ignored. 24 | -------------------------------------------------------------------------------- /source/v1.9/bundle_outdated.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle outdated 2 | 3 | .contents 4 | .bullet 5 | .description 6 | List installed gems with newer versions available 7 | :code 8 | $ bundle outdated [GEM] [--local] [--pre] [--source] [--strict] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --local: Do not attempt to fetch gems remotely and use the gem cache instead 14 | %p 15 | --pre: Check for newer pre-release gems 16 | %p 17 | --source: Check against a specific source 18 | %p 19 | --strict: Display outdated gems that match the dependency requirements. 20 | .description 21 | Outdated lists the names and versions of gems that have a newer version available 22 | in the given source. Calling outdated with [GEM [GEM]] will only check for newer 23 | versions of the given gems. By default, available prerelease gems will be ignored. 24 | -------------------------------------------------------------------------------- /source/v1.6/bundle_check.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle check 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Checks if the dependencies listed in Gemfile are satisfied by currently installed gems 7 | :code 8 | $ bundle check [--dry-run] [--gemfile=FILE] [--path=PATH] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --dry-run: Locks the Gemfile. 14 | %p 15 | --gemfile: Use the specified gemfile instead of Gemfile. 16 | %p 17 | --path: Specify a different path than the system default 18 | ($BUNDLE_PATH or $GEM_HOME). Bundler will remember this value for future 19 | installs on this machine. 20 | .description 21 | Check searches the local machine for each of the gems requested in the Gemfile. If 22 | all gems are found, Bundler prints a success message and exits with a status of 0. 23 | If not, the first missing gem is listed and Bundler exits status 1. 24 | -------------------------------------------------------------------------------- /source/v1.7/bundle_check.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle check 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Checks if the dependencies listed in Gemfile are satisfied by currently installed gems 7 | :code 8 | $ bundle check [--dry-run] [--gemfile=FILE] [--path=PATH] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --dry-run: Locks the Gemfile. 14 | %p 15 | --gemfile: Use the specified gemfile instead of Gemfile. 16 | %p 17 | --path: Specify a different path than the system default 18 | ($BUNDLE_PATH or $GEM_HOME). Bundler will remember this value for future 19 | installs on this machine. 20 | .description 21 | Check searches the local machine for each of the gems requested in the Gemfile. If 22 | all gems are found, Bundler prints a success message and exits with a status of 0. 23 | If not, the first missing gem is listed and Bundler exits status 1. 24 | -------------------------------------------------------------------------------- /source/v1.8/bundle_check.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle check 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Checks if the dependencies listed in Gemfile are satisfied by currently installed gems 7 | :code 8 | $ bundle check [--dry-run] [--gemfile=FILE] [--path=PATH] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --dry-run: Locks the Gemfile. 14 | %p 15 | --gemfile: Use the specified gemfile instead of Gemfile. 16 | %p 17 | --path: Specify a different path than the system default 18 | ($BUNDLE_PATH or $GEM_HOME). Bundler will remember this value for future 19 | installs on this machine. 20 | .description 21 | Check searches the local machine for each of the gems requested in the Gemfile. If 22 | all gems are found, Bundler prints a success message and exits with a status of 0. 23 | If not, the first missing gem is listed and Bundler exits status 1. 24 | -------------------------------------------------------------------------------- /source/v1.9/bundle_check.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle check 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Checks if the dependencies listed in Gemfile are satisfied by currently installed gems 7 | :code 8 | $ bundle check [--dry-run] [--gemfile=FILE] [--path=PATH] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --dry-run: Locks the Gemfile. 14 | %p 15 | --gemfile: Use the specified gemfile instead of Gemfile. 16 | %p 17 | --path: Specify a different path than the system default 18 | ($BUNDLE_PATH or $GEM_HOME). Bundler will remember this value for future 19 | installs on this machine. 20 | .description 21 | Check searches the local machine for each of the gems requested in the Gemfile. If 22 | all gems are found, Bundler prints a success message and exits with a status of 0. 23 | If not, the first missing gem is listed and Bundler exits status 1. 24 | -------------------------------------------------------------------------------- /source/v1.3/rubymotion.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with RubyMotion 2 | .contents 3 | .bullet 4 | .description 5 | If you don't have a RubyMotion app yet, generate one. 6 | :code 7 | $ motion create myapp 8 | $ cd myapp 9 | .bullet 10 | .description 11 | You'll need to create a Gemfile. Here we're using bubblewrap. 12 | :code 13 | # lang: ruby 14 | gem 'bubble-wrap' 15 | 16 | .bullet 17 | .description 18 | Then, set up your Rakefile to require your bundled gems at compile time. 19 | Add this to the top of the file, right beneath the line `require 'motion/project'` 20 | :code 21 | # lang: ruby 22 | require 'bundler' 23 | 24 | Bundler.require 25 | 26 | .bullet 27 | .description 28 | Next, install your dependencies: 29 | :code 30 | $ bundle install 31 | 32 | .bullet 33 | .description 34 | Now you can just compile your app as normal. 35 | :code 36 | $ rake 37 | -------------------------------------------------------------------------------- /source/v1.5/rubymotion.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with RubyMotion 2 | .contents 3 | .bullet 4 | .description 5 | If you don't have a RubyMotion app yet, generate one. 6 | :code 7 | $ motion create myapp 8 | $ cd myapp 9 | .bullet 10 | .description 11 | You'll need to create a Gemfile. Here we're using bubblewrap. 12 | :code 13 | # lang: ruby 14 | gem 'bubble-wrap' 15 | 16 | .bullet 17 | .description 18 | Then, set up your Rakefile to require your bundled gems at compile time. 19 | Add this to the top of the file, right beneath the line `require 'motion/project'` 20 | :code 21 | # lang: ruby 22 | require 'bundler' 23 | 24 | Bundler.require 25 | 26 | .bullet 27 | .description 28 | Next, install your dependencies: 29 | :code 30 | $ bundle install 31 | 32 | .bullet 33 | .description 34 | Now you can just compile your app as normal. 35 | :code 36 | $ rake 37 | -------------------------------------------------------------------------------- /source/v1.6/rubymotion.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with RubyMotion 2 | .contents 3 | .bullet 4 | .description 5 | If you don't have a RubyMotion app yet, generate one. 6 | :code 7 | $ motion create myapp 8 | $ cd myapp 9 | .bullet 10 | .description 11 | You'll need to create a Gemfile. Here we're using bubblewrap. 12 | :code 13 | # lang: ruby 14 | gem 'bubble-wrap' 15 | 16 | .bullet 17 | .description 18 | Then, set up your Rakefile to require your bundled gems at compile time. 19 | Add this to the top of the file, right beneath the line `require 'motion/project'` 20 | :code 21 | # lang: ruby 22 | require 'bundler' 23 | 24 | Bundler.require 25 | 26 | .bullet 27 | .description 28 | Next, install your dependencies: 29 | :code 30 | $ bundle install 31 | 32 | .bullet 33 | .description 34 | Now you can just compile your app as normal. 35 | :code 36 | $ rake 37 | -------------------------------------------------------------------------------- /source/blog/2014-08-15-gem-not-found-error-on-1-7-0.html.markdown: -------------------------------------------------------------------------------- 1 | --- 2 | title: Gem not found error on 1.7.0 3 | date: 2014-08-15 17:02 UTC 4 | author: André Arko 5 | author_url: "http://arko.net" 6 | category: announcement 7 | --- 8 | After the release of Bundler 1.7.0 yesterday, we discovered a bug that can cause Bundler to report that a gem was not found, even though that gem is available from one of the relevant sources. We're understand the problem, and we're working on a fix as fast as we can. In the meantime, it's possible to work completely around the problem by adding the `--full-index` option when you run `bundle install`. I fully recognize that it sucks to have a regression in a security update, and I'm sorry that this happened. I can't guarantee something like this well never happen again, but we're adding tests to prevent this particular bug from recurring. 9 | 10 | Sorry it's broken; we're working on fixing it. In the meantime, please work around the issue with `bundle install --full-index`. 11 | -------------------------------------------------------------------------------- /source/v1.2/rubymotion.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with RubyMotion 2 | .contents 3 | .bullet 4 | .description 5 | If you don't have a RubyMotion app yet, generate one. 6 | :code 7 | $ motion create myapp 8 | $ cd myapp 9 | .bullet 10 | .description 11 | You'll need to create a Gemfile. Here we're using bubblewrap. 12 | :code 13 | # lang: ruby 14 | gem 'bubble-wrap' 15 | 16 | .bullet 17 | .description 18 | Then, set up your Rakefile to require your bundled gems at compile time. 19 | Add this to the top of the file, right beneath the line require 'motion/project' 20 | :code 21 | # lang: ruby 22 | require 'bundler' 23 | 24 | Bundler.require 25 | 26 | .bullet 27 | .description 28 | Next, install your dependencies: 29 | :code 30 | $ bundle install 31 | 32 | .bullet 33 | .description 34 | Now you can just compile your app as normal. 35 | :code 36 | $ rake 37 | -------------------------------------------------------------------------------- /source/v1.7/rubymotion.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with RubyMotion 2 | .contents 3 | .bullet 4 | .description 5 | If you don't have a RubyMotion app yet, generate one. 6 | :code 7 | $ motion create myapp 8 | $ cd myapp 9 | .bullet 10 | .description 11 | You'll need to create a Gemfile. Here we're using bubblewrap. 12 | :code 13 | # lang: ruby 14 | gem 'bubble-wrap' 15 | 16 | .bullet 17 | .description 18 | Then, set up your Rakefile to require your bundled gems at compile time. 19 | Add this to the top of the file, right beneath the line `require 'motion/project'` 20 | :code 21 | # lang: ruby 22 | require 'bundler' 23 | 24 | Bundler.require 25 | 26 | .bullet 27 | .description 28 | Next, install your dependencies: 29 | :code 30 | $ bundle install 31 | 32 | .bullet 33 | .description 34 | Now you can just compile your app as normal. 35 | :code 36 | $ bundle exec rake 37 | -------------------------------------------------------------------------------- /source/v1.8/rubymotion.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with RubyMotion 2 | .contents 3 | .bullet 4 | .description 5 | If you don't have a RubyMotion app yet, generate one. 6 | :code 7 | $ motion create myapp 8 | $ cd myapp 9 | .bullet 10 | .description 11 | You'll need to create a Gemfile. Here we're using bubblewrap. 12 | :code 13 | # lang: ruby 14 | gem 'bubble-wrap' 15 | 16 | .bullet 17 | .description 18 | Then, set up your Rakefile to require your bundled gems at compile time. 19 | Add this to the top of the file, right beneath the line `require 'motion/project'` 20 | :code 21 | # lang: ruby 22 | require 'bundler' 23 | 24 | Bundler.require 25 | 26 | .bullet 27 | .description 28 | Next, install your dependencies: 29 | :code 30 | $ bundle install 31 | 32 | .bullet 33 | .description 34 | Now you can just compile your app as normal. 35 | :code 36 | $ bundle exec rake 37 | -------------------------------------------------------------------------------- /source/v1.9/rubymotion.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with RubyMotion 2 | .contents 3 | .bullet 4 | .description 5 | If you don't have a RubyMotion app yet, generate one. 6 | :code 7 | $ motion create myapp 8 | $ cd myapp 9 | .bullet 10 | .description 11 | You'll need to create a Gemfile. Here we're using bubblewrap. 12 | :code 13 | # lang: ruby 14 | gem 'bubble-wrap' 15 | 16 | .bullet 17 | .description 18 | Then, set up your Rakefile to require your bundled gems at compile time. 19 | Add this to the top of the file, right beneath the line `require 'motion/project'` 20 | :code 21 | # lang: ruby 22 | require 'bundler' 23 | 24 | Bundler.require 25 | 26 | .bullet 27 | .description 28 | Next, install your dependencies: 29 | :code 30 | $ bundle install 31 | 32 | .bullet 33 | .description 34 | Now you can just compile your app as normal. 35 | :code 36 | $ bundle exec rake 37 | -------------------------------------------------------------------------------- /source/v0.9/deploying.haml: -------------------------------------------------------------------------------- 1 | %h2 Deploying bundled applications 2 | 3 | .contents 4 | .bullet 5 | .description 6 | When you are ready to deploy your application, you should lock your bundle to guarantee that dependency versions will no longer change. 7 | :code 8 | $ bundle lock 9 | = link_to 'Learn more: bundle lock', 'bundle_lock.html' 10 | 11 | .bullet 12 | .description 13 | Add your Gemfile and lockfile to source control, but ignore the .bundle folder, which is specific to each machine. 14 | :code 15 | $ echo ".bundle" >> .gitignore 16 | $ git add Gemfile Gemfile.lock .gitignore 17 | $ git commit -m "Add bundler" 18 | 19 | .bullet 20 | .description 21 | In your deploy script, after updating to the latest code, install your bundle to ensure all your dependencies are met. 22 | .how 23 | :code 24 | $ bundle install 25 | .notes 26 | Start your application servers as usual, and your application will use your bundled environment just like it does locally in development. 27 | -------------------------------------------------------------------------------- /source/v1.8/bundle_exec.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle exec 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Run the command in context of the bundle 7 | :code 8 | $ bundle exec [--keep-file-descriptors] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --keep-file-descriptors: For Ruby versions less than 2.0, 14 | keeps non-standard file descriptors on Kernel#exec 15 | 16 | .description 17 | This command executes the command, making all gems specified in the 18 | Gemfile(5) available to require in Ruby programs. 19 | 20 | Essentially, if you would normally have run something like 21 | rspec spec/my_spec.rb, and you want to use the gems specified 22 | in the Gemfile and installed via bundle install, you 23 | should run bundle exec rspec spec/my_spec.rb. 24 | 25 | Note that bundle exec does not require that an executable is 26 | available on your shell's $PATH. 27 | -------------------------------------------------------------------------------- /source/v1.9/bundle_exec.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle exec 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Run the command in context of the bundle 7 | :code 8 | $ bundle exec [--keep-file-descriptors] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --keep-file-descriptors: For Ruby versions less than 2.0, 14 | keeps non-standard file descriptors on Kernel#exec 15 | 16 | .description 17 | This command executes the command, making all gems specified in the 18 | Gemfile(5) available to require in Ruby programs. 19 | 20 | Essentially, if you would normally have run something like 21 | rspec spec/my_spec.rb, and you want to use the gems specified 22 | in the Gemfile and installed via bundle install, you 23 | should run bundle exec rspec spec/my_spec.rb. 24 | 25 | Note that bundle exec does not require that an executable is 26 | available on your shell's $PATH. 27 | -------------------------------------------------------------------------------- /source/blog/feed.xml.builder: -------------------------------------------------------------------------------- 1 | xml.instruct! 2 | xml.feed "xmlns" => "http://www.w3.org/2005/Atom" do 3 | site_url = "http://bundler.io/" 4 | xml.title "Bundler Blog" 5 | xml.subtitle "The latest news on Bundler" 6 | xml.id URI.join(site_url, blog.options.prefix.to_s) 7 | xml.link "href" => URI.join(site_url, blog.options.prefix.to_s) 8 | xml.link "href" => URI.join(site_url, current_page.path), "rel" => "self" 9 | xml.updated(blog.articles.first.date.to_time.iso8601) unless blog.articles.empty? 10 | xml.author { xml.name "The Bundler Team" } 11 | 12 | blog.articles[0..5].each do |article| 13 | xml.entry do 14 | xml.title article.title 15 | xml.link "rel" => "alternate", "href" => URI.join(site_url, article.url) 16 | xml.id URI.join(site_url, article.url) 17 | xml.published article.date.to_time.iso8601 18 | xml.updated File.mtime(article.source_file).iso8601 19 | xml.author { xml.name article.data[:author] } 20 | # xml.summary article.summary, "type" => "html" 21 | xml.content article.body, "type" => "html" 22 | end 23 | end 24 | end 25 | -------------------------------------------------------------------------------- /source/v1.0/sinatra.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Sinatra 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Let's say you wanted to run the following Sinatra app. 7 | :code 8 | # lang: ruby 9 | class MySinatraApp < Sinatra::Base 10 | get "/" do 11 | "Hello Bundler" 12 | end 13 | end 14 | 15 | .bullet 16 | .description 17 | To use bundler with a Sinatra application, you only need to do two things. First, create a Gemfile. 18 | :code 19 | # lang: ruby 20 | source "https://rubygems.org" 21 | gem "sinatra", :require => "sinatra/base" 22 | 23 | .bullet 24 | .description 25 | Then, set up your config.ru file to load the bundle before it loads your Sinatra app. 26 | :code 27 | # lang: ruby 28 | require 'rubygems' 29 | require 'bundler' 30 | 31 | Bundler.require 32 | 33 | require './my_sinatra_app' 34 | run MySinatraApp 35 | 36 | .bullet 37 | .description 38 | Start your development server with rackup, and Sinatra will be loaded via Bundler. 39 | :code 40 | $ rackup 41 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # bundler.io 2 | bundler.io is intended to serve as a convenient source for documentation on the [bundler](https://github.com/bundler/bundler) gem. 3 | 4 | The site bundler.io is a static site generated using [Middleman](http://middlemanapp.com/). 5 | 6 | [Bundler's manual pages](https://github.com/bundler/bundler/tree/master/man) document much of its functionality and serve as an important part of the site. They are included via the **Rakefile**. 7 | 8 | ## Basic Middleman Commands 9 | 10 | Run a local development web server: 11 | 12 | bundle exec middleman server 13 | 14 | This will start a local web server running at: *http://localhost:4567*. It will serve the site as it exists in **/source**. 15 | 16 | To specify the host and/or port, add the -h, -p flag(s): 17 | 18 | bundle exec middleman -h 0.0.0.0 -p 8080 19 | 20 | Note: the development server will automatically reload pages when they or there associated stylesheets are modified. This feature is enabled in **config.rb**. 21 | 22 | Build the site: 23 | 24 | bundle exec middleman build 25 | 26 | This will use the files in **/source** to generate a static site in **/build**. 27 | -------------------------------------------------------------------------------- /source/v1.8/bundle_viz.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle viz 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a visual dependency graph 7 | :code 8 | $ bundle viz [--file=FILE] [--format=FORMAT] [--requirements] [--version] 9 | [--without=GROUP GROUP] 10 | .notes 11 | %p 12 | Options: 13 | %p 14 | --file or -f: The name to use for the generated file. see format option 15 | %p 16 | --format or -F: This is output format option. Supported format is png, jpg, svg, dot ... 17 | %p 18 | --requirements or -r: Set to show the version of each required dependency. 19 | %p 20 | --version or -v: Set to show each gem version. 21 | %p 22 | --without: Exclude gems that are part of the specified named group. 23 | = link_to 'Learn More: Groups', './groups.html' 24 | .description 25 | Viz generates a PNG file of the current Gemfile as a dependency graph. 26 | Viz requires the ruby-graphviz gem (and its dependencies). 27 | The associated gems must also be installed via 'bundle install'. 28 | -------------------------------------------------------------------------------- /source/v1.9/bundle_viz.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle viz 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Generates a visual dependency graph 7 | :code 8 | $ bundle viz [--file=FILE] [--format=FORMAT] [--requirements] [--version] 9 | [--without=GROUP GROUP] 10 | .notes 11 | %p 12 | Options: 13 | %p 14 | --file or -f: The name to use for the generated file. see format option 15 | %p 16 | --format or -F: This is output format option. Supported format is png, jpg, svg, dot ... 17 | %p 18 | --requirements or -r: Set to show the version of each required dependency. 19 | %p 20 | --version or -v: Set to show each gem version. 21 | %p 22 | --without: Exclude gems that are part of the specified named group. 23 | = link_to 'Learn More: Groups', './groups.html' 24 | .description 25 | Viz generates a PNG file of the current Gemfile as a dependency graph. 26 | Viz requires the ruby-graphviz gem (and its dependencies). 27 | The associated gems must also be installed via 'bundle install'. 28 | -------------------------------------------------------------------------------- /source/partials/_footer.haml: -------------------------------------------------------------------------------- 1 | #footer 2 | = image_tag 'emocow.png' 3 | = image_tag 'panda.jpg' 4 | .spacer 5 | #credits 6 | %p 7 | == Many thanks to Bundler's #{link_to 'contributors', '/contributors.html' } 8 | == and #{link_to 'sponsors', '/sponsors.html' } 9 | .spacer 10 | = image_tag 'bundler-small.png' 11 | %a#github{ :href => 'http://github.com/bundler/bundler/' } 12 | %img{ :src => 'http://s3.amazonaws.com/github/ribbons/forkme_right_darkblue_121621.png', :alt => 'Fork me on GitHub' } 13 | #prod-versions 14 | Docs: 15 | = link_to("Previous Version (#{versions[-2]})", "/#{versions[-2]}/index.html", :class => ('current' if v == versions[-2])) 16 | = link_to("Current Version (#{current_version})", "/", :class => ('current' if v == current_version)) 17 | 18 | :javascript 19 | (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ 20 | (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), 21 | m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) 22 | })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); 23 | ga('create', 'UA-39559982-1', 'bundler.io'); 24 | ga('send', 'pageview'); 25 | -------------------------------------------------------------------------------- /source/v1.2/bundle_platform.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle platform 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Displays platform compatibility information 7 | :code 8 | $ bundle platform [--ruby] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --ruby: only display ruby related platform information 14 | 15 | .bullet 16 | .description 17 | When not passed any options, platform will display information from your Gemfile, Gemfile.lock, and Ruby VM about your platform. You'll see output like the following: 18 | :code 19 | $ bundle platform 20 | Your platform is: x86_64-linux 21 | 22 | Your app has gems that work on these platforms: 23 | * ruby 24 | 25 | Your Gemfile specifies a Ruby version requirement: 26 | * ruby 1.9.3 27 | 28 | Your current platform satisfies the Ruby version requirement. 29 | .description 30 | When the ruby directive doesn't match the running Ruby VM, it will tell you what part does not. 31 | :code 32 | Your Ruby version is 1.9.3, but your Gemfile specified 1.8.7 33 | 34 | .bullet#ruby 35 | .description 36 | When using the --ruby flag, it will just display the ruby directive information, so you don't have to parse it from the Gemfile. 37 | :code 38 | $ bundle platform --ruby 39 | ruby 1.9.3 (jruby 1.6.7) 40 | -------------------------------------------------------------------------------- /source/v1.3/bundle_platform.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle platform 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Displays platform compatibility information 7 | :code 8 | $ bundle platform [--ruby] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --ruby: only display ruby related platform information 14 | 15 | .bullet 16 | .description 17 | When not passed any options, platform will display information from your Gemfile, Gemfile.lock, and Ruby VM about your platform. You'll see output like the following: 18 | :code 19 | $ bundle platform 20 | Your platform is: x86_64-linux 21 | 22 | Your app has gems that work on these platforms: 23 | * ruby 24 | 25 | Your Gemfile specifies a Ruby version requirement: 26 | * ruby 1.9.3 27 | 28 | Your current platform satisfies the Ruby version requirement. 29 | .description 30 | When the ruby directive doesn't match the running Ruby VM, it will tell you what part does not. 31 | :code 32 | Your Ruby version is 1.9.3, but your Gemfile specified 1.8.7 33 | 34 | .bullet#ruby 35 | .description 36 | When using the --ruby flag, it will just display the ruby directive information, so you don't have to parse it from the Gemfile. 37 | :code 38 | $ bundle platform --ruby 39 | ruby 1.9.3 (jruby 1.6.7) 40 | -------------------------------------------------------------------------------- /source/v1.5/bundle_platform.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle platform 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Displays platform compatibility information 7 | :code 8 | $ bundle platform [--ruby] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --ruby: only display ruby related platform information 14 | 15 | .bullet 16 | .description 17 | When not passed any options, platform will display information from your Gemfile, Gemfile.lock, and Ruby VM about your platform. You'll see output like the following: 18 | :code 19 | $ bundle platform 20 | Your platform is: x86_64-linux 21 | 22 | Your app has gems that work on these platforms: 23 | * ruby 24 | 25 | Your Gemfile specifies a Ruby version requirement: 26 | * ruby 1.9.3 27 | 28 | Your current platform satisfies the Ruby version requirement. 29 | .description 30 | When the ruby directive doesn't match the running Ruby VM, it will tell you what part does not. 31 | :code 32 | Your Ruby version is 1.9.3, but your Gemfile specified 1.8.7 33 | 34 | .bullet#ruby 35 | .description 36 | When using the --ruby flag, it will just display the ruby directive information, so you don't have to parse it from the Gemfile. 37 | :code 38 | $ bundle platform --ruby 39 | ruby 1.9.3 (jruby 1.6.7) 40 | -------------------------------------------------------------------------------- /source/v1.6/bundle_platform.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle platform 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Displays platform compatibility information 7 | :code 8 | $ bundle platform [--ruby] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --ruby: only display ruby related platform information 14 | 15 | .bullet 16 | .description 17 | When not passed any options, platform will display information from your Gemfile, Gemfile.lock, and Ruby VM about your platform. You'll see output like the following: 18 | :code 19 | $ bundle platform 20 | Your platform is: x86_64-linux 21 | 22 | Your app has gems that work on these platforms: 23 | * ruby 24 | 25 | Your Gemfile specifies a Ruby version requirement: 26 | * ruby 1.9.3 27 | 28 | Your current platform satisfies the Ruby version requirement. 29 | .description 30 | When the ruby directive doesn't match the running Ruby VM, it will tell you what part does not. 31 | :code 32 | Your Ruby version is 1.9.3, but your Gemfile specified 1.8.7 33 | 34 | .bullet#ruby 35 | .description 36 | When using the --ruby flag, it will just display the ruby directive information, so you don't have to parse it from the Gemfile. 37 | :code 38 | $ bundle platform --ruby 39 | ruby 1.9.3 (jruby 1.6.7) 40 | -------------------------------------------------------------------------------- /source/v1.7/bundle_platform.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle platform 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Displays platform compatibility information 7 | :code 8 | $ bundle platform [--ruby] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --ruby: only display ruby related platform information 14 | 15 | .bullet 16 | .description 17 | When not passed any options, platform will display information from your Gemfile, Gemfile.lock, and Ruby VM about your platform. You'll see output like the following: 18 | :code 19 | $ bundle platform 20 | Your platform is: x86_64-linux 21 | 22 | Your app has gems that work on these platforms: 23 | * ruby 24 | 25 | Your Gemfile specifies a Ruby version requirement: 26 | * ruby 1.9.3 27 | 28 | Your current platform satisfies the Ruby version requirement. 29 | .description 30 | When the ruby directive doesn't match the running Ruby VM, it will tell you what part does not. 31 | :code 32 | Your Ruby version is 1.9.3, but your Gemfile specified 1.8.7 33 | 34 | .bullet#ruby 35 | .description 36 | When using the --ruby flag, it will just display the ruby directive information, so you don't have to parse it from the Gemfile. 37 | :code 38 | $ bundle platform --ruby 39 | ruby 1.9.3 (jruby 1.6.7) 40 | -------------------------------------------------------------------------------- /source/v1.8/bundle_platform.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle platform 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Displays platform compatibility information 7 | :code 8 | $ bundle platform [--ruby] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --ruby: only display ruby related platform information 14 | 15 | .bullet 16 | .description 17 | When not passed any options, platform will display information from your Gemfile, Gemfile.lock, and Ruby VM about your platform. You'll see output like the following: 18 | :code 19 | $ bundle platform 20 | Your platform is: x86_64-linux 21 | 22 | Your app has gems that work on these platforms: 23 | * ruby 24 | 25 | Your Gemfile specifies a Ruby version requirement: 26 | * ruby 1.9.3 27 | 28 | Your current platform satisfies the Ruby version requirement. 29 | .description 30 | When the ruby directive doesn't match the running Ruby VM, it will tell you what part does not. 31 | :code 32 | Your Ruby version is 1.9.3, but your Gemfile specified 1.8.7 33 | 34 | .bullet#ruby 35 | .description 36 | When using the --ruby flag, it will just display the ruby directive information, so you don't have to parse it from the Gemfile. 37 | :code 38 | $ bundle platform --ruby 39 | ruby 1.9.3 (jruby 1.6.7) 40 | -------------------------------------------------------------------------------- /source/v1.9/bundle_platform.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle platform 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Displays platform compatibility information 7 | :code 8 | $ bundle platform [--ruby] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --ruby: only display ruby related platform information 14 | 15 | .bullet 16 | .description 17 | When not passed any options, platform will display information from your Gemfile, Gemfile.lock, and Ruby VM about your platform. You'll see output like the following: 18 | :code 19 | $ bundle platform 20 | Your platform is: x86_64-linux 21 | 22 | Your app has gems that work on these platforms: 23 | * ruby 24 | 25 | Your Gemfile specifies a Ruby version requirement: 26 | * ruby 1.9.3 27 | 28 | Your current platform satisfies the Ruby version requirement. 29 | .description 30 | When the ruby directive doesn't match the running Ruby VM, it will tell you what part does not. 31 | :code 32 | Your Ruby version is 1.9.3, but your Gemfile specified 1.8.7 33 | 34 | .bullet#ruby 35 | .description 36 | When using the --ruby flag, it will just display the ruby directive information, so you don't have to parse it from the Gemfile. 37 | :code 38 | $ bundle platform --ruby 39 | ruby 1.9.3 (jruby 1.6.7) 40 | -------------------------------------------------------------------------------- /config.rb: -------------------------------------------------------------------------------- 1 | activate :syntax 2 | set :markdown_engine, :kramdown 3 | 4 | set :versions, `rake versions`.split 5 | set :current_version, versions.last 6 | 7 | # Make documentation for the latest version available at the top level, too. 8 | # Any pages with names that conflict with files already at the top level will be skipped. 9 | ready do 10 | sitemap.resources.each do |page| 11 | if page.path.start_with? "#{current_version}/" 12 | proxy_path = page.path["#{current_version}/".length..-1] 13 | proxy proxy_path, page.path if sitemap.find_resource_by_path(proxy_path).nil? 14 | end 15 | end 16 | end 17 | 18 | page '/sitemap.xml', layout: false 19 | 20 | ### 21 | # Helpers 22 | ### 23 | Dir.glob(File.expand_path('../helpers/**/*.rb', __FILE__), &method(:require)) 24 | 25 | set :css_dir, 'stylesheets' 26 | set :js_dir, 'javascripts' 27 | set :images_dir, 'images' 28 | 29 | activate :blog do |blog| 30 | blog.name = 'blog' 31 | blog.prefix = 'blog' 32 | blog.permalink = '{year}/{month}/{day}/{title}.html' 33 | blog.layout = 'blog_layout' 34 | 35 | blog.calendar_template = 'blog/calendar.html' 36 | blog.year_link = "{year}/index.html" 37 | blog.month_link = "{year}/{month}/index.html" 38 | blog.day_link = "{year}/{month}/{day}/index.html" 39 | end 40 | 41 | page "/blog/feed.xml", layout: false 42 | 43 | configure :development do 44 | activate :livereload 45 | end 46 | 47 | configure :build do 48 | activate :minify_css 49 | end 50 | -------------------------------------------------------------------------------- /source/v0.9/groups.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Groups 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Grouping your dependencies allows you to perform operations on the entire 7 | group. 8 | :code 9 | # lang: ruby 10 | # These gems are in the :default group 11 | gem 'nokogiri' 12 | gem 'sinatra' 13 | 14 | gem 'wirble', :group => :development 15 | 16 | group :test do 17 | gem 'rspec' 18 | gem 'faker' 19 | end 20 | 21 | .bullet 22 | .description 23 | Install all dependencies, except 24 | those in specified groups 25 | :code 26 | $ bundle install --without test 27 | 28 | .bullet 29 | .description 30 | Require the gems in particular groups, 31 | noting that gems outside of a named group 32 | are in the :default group 33 | :code 34 | # lang: ruby 35 | Bundler.require(:default, :development) 36 | 37 | .bullet 38 | .description 39 | Require the default gems, plus the gems 40 | in a group named the same as the current 41 | Rails environment 42 | :code 43 | # lang: ruby 44 | Bundler.require(:default, Rails.env) 45 | 46 | .bullet 47 | .description 48 | Restrict the groups of gems that you 49 | want to add to the load path. Only gems 50 | in these groups will be require'able 51 | :code 52 | # lang: ruby 53 | require 'rubygems' 54 | require 'bundler' 55 | Bundler.setup(:default, :ci) 56 | require 'nokogiri' 57 | = link_to 'Learn More: Bundler.setup', 'bundler_setup.html' 58 | -------------------------------------------------------------------------------- /source/v1.0/groups.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Groups 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Grouping your dependencies allows you 7 | to perform operations on the entire 8 | group. 9 | :code 10 | # lang: ruby 11 | # These gems are in the :default group 12 | gem "nokogiri" 13 | gem "sinatra" 14 | 15 | gem "wirble", :group => :development 16 | 17 | group :test do 18 | gem "rspec" 19 | gem "faker" 20 | end 21 | 22 | .bullet 23 | .description 24 | Install all dependencies, except 25 | those in specified groups 26 | :code 27 | $ bundle install --without test development 28 | 29 | .bullet 30 | .description 31 | Require the gems in particular groups, 32 | noting that gems outside of a named group 33 | are in the :default group 34 | :code 35 | # lang: ruby 36 | Bundler.require(:default, :development) 37 | 38 | .bullet 39 | .description 40 | Require the default gems, plus the gems 41 | in a group named the same as the current 42 | Rails environment 43 | :code 44 | # lang: ruby 45 | Bundler.require(:default, Rails.env) 46 | 47 | .bullet 48 | .description 49 | Restrict the groups of gems that you 50 | want to add to the load path. Only gems 51 | in these groups will be require'able 52 | :code 53 | # lang: ruby 54 | require "rubygems" 55 | require "bundler" 56 | Bundler.setup(:default, :ci) 57 | require "nokogiri" 58 | = link_to("Learn More: Bundler.setup", "./bundler_setup.html") 59 | -------------------------------------------------------------------------------- /source/v1.1/groups.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Groups 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Grouping your dependencies allows you 7 | to perform operations on the entire 8 | group. 9 | :code 10 | # lang: ruby 11 | # These gems are in the :default group 12 | gem 'nokogiri' 13 | gem 'sinatra' 14 | 15 | gem 'wirble', :group => :development 16 | 17 | group :test do 18 | gem 'rspec' 19 | gem 'faker' 20 | end 21 | 22 | .bullet 23 | .description 24 | Install all dependencies, except 25 | those in specified groups 26 | :code 27 | $ bundle install --without test development 28 | 29 | .bullet 30 | .description 31 | Require the gems in particular groups, 32 | noting that gems outside of a named group 33 | are in the :default group 34 | :code 35 | # lang: ruby 36 | Bundler.require(:default, :development) 37 | 38 | .bullet 39 | .description 40 | Require the default gems, plus the gems 41 | in a group named the same as the current 42 | Rails environment 43 | :code 44 | # lang: ruby 45 | Bundler.require(:default, Rails.env) 46 | 47 | .bullet 48 | .description 49 | Restrict the groups of gems that you 50 | want to add to the load path. Only gems 51 | in these groups will be require'able 52 | :code 53 | # lang: ruby 54 | require 'rubygems' 55 | require 'bundler' 56 | Bundler.setup(:default, :ci) 57 | require 'nokogiri' 58 | = link_to 'Learn More: Bundler.setup', './bundler_setup.html' 59 | -------------------------------------------------------------------------------- /source/v0.9/rubygems.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Rubygem gemspecs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | If you already have a gem with a gemspec, you can generate a Gemfile for your gem. 7 | .how 8 | :code 9 | $ bundle init 10 | .notes 11 | If you are creating a new gem, simply create a new Gemfile. Otherwise, add the following to your new Gemfile 12 | :code 13 | # lang: ruby 14 | gemspec 15 | 16 | .bullet 17 | .description 18 | Runtime dependencies in your gemspec are treated like base dependencies, and development dependencies are added by default to the group, :development. You can change that group with the :development_group option 19 | :code 20 | # lang: ruby 21 | gemspec :development_group => :dev 22 | 23 | .bullet 24 | .description 25 | As well, you can point to a specific gemspec using :path. If your gemspec is in /gemspec/path, use 26 | :code 27 | # lang: ruby 28 | gemspec :path => '/gemspec/path' 29 | 30 | .bullet 31 | .description 32 | If you have multiple gemspecs in the same directory, specify which one you'd like to reference using :name 33 | :code 34 | # lang: ruby 35 | gemspec :name => 'my_awesome_gem' 36 | .notes 37 | This will use my_awesome_gem.gemspec 38 | 39 | .bullet 40 | .description 41 | That's it! Use bundler when developing your gem, and otherwise, use gemspecs normally! 42 | :code 43 | $ gem build my_gem.gemspec 44 | -------------------------------------------------------------------------------- /source/v1.3/whats_new.haml: -------------------------------------------------------------------------------- 1 | = partial "shared/whats_new" 2 | 3 | %h2#version13 What's New in v1.3 4 | 5 | .contents 6 | .bullet 7 | .description 8 | In this section, you'll find the major features introduced in the release. All the changes are documented in the Bundler 1.3 CHANGELOG. 9 | = link_to 'CHANGELOG', 'https://github.com/bundler/bundler/blob/1-3-stable/CHANGELOG.md' 10 | 11 | %h2#ruby-2 Compatible with Ruby 2 and RubyGems 2 12 | 13 | .contents 14 | .bullet 15 | .description 16 | Bundler 1.3 is compatible with Ruby 2.0.0 and RubyGems 2.0.0. The way of the future! 17 | 18 | %h2#rails-4 Compatible with Rails 4 19 | 20 | .contents 21 | .bullet 22 | .description 23 | Bundler 1.3 provides the binstubs command, which is used by Rails 4 to create executables that will run inside the context of your Rails app. For example, bundle binstubs rspec-core will create bin/rspec that you can run directly without needing bundle exec. 24 | 25 | %h2#resolver Install and update speed improvements 26 | 27 | .contents 28 | .bullet 29 | .description 30 | Installing a Gemfile with no lock or running bundle update used to be extremely slow in certain cases. In our testing, all of those cases now complete within a few seconds. In some cases, the install or update completes 150 times faster! 31 | 32 | 33 | %h2#signing Support for signed gems 34 | 35 | .contents 36 | .bullet 37 | .description 38 | Bundler now supports signed gems! bundle install --trust-policy takes the same arguments as gem install --trust-policy does. 39 | -------------------------------------------------------------------------------- /source/blog/2013-10-12-goodbye-bundler-14-hello-bundler-15.markdown: -------------------------------------------------------------------------------- 1 | --- 2 | title: Goodbye Bundler 1.4, Hello Bundler 1.5 3 | date: 2013/10/12 4 | draft: false 5 | author: Terence Lee 6 | author_url: https://hone.heroku.com 7 | category: release 8 | --- 9 | 10 | People [have been asking](#) why we jumped from a 1.4 release candidate to a 1.5 one without ever releasing Bundler 1.4.0. The Bundler core team takes releases very seriously and tries to be an example of thoughtful release practices to the Ruby community. Since we follow [standard releases candidate](#) policies, release candidates are automatically under a feature freeze. Each release candidate gets roughly two weeks of testing, and any significant bugfixes result in a new release candidate and the timer starting over. The exact code from the first release candidate with no significant bugs will be the code released as the final version. 11 | 12 | When we released [Bundler 1.4.0.rc.1](#) it was missing some important features that we wanted to include. While we could have released 1.4 immediately and started testing 1.5, the 1.4 RC had significant bugs as well. While discussing our options, it became clear that the best way to improve Bundler for all users was to drop the 1.4 release and cut a new 1.5.0 release candidate that included all the features in 1.4.0 and the features we had intended to release in 1.4 originally but missed in the RC. Even though there isn't a 1.4.0, we're excited to bring an even faster Bundler to the community with parallel installs. Please help us test 1.5.0! We've compiled a list of changes in the [what's new section](#) on [Bundler documentation website](#). 13 | 14 | Special thanks to [Jacob Kaplan Moss](#) and [Daniel Farina](#) for advising me on this course of action and bringing their sane Python practices with them. 15 | -------------------------------------------------------------------------------- /source/v1.9/whats_new.haml: -------------------------------------------------------------------------------- 1 | = partial "shared/whats_new" 2 | 3 | %h2#version19 What's New in v1.9 4 | 5 | .contents 6 | .bullet 7 | .description 8 | %p 9 | Bundler 1.9 comes with a new dependency resolver, called Molinillo, 10 | among other changes. 11 | %p 12 | In this section, you’ll find the major features introduced in this release. All the changes are documented in the Bundler 1.9 changelog. 13 | = link_to 'Full 1.9 changelog', 'https://github.com/bundler/bundler/blob/1-9-stable/CHANGELOG.md' 14 | 15 | 16 | %h2#molinillo Using Molinillo for Dependency Resolution 17 | 18 | .contents 19 | .bullet 20 | .description 21 | %p 22 | Bundler's dependency resolver is now powered by Molinillo, the CocoaPods 23 | dependency resolution algorithm sponsored by Stripe that is fully 24 | documented, tested, and built for use across different dependency 25 | managers built in Ruby. 26 | = link_to 'Molinillo', 'https://github.com/CocoaPods/Molinillo' 27 | 28 | %h2#path-gemspec-detection Improved gemspec detection 29 | 30 | .contents 31 | .bullet 32 | .description 33 | %p 34 | Directories are now searched resursively for gemspecs, with specs found 35 | closer to the root being preferred. 36 | 37 | %h2#other-changes Other changes 38 | 39 | .contents 40 | .bullet 41 | .description 42 | Bundler 1.9 also includes: 43 | %ul 44 | %li improved vendoring of thor that will make conflicts less common 45 | %li fixed gemspecs generated by bundle gem from a pre-release bundler version 46 | %li bundle which will no longer be confused by directories 47 | = link_to 'Full 1.9 changelog', 'https://github.com/bundler/bundler/blob/1-9-stable/CHANGELOG.md' 48 | -------------------------------------------------------------------------------- /source/v1.7/rubygems.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Rubygem gemspecs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | If you're creating a gem from scratch, you can use bundler's built in gem skeleton to create a base gem for you to edit. 7 | .how 8 | :code 9 | $ bundle gem my_gem 10 | .notes 11 | This will create a new directory named my_gem with your new gem skeleton. 12 | 13 | .bullet 14 | .description 15 | If you already have a gem with a gemspec, you can generate a Gemfile for your gem. 16 | :code 17 | $ bundle init 18 | .notes 19 | Then, add the following to your new Gemfile 20 | :code 21 | # lang: ruby 22 | gemspec 23 | 24 | .bullet 25 | .description 26 | Runtime dependencies in your gemspec are treated like base dependencies, and development dependencies are added by default to the group, :development. You can change that group with the :development_group option 27 | :code 28 | # lang: ruby 29 | gemspec :development_group => :dev 30 | 31 | .bullet 32 | .description 33 | As well, you can point to a specific gemspec using :path. If your gemspec is in /gemspec/path, use 34 | :code 35 | # lang: ruby 36 | gemspec :path => '/gemspec/path' 37 | 38 | .bullet 39 | .description 40 | If you have multiple gemspecs in the same directory, specify which one you'd like to reference using :name 41 | :code 42 | # lang: ruby 43 | gemspec :name => 'my_awesome_gem' 44 | .notes 45 | This will use my_awesome_gem.gemspec 46 | 47 | .bullet 48 | .description 49 | That's it! Use bundler when developing your gem, and otherwise, use gemspecs normally! 50 | :code 51 | $ gem build my_gem.gemspec 52 | -------------------------------------------------------------------------------- /source/v1.8/rubygems.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Rubygem gemspecs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | If you're creating a gem from scratch, you can use bundler's built in gem skeleton to create a base gem for you to edit. 7 | .how 8 | :code 9 | $ bundle gem my_gem 10 | .notes 11 | This will create a new directory named my_gem with your new gem skeleton. 12 | 13 | .bullet 14 | .description 15 | If you already have a gem with a gemspec, you can generate a Gemfile for your gem. 16 | :code 17 | $ bundle init 18 | .notes 19 | Then, add the following to your new Gemfile 20 | :code 21 | # lang: ruby 22 | gemspec 23 | 24 | .bullet 25 | .description 26 | Runtime dependencies in your gemspec are treated like base dependencies, and development dependencies are added by default to the group, :development. You can change that group with the :development_group option 27 | :code 28 | # lang: ruby 29 | gemspec :development_group => :dev 30 | 31 | .bullet 32 | .description 33 | As well, you can point to a specific gemspec using :path. If your gemspec is in /gemspec/path, use 34 | :code 35 | # lang: ruby 36 | gemspec :path => '/gemspec/path' 37 | 38 | .bullet 39 | .description 40 | If you have multiple gemspecs in the same directory, specify which one you'd like to reference using :name 41 | :code 42 | # lang: ruby 43 | gemspec :name => 'my_awesome_gem' 44 | .notes 45 | This will use my_awesome_gem.gemspec 46 | 47 | .bullet 48 | .description 49 | That's it! Use bundler when developing your gem, and otherwise, use gemspecs normally! 50 | :code 51 | $ gem build my_gem.gemspec 52 | -------------------------------------------------------------------------------- /source/v1.9/rubygems.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Rubygem gemspecs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | If you're creating a gem from scratch, you can use bundler's built in gem skeleton to create a base gem for you to edit. 7 | .how 8 | :code 9 | $ bundle gem my_gem 10 | .notes 11 | This will create a new directory named my_gem with your new gem skeleton. 12 | 13 | .bullet 14 | .description 15 | If you already have a gem with a gemspec, you can generate a Gemfile for your gem. 16 | :code 17 | $ bundle init 18 | .notes 19 | Then, add the following to your new Gemfile 20 | :code 21 | # lang: ruby 22 | gemspec 23 | 24 | .bullet 25 | .description 26 | Runtime dependencies in your gemspec are treated like base dependencies, and development dependencies are added by default to the group, :development. You can change that group with the :development_group option 27 | :code 28 | # lang: ruby 29 | gemspec :development_group => :dev 30 | 31 | .bullet 32 | .description 33 | As well, you can point to a specific gemspec using :path. If your gemspec is in /gemspec/path, use 34 | :code 35 | # lang: ruby 36 | gemspec :path => '/gemspec/path' 37 | 38 | .bullet 39 | .description 40 | If you have multiple gemspecs in the same directory, specify which one you'd like to reference using :name 41 | :code 42 | # lang: ruby 43 | gemspec :name => 'my_awesome_gem' 44 | .notes 45 | This will use my_awesome_gem.gemspec 46 | 47 | .bullet 48 | .description 49 | That's it! Use bundler when developing your gem, and otherwise, use gemspecs normally! 50 | :code 51 | $ gem build my_gem.gemspec 52 | -------------------------------------------------------------------------------- /source/v1.2/groups.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Groups 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Grouping your dependencies allows you 7 | to perform operations on the entire 8 | group. 9 | :code 10 | # lang: ruby 11 | # These gems are in the :default group 12 | gem 'nokogiri' 13 | gem 'sinatra' 14 | 15 | gem 'wirble', :group => :development 16 | 17 | group :test do 18 | gem 'faker' 19 | gem 'rspec' 20 | end 21 | 22 | group :test, :development do 23 | gem 'capybara' 24 | gem 'rspec-rails' 25 | end 26 | 27 | gem 'cucumber', :group => [:cucumber, :test] 28 | 29 | .bullet 30 | .description 31 | Install all gems, except those in the 32 | listed groups. Gems in at least one 33 | non-excluded group will still be installed. 34 | :code 35 | $ bundle install --without test development 36 | 37 | .bullet 38 | .description 39 | Require the gems in particular groups, 40 | noting that gems outside of a named group 41 | are in the :default group 42 | :code 43 | # lang: ruby 44 | Bundler.require(:default, :development) 45 | 46 | .bullet 47 | .description 48 | Require the default gems, plus the gems 49 | in a group named the same as the current 50 | Rails environment 51 | :code 52 | # lang: ruby 53 | Bundler.require(:default, Rails.env) 54 | 55 | .bullet 56 | .description 57 | Restrict the groups of gems that you 58 | want to add to the load path. Only gems 59 | in these groups will be require'able 60 | :code 61 | # lang: ruby 62 | require 'rubygems' 63 | require 'bundler' 64 | Bundler.setup(:default, :ci) 65 | require 'nokogiri' 66 | = link_to 'Learn More: Bundler.setup', './bundler_setup.html' 67 | -------------------------------------------------------------------------------- /source/v1.0/rubygems.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Rubygem gemspecs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | If you're creating a gem from scratch, you can use bundler's built in gem skeleton to create a base gem for you to edit. 7 | .how 8 | :code 9 | $ bundle gem my_gem 10 | .notes 11 | This will create a new directory named my_gem with your new gem skeleton. 12 | 13 | .bullet 14 | .description 15 | If you already have a gem with a gemspec, you can generate a Gemfile for your gem. 16 | :code 17 | $ bundle init 18 | .notes 19 | Then, add the following to your new Gemfile 20 | :code 21 | # lang: ruby 22 | gemspec 23 | 24 | .bullet 25 | .description 26 | Runtime dependencies in your gemspec are treated like base dependencies, and development dependencies are added by default to the group, :development. You can change that group with the :development_group option 27 | :code 28 | # lang: ruby 29 | gemspec :development_group => :dev 30 | 31 | .bullet 32 | .description 33 | As well, you can point to a specific gemspec using :path. If your gemspec is in /gemspec/path, use 34 | :code 35 | # lang: ruby 36 | gemspec :path => '/gemspec/path' 37 | 38 | .bullet 39 | .description 40 | If you have multiple gemspecs in the same directory, specify which one you'd like to reference using :name 41 | :code 42 | # lang: ruby 43 | gemspec :name => 'my_awesome_gem' 44 | .notes 45 | This will use my_awesome_gem.gemspec 46 | 47 | .bullet 48 | .description 49 | That's it! Use bundler when developing your gem, and otherwise, use gemspecs normally! 50 | :code 51 | $ gem build my_gem.gemspec 52 | -------------------------------------------------------------------------------- /source/v1.1/rubygems.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Rubygem gemspecs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | If you're creating a gem from scratch, you can use bundler's built in gem skeleton to create a base gem for you to edit. 7 | .how 8 | :code 9 | $ bundle gem my_gem 10 | .notes 11 | This will create a new directory named my_gem with your new gem skeleton. 12 | 13 | .bullet 14 | .description 15 | If you already have a gem with a gemspec, you can generate a Gemfile for your gem. 16 | :code 17 | $ bundle init 18 | .notes 19 | Then, add the following to your new Gemfile 20 | :code 21 | # lang: ruby 22 | gemspec 23 | 24 | .bullet 25 | .description 26 | Runtime dependencies in your gemspec are treated like base dependencies, and development dependencies are added by default to the group, :development. You can change that group with the :development_group option 27 | :code 28 | # lang: ruby 29 | gemspec :development_group => :dev 30 | 31 | .bullet 32 | .description 33 | As well, you can point to a specific gemspec using :path. If your gemspec is in /gemspec/path, use 34 | :code 35 | # lang: ruby 36 | gemspec :path => '/gemspec/path' 37 | 38 | .bullet 39 | .description 40 | If you have multiple gemspecs in the same directory, specify which one you'd like to reference using :name 41 | :code 42 | # lang: ruby 43 | gemspec :name => 'my_awesome_gem' 44 | .notes 45 | This will use my_awesome_gem.gemspec 46 | 47 | .bullet 48 | .description 49 | That's it! Use bundler when developing your gem, and otherwise, use gemspecs normally! 50 | :code 51 | $ gem build my_gem.gemspec 52 | -------------------------------------------------------------------------------- /source/v1.2/rubygems.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Rubygem gemspecs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | If you're creating a gem from scratch, you can use bundler's built in gem skeleton to create a base gem for you to edit. 7 | .how 8 | :code 9 | $ bundle gem my_gem 10 | .notes 11 | This will create a new directory named my_gem with your new gem skeleton. 12 | 13 | .bullet 14 | .description 15 | If you already have a gem with a gemspec, you can generate a Gemfile for your gem. 16 | :code 17 | $ bundle init 18 | .notes 19 | Then, add the following to your new Gemfile 20 | :code 21 | # lang: ruby 22 | gemspec 23 | 24 | .bullet 25 | .description 26 | Runtime dependencies in your gemspec are treated like base dependencies, and development dependencies are added by default to the group, :development. You can change that group with the :development_group option 27 | :code 28 | # lang: ruby 29 | gemspec :development_group => :dev 30 | 31 | .bullet 32 | .description 33 | As well, you can point to a specific gemspec using :path. If your gemspec is in /gemspec/path, use 34 | :code 35 | # lang: ruby 36 | gemspec :path => '/gemspec/path' 37 | 38 | .bullet 39 | .description 40 | If you have multiple gemspecs in the same directory, specify which one you'd like to reference using :name 41 | :code 42 | # lang: ruby 43 | gemspec :name => 'my_awesome_gem' 44 | .notes 45 | This will use my_awesome_gem.gemspec 46 | 47 | .bullet 48 | .description 49 | That's it! Use bundler when developing your gem, and otherwise, use gemspecs normally! 50 | :code 51 | $ gem build my_gem.gemspec 52 | -------------------------------------------------------------------------------- /source/v1.3/rubygems.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Rubygem gemspecs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | If you're creating a gem from scratch, you can use bundler's built in gem skeleton to create a base gem for you to edit. 7 | .how 8 | :code 9 | $ bundle gem my_gem 10 | .notes 11 | This will create a new directory named my_gem with your new gem skeleton. 12 | 13 | .bullet 14 | .description 15 | If you already have a gem with a gemspec, you can generate a Gemfile for your gem. 16 | :code 17 | $ bundle init 18 | .notes 19 | Then, add the following to your new Gemfile 20 | :code 21 | # lang: ruby 22 | gemspec 23 | 24 | .bullet 25 | .description 26 | Runtime dependencies in your gemspec are treated like base dependencies, and development dependencies are added by default to the group, :development. You can change that group with the :development_group option 27 | :code 28 | # lang: ruby 29 | gemspec :development_group => :dev 30 | 31 | .bullet 32 | .description 33 | As well, you can point to a specific gemspec using :path. If your gemspec is in /gemspec/path, use 34 | :code 35 | # lang: ruby 36 | gemspec :path => '/gemspec/path' 37 | 38 | .bullet 39 | .description 40 | If you have multiple gemspecs in the same directory, specify which one you'd like to reference using :name 41 | :code 42 | # lang: ruby 43 | gemspec :name => 'my_awesome_gem' 44 | .notes 45 | This will use my_awesome_gem.gemspec 46 | 47 | .bullet 48 | .description 49 | That's it! Use bundler when developing your gem, and otherwise, use gemspecs normally! 50 | :code 51 | $ gem build my_gem.gemspec 52 | -------------------------------------------------------------------------------- /source/v1.5/rubygems.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Rubygem gemspecs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | If you're creating a gem from scratch, you can use bundler's built in gem skeleton to create a base gem for you to edit. 7 | .how 8 | :code 9 | $ bundle gem my_gem 10 | .notes 11 | This will create a new directory named my_gem with your new gem skeleton. 12 | 13 | .bullet 14 | .description 15 | If you already have a gem with a gemspec, you can generate a Gemfile for your gem. 16 | :code 17 | $ bundle init 18 | .notes 19 | Then, add the following to your new Gemfile 20 | :code 21 | # lang: ruby 22 | gemspec 23 | 24 | .bullet 25 | .description 26 | Runtime dependencies in your gemspec are treated like base dependencies, and development dependencies are added by default to the group, :development. You can change that group with the :development_group option 27 | :code 28 | # lang: ruby 29 | gemspec :development_group => :dev 30 | 31 | .bullet 32 | .description 33 | As well, you can point to a specific gemspec using :path. If your gemspec is in /gemspec/path, use 34 | :code 35 | # lang: ruby 36 | gemspec :path => '/gemspec/path' 37 | 38 | .bullet 39 | .description 40 | If you have multiple gemspecs in the same directory, specify which one you'd like to reference using :name 41 | :code 42 | # lang: ruby 43 | gemspec :name => 'my_awesome_gem' 44 | .notes 45 | This will use my_awesome_gem.gemspec 46 | 47 | .bullet 48 | .description 49 | That's it! Use bundler when developing your gem, and otherwise, use gemspecs normally! 50 | :code 51 | $ gem build my_gem.gemspec 52 | -------------------------------------------------------------------------------- /source/v1.6/rubygems.haml: -------------------------------------------------------------------------------- 1 | %h2 Using Bundler with Rubygem gemspecs 2 | 3 | .contents 4 | .bullet 5 | .description 6 | If you're creating a gem from scratch, you can use bundler's built in gem skeleton to create a base gem for you to edit. 7 | .how 8 | :code 9 | $ bundle gem my_gem 10 | .notes 11 | This will create a new directory named my_gem with your new gem skeleton. 12 | 13 | .bullet 14 | .description 15 | If you already have a gem with a gemspec, you can generate a Gemfile for your gem. 16 | :code 17 | $ bundle init 18 | .notes 19 | Then, add the following to your new Gemfile 20 | :code 21 | # lang: ruby 22 | gemspec 23 | 24 | .bullet 25 | .description 26 | Runtime dependencies in your gemspec are treated like base dependencies, and development dependencies are added by default to the group, :development. You can change that group with the :development_group option 27 | :code 28 | # lang: ruby 29 | gemspec :development_group => :dev 30 | 31 | .bullet 32 | .description 33 | As well, you can point to a specific gemspec using :path. If your gemspec is in /gemspec/path, use 34 | :code 35 | # lang: ruby 36 | gemspec :path => '/gemspec/path' 37 | 38 | .bullet 39 | .description 40 | If you have multiple gemspecs in the same directory, specify which one you'd like to reference using :name 41 | :code 42 | # lang: ruby 43 | gemspec :name => 'my_awesome_gem' 44 | .notes 45 | This will use my_awesome_gem.gemspec 46 | 47 | .bullet 48 | .description 49 | That's it! Use bundler when developing your gem, and otherwise, use gemspecs normally! 50 | :code 51 | $ gem build my_gem.gemspec 52 | -------------------------------------------------------------------------------- /source/v1.1/rails3.haml: -------------------------------------------------------------------------------- 1 | #intro 2 | Rails 3 comes with baked in support with bundler. 3 | 4 | %h2 Using Bundler with Rails 3 5 | 6 | .contents 7 | .bullet 8 | .description 9 | Install Rails as you normally would. Use sudo if you would normally use 10 | sudo to install gems. 11 | .how 12 | :code 13 | $ gem install rails 14 | .notes 15 | We recommend using rvm for dependable Ruby installations, especially if 16 | you are switching between different versions of Ruby 17 | 18 | .bullet 19 | .description 20 | Generate a Rails app as usual 21 | :code 22 | $ rails new myapp 23 | $ cd myapp 24 | 25 | .bullet 26 | .description 27 | Run the server. Bundler is transparently managing your dependencies! 28 | :code 29 | $ rails server 30 | 31 | .bullet 32 | .description 33 | Add new dependencies to your Gemfile as you need them. 34 | :code 35 | # lang: ruby 36 | gem 'nokogiri' 37 | gem 'geokit' 38 | 39 | .bullet 40 | .description 41 | If you want a dependency to be loaded only in a certain Rails environment, 42 | place it in a group named after that Rails environment 43 | :code 44 | # lang: ruby 45 | group :test do 46 | gem 'rspec' 47 | gem 'faker' 48 | end 49 | 50 | .bullet#shared_with_23 51 | .description 52 | You can place a dependency in multiple groups at once as well 53 | :code 54 | # lang: ruby 55 | group :development, :test do 56 | gem 'wirble' 57 | gem 'ruby-debug' 58 | end 59 | = link_to 'Learn More: Groups', './groups.html' 60 | 61 | .bullet 62 | .description 63 | After adding a dependency, if it is not yet installed, install it 64 | .how 65 | :code 66 | $ bundle install 67 | .notes 68 | This will update all dependencies in your Gemfile to the latest versions 69 | that do not conflict with other dependencies 70 | -------------------------------------------------------------------------------- /source/compatibility.haml: -------------------------------------------------------------------------------- 1 | %h2 Bundler compatibility with Ruby 2 | 3 | .contents 4 | 5 | .bullet 6 | .description 7 | Ruby 2.0 8 | .notes 9 | Requires Bundler 1.3 or greater. 10 | 11 | .bullet 12 | .description 13 | Ruby 1.9 14 | .notes 15 | Requires Bundler 1.0.10 or greater. Ruby 1.9.1 is not supported. 16 | 17 | .bullet 18 | .description 19 | Bundler 1.0 requires a minimum Ruby version of 1.8.7. 20 | 21 | 22 | %h2 Bundler compatibility with RubyGems 23 | 24 | .contents 25 | 26 | .bullet 27 | .description 28 | RubyGems 2.2 29 | .notes 30 | %p Requires at least Bundler 1.3.0. 31 | %p Installing gems with C extensions using sudo requires Bundler 1.6.1 or higher. 32 | 33 | .bullet 34 | .description 35 | RubyGems 2.0 36 | .notes 37 | %p Requires at least Bundler version 1.3.0. 38 | %p Users of RubyGems 2.0.2 and Bundler 1.3.0-1.3.3 may encounter exceptions while running install or update, and should upgrade either Bundler or RubyGems to a newer version. 39 | 40 | .bullet 41 | .description 42 | RubyGems 1.8 43 | .notes 44 | %p Requires Bundler version 1.0.14. 45 | %p 46 | Users with RubyGems 1.8.0-1.8.2 may encounter exceptions running rake. 47 | They should use bundle exec rake instead. 48 | 49 | .bullet 50 | .description 51 | RubyGems 1.6 and 1.7 52 | .notes 53 | Requires Bundler version 1.0.11. 54 | 55 | .bullet 56 | .description 57 | RubyGems 1.5 58 | .notes 59 | Requires Bundler version 1.0.10. 60 | 61 | .bullet 62 | .description 63 | RubyGems 1.3 and 1.4. 64 | .notes 65 | %p Requires Bundler version 1.0. 66 | %p On RubyGems 1.3, Bundler may be unable to find prerelease gems cached via the bundle pack command. 67 | 68 | .bullet 69 | .description 70 | Bundler 1.0 requires a minimum RubyGems version of 1.3.6. 71 | -------------------------------------------------------------------------------- /source/v1.2/gemfile_ruby.haml: -------------------------------------------------------------------------------- 1 | %h2 Specifying a Ruby Version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Like gems, developers can setup a dependency on Ruby. This makes your app fail faster in case you depend on specific features in a Ruby VM. This way, the Ruby VM on your deployment server will match your local one. You can do this by using the ruby directive in the Gemfile: 7 | :code 8 | # lang: ruby 9 | ruby 'RUBY_VERSION', :engine => 'ENGINE', :engine_version => 'ENGINE_VERSION' 10 | 11 | .bullet 12 | .description 13 | If you wanted to use JRuby 1.6.7 using Ruby 1.9.3, you would simply do the following: 14 | :code 15 | # lang: ruby 16 | ruby '1.9.3', :engine => 'jruby', :engine_version => '1.6.7" 17 | 18 | .bullet 19 | .description 20 | Bundler will make checks against the current running Ruby VM to make sure it matches what is specified in the Gemfile. If things don't match, Bundler will raise an Exception explaining what doesn't match. 21 | :code 22 | Your Ruby version is 1.8.7, but your Gemfile specified 1.9.3 23 | 24 | .bullet 25 | .description 26 | Both :engine and :engine_version are optional. When these options are omitted, this means the app is compatible with a particular Ruby ABI but the engine is irrelevant. When :engine is used, :engine_version must also be specified. 27 | .bullet 28 | .description 29 | Using the platform command with the --ruby flag, you can see what ruby directive is specified in the Gemfile. 30 | :code 31 | ruby 1.9.3 (jruby 1.6.7) 32 | = link_to 'Learn More: bundle platform', './bundle_platform.html' 33 | 34 | .bullet 35 | .description 36 | The ruby directive explicitly leaves out the ability to specify a patch level. Ruby patches often include important bug and security fixes and are extremely compatible. 37 | -------------------------------------------------------------------------------- /source/v1.3/gemfile_ruby.haml: -------------------------------------------------------------------------------- 1 | %h2 Specifying a Ruby Version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Like gems, developers can setup a dependency on Ruby. This makes your app fail faster in case you depend on specific features in a Ruby VM. This way, the Ruby VM on your deployment server will match your local one. You can do this by using the ruby directive in the Gemfile: 7 | :code 8 | # lang: ruby 9 | ruby 'RUBY_VERSION', :engine => 'ENGINE', :engine_version => 'ENGINE_VERSION' 10 | 11 | .bullet 12 | .description 13 | If you wanted to use JRuby 1.6.7 using Ruby 1.9.3, you would simply do the following: 14 | :code 15 | # lang: ruby 16 | ruby '1.9.3', :engine => 'jruby', :engine_version => '1.6.7' 17 | 18 | .bullet 19 | .description 20 | Bundler will make checks against the current running Ruby VM to make sure it matches what is specified in the Gemfile. If things don't match, Bundler will raise an Exception explaining what doesn't match. 21 | :code 22 | Your Ruby version is 1.8.7, but your Gemfile specified 1.9.3 23 | 24 | .bullet 25 | .description 26 | Both :engine and :engine_version are optional. When these options are omitted, this means the app is compatible with a particular Ruby ABI but the engine is irrelevant. When :engine is used, :engine_version must also be specified. 27 | .bullet 28 | .description 29 | Using the platform command with the --ruby flag, you can see what ruby directive is specified in the Gemfile. 30 | :code 31 | ruby 1.9.3 (jruby 1.6.7) 32 | = link_to 'Learn More: bundle platform', './bundle_platform.html' 33 | 34 | .bullet 35 | .description 36 | The ruby directive explicitly leaves out the ability to specify a patch level. Ruby patches often include important bug and security fixes and are extremely compatible. 37 | -------------------------------------------------------------------------------- /source/v1.0/rails3.haml: -------------------------------------------------------------------------------- 1 | #intro 2 | Rails 3 comes with baked in support with bundler. 3 | 4 | %h2 Using Bundler with Rails 3 5 | 6 | .contents 7 | .bullet 8 | .description 9 | Install Rails as you normally would. Use sudo 10 | if you would normally use sudo to install gems. 11 | .how 12 | :code 13 | $ gem install rails 14 | .notes 15 | We recommend using rvm for dependable Ruby 16 | installations, especially if you are switching 17 | between different versions of Ruby 18 | 19 | .bullet 20 | .description 21 | Generate a Rails app as usual 22 | :code 23 | $ rails new myapp 24 | $ cd myapp 25 | 26 | .bullet 27 | .description 28 | Run the server. Bundler is transparently managing 29 | your dependencies! 30 | :code 31 | $ rails server 32 | 33 | .bullet 34 | .description 35 | Add new dependencies to your Gemfile as you 36 | need them. 37 | :code 38 | # lang: ruby 39 | gem "nokogiri" 40 | gem "geokit" 41 | 42 | .bullet 43 | .description 44 | If you want a dependency to be loaded only in 45 | a certain Rails environment, place it in a group 46 | named after that Rails environment 47 | :code 48 | # lang: ruby 49 | group :test do 50 | gem "rspec" 51 | gem "faker" 52 | end 53 | 54 | .bullet#shared_with_23 55 | .description 56 | You can place a dependency in multiple groups 57 | at once as well 58 | :code 59 | # lang: ruby 60 | group :development, :test do 61 | gem "wirble" 62 | gem "ruby-debug" 63 | end 64 | =link_to("Learn More: Groups", "./groups.html") 65 | 66 | .bullet 67 | .description 68 | After adding a dependency, if it is not yet 69 | installed, install it 70 | .how 71 | :code 72 | $ bundle install 73 | .notes 74 | This will update all dependencies in your 75 | Gemfile to the latest versions that do not 76 | conflict with other dependencies 77 | -------------------------------------------------------------------------------- /source/v1.2/rails3.haml: -------------------------------------------------------------------------------- 1 | #intro 2 | Rails 3 comes with baked in support with bundler. 3 | 4 | %h2 Using Bundler with Rails 3 5 | 6 | .contents 7 | .bullet 8 | .description 9 | Install Rails as you normally would. Use sudo 10 | if you would normally use sudo to install gems. 11 | .how 12 | :code 13 | $ gem install rails 14 | .notes 15 | We recommend using rvm for dependable Ruby 16 | installations, especially if you are switching 17 | between different versions of Ruby 18 | 19 | .bullet 20 | .description 21 | Generate a Rails app as usual 22 | :code 23 | $ rails new myapp 24 | $ cd myapp 25 | 26 | .bullet 27 | .description 28 | Run the server. Bundler is transparently managing 29 | your dependencies! 30 | :code 31 | $ rails server 32 | 33 | .bullet 34 | .description 35 | Add new dependencies to your Gemfile as you 36 | need them. 37 | :code 38 | # lang: ruby 39 | gem 'nokogiri' 40 | gem 'geokit' 41 | 42 | .bullet 43 | .description 44 | If you want a dependency to be loaded only in 45 | a certain Rails environment, place it in a group 46 | named after that Rails environment 47 | :code 48 | # lang: ruby 49 | group :test do 50 | gem 'rspec' 51 | gem 'faker' 52 | end 53 | 54 | .bullet#shared_with_23 55 | .description 56 | You can place a dependency in multiple groups 57 | at once as well 58 | :code 59 | # lang: ruby 60 | group :development, :test do 61 | gem 'wirble' 62 | gem 'ruby-debug' 63 | end 64 | = link_to 'Learn More: Groups', './groups.html' 65 | 66 | .bullet 67 | .description 68 | After adding a dependency, if it is not yet 69 | installed, install it 70 | .how 71 | :code 72 | $ bundle install 73 | .notes 74 | This will update all dependencies in your 75 | Gemfile to the latest versions that do not 76 | conflict with other dependencies 77 | -------------------------------------------------------------------------------- /source/v1.3/rails3.haml: -------------------------------------------------------------------------------- 1 | #intro 2 | Rails 3 comes with baked in support with bundler. 3 | 4 | %h2 Using Bundler with Rails 3 5 | 6 | .contents 7 | .bullet 8 | .description 9 | Install Rails as you normally would. Use sudo 10 | if you would normally use sudo to install gems. 11 | .how 12 | :code 13 | $ gem install rails 14 | .notes 15 | We recommend using rvm for dependable Ruby 16 | installations, especially if you are switching 17 | between different versions of Ruby 18 | 19 | .bullet 20 | .description 21 | Generate a Rails app as usual 22 | :code 23 | $ rails new myapp 24 | $ cd myapp 25 | 26 | .bullet 27 | .description 28 | Run the server. Bundler is transparently managing 29 | your dependencies! 30 | :code 31 | $ rails server 32 | 33 | .bullet 34 | .description 35 | Add new dependencies to your Gemfile as you 36 | need them. 37 | :code 38 | # lang: ruby 39 | gem 'nokogiri' 40 | gem 'geokit' 41 | 42 | .bullet 43 | .description 44 | If you want a dependency to be loaded only in 45 | a certain Rails environment, place it in a group 46 | named after that Rails environment 47 | :code 48 | # lang: ruby 49 | group :test do 50 | gem 'rspec' 51 | gem 'faker' 52 | end 53 | 54 | .bullet#shared_with_23 55 | .description 56 | You can place a dependency in multiple groups 57 | at once as well 58 | :code 59 | # lang: ruby 60 | group :development, :test do 61 | gem 'wirble' 62 | gem 'ruby-debug' 63 | end 64 | = link_to 'Learn More: Groups', './groups.html' 65 | 66 | .bullet 67 | .description 68 | After adding a dependency, if it is not yet 69 | installed, install it 70 | .how 71 | :code 72 | $ bundle install 73 | .notes 74 | This will update all dependencies in your 75 | Gemfile to the latest versions that do not 76 | conflict with other dependencies 77 | -------------------------------------------------------------------------------- /source/v1.5/rails3.haml: -------------------------------------------------------------------------------- 1 | #intro 2 | Rails 3 comes with baked in support with bundler. 3 | 4 | %h2 Using Bundler with Rails 3 5 | 6 | .contents 7 | .bullet 8 | .description 9 | Install Rails as you normally would. Use sudo 10 | if you would normally use sudo to install gems. 11 | .how 12 | :code 13 | $ gem install rails 14 | .notes 15 | We recommend using rvm for dependable Ruby 16 | installations, especially if you are switching 17 | between different versions of Ruby 18 | 19 | .bullet 20 | .description 21 | Generate a Rails app as usual 22 | :code 23 | $ rails new myapp 24 | $ cd myapp 25 | 26 | .bullet 27 | .description 28 | Run the server. Bundler is transparently managing 29 | your dependencies! 30 | :code 31 | $ rails server 32 | 33 | .bullet 34 | .description 35 | Add new dependencies to your Gemfile as you 36 | need them. 37 | :code 38 | # lang: ruby 39 | gem 'nokogiri' 40 | gem 'geokit' 41 | 42 | .bullet 43 | .description 44 | If you want a dependency to be loaded only in 45 | a certain Rails environment, place it in a group 46 | named after that Rails environment 47 | :code 48 | # lang: ruby 49 | group :test do 50 | gem 'rspec' 51 | gem 'faker' 52 | end 53 | 54 | .bullet#shared_with_23 55 | .description 56 | You can place a dependency in multiple groups 57 | at once as well 58 | :code 59 | # lang: ruby 60 | group :development, :test do 61 | gem 'wirble' 62 | gem 'ruby-debug' 63 | end 64 | = link_to 'Learn More: Groups', './groups.html' 65 | 66 | .bullet 67 | .description 68 | After adding a dependency, if it is not yet 69 | installed, install it 70 | .how 71 | :code 72 | $ bundle install 73 | .notes 74 | This will update all dependencies in your 75 | Gemfile to the latest versions that do not 76 | conflict with other dependencies 77 | -------------------------------------------------------------------------------- /source/v1.6/rails3.haml: -------------------------------------------------------------------------------- 1 | #intro 2 | Rails 3 comes with baked in support with bundler. 3 | 4 | %h2 Using Bundler with Rails 3 5 | 6 | .contents 7 | .bullet 8 | .description 9 | Install Rails as you normally would. Use sudo 10 | if you would normally use sudo to install gems. 11 | .how 12 | :code 13 | $ gem install rails 14 | .notes 15 | We recommend using rvm for dependable Ruby 16 | installations, especially if you are switching 17 | between different versions of Ruby 18 | 19 | .bullet 20 | .description 21 | Generate a Rails app as usual 22 | :code 23 | $ rails new myapp 24 | $ cd myapp 25 | 26 | .bullet 27 | .description 28 | Run the server. Bundler is transparently managing 29 | your dependencies! 30 | :code 31 | $ rails server 32 | 33 | .bullet 34 | .description 35 | Add new dependencies to your Gemfile as you 36 | need them. 37 | :code 38 | # lang: ruby 39 | gem 'nokogiri' 40 | gem 'geokit' 41 | 42 | .bullet 43 | .description 44 | If you want a dependency to be loaded only in 45 | a certain Rails environment, place it in a group 46 | named after that Rails environment 47 | :code 48 | # lang: ruby 49 | group :test do 50 | gem 'rspec' 51 | gem 'faker' 52 | end 53 | 54 | .bullet#shared_with_23 55 | .description 56 | You can place a dependency in multiple groups 57 | at once as well 58 | :code 59 | # lang: ruby 60 | group :development, :test do 61 | gem 'wirble' 62 | gem 'ruby-debug' 63 | end 64 | = link_to 'Learn More: Groups', './groups.html' 65 | 66 | .bullet 67 | .description 68 | After adding a dependency, if it is not yet 69 | installed, install it 70 | .how 71 | :code 72 | $ bundle install 73 | .notes 74 | This will update all dependencies in your 75 | Gemfile to the latest versions that do not 76 | conflict with other dependencies 77 | -------------------------------------------------------------------------------- /source/v1.7/rails3.haml: -------------------------------------------------------------------------------- 1 | #intro 2 | Rails 3 comes with baked in support with bundler. 3 | 4 | %h2 Using Bundler with Rails 3 5 | 6 | .contents 7 | .bullet 8 | .description 9 | Install Rails as you normally would. Use sudo 10 | if you would normally use sudo to install gems. 11 | .how 12 | :code 13 | $ gem install rails 14 | .notes 15 | We recommend using rvm for dependable Ruby 16 | installations, especially if you are switching 17 | between different versions of Ruby 18 | 19 | .bullet 20 | .description 21 | Generate a Rails app as usual 22 | :code 23 | $ rails new myapp 24 | $ cd myapp 25 | 26 | .bullet 27 | .description 28 | Run the server. Bundler is transparently managing 29 | your dependencies! 30 | :code 31 | $ rails server 32 | 33 | .bullet 34 | .description 35 | Add new dependencies to your Gemfile as you 36 | need them. 37 | :code 38 | # lang: ruby 39 | gem 'nokogiri' 40 | gem 'geokit' 41 | 42 | .bullet 43 | .description 44 | If you want a dependency to be loaded only in 45 | a certain Rails environment, place it in a group 46 | named after that Rails environment 47 | :code 48 | # lang: ruby 49 | group :test do 50 | gem 'rspec' 51 | gem 'faker' 52 | end 53 | 54 | .bullet#shared_with_23 55 | .description 56 | You can place a dependency in multiple groups 57 | at once as well 58 | :code 59 | # lang: ruby 60 | group :development, :test do 61 | gem 'wirble' 62 | gem 'ruby-debug' 63 | end 64 | = link_to 'Learn More: Groups', './groups.html' 65 | 66 | .bullet 67 | .description 68 | After adding a dependency, if it is not yet 69 | installed, install it 70 | .how 71 | :code 72 | $ bundle install 73 | .notes 74 | This will update all dependencies in your 75 | Gemfile to the latest versions that do not 76 | conflict with other dependencies 77 | -------------------------------------------------------------------------------- /source/v1.8/rails3.haml: -------------------------------------------------------------------------------- 1 | #intro 2 | Rails 3 comes with baked in support with bundler. 3 | 4 | %h2 Using Bundler with Rails 3 5 | 6 | .contents 7 | .bullet 8 | .description 9 | Install Rails as you normally would. Use sudo 10 | if you would normally use sudo to install gems. 11 | .how 12 | :code 13 | $ gem install rails 14 | .notes 15 | We recommend using rvm for dependable Ruby 16 | installations, especially if you are switching 17 | between different versions of Ruby 18 | 19 | .bullet 20 | .description 21 | Generate a Rails app as usual 22 | :code 23 | $ rails new myapp 24 | $ cd myapp 25 | 26 | .bullet 27 | .description 28 | Run the server. Bundler is transparently managing 29 | your dependencies! 30 | :code 31 | $ rails server 32 | 33 | .bullet 34 | .description 35 | Add new dependencies to your Gemfile as you 36 | need them. 37 | :code 38 | # lang: ruby 39 | gem 'nokogiri' 40 | gem 'geokit' 41 | 42 | .bullet 43 | .description 44 | If you want a dependency to be loaded only in 45 | a certain Rails environment, place it in a group 46 | named after that Rails environment 47 | :code 48 | # lang: ruby 49 | group :test do 50 | gem 'rspec' 51 | gem 'faker' 52 | end 53 | 54 | .bullet#shared_with_23 55 | .description 56 | You can place a dependency in multiple groups 57 | at once as well 58 | :code 59 | # lang: ruby 60 | group :development, :test do 61 | gem 'wirble' 62 | gem 'ruby-debug' 63 | end 64 | = link_to 'Learn More: Groups', './groups.html' 65 | 66 | .bullet 67 | .description 68 | After adding a dependency, if it is not yet 69 | installed, install it 70 | .how 71 | :code 72 | $ bundle install 73 | .notes 74 | This will update all dependencies in your 75 | Gemfile to the latest versions that do not 76 | conflict with other dependencies 77 | -------------------------------------------------------------------------------- /source/v1.9/rails3.haml: -------------------------------------------------------------------------------- 1 | #intro 2 | Rails 3 comes with baked in support with bundler. 3 | 4 | %h2 Using Bundler with Rails 3 5 | 6 | .contents 7 | .bullet 8 | .description 9 | Install Rails as you normally would. Use sudo 10 | if you would normally use sudo to install gems. 11 | .how 12 | :code 13 | $ gem install rails 14 | .notes 15 | We recommend using rvm for dependable Ruby 16 | installations, especially if you are switching 17 | between different versions of Ruby 18 | 19 | .bullet 20 | .description 21 | Generate a Rails app as usual 22 | :code 23 | $ rails new myapp 24 | $ cd myapp 25 | 26 | .bullet 27 | .description 28 | Run the server. Bundler is transparently managing 29 | your dependencies! 30 | :code 31 | $ rails server 32 | 33 | .bullet 34 | .description 35 | Add new dependencies to your Gemfile as you 36 | need them. 37 | :code 38 | # lang: ruby 39 | gem 'nokogiri' 40 | gem 'geokit' 41 | 42 | .bullet 43 | .description 44 | If you want a dependency to be loaded only in 45 | a certain Rails environment, place it in a group 46 | named after that Rails environment 47 | :code 48 | # lang: ruby 49 | group :test do 50 | gem 'rspec' 51 | gem 'faker' 52 | end 53 | 54 | .bullet#shared_with_23 55 | .description 56 | You can place a dependency in multiple groups 57 | at once as well 58 | :code 59 | # lang: ruby 60 | group :development, :test do 61 | gem 'wirble' 62 | gem 'ruby-debug' 63 | end 64 | = link_to 'Learn More: Groups', './groups.html' 65 | 66 | .bullet 67 | .description 68 | After adding a dependency, if it is not yet 69 | installed, install it 70 | .how 71 | :code 72 | $ bundle install 73 | .notes 74 | This will update all dependencies in your 75 | Gemfile to the latest versions that do not 76 | conflict with other dependencies 77 | -------------------------------------------------------------------------------- /source/v0.9/bundle_install.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle install 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Make sure all dependencies in your Gemfile are 7 | available to your application. 8 | .how 9 | :code 10 | $ bundle install 11 | .notes 12 | Gems may be installed to system gems or BUNDLE_PATH 13 | (which defaults to ~/.bundle). Git repos will 14 | be checked out into to BUNDLE_PATH as well. 15 | 16 | .bullet 17 | .description 18 | Install your dependencies to a location other than 19 | BUNDLE_PATH, in this case 20 | vendor/bundle. 21 | .how 22 | :code 23 | $ bundle install vendor/bundle 24 | .notes 25 | Further bundle commands or 26 | calls to Bundler.setup or Bundler.require will 27 | remember this location 28 | = link_to 'Learn More: Bundler.setup', 'bundler_setup.html' 29 | = link_to 'Learn More: Bundler.require', 'groups.html' 30 | 31 | .bullet 32 | .description 33 | Install all dependencies except those in groups 34 | that are explicitly excluded. 35 | :code 36 | $ bundle install --without development test 37 | = link_to 'Learn More: Groups', 'groups.html' 38 | 39 | .bullet 40 | .description 41 | Install all gems to BUNDLE_PATH, regardless of 42 | whether those gems are installed in your system. 43 | Bundler will not install gems already in system gems 44 | by default, so this is especially useful if you're 45 | trying to package up an application with all 46 | dependencies unpacked. 47 | .how 48 | :code 49 | $ bundle install --disable-shared-gems 50 | 51 | .bullet 52 | .description 53 | Install all gems into vendor/bundle, 54 | even gems that are already installed to your system 55 | and would normally be used from there instead of installed. 56 | .how 57 | :code 58 | $ bundle install vendor/bundle --disable-shared-gems 59 | -------------------------------------------------------------------------------- /source/blog/2015-03-21-hello-bundler-19.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Hello, Bundler 1.9! 3 | date: 2015-03-21 00:00 UTC 4 | author: Samuel Giddins 5 | author_url: http://segiddins.me 6 | category: release 7 | --- 8 | 9 | A mere month and a half after the release of Bundler 1.8, we're happy to announce our next act: Bundler 1.9. 10 | 11 | While the [CHANGELOG](https://github.com/bundler/bundler/blob/v1.9.0/CHANGELOG.md#190-2015-03-20) for this version might seem rather short (and light on big new features), there is one cool thing to talk about: [Molinillo](https://github.com/CocoaPods/Molinillo). Molinillo is a new dependency resolution algorithm developed for [CocoaPods](http://cocoapods.org) -- the Cocoa dependency manager. Now, Bundler shares its dependency resolver -- one of the most integral parts of a dependency manager -- with CocoaPods, with the core logic being independently documented and tested. Molinillo was developed thanks to a [generous grant from Stripe](https://stripe.com/blog/stripe-open-source-retreat) for the express purpose of being a generic dependency resolution algorithm that was sharable across different code bases -- specifically CocoaPods and Bundler (and possibly even [RubyGems](https://github.com/rubygems/rubygems/pull/1189))! 12 | 13 | #### Dependencies in Bundler? 14 | 15 | Having dependencies inside Bundler itself is a bit crazy: Bundler is a dependency manager _for_ gems, written in Ruby. How could it use gems itself? Well, it can't _really_. But we can cheat a bit by shipping Molinillo's source files inside the `bundler` gem. This has its own challenge -- what if a gem (such as CocoaPods), requires a different version of `molinillo` (or `thor`, which is likewise vendored in Bundler)? The solution is to prefix the top-level namespace constant in the vendored gem with Bundler's own namespace. The upshot of this song-and-dance is that Bundler can share open source libraries just like every other gem! 16 | 17 | #### Updating 18 | 19 | To install the last release of Bundler you can run: 20 | 21 | ``` 22 | $ [sudo] gem install bundler 23 | ``` 24 | 25 | For all the details, don’t miss the Changelog! 26 | -------------------------------------------------------------------------------- /source/v1.6/whats_new.haml: -------------------------------------------------------------------------------- 1 | = partial "shared/whats_new" 2 | 3 | %h2#version16 What's New in v1.6 4 | 5 | .contents 6 | .bullet 7 | .description 8 | In this section, you'll find the major features introduced in the release. All the changes are documented in the Bundler 1.6 changelog. 9 | = link_to 'Full 1.6 changelog', 'https://github.com/bundler/bundler/blob/1-6-stable/CHANGELOG.md' 10 | 11 | %h2#new-resolver 12 | 13 | .contents 14 | .bullet 15 | .description 16 | The resolver has been rewritten to avoid recursion and can now resolve Gemfiles up to 10x faster than before. 17 | 18 | %h2#bundle-console-irb-alternatives 19 | 20 | .contents 21 | .bullet 22 | .description 23 | bundle console now supports IRB alternatives Pry and Ripl. If we want to use Pry, set the console Bundler setting: bundle config console pry. You'll need make sure pry is in your Gemfile. Now when running bundle console it will open Pry instead of IRB. 24 | = link_to 'Learn More: Bundle Console', './bundle_console.html' 25 | 26 | %h2#bundle-gem-ext 27 | 28 | .contents 29 | .bullet 30 | .description 31 | Now when creating a new gem, bundle gem supports the --ext flag which creates skeleton files for a C-extension. When running bundle gem newgem --ext, it will create some new files in a ext directory: extconf.rb, newgem.c, newgem.h 32 | = link_to 'Learn More: Bundle Gem', './bundle_gem.html' 33 | 34 | 35 | %h2#other-changes 36 | 37 | .contents 38 | .bullet 39 | .description 40 | Bundler 1.6 also includes: 41 | %ul 42 | %li other performance improvements to make resolving and installing faster 43 | %li :git_source for custom options like :github and :gist 44 | %li color highlighting installed or updated gems 45 | %li HTTP auth may now be stored in bundle config 46 | = link_to 'Full 1.6 changelog', 'https://github.com/bundler/bundler/blob/1-6-stable/CHANGELOG.md' 47 | 48 | -------------------------------------------------------------------------------- /source/blog/2015-03-19-announcing-ruby-together.html.markdown: -------------------------------------------------------------------------------- 1 | --- 2 | title: Announcing Ruby Together 3 | date: 2015-03-19 02:56 UTC 4 | author_url: "http://arko.net" 5 | category: announcement 6 | --- 7 | 8 | All of the infrastructure used by Ruby developers today, including [Bundler][bundler], [RubyGems][rubygems], and [RubyGems.org](https://rubygems.org/) is maintained and developed by volunteers. While it's good that no one company controls resources shared by the community, it's terrible that the only people who work on our shared infrastructure are doing so for free and in their spare time. 9 | 10 | [Ruby Together][rubytogether] was founded so the community can cooperate to solve that problem. It will fund on-call rotations, maintenance work, and improvements to the [shared, public infrastructure][projects] used by the entire community. 11 | 12 | We'll also provide [benefits just for members][benefits]. To begin with, opportunities to connect and exchange knowledge, turning [RubyBench.org](https://rubybench.org) into a fully-fledged community performance benchmarking resource, and tracking and reporting on important deprecations and security issues for members. 13 | 14 | The community that has grown up around Ruby is amazing, and provides many fantastic (and fantastically useful) tools that any developer can use. Let's work together to make sure those tools (and the community) are the best that they can be, for everyone. 15 | 16 | If you or your company has benefited from the free and open-source tools available in Ruby, support those tools by becoming a member of Ruby Together. Membership dues directly fund work that benefits everyone using Ruby, and are usually tax-deductible. Both individual and corporate memberships are available. [Join us today][join]! 17 | 18 | This post was originally written for [Ruby Together][post]. 19 | 20 | [rubytogether]: https://rubytogether.org 21 | [bundler]: https://bundler.io 22 | [rubygems]: https://rubygems.org/pages/download 23 | [projects]: https://rubytogether.org/projects 24 | [benefits]: https://rubytogether.org/benefits 25 | [join]: https://rubytogether.org/join 26 | [post]: https://rubytogether.org/news/2015-03-17-announcing-ruby-together 27 | -------------------------------------------------------------------------------- /source/v0.9/git.haml: -------------------------------------------------------------------------------- 1 | %h2 Gems from git repositories 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Specify that a gem should come from a git repository with a .gemspec at its root 7 | :code 8 | # lang: ruby 9 | gem 'nokogiri', :git => 'https://github.com/tenderlove/nokogiri.git' 10 | 11 | .bullet 12 | .description 13 | If there is no .gemspec at the root of a git repository, you must specify a version that bundler should use when resolving dependencies 14 | :code 15 | # lang: ruby 16 | gem 'deep_merge', '1.0', :git => 'https://github.com/peritor/deep_merge.git' 17 | 18 | .bullet 19 | .description 20 | Specify that a git repository containing multiple .gemspec files should be treated as a gem source 21 | :code 22 | # lang: ruby 23 | git 'https://github.com/rails/rails.git' 24 | gem 'railties' 25 | gem 'action_pack' 26 | gem 'active_model' 27 | end 28 | 29 | .bullet 30 | .description 31 | Specify that a git repository should use a particular ref, branch, or tag 32 | :code 33 | # lang: ruby 34 | git 'https://github.com/rails/rails.git', :ref => '4aded' 35 | 36 | git 'https://github.com/rails/rails.git', :branch => '2-3-stable' 37 | 38 | git 'https://github.com/rails/rails.git', :tag => 'v2.3.5' 39 | 40 | .bullet 41 | .description 42 | Specifying a ref, branch, or tag for a git repository specified inline works exactly the same way 43 | :code 44 | # lang: ruby 45 | gem 'nokogiri', :git => 'https://github.com/tenderlove/nokogiri.git', :ref => '0eec4' 46 | 47 | .bullet 48 | .description 49 | Bundler can use HTTP(S), SSH, or git 50 | :code 51 | # lang: ruby 52 | gem 'nokogiri', :git => 'https://github.com/tenderlove/nokogiri.git' 53 | gem 'nokogiri', :git => 'git@github.com:tenderlove/nokogiri.git' 54 | gem 'nokogiri', :git => 'git://github.com/tenderlove/nokogiri.git' 55 | 56 | %h2 Security 57 | .contents 58 | .bullet 59 | .description 60 | http:// and git:// URLs are insecure, and should 61 | be avoided if at all possible. These protocols are unauthenticated, so a 62 | man-in-the-middle attacker can tamper with the code and compromise your system. 63 | -------------------------------------------------------------------------------- /source/v0.9/gemfile.haml: -------------------------------------------------------------------------------- 1 | %h2 Gemfiles 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Gemfiles require at least one gem source, in the form of the URL for a RubyGems server. 7 | There are shortcuts for the default gem server, so all of these sources are the same. 8 | :code 9 | # lang: ruby 10 | source :rubygems 11 | source 'https://rubygems.org' 12 | source :rubyforge 13 | source 'http://gems.rubyforge.org' 14 | source :gemcutter 15 | source 'http://gemcutter.org' 16 | 17 | .bullet 18 | .description 19 | Declare the gems that you need, including version numbers. Specify versions using the same 20 | syntax that RubyGems supports for dependencies. 21 | :code 22 | # lang: ruby 23 | gem 'nokogiri' 24 | gem 'rails', '3.0.0.beta3' 25 | gem 'rack', '>=1.0' 26 | gem 'thin', '~>1.1' 27 | 28 | .bullet 29 | .description 30 | If a gem's main file is different than the gem name, specify how to require it. 31 | :code 32 | # lang: ruby 33 | gem 'rspec', :require => 'spec' 34 | gem 'sqlite3' 35 | 36 | .bullet 37 | .description 38 | Git repositories are also valid gem sources, as long as the repo contains one or more valid gems. 39 | Specify what to check out with :tag, :branch, or :ref. The default is the master branch. 40 | :code 41 | # lang: ruby 42 | gem 'nokogiri', :git => 'https://github.com/tenderlove/nokogiri.git', :branch => '1.4' 43 | 44 | git 'https://github.com/wycats/thor.git', :tag => 'v0.13.4' 45 | gem 'thor' 46 | = link_to 'Learn more: Git', 'git.html' 47 | 48 | .bullet 49 | .description 50 | If you are actively developing a gem, perhaps checked out from Github, you can use the gem 51 | directly from its directory on your filesystem. 52 | :code 53 | # lang: ruby 54 | gem 'nokogiri', :path => '~/sw/gems/nokogiri' 55 | 56 | .bullet 57 | .description 58 | Dependencies can be placed into groups, to be ignored at install-time or required all at once. 59 | :code 60 | # lang: ruby 61 | gem 'wirble', :group => :development 62 | gem 'ruby-debug', :group => [:development, :test] 63 | 64 | group :test do 65 | gem 'rspec' 66 | end 67 | = link_to 'Learn more: Groups', 'groups.html' 68 | -------------------------------------------------------------------------------- /source/v1.5/gemfile_ruby.haml: -------------------------------------------------------------------------------- 1 | %h2 Specifying a Ruby Version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Like gems, developers can setup a dependency on Ruby. This makes your app fail faster in case you depend on specific features in a Ruby VM. This way, the Ruby VM on your deployment server will match your local one. You can do this by using the ruby directive in the Gemfile: 7 | :code 8 | # lang: ruby 9 | ruby 'RUBY_VERSION', :engine => 'ENGINE', :engine_version => 'ENGINE_VERSION', :patchlevel => 'RUBY_PATCHLEVEL' 10 | 11 | .bullet 12 | .description 13 | If you wanted to use JRuby 1.6.7 using Ruby 1.9.3, you would simply do the following: 14 | :code 15 | # lang: ruby 16 | ruby '1.9.3', :engine => 'jruby', :engine_version => '1.6.7' 17 | 18 | .bullet#patchlevel 19 | .description 20 | It's also possible to restrict the patchlevel of the Ruby used by doing the following: 21 | :code 22 | # lang: ruby 23 | ruby '1.9.3', :patchlevel => 448 24 | 25 | .bullet 26 | .description 27 | Bundler will make checks against the current running Ruby VM to make sure it matches what is specified in the Gemfile. If things don't match, Bundler will raise an Exception explaining what doesn't match. 28 | :code 29 | Your Ruby version is 1.8.7, but your Gemfile specified 1.9.3 30 | 31 | .bullet 32 | .description 33 | Both :engine and :engine_version are optional. When these options are omitted, this means the app is compatible with a particular Ruby ABI but the engine is irrelevant. When :engine is used, :engine_version must also be specified. 34 | .bullet 35 | .description 36 | Using the platform command with the --ruby flag, you can see what ruby directive is specified in the Gemfile. 37 | :code 38 | ruby 1.9.3 (jruby 1.6.7) 39 | = link_to 'Learn More: bundle platform', './bundle_platform.html' 40 | 41 | .bullet 42 | .description 43 | In the ruby directive, :patchlevel is optional, as patchlevel releases are usually compatible and include important security fixes. The patchlevel option checks the RUBY_PATCHLEVEL constant, and if not specified then bundler will simply ignore it. 44 | -------------------------------------------------------------------------------- /source/v1.6/gemfile_ruby.haml: -------------------------------------------------------------------------------- 1 | %h2 Specifying a Ruby Version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Like gems, developers can setup a dependency on Ruby. This makes your app fail faster in case you depend on specific features in a Ruby VM. This way, the Ruby VM on your deployment server will match your local one. You can do this by using the ruby directive in the Gemfile: 7 | :code 8 | # lang: ruby 9 | ruby 'RUBY_VERSION', :engine => 'ENGINE', :engine_version => 'ENGINE_VERSION', :patchlevel => 'RUBY_PATCHLEVEL' 10 | 11 | .bullet 12 | .description 13 | If you wanted to use JRuby 1.6.7 using Ruby 1.9.3, you would simply do the following: 14 | :code 15 | # lang: ruby 16 | ruby '1.9.3', :engine => 'jruby', :engine_version => '1.6.7' 17 | 18 | .bullet#patchlevel 19 | .description 20 | It's also possible to restrict the patchlevel of the Ruby used by doing the following: 21 | :code 22 | # lang: ruby 23 | ruby '1.9.3', :patchlevel => '448' 24 | 25 | .bullet 26 | .description 27 | Bundler will make checks against the current running Ruby VM to make sure it matches what is specified in the Gemfile. If things don't match, Bundler will raise an Exception explaining what doesn't match. 28 | :code 29 | Your Ruby version is 1.8.7, but your Gemfile specified 1.9.3 30 | 31 | .bullet 32 | .description 33 | Both :engine and :engine_version are optional. When these options are omitted, this means the app is compatible with a particular Ruby ABI but the engine is irrelevant. When :engine is used, :engine_version must also be specified. 34 | .bullet 35 | .description 36 | Using the platform command with the --ruby flag, you can see what ruby directive is specified in the Gemfile. 37 | :code 38 | ruby 1.9.3 (jruby 1.6.7) 39 | = link_to 'Learn More: bundle platform', './bundle_platform.html' 40 | 41 | .bullet 42 | .description 43 | In the ruby directive, :patchlevel is optional, as patchlevel releases are usually compatible and include important security fixes. The patchlevel option checks the RUBY_PATCHLEVEL constant, and if not specified then bundler will simply ignore it. 44 | -------------------------------------------------------------------------------- /source/partials/_sidebar.haml: -------------------------------------------------------------------------------- 1 | #sidebar 2 | %h2 Would you like to 3 | %ul 4 | %li= link_to 'Get started', '/#getting-started' 5 | %li= link_to 'Report a bug', '/issues.html' 6 | %li= link_to "See what's new", "/#{current_version}/whats_new.html" 7 | %li= link_to 'Read documentation', "/#{current_version}/man/bundle.1.html" 8 | %li= link_to 'Discuss and Contribute', '/#get-involved' 9 | %li= link_to 'View FAQs', "/#{current_version}/faq.html" 10 | 11 | %h2 Read the latest news 12 | %ul 13 | - blog.articles[0..1].each_with_index do |article, index| 14 | %li 15 | = link_to article.title, article.url 16 | .buttons 17 | = link_to 'All posts', '/blog/' 18 | 19 | %h2 Bundler commands 20 | %ul 21 | %li= link_to 'bundle install', "/#{current_version}/bundle_install.html" 22 | %li= link_to 'bundle update', "/#{current_version}/bundle_update.html" 23 | .buttons 24 | = link_to 'View all commands', "/#{current_version}/commands.html" 25 | 26 | %h2 Help with 27 | %ul 28 | %li= link_to 'Gemfiles', "/#{current_version}/gemfile.html" 29 | %li= link_to 'Groups', "/#{current_version}/groups.html" 30 | %li= link_to 'Gems from git', "/#{current_version}/git.html" 31 | %li= link_to 'Bundler.setup', "/#{current_version}/bundler_setup.html" 32 | %li= link_to 'Deploying', "/#{current_version}/deploying.html" 33 | %li= link_to 'Sharing', "/#{current_version}/bundler_sharing.html" 34 | %li= link_to 'Updating Gems', "/#{current_version}/updating_gems.html" 35 | %li= link_to 'Compatiblity', '/compatibility.html' 36 | %li= link_to 'Older Versions', '/older_versions.html' 37 | 38 | %h2 Use Bundler with 39 | %ul 40 | %li= link_to 'Rails 3', "/#{current_version}/rails3.html" 41 | %li= link_to 'Rails 2.3', "/#{current_version}/rails23.html" 42 | %li= link_to 'Sinatra', "/#{current_version}/sinatra.html" 43 | %li= link_to 'RubyGems', "/#{current_version}/rubygems.html" 44 | %li= link_to 'RubyMotion', "/#{current_version}/rubymotion.html" 45 | 46 | .shirts 47 | .content 48 | = link_to 'http://www.devswag.com/collections/bundler', :class => 'image', :onclick => "ga('send', 'devswag');" do 49 | = image_tag '/images/bundler-shirt.png' 50 | %p 51 | =link_to 'Buy Bundler Shirts & Stickers!', 'http://www.devswag.com/collections/bundler', :onclick => "ga('send', 'devswag');" 52 | -------------------------------------------------------------------------------- /source/v1.7/gemfile_ruby.haml: -------------------------------------------------------------------------------- 1 | %h2 Specifying a Ruby Version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Like gems, developers can setup a dependency on Ruby. This makes your app fail faster in case you depend on specific features in a Ruby VM. This way, the Ruby VM on your deployment server will match your local one. You can do this by using the ruby directive in the Gemfile: 7 | :code 8 | # lang: ruby 9 | ruby 'RUBY_VERSION', :engine => 'ENGINE', :engine_version => 'ENGINE_VERSION', 10 | :patchlevel => 'RUBY_PATCHLEVEL' 11 | 12 | .bullet 13 | .description 14 | If you wanted to use JRuby 1.6.7 using Ruby 1.9.3, you would simply do the following: 15 | :code 16 | # lang: ruby 17 | ruby '1.9.3', :engine => 'jruby', :engine_version => '1.6.7' 18 | 19 | .bullet#patchlevel 20 | .description 21 | It's also possible to restrict the patchlevel of the Ruby used by doing the following: 22 | :code 23 | # lang: ruby 24 | ruby '1.9.3', :patchlevel => '448' 25 | 26 | .bullet 27 | .description 28 | Bundler will make checks against the current running Ruby VM to make sure it matches what is specified in the Gemfile. If things don't match, Bundler will raise an Exception explaining what doesn't match. 29 | :code 30 | Your Ruby version is 1.8.7, but your Gemfile specified 1.9.3 31 | 32 | .bullet 33 | .description 34 | Both :engine and :engine_version are optional. When these options are omitted, this means the app is compatible with a particular Ruby ABI but the engine is irrelevant. When :engine is used, :engine_version must also be specified. 35 | .bullet 36 | .description 37 | Using the platform command with the --ruby flag, you can see what ruby directive is specified in the Gemfile. 38 | :code 39 | ruby 1.9.3 (jruby 1.6.7) 40 | = link_to 'Learn More: bundle platform', './bundle_platform.html' 41 | 42 | .bullet 43 | .description 44 | In the ruby directive, :patchlevel is optional, as patchlevel releases are usually compatible and include important security fixes. The patchlevel option checks the RUBY_PATCHLEVEL constant, and if not specified then bundler will simply ignore it. 45 | -------------------------------------------------------------------------------- /source/v1.8/gemfile_ruby.haml: -------------------------------------------------------------------------------- 1 | %h2 Specifying a Ruby Version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Like gems, developers can setup a dependency on Ruby. This makes your app fail faster in case you depend on specific features in a Ruby VM. This way, the Ruby VM on your deployment server will match your local one. You can do this by using the ruby directive in the Gemfile: 7 | :code 8 | # lang: ruby 9 | ruby 'RUBY_VERSION', :engine => 'ENGINE', :engine_version => 'ENGINE_VERSION', 10 | :patchlevel => 'RUBY_PATCHLEVEL' 11 | 12 | .bullet 13 | .description 14 | If you wanted to use JRuby 1.6.7 using Ruby 1.9.3, you would simply do the following: 15 | :code 16 | # lang: ruby 17 | ruby '1.9.3', :engine => 'jruby', :engine_version => '1.6.7' 18 | 19 | .bullet#patchlevel 20 | .description 21 | It's also possible to restrict the patchlevel of the Ruby used by doing the following: 22 | :code 23 | # lang: ruby 24 | ruby '1.9.3', :patchlevel => '448' 25 | 26 | .bullet 27 | .description 28 | Bundler will make checks against the current running Ruby VM to make sure it matches what is specified in the Gemfile. If things don't match, Bundler will raise an Exception explaining what doesn't match. 29 | :code 30 | Your Ruby version is 1.8.7, but your Gemfile specified 1.9.3 31 | 32 | .bullet 33 | .description 34 | Both :engine and :engine_version are optional. When these options are omitted, this means the app is compatible with a particular Ruby ABI but the engine is irrelevant. When :engine is used, :engine_version must also be specified. 35 | .bullet 36 | .description 37 | Using the platform command with the --ruby flag, you can see what ruby directive is specified in the Gemfile. 38 | :code 39 | ruby 1.9.3 (jruby 1.6.7) 40 | = link_to 'Learn More: bundle platform', './bundle_platform.html' 41 | 42 | .bullet 43 | .description 44 | In the ruby directive, :patchlevel is optional, as patchlevel releases are usually compatible and include important security fixes. The patchlevel option checks the RUBY_PATCHLEVEL constant, and if not specified then bundler will simply ignore it. 45 | -------------------------------------------------------------------------------- /source/v1.9/gemfile_ruby.haml: -------------------------------------------------------------------------------- 1 | %h2 Specifying a Ruby Version 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Like gems, developers can setup a dependency on Ruby. This makes your app fail faster in case you depend on specific features in a Ruby VM. This way, the Ruby VM on your deployment server will match your local one. You can do this by using the ruby directive in the Gemfile: 7 | :code 8 | # lang: ruby 9 | ruby 'RUBY_VERSION', :engine => 'ENGINE', :engine_version => 'ENGINE_VERSION', 10 | :patchlevel => 'RUBY_PATCHLEVEL' 11 | 12 | .bullet 13 | .description 14 | If you wanted to use JRuby 1.6.7 using Ruby 1.9.3, you would simply do the following: 15 | :code 16 | # lang: ruby 17 | ruby '1.9.3', :engine => 'jruby', :engine_version => '1.6.7' 18 | 19 | .bullet#patchlevel 20 | .description 21 | It's also possible to restrict the patchlevel of the Ruby used by doing the following: 22 | :code 23 | # lang: ruby 24 | ruby '1.9.3', :patchlevel => '448' 25 | 26 | .bullet 27 | .description 28 | Bundler will make checks against the current running Ruby VM to make sure it matches what is specified in the Gemfile. If things don't match, Bundler will raise an Exception explaining what doesn't match. 29 | :code 30 | Your Ruby version is 1.8.7, but your Gemfile specified 1.9.3 31 | 32 | .bullet 33 | .description 34 | Both :engine and :engine_version are optional. When these options are omitted, this means the app is compatible with a particular Ruby ABI but the engine is irrelevant. When :engine is used, :engine_version must also be specified. 35 | .bullet 36 | .description 37 | Using the platform command with the --ruby flag, you can see what ruby directive is specified in the Gemfile. 38 | :code 39 | ruby 1.9.3 (jruby 1.6.7) 40 | = link_to 'Learn More: bundle platform', './bundle_platform.html' 41 | 42 | .bullet 43 | .description 44 | In the ruby directive, :patchlevel is optional, as patchlevel releases are usually compatible and include important security fixes. The patchlevel option checks the RUBY_PATCHLEVEL constant, and if not specified then bundler will simply ignore it. 45 | -------------------------------------------------------------------------------- /source/contributors.haml: -------------------------------------------------------------------------------- 1 | %p== Development of Bundler and related projects is managed by the Bundler Core Team, led by André Arko. Bundler was originally written by Yehuda Katz and Carl Lerche. Additional support and code has been provided by #{link_to 'over 300 other contributors, as listed on Github.', 'http://github.com/bundler/bundler/contributors'} 2 | 3 | %h2 Bundler Core Team 4 | 5 | .contributors 6 | 7 | .contributor 8 | = image_tag 'contributors/andre.jpg', :class => 'avatar' 9 | %h3== André Arko 10 | %h4= link_to '@indirect', 'https://github.com/indirect' 11 | 12 | .contributor 13 | = image_tag 'contributors/terence.jpg', :class => 'avatar' 14 | %h3== Terence Lee 15 | %h4= link_to '@hone', 'https://github.com/hone' 16 | 17 | .contributor 18 | = image_tag 'contributors/tim.jpg', :class => 'avatar' 19 | %h3== Tim Moore 20 | %h4= link_to '@TimMoore', 'https://github.com/TimMoore' 21 | 22 | .contributors 23 | 24 | .contributor 25 | = image_tag 'contributors/smit.jpg', :class => 'avatar' 26 | %h3== Smit Shah 27 | %h4= link_to '@Who828', 'https://github.com/Who828' 28 | 29 | .contributor 30 | = image_tag 'contributors/andremedeiros.jpg', :class => 'avatar' 31 | %h3== André Medeiros 32 | %h4= link_to '@andremedeiros', 'https://github.com/andremedeiros' 33 | 34 | .contributor 35 | = image_tag 'contributors/segiddins.jpg', :class => 'avatar' 36 | %h3== Samuel Giddins 37 | %h4= link_to '@segiddins', 'https://github.com/segiddins' 38 | 39 | %h2 Core Team Alumni 40 | 41 | .contributors 42 | 43 | .contributor 44 | = image_tag 'contributors/yehuda.jpg', :class => 'avatar' 45 | %h3== Yehuda Katz 46 | %h4= link_to '@wycats', 'https://github.com/wycats' 47 | 48 | .contributor 49 | = image_tag 'contributors/carl.jpg', :class => 'avatar' 50 | %h3== Carl Lerche 51 | %h4= link_to '@carllerche', 'https://github.com/carllerche' 52 | 53 | .contributor 54 | = image_tag 'contributors/jessica.jpg', :class => 'avatar' 55 | %h3== Jessica Lynn Suttles 56 | %h4= link_to '@jlsuttles', 'https://github.com/jlsuttles' 57 | 58 | .contributors 59 | 60 | .contributor 61 | = image_tag 'contributors/larry.jpg', :class => 'avatar' 62 | %h3== Larry Marburger 63 | %h4= link_to '@lmarburger', 'https://github.com/lmarburger' 64 | 65 | %h2 Icon and Logo 66 | %p 67 | == Provided by #{link_to 'John Neiner', 'http://twitter.com/johnneiner'} and 68 | == the #{link_to 'Pixel Graphic Design Studio', 'http://pixelgraphics.us'} 69 | -------------------------------------------------------------------------------- /source/v1.0/bundle_install.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle install 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Make sure all dependencies in your Gemfile are available to your application. 7 | :code 8 | $ bundle install [--system] 9 | .notes 10 | %p 11 | Gems will be installed to your default system location for gems. If your 12 | system gems are stored in a root-owned location (such as in Mac OSX), 13 | bundle will ask for your root password to install them there. 14 | %p 15 | While installing gems, Bundler will check vendor/cache and then 16 | your system's gems. If a gem isn't cached or installed, Bundler will try to 17 | install it from the sources you have declared in your Gemfile. 18 | %p 19 | The --system option is the default. Pass it to switch back after 20 | using the --path option as described below. 21 | 22 | .bullet 23 | .description 24 | Install your dependencies, even gems that are already installed 25 | to your system gems, to a location other than your system's gem 26 | repository. In this case, install them to vendor/bundle. 27 | .how 28 | :code 29 | $ bundle install --path vendor/bundle 30 | .notes 31 | Further bundle commands or calls to Bundler.setup or 32 | Bundler.require will remember this location. 33 | = link_to("Learn More: Bundler.setup", "./bundler_setup.html") 34 | = link_to("Learn More: Bundler.require", "./groups.html") 35 | 36 | .bullet 37 | .description 38 | Install all dependencies except those in groups that are explicitly excluded. 39 | :code 40 | $ bundle install --without development test 41 | = link_to("Learn More: Groups", "./groups.html") 42 | 43 | .bullet 44 | .description 45 | Install all dependencies on to a production server. 46 | Do not use this flag on a development machine. 47 | :code 48 | $ bundle install --deployment 49 | .notes 50 | %p 51 | The --deployment flag activates a number of deployment-friendly 52 | conventions: 53 | 54 | %ul 55 | %li Isolate all gems into vendor/bundle 56 | %li Require an up-to-date Gemfile.lock 57 | %li 58 | If bundle package was run, do not fetch gems 59 | from rubygems.org. Instead, only use gems in the checked 60 | in vendor/cache 61 | = link_to("Learn More: Deploying", "./deploying.html") 62 | -------------------------------------------------------------------------------- /source/v1.2/bundle_package.haml: -------------------------------------------------------------------------------- 1 | %h2 bundle package 2 | 3 | .contents 4 | .bullet 5 | .description 6 | Locks and then caches the gems into ./vendor/cache. 7 | :code 8 | $ bundle package [--no-prune] [--all] 9 | .notes 10 | %p 11 | Options: 12 | %p 13 | --no-prune: Don't remove stale gems from the cache. 14 | %p 15 | --all: package :git, :path, and .gem dependencies. Once used, the --all option will be remembered. 16 | .description 17 | %p 18 | The package command will copy the .gem files for your gems in the 19 | bundle into ./vendor/cache. Afterward, when you run bundle install, 20 | Bundler will use the gems in the cache in preference to the ones on rubygems.org. 21 | 22 | %p 23 | Additionally, if you then check that directory into your source control repository, 24 | others who check out your source will be able to install the bundle without having 25 | to download any additional gems. 26 | 27 | .bullet 28 | .description 29 | Lock and cache gems from RubyGems into ./vendor/cache. 30 | 31 | .how 32 | :code 33 | $ bundle package 34 | 35 | .notes 36 | %p 37 | By default, if you simply run bundle install after running 38 | bundle package, Bundler will still connect to rubygems.org to check 39 | whether a platform-specific gem exists for any of the gems in vendor/cache. 40 | 41 | %p 42 | This behavior can be avoided by instead running bundle install --local. 43 | Note that this requires you to have the correctly platformed version for all of your gems 44 | already cached. The easiest way to achieve this is to run bundle package 45 | on an identical machine and then check in those vendored gems. 46 | 47 | .bullet#no-prune 48 | .description 49 | Lock and cache gems from RubyGems into ./vendor/cache, and don't remove any stale gems from the existing cache. 50 | 51 | .how 52 | :code 53 | $ bundle package --no-prune 54 | 55 | .bullet#all 56 | .description 57 | Lock and cache all gems into ./vendor/cache, including :git, :path, and .gem dependencies. 58 | 59 | .how 60 | :code 61 | $ bundle package --all 62 | .notes 63 | %p 64 | Once used, the --all option will be remembered. 65 | 66 | %p 67 | This will be the default on Bundler 2.0. 68 | --------------------------------------------------------------------------------