Just in case you haven’t heard the news, Github discontinued support for building gems. Gem building has been disabled since the move to Rackspace and existing Gem will be available at gems.github.com for at least one year.
In the meanwhile, there’s an other Gem hosting solution silently gaining popularity: Gemcutter. Gemcutter aims to be a Gem hosting alternative to RubyForge. I never really liked the GitHub Gem system: altering the original Gem name with my login was a quick workaround for name clashes but causes a lot of confusion when trying to install the original version of a Gem or upgrading a Gem from multiple sources. But GitHub was effectively the most simple (and the unique) alternative to distribute a Ruby library as a Gem without creating a full RubyForge project and, most of all, it worked.
The main benefit of using GemCutter is that you no longer need to pass the :lib option when declaring a Gem dependency in your Rails project.
Rails::Initializer.run do |config| # other configurations # ... config.gem "weppos-tabs_on_rails", :lib => "tabs_on_rails", :source => "http://gemcutter.org/" end
is now simply
Rails::Initializer.run do |config| # other configurations # ... config.gem "tabs_on_rails", :source => "http://gemcutter.org/" end
Thank you GitHub for taking care of my Gems and welcome Gemcutter.