@alexanderkahn asked me via Twitter whether I’d be pushing VoteFu to GemCutter. To tell you the truth, I hadn’t really thought about it. But, it does seem to be what all the cool kids are doing.
Want to see how easy it was to move to GemCutter?
ping:$ sudo gem install gemcutter Password: ======================================================================== Thanks for installing Gemcutter! You can now run: gem tumble use Gemcutter as your primary RubyGem source gem push publish your gems for the world to use and enjoy gem migrate take over your gem from <a class="zem_slink" title="RubyForge" rel="homepage" href="http://rubyforge.org/">RubyForge</a> on Gemcutter gem owner allow/disallow others to push to your gems ======================================================================== Successfully installed gemcutter-0.1.6 1 gem installed Installing ri documentation for gemcutter-0.1.6... Installing RDoc documentation for gemcutter-0.1.6... ping: Pete$ gem tumble Thanks for using Gemcutter! Your gem sources are now: - http://gemcutter.org - http://gems.rubyforge.org - http://gems.github.com ping:workspace Pete$ cd vote_fu_harness/vendor/plugins/vote_fu/ ping:vote_fu Pete$ ls CHANGELOG.markdown README.markdown examples init.rb rails test MIT-LICENSE db generators lib spec vote_fu.gemspec ping:vote_fu Pete$ gem build vote_fu.gemspec WARNING: no rubyforge_project specified Successfully built RubyGem Name: vote_fu Version: 0.0.11 File: vote_fu-0.0.11.gem ping:vote_fu Pete$ gem push vote_fu-0.0.11.gem Enter your Gemcutter credentials. Don't have an account yet? Create one at http://gemcutter.org/sign_up Email: firstname.lastname@example.org Password: Signed in. Your api key has been stored in ~/.gemrc Pushing gem to Gemcutter... Successfully registered gem: vote_fu (0.0.11) ping:vote_fu Pete$
Scarily easy. In under 3 minutes I have a new primary gem source and am set up to publish to GemCutter.
So, why would one want o host Gems on GemCutter? I asked the same question. In a nutshell:
- Download counts are shown inline
- Build locally, then push-to-publish. No more waiting to make your way through DJ, BJ, Resque, or whatever the background framework of the day is at GitHub.
- It’s nothing but gem hosting, so it’ll probably grow to do gem hosting really well.
- It’s ThoughtBot. I like the ThoughtBot guys.
So, there’s no real compelling reason to run out and move your gems to GemCutter, but if your users ask you to do it, it takes 3 minutes or less.