I'm Jason, a web application developer in East Tennessee.

History of the Canonical Gem Host for Ruby Gems

The default repository for downloading gems using RubyGems was originally This was likely because the RubyGems project was hosted only from RubyForge. This meant that when you ran ‘gem install rails’, your RubyGems installation was configured to download the gem from ‘’. In August of 2008 Github started gaining popularity amongst the Ruby community after it started providing it’s own gem server via This resulted in many Ruby developers configuring RubyGems to use the Github server as a secondary source of gems.

In August of 2009 a new gem hosting repository came onto the scene known as GemCutter, aiming to resolve issues caused by how Github and RubyForge were handling hosting of gems. In September they decided to move the service to In October of Github discontinued building and serving gems from, and became the official default host for Ruby gems.

comments powered by Disqus