Total Pageviews

Saturday, 3 September 2016


Automated Gem installation, activation, and much more! 
* mailto:"GemInstaller Development" <>
* mailto:"Chad Woolley" <>


* GemInstaller is being deprecated in favor of Bundler:
* There is a --bundler-export option on geminstaller to help GemInstaller users migrate to Bundler.
* This site is outdated, and will remain that way.  I'll try to keep GemInstaller working with new RubyGems releases for as long as I can, but I won't do much else.  I've also given up on testing older Rubygems versions and Windows (although they should still work, feel free to open a bug if they don't).
* Why Bundler instead of (some other tool)?  Dependency Management is a hard problem to solve properly.  Bundler does the right things.
* If you think Bundler is too complex, then you probably don't understand the problem, or have never dealt (properly) with long-term or complex dependency management issues in the real world, or just like to be contrary.  Bundler resolves your entire Gem dependency graph and freezes it in your app.  If your tool of choice doesn't do this, it is inferior.  Perhaps very usable (like GemInstaller), but still inferior.  If you have problems with Bundler, I'd recommend opening an issue:


Automated Gem installation, activation, and much more!

GemInstaller provides automated installation, loading and activation of RubyGems.  It uses a simple YAML config file to:
* Automatically install the correct versions of all required gems wherever your app runs.
* Automatically ensure installed gems and versions are consistent across multiple applications, machines, platforms, and environments 
* Automatically activate correct versions of gems on the ruby load path when your app runs ('require_gem'/'gem')
* Automatically reinstall missing dependency gems (built in to RubyGems > 1.0)
* Automatically detect correct platform to install for multi-platform gems (built in to RubyGems > 1.0)
* Print YAML for "rogue gems" which are not specified in the current config, to easily bootstrap your config file, or find gems that were manually installed without GemInstaller.
* Allow for common configs to be reused across projects or environments by supporting multiple config files, including common config file snippets, and defaults with overrides.
* Allow for dynamic selection of gems, versions, and platforms to be used based on environment vars or any other logic.
* Avoid the "works on demo, breaks on production" syndrome
* Find lost socks.


See Quick Start at

=== Bugs/Patches

=== Quick Start:



* RubyGems


* [sudo] gem install gem installer