jwhitmire-geminstaller 0.5.4

data/website/src/documentation/tutorials.page

@@ -0,0 +1,337 @@
+h1. Tutorials
+
+These are tutorials which show how to use the various features of GemInstaller.  They are mostly brief, only showing the commands you need to type.
+
+If anything is unclear, or if you'd like to see a tutorial on a topic, please submit a request on the mailing list.
+
+* "Installing GemInstaller":#installing_geminstaller
+* "Bootstrapping your GemInstaller Config with the <code>--print-rogue-gems</code> option":#bootstrapping_your_geminstaller_config
+* "Using the <code>autogem</code> Option to Automatically Require Gems":#using_the_autogem_option_to_automatically_require_gems
+* "Integrating GemInstaller into Ruby on Rails":#integrating_geminstaller_into_ruby_on_rails
+* "Using Common or Shared Config Files or Snippets":#using_common_or_shared_config_files
+* "Running GemInstaller from Capistrano":#running_geminstaller_from_capistrano
+* "Running GemInstaller from Vlad the Deployer":#running_geminstaller_from_vlad_the_deployer
+
+h2(#installing_geminstaller). Installing GemInstaller
+
+<pre><code>$ gem install geminstaller
+   - OR, if you get a permission error -
+$ sudo gem install geminstaller 
+</code></pre>
+
+See also: Docs on "installation":documentation.html#installation.
+
+h2(#bootstrapping_your_geminstaller_config). Bootstrapping your GemInstaller Config with the <code>--print-rogue-gems</code> option
+
+You may have no idea what gems your app uses, or you might just want to create a GemInstaller config file with all the gems currently on your system, in order to install the same gems on a different system.  This tutorial will show you how to use the <code>--print-rogue-gems</code> option to automatically create a GemInstaller config file.
+
+<pre><code>
+$ geminstaller --print-rogue-gems > geminstaller.yml
+</code></pre>
+
+That was easy, wasn't it?  This config file should specify the exact versions for all of the gems which are currently installed on your system.
+
+Gotchas/Notes:
+
+# If you generated the file on a unix/mac system with compiled gems and then try to run it on a different platform (like windows) which does not have a compiler, you may get errors.  The "<code>prefer_binary_platform</code> config property":documentation.html#prefer_binary_platform_config_property (deprecated) will try to guess at the correct platform, but if a binary version of the gem does not exist for your platform, or if <code>prefer_binary_platform</code> fails to guess the right platform, you may still fail.
+# The <code>--print-rogue-gems</code> option generates *exact* version specifications.  This means that you won't ever get any gem upgrades by running GemInstaller with the standard generated file.  This may be good (an upgrade can never break your app unexpectedly).  However, you may wish to modify some of the version specifications to allow for upgrades.  If you do this, remember to set the "<code>check_for_upgrade</code> config property":documentation.html#check_for_upgrade_config_property to true, but be aware that this will cause GemInstaller to check the remote gem server for upgrades each time it runs, and cause it to run slow or fail if the server is unavailable.    
+
+See also: Docs on "<code>--print-rogue-gems</code> option":documentation.html#print_rogue_gems_option, "<code>check_for_upgrade</code> config property":documentation.html#check_for_upgrade_config_property, and "<code>prefer_binary_platform</code> config property":documentation.html#prefer_binary_platform_config_property (deprecated).
+
+h2(#using_the_autogem_option_to_automatically_require_gems). Using the <code>autogem</code> Option to Automatically Require Gems option
+
+GemInstaller can automatically run the RubyGems 'gem' or 'require_gem' method to automatically add all of the gems in your GemInstaller config file(s) to the load path.  Here's an example.
+
+First, create a simple *<code>geminstaller.yml</code>* file:
+<pre><code>---
+gems:
+- name: ruby-doom
+  version: '= 0.8'
+</code></pre>
+
+Now, we'll use <code>irb</code> to test autogem, and verify that it can add the ruby-doom gem to the load path:
+<pre><code>
+$ irb
+irb(main):001:0> require 'rubygems'
+=> true
+irb(main):002:0> require 'geminstaller'
+=> true
+irb(main):003:0> GemInstaller.autogem('--config=geminstaller.yml')
+=> autogem returns the gem object(s) as it's return value...
+irb(main):004:0> $: # Now verify the gem was added to the load path
+=> ["/usr/local/lib/ruby/gems/1.8/gems/ruby-doom-0.8/lib", ...]
+</code></pre>
+
+Note that <code>autogem</code> takes arguments in the same format as the GemInstaller command line and <code>run</code> method, but it ignores arguments which are not applicable (such as -r or -s).  You could also specify no argument at all if you wanted to simply use the default <code>geminstaller.yml</code> file in the current directory.  If you don't want a certain gem to be loaded, you can set the <code>no-autogem</code> property to true for that gem in your config file.
+
+You can also put a call to <code>autogem</code> during your application startup to automatically load all the correct gem versions which are specified by your config file.  See "Integrating GemInstaller into Ruby on Rails":#integrating_geminstaller_into_ruby_on_rails for an example.
+
+See also:  Docs on "Automatically Requiring Gems with the <code>autogem</code> Method":documentation.html#automatically_requiring_gems_with_the_autogem_method
+
+
+
+
+h2(#integrating_geminstaller_into_ruby_on_rails). Integrating GemInstaller into Ruby on Rails
+
+<strong>RAILS 2.0 UPDATE:</strong>
+
+I've created a "Sample Rails App":http://geminstaller.rubyforge.org/svn/trunk/spec/fixture/sample_rails_app/ in the source, which shows how to use the Rails 2.0 config/preinitializer.rb hook.  I need to spend some time updating the docs to reflect this, but for now just "check out the source":http://geminstaller.rubyforge.org/svn/trunk/spec/fixture/sample_rails_app/
+
+<strong>OLD RAILS 1.0 INSTRUCTIONS:</strong>
+
+GemInstaller can be configured to automatically install all gems in the config file, and add them to the load path when Rails boots.  This means that you can check out and run your application anywhere, without having to worry about manually ensuring that the required dependency gems are installed.  This works with Webrick and Mongrel.
+
+First, you need a Rails app.  I'll let you handle this step on your own.  See the "Rails documentation":http://www.rubyonrails.org/docs for details.
+
+Next, you need a *<code>geminstaller.yml</code>* config file.  Create this under the Rails <code>config</code> directory.  For details, see the documentation on the "config file":documentation.html#config_file and the tutorial on "bootstrapping your GemInstaller config with the <code>--print-rogue-gems</code> option":#bootstrapping_your_geminstaller_config.  Here's an example config which contains only entries for Mongrel and Rails, and ruby-doom:
+
+*RAILS_ROOT/config/geminstaller.yml*:
+<pre><code>  ---
+  defaults:
+    install_options: --include-dependencies
+  gems:
+  - name: ruby-doom
+    version: '= 0.8'
+  - name: rails
+    version: '= 1.1.6'
+  - name: mongrel
+    version: '= 1.0.1'
+    platform: <%= RUBY_PLATFORM =~ /mswin/ ? 'mswin32' : 'ruby'%>
+</code></pre>
+
+Once you have your *<code>geminstaller.yml</code>* created, the last step is to add calls to <code>GemInstaller.install</code> and <code>GemInstaller.autogem</code> in your boot.rb.  They should be placed right after the block which defines the RAILS_ROOT constant, as shown below ("..." indicates omitted lines):
+
+
+*RAILS_ROOT/config/boot.rb*:
+<pre><code>  ...
+  unless defined?(RAILS_ROOT)
+  ...
+  end
+ 
+  ############# Begin GemInstaller config - see http://geminstaller.rubyforge.org
+  require "rubygems"
+  require "geminstaller"
+ 
+  # Path(s) to your GemInstaller config file(s)
+  config_paths = "#{File.expand_path(RAILS_ROOT)}/config/geminstaller.yml" 
+ 
+  # Arguments which will be passed to GemInstaller (you can add any extra ones)
+  args = "--config #{config_paths}" 
+ 
+  # The 'exceptions' flag determines whether errors encountered while running GemInstaller
+  # should raise exceptions (and abort Rails), or just return a nonzero return code
+  args += " --exceptions"
+ 
+  # This will use sudo by default on all non-windows platforms, but requires an entry in your
+  # sudoers file to avoid having to type a password.  It can be omitted if you don't want to use sudo.
+  # See http://geminstaller.rubyforge.org/documentation/documentation.html#dealing_with_sudo
+  args += " --sudo" unless RUBY_PLATFORM =~ /mswin/ 
+ 
+  # The 'install' method will auto-install gems as specified by the args and config
+  GemInstaller.install(args)
+ 
+  # The 'autogem' method will automatically add all gems in the GemInstaller config to your load path, using the 'gem'
+  # or 'require_gem' command.  Note that only the *first* version of any given gem will be loaded.
+  GemInstaller.autogem(args)
+  ############# End GemInstaller config
+ 
+  unless defined?(Rails::Initializer)
+  ...
+</code></pre>
+
+This example also has configurable variables which illustrate the common option arguments you can control.  The <code>--exceptions</code> argument will cause GemInstaller to raise an exception if errors occur, and thus abort Rails startup.  The <code>--sudo</code> argument causes GemInstaller to be run via sudo.
+
+Now, all you need to do is start Rails.  You can use Webrick with <code>ruby script/server</code>, or Mongrel with <code>mongrel_rails start</code>.  You should see the message from Geminstaller that the gems are being installed:
+
+<pre>
+$ ruby script/server
+GemInstaller is verifying gem installation: mongrel = 1.0.1, rails = 1.1.6, ruby-doom = 0.8
+GemInstaller is automatically requiring gems: mongrel = 1.0.1, rails = 1.1.6, ruby-doom = 0.8
+./script/../config/boot.rb:55:Warning: require_gem is obsolete.  Use gem instead.
+=> Booting WEBrick...
+GemInstaller is verifying gem installation: mongrel = 1.0.1, rails = 1.1.6, ruby-doom = 0.8
+GemInstaller is automatically requiring gems: mongrel = 1.0.1, rails = 1.1.6, ruby-doom = 0.8
+=> Rails application started on http://0.0.0.0:3000
+=> Ctrl-C to shutdown server; call with --help for options
+[2007-05-13 22:41:37] INFO  WEBrick 1.3.1
+[2007-05-13 22:41:37] INFO  ruby 1.8.5 (2006-08-25) [i686-darwin8.7.1]
+[2007-05-13 22:41:37] INFO  WEBrick::HTTPServer#start: pid=2519 port=3000
+</code></pre>
+
+If that worked, good!  If not, carefully read the error message.  If it was a RubyGems failure (as opposed to a bug in GemInstaller), the "<code>gem</code>" command that GemInstaller tried to execute should be echoed as part of the error message.  Cut and paste this command onto the command line, and see if you get the same error.  If you do, then resolve it and the problem should go away under GemInstaller as well.
+
+For extra credit, we can write a simple Rails controller to verify that the correct gems are getting added to the load path by the <code>autogem</code> command.  First, create the Rails app and a controller:
+
+<pre><code>
+$ rails geminstaller_example
+$ ruby script/generate controller GemInstallerExample
+</code></pre>
+
+Next, create the Rails app.  You need...
+
+...an action:
+*RAILS_ROOT/app/controllers/gem_installer_example_controller.rb*
+<pre><code>
+class GemInstallerExampleController < ApplicationController
+  def index
+  end
+end
+</code></pre>
+
+...a sample rhtml page which will show your config and load path:
+*RAILS_ROOT/app/views/gem_installer/index.rhtml*
+<pre>
+<% config = File.open("#{RAILS_ROOT}/config/geminstaller.yml")
+   config_lines = config.read.gsub!("\n","<br/>") %>
+<hr/>
+<h2>geminstaller.yml</h2>
+<h2><%= config_lines %></h2>
+<hr/>
+<h2>Load Path: </h2>
+<h2><%= $:.join("\n") %></h2>
+<hr/>
+</code></pre>
+
+...a default route to your page:
+*RAILS_ROOT/config/routes.rb*
+<pre>
+...
+# Put the following line as the first route in the routes.rb file:
+map.connect '', :controller => "gem_installer_example"
+...
+</code></pre>
+
+...a GemInstaller config file:
+*RAILS_ROOT/config/geminstaller.yml*:
+<pre><code>---
+defaults:
+  install_options: --include-dependencies
+gems:
+- name: ruby-doom
+  version: '= 0.8'
+</code></pre>
+
+...the modifications to boot.rb (comments and local variables omitted here for brevity):
+</code></pre>
+...
+unless defined?(RAILS_ROOT)
+...
+end
+
+############# Begin GemInstaller config - see http://geminstaller.rubyforge.org
+require "rubygems"
+require "geminstaller"
+config_paths = "#{File.expand_path(RAILS_ROOT)}/config/geminstaller.yml" 
+args = "--config #{config_paths}" 
+args += " --exceptions"
+args += " --sudo" unless RUBY_PLATFORM =~ /mswin/ 
+GemInstaller.install(args)
+GemInstaller.autogem(args)
+############# End GemInstaller config
+
+unless defined?(Rails::Initializer)
+...
+</code></pre>
+
+...and delete the public/index.html file:
+<pre>
+$ rm public/index.html
+</code></pre>
+
+Now, you should be able to start the example Rails app and navigate to <code>http://localhost:3000</code> to view your config file and load path with the gems auto-required:
+
+<pre>
+$ ... cd to root of your rails app ...
+$ mongrel_rails start
+</code></pre>
+
+...open http://localhost:3000, and you should see something like this:
+<pre>
+_____________________________
+geminstaller.yml
+/---
+defaults:
+install_options: --include-dependencies
+gems:
+- name: ruby-doom
+version: '= 0.8'
+_____________________________
+Load Path:
+...
+(lots of load path stuff omitted)
+...
+(here's our gem!)
+/usr/local/lib/ruby/gems/1.8/gems/ruby-doom-0.8/lib /usr/local/lib/ruby/gems/1.8/gems/sources-0.0.1/bin</pre>
+...
+(more stuff omitted)
+...
+</code></pre>
+
+That's about it!
+
+See also: Docs on "Using GemInstaller with Ruby on Rails or Other Ruby Apps":documentation.html#using_geminstaller_with_ruby_on_rails_or_other_ruby_apps. 
+
+
+h2(#using_common_or_shared_config_files). Using Common or Shared Config Files or Snippets
+
+GemInstaller supports multiple config files, with the last config files in the list overriding the previous ones.  It also supports the "<code>include_config</code>":documentation.html#include_config property in the <code>geminstaller.yml</code> file, which allows you to share a YAML snippet across multiple config files.  This means you could do any of the following:
+
+* With multiple config files:
+** Have a common config file across all your projects, which is shared via an svn:external, and a custom config file to override or add gems which are not in the common config.
+** Have a common config file across all development machines, shared on a windows share or NFS mounted drive, with machine- or platform-specific gems listed in local config files.
+** Have config files that are specific to certain environments such as development and test, which will not be included when GemInstaller is run in a demo or production environment.
+* With the "<code>include_config</code>":documentation.html#include_config property:
+** Shared YAML snippets across multiple geminstaller.yml files via an svn:external.
+** Extract geminstaller.yml entries that are duplicated across multiple files to a single shared include snippet file.
+** Use a common include to simultaneously upgrade to the same version of a gem dependency across multiple projects.
+** Extract complicated or shared ERB logic in geminstaller.yml (such as automatically determining the correct version of a gem based on an environment variable) into a separate file. 
+
+TODO: Finish writing examples of this, for now see docs on the "<code>--config</code>":documentation.html#config_option option. 
+
+See also: Docs on the "<code>--config</code>":documentation.html#config_option option, Docs on the "<code>include_config</code>":documentation.html#include_config property. 
+
+
+h2(#running_geminstaller_from_capistrano). Running GemInstaller from Capistrano
+
+GemInstaller can be hooked in as a capistrano task.  This is a way to avoid having gems installed via the preinitializer.rb run in demo or production, and possibly cause problems with app startup in these environments (note you still want to Activate them in preinitializer.rb via GemInstaller.autorun).  It also is a way to avoid the current bug with Rails and Mongrel gems not being loaded correctly if they are upgraded during the app startup process.  Here's an example recipe:
+
+<pre><code>
+namespace :deploy do
+  desc "gem installer"
+  task :geminstaller, :roles => :app do
+    sudo "geminstaller -c #{current_release}/config/geminstaller.yml"
+  end
+end
+</code></pre>
+
+See also: Docs on "Using GemInstaller from Other Ruby Apps":documentation.html#using_geminstaller_from_other_ruby_apps.
+
+h2(#running_geminstaller_from_vlad_the_deployer). Running GemInstaller from Vlad the Deployer
+
+You can also run GemInstaller from "Vlad the Deployer":http://rubyhitsquad.com/Vlad_the_Deployer.html.  Check out "this gist":http://gist.github.com/72143 and "blog post":http://geminstallthat.wordpress.com/2009/02/28/using-geminstaller-with-vlad-the-deployer from "John Dewey":http://geminstallthat.wordpress.com .  Here's the contents of that gist:
+
+<pre><code>
+### lib/tasks/app.rake
+ 
+begin
+  require 'vlad'
+  Vlad.load :scm => :git, :web => :apache
+rescue LoadError
+  puts $!
+end
+ 
+### Extending 'vlad:update' with 'gems:geminstaller'
+namespace :vlad do
+  desc "Install gems via geminstaller."
+  remote_task :update, :roles => :app do
+    Rake::Task['gems:geminstaller'].invoke
+  end
+end
+ 
+namespace :gems do
+  desc "Run geminstaller."
+  remote_task :geminstaller, :roles => :app do
+    run "geminstaller --sudo -c #{current_path}/config/geminstaller.yml"
+  end
+end
+</code></pre>

data/website/src/download.page

@@ -0,0 +1,12 @@
+---
+title: Download
+---
+h1. Installation / Download
+
+GemInstaller is a standard RubyGem, and can be installed as usual (prefix with <code>sudo</code> if necessary):
+
+<pre><code>
+gem install geminstaller
+</code></pre>
+
+Alternately, you can download and install the gem file from the GemInstaller RubyForge download page:  "http://rubyforge.org/frs/?group_id=1902":http://rubyforge.org/frs/?group_id=1902

data/website/src/faq.page

@@ -0,0 +1,36 @@
+---
+title: FAQ
+---
+h1. Frequently Asked Questions
+
+<span id="source_index_cannot_be_created_from_disk"/>
+Q: I got an error "source index cannot be created from disk"<br/>
+A: This is an incompatibility introduced in recent versions of RubyGems.  Upgrade to the latest version of GemInstaller.
+
+<span id="geminstaller_is_slow"/>
+Q: GemInstaller is taking FOREVER to run!<br/>
+A: First, run with the '-gall -rall' options to see all verbose output.  It is probably the underlying RubyGems command that is slow.  If you are on a version of RubyGems which is earlier than 1.2.0, there are know cache performance problems, and you should upgrade.  "This little script may help":http://gist.github.com/13223
+
+<span id="rails_config_gems"/>
+Q: Why not just use Rails' config.gems and rake tasks instead of GemInstaller?<br/>
+A: A few reasons:  1) There are known issues with config.gems, since it attempts to load dependencies while the Rails environment is initializing, resulting in the possibility of "circular dependencies":http://groups.google.com/group/rubyonrails-core/browse_thread/thread/cffe26aaf784acf9/2480c6d27da36bd2.  GemInstaller does not have these issues when run from config/preinitializer.rb.  2) Rails itself cannot manage the Rails gems - but GemInstaller can via preinitializer.rb. 3) GemInstaller has more features that config.gems.  4) GemInstaller runs for any app or environment that needs to manage RubyGems, not just Rails.  See more discussion on "this rails core list thread":http://groups.google.com/group/rubyonrails-core/browse_thread/thread/cffe26aaf784acf9/2480c6d27da36bd2 or "this rails ticket":http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/59
+
+<span id="environment_vars_and_sudo"/>
+Q: Why can't I use environment variables via ERB in geminstaller.yml when using sudo?<br/>
+A: For security, the sudo command does NOT pass most environment variables.  That means if you are trying to use an environment variable to control logic in your geminstaller.yml (for example to dynamically specify a gem version), then it won't work!  The workaround would be to not use sudo (http://thewoolleyweb.lighthouseapp.com/projects/11580/tickets/1-automatically-create-use-and-manage-writeable-gem-home-if-system-gem-home-is-not-writeable)
+
+Q: Why do some gems (like BlueCloth) always get reinstalled, even though they are already installed?<br/>
+A: Dunno, this is either a bug in the gem or in RubyGems.  It isn't a problem with GemInstaller AFAIK, it happens even if you install manually via 'gem install'.  Haven't had time to debug, let me know if you figure it out.
+
+Q: What about gems like RMagick that have platform-specific binary dependencies?<br/>
+A: You are on your own, this is outside of the scope of GemInstaller.  The geminstaller.yml file is parsed with ERB, so you can put whatever hooks you want to perform necessary system setup and/or prereq validation.  You can also google or check the RMagick home page: "http://rmagick.rubyforge.org/":http://rmagick.rubyforge.org/.  For Debian systems, check out the "AptInstaller":http://github.com/ngauthier/aptinstaller tool.
+
+Q: Why don't the tests/specs run on Windows?<br/>
+A: This has been improved with GemInstaller 0.3.0.  Using RubyGems 1.0.1 on Windows, install_smoketest.rb, autogem_smoketest.rb, and ruby test_suites/test_all.rb all work.  See references to 'windows' on the "Code Page":code/index.html for more details.
+
+Q: Why else should I support GemInstaller?<br/>
+A: GemInstaller has an extensive, multifaceted and multiplatform suite of specs and tests which is actively maintained against the latest trunk version of RubyGems and run via Continuous Integration.  It is valuable for alerting about regressions in RubyGems itself.  For example, leading up to the the RubyGems 1.2.0 release, the GemInstaller spec suite identified several regression bugs in RubyGems which were promptly reported and proactively fixed by awesome Eric Hodel and others before the release.
+
+
+<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>This space intentionally left blank.<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>
+

data/website/src/index.page

@@ -0,0 +1,103 @@
+---
+title: Overview
+---
+h1. Overview
+
+h2. What is GemInstaller?
+
+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.
+
+GemInstaller can be used from the command line, or embedded to run automatically on startup for a Rails app or any other Ruby program.
+
+It has been tested on all major platforms (mac, linux, windows), and has an "extensive suite of tests":code/coverage/index.html which are "automatically run by Continuous Integration":http://ci.thewoolleyweb.com against recent versions of RubyGems (selected older releases and trunk)..
+
+h2. How do I get it?
+
+GemInstaller can be installed with 'gem install geminstaller' or "downloaded":http://rubyforge.org/frs/?group_id=1902 from RubyForge.
+
+h2. How do I use it?
+
+See the "Quick Start Guide":documentation/index.html, "Tutorials":documentation/tutorials.html,  or the "Detailed Documentation":documentation/documentation.html.
+
+h2. Who is responsible for GemInstaller?
+
+GemInstaller was created by "Chad Woolley":http://www.thewoolleyweb.com.
+
+h2. Why not just use Rails' config.gems?
+
+GemInstaller "has advantages":faq.html#rails_config_gems over Rails' config.gems.
+
+h2(#known_issues). Known Issues
+
+I have a "list of high priority bugs and features":http://thewoolleyweb.lighthouseapp.com/projects/11580-geminstaller/tickets?q=tagged%3Ahigh_priority that need to be addressed before a 1.0 release.
+
+Please "report any others that you find":http://thewoolleyweb.lighthouseapp.com/projects/11580-geminstaller/overview !
+
+h2(#history). History
+
+* 0.5.3
+** Many long overdue bugfixes and patches, see http://tinyurl.com/geminstaller-0-5-3-release for details.
+** Thanks to Greg Fitzgerald, Britt Crawford, John Trupiano, Gabriel Gironda, and Eric Hodel for patches and assistance.
+** Issues with case statement under Ruby 1.9
+** GemInstaller cannot distinguish between gems that have the ame name but capitalized differently.
+** add ./ci as default location for config file
+** Disable GemInstaller install in default rails preinitializer.rb, but fork if it is used
+** autogem() fails when run for newly-installed gem
+** Sometimes installing fails due to RubyGems cache not being cleared between multiple API calls
+* 0.5.2
+** Support for Rubygems 1.3.5.
+* 0.5.1
+** Print a very verbose and helpful error message if gem cannot be found on remote server.  Attempts to help "http://thewoolleyweb.lighthouseapp.com/projects/11580/tickets/5-sometimes-installing-fails":http://thewoolleyweb.lighthouseapp.com/projects/11580/tickets/5-sometimes-installing-fails
+** Fix bug with stderr being swallowed silently when '--sudo' option is used.  
+* 0.5.0
+** change default processing order of gems from alpha-version-platform to be order found in file (last config file wins)
+* 0.4.5
+** Re-release without Hoe as a dependency, since it snuck itself in as a dependency in 0.4.4
+* 0.4.4
+** Compatibility with RubyGems 1.3.0
+* 0.4.3
+** Repackage gem with released version of RubyGems 1.2.0.
+* 0.4.2
+** Compatibility with RubyGems 1.2.0.
+* 0.4.1
+** Fix bug with warnings for outdated/incompatible rubygems versions.
+* 0.4.0
+** Fix multiplatform bug on windows where ruby platform requiring compile was selected over native mswin platform.
+** deprecate support of rubygems 0.9.5, 1.0.0, and 1.1.0.
+** Change handling of platforms on rubygems on Rubygems > 0.9.5, let RubyGems handle default.
+** Rename GemInstaller.run method to GemInstaller.install, keep 'run' as an alias for 'install'
+** Include instructions ‍to‍ run‍ geminstaller‍ to‍ install‍ the‍ missing‍ version  when‍ gem‍ version‍ error‍ is‍ detected.
+** Rubygems‍ 1.x ‍compatibility.
+** Better internal support for uninstall options.
+** Use‍ new,‍ correct‍ x86-mswin32‍ format‍ for‍ mswin32‍ platform‍ gems.
+** Update‍ warning‍ message‍ for‍ older‍ rubygems‍ versions.
+** Made tests run on Mac OS X Leopard w/RubyGems 1.0.1.
+* 0.3.0
+** Changes to work with RubyGems >= 0.9.5 and take advantage of new platform and auto-install features.  See "notes on RubyGems version compatibility":code/index.html#rubygems_compatibility
+** On Linux/Mac, you can now specify a RUBYGEMS_VERSION environment var to test against a specific version of RubyGems.
+** Improved smoketest.rb and autogem_test.rb
+** Tests now run on windows (only against latest rubygems, with it installed, and only via test_suites/test_all.rb, not rake)
+** deprecated/disabled prefer_binary_platform
+** many other small cleanups
+* 0.2.5
+** Add 'include_config' directive to yaml config file, allowing other files to be included via ERB.
+** Fix broken links in docs - patch from  Maciej Kozak (macio)
+* 0.2.4
+** Look for config file at config/geminstaller.yml as well as geminstaller.yml
+** make startup message ('Installing Gems...') debug level instead of info
+** Add custom descriptive error if user gets access permission error when installing a gem
+* 0.2.3 - Fix debug statement left in, upgrade rspec, improvements to test suite
+* 0.2.2 - Fix performance problems with autogem command (don't manually recurse dependencies, gem method does it already)
+* 0.2.1 - RubyGems release 0.9.3 had some major refactoring done to the internals, which broke GemInstaller 0.2.0.  GemInstaller 0.2.1 is a patch release to fix this.  I did limited testing on 0.9.3 and 0.9.0.  Please let me know if anything is broken on any version of RubyGems.
+* 0.2.0 - Initial release.  Yay!

data/website/src/metainfo

@@ -0,0 +1,54 @@
+index.page:
+  in_menu: true
+  sort_info: 10
+
+documentation:
+  title: Documentation
+  sort_info: 20
+
+download.page:
+  in_menu: true
+  sort_info: 30
+
+faq.page:
+  in_menu: true
+  sort_info: 40
+
+community:
+  title: Community
+  sort_info: 50
+
+code:
+  title: Code
+  sort_info: 60
+
+documentation/index.page:
+  in_menu: true
+  sort_info: 10
+
+documentation/tutorials.page:
+  title: Tutorials
+  in_menu: true
+  sort_info: 20
+
+documentation/documentation.page:
+  title: Documentation
+  in_menu: true
+  sort_info: 30
+
+community/index.page:
+  in_menu: true
+  sort_info: 10
+
+community/links.page:
+  title: Links
+  in_menu: true
+  sort_info: 30
+
+code/index.page:
+  title: Design
+  in_menu: true
+  sort_info: 10
+
+
+

data/website/src/webgen.css

@@ -0,0 +1,112 @@
+/* START webgen download tag */
+.webgen-file-icon, .webgen-download-icon { vertical-align: middle; }
+/* STOP webgen download tag */
+.CodeRay {
+  background-color: #f8f8f8;
+  border: 1px solid silver;
+  font-family: 'Courier New', 'Terminal', monospace;
+  color: #100;
+}
+.CodeRay pre { margin: 0px }
+
+div.CodeRay { }
+
+span.CodeRay { white-space: pre; border: 0px; padding: 2px }
+
+table.CodeRay { border-collapse: collapse; width: 100%; padding: 2px }
+table.CodeRay td { padding: 2px 4px; vertical-align: top }
+
+.CodeRay .line_numbers, .CodeRay .no {
+  background-color: #def;
+  color: gray;
+  text-align: right;
+}
+.CodeRay .line_numbers tt { font-weight: bold }
+.CodeRay .no { padding: 0px 4px }
+.CodeRay .code { width: 100% }
+
+ol.CodeRay { font-size: 10pt }
+ol.CodeRay li { white-space: pre }
+
+.CodeRay .code pre { overflow: auto }
+
+.CodeRay .af { color:#00C }
+.CodeRay .an { color:#007 }
+.CodeRay .av { color:#700 }
+.CodeRay .aw { color:#C00 }
+.CodeRay .bi { color:#509; font-weight:bold }
+.CodeRay .c  { color:#888 }
+
+.CodeRay .ch { color:#04D }
+.CodeRay .ch .k { color:#04D }
+.CodeRay .ch .dl { color:#039 }
+
+.CodeRay .cl { color:#B06; font-weight:bold }
+.CodeRay .co { color:#036; font-weight:bold }
+.CodeRay .cr { color:#0A0 }
+.CodeRay .cv { color:#369 }
+.CodeRay .df { color:#099; font-weight:bold }
+.CodeRay .di { color:#088; font-weight:bold }
+.CodeRay .dl { color:black }
+.CodeRay .do { color:#970 }
+.CodeRay .ds { color:#D42; font-weight:bold }
+.CodeRay .e  { color:#666; font-weight:bold }
+.CodeRay .en { color:#800; font-weight:bold }
+.CodeRay .er { color:#F00; background-color:#FAA }
+.CodeRay .ex { color:#F00; font-weight:bold }
+.CodeRay .fl { color:#60E; font-weight:bold }
+.CodeRay .fu { color:#06B; font-weight:bold }
+.CodeRay .gv { color:#d70; font-weight:bold }
+.CodeRay .hx { color:#058; font-weight:bold }
+.CodeRay .i  { color:#00D; font-weight:bold }
+.CodeRay .ic { color:#B44; font-weight:bold }
+
+.CodeRay .il { background: #eee }
+.CodeRay .il .il { background: #ddd }
+.CodeRay .il .il .il { background: #ccc }
+.CodeRay .il .idl { font-weight: bold; color: #888 }
+
+.CodeRay .in { color:#B2B; font-weight:bold }
+.CodeRay .iv { color:#33B }
+.CodeRay .la { color:#970; font-weight:bold }
+.CodeRay .lv { color:#963 }
+.CodeRay .oc { color:#40E; font-weight:bold }
+.CodeRay .on { color:#000; font-weight:bold }
+.CodeRay .op { }
+.CodeRay .pc { color:#038; font-weight:bold }
+.CodeRay .pd { color:#369; font-weight:bold }
+.CodeRay .pp { color:#579 }
+.CodeRay .pt { color:#339; font-weight:bold }
+.CodeRay .r  { color:#080; font-weight:bold }
+
+.CodeRay .rx { background-color:#fff0ff }
+.CodeRay .rx .k { color:#808 }
+.CodeRay .rx .dl { color:#404 }
+.CodeRay .rx .mod { color:#C2C }
+.CodeRay .rx .fu  { color:#404; font-weight: bold }
+
+.CodeRay .s  { background-color:#fff0f0 }
+.CodeRay .s  .s { background-color:#ffe0e0 }
+.CodeRay .s  .s  .s { background-color:#ffd0d0 }
+.CodeRay .s  .k { color:#D20 }
+.CodeRay .s  .dl { color:#710 }
+
+.CodeRay .sh { background-color:#f0fff0 }
+.CodeRay .sh .k { color:#2B2 }
+.CodeRay .sh .dl { color:#161 }
+
+.CodeRay .sy { color:#A60 }
+.CodeRay .sy .k { color:#A60 }
+.CodeRay .sy .dl { color:#630 }
+
+.CodeRay .ta { color:#070 }
+.CodeRay .tf { color:#070; font-weight:bold }
+.CodeRay .ts { color:#D70; font-weight:bold }
+.CodeRay .ty { color:#339; font-weight:bold }
+.CodeRay .v  { color:#036 }
+.CodeRay .xt { color:#444 }
+
+/* START webgen horizontal menu style */
+.webgen-menu-horiz ul { display: block; }
+.webgen-menu-horiz li { display: inline; }
+/* STOP webgen horizontal menu style */