Ruby Weekly is a weekly newsletter covering the latest Ruby and Rails news.

Gemcutter Is The New Official Default RubyGem Host

By Peter Cooper / October 26, 2009

rubygems.pngJust two months ago we posted about Gemcutter, a new RubyGem hosting repository that, we said, was "taking aim at RubyForge and GitHub." It only took six weeks for GitHub to give up on building gems and to start recommending Gemcutter instead. Today, RubyForge is toppled also. Gemcutter developer Nick Quaranto has announced that Ruby Central has given the thumbs up to replacing with (the new Gemcutter URL) as the default gem host in RubyGems.

The transition from RubyForge to Gemcutter/ isn't an overnight deal and gem publishing from RubyForge will continue to work for the time being, but within the next couple of months, RubyForge accounts will be merged with Gemcutter and an update will be made to change the canonical gem source (though, of course, you can use Gemcutter already if you like by following their instructions).

What all of this means for you as a Ruby developer is that if you want to release your own RubyGems (or "gems") in future, things will become a lot easier. Gemcutter, if you haven't checked it out, is definitely a refined evolution in terms of gem hosting - you can "push" a built gem to their server with a single command. If you want to learn how, check out Ryan Bates' awesome Gemcutter & Jeweler screencast that demonstrates how to create a gem and deploy it with Gemcutter.

CodebaseLogo-RI.png[ad] Codebase is a fast & reliable git, mercurial & subversion hosting service with complete project management built-in - ticketing, milestones, wikis & time tracking - all under one roof. Click here to try it - free.


  1. Danny Tatom says:

    I, for one, welcome our new gemcutter overloards.

  2. Peter Cooper says:

    So do I! I think it's awesome news. Tom has been doing a great job maintaining RubyForge but this seems like a good time to pass the torch on the gem front - if only to reinvigorate the idea of releasing gems.. :-)

  3. Tj says:

    If you work with Github check out it will help speed up releasing to Gemcutter as well as github, many cool bash utilities for Rubyists

  4. Peter Cooper says:

    @Tj: Nice! I like the look of that. Did you post about it to RubyFlow yet? I think it might work there too.

  5. Ian Tindale says:

    Will this mean an awful lot of errata and corrections to existing books, which, in explaining things to a beginner, use this or that gem from a rubyforge project in their examples?

  6. Juvenn Woo says:

    cheers and enjoy

  7. Gimi Liang says:

    Good job! Guess a new rubygems with gemcutter as its default repository is coming? Or maybe will redirect you to so there will be no pain for new blood.

  8. Nick Quaranto says:

    Ian: The existing links from RubyForge will continue to work, so hopefully there shouldn't be any trouble.

    Gimi: Yes, soon.

  9. Daniel Berger says:

    RubyForge isn't going anywhere soon. You can still push your gems there, and it does bug tracking, mailing lists, wiki, etc. Stuff gemcutter doesn't do.

    Really, I see gemcutter as the final nail in the coffin of the RAA, not RubyForge.

  10. Arj says:

    This will be a problem :(

    Company has firewall policies blocking access to all data hosting services, Amazon S3 included which renders gemcutter useless.

    Better go and bug the manager again...

  11. type says:

    RubyForge is great.I like it.

  12. Peter Cooper says:

    @Daniel: Are there any projects that really use those RF features in anger? Of all the libraries I've checked out in the last year, I can't think of any examples where I've gone to RubyForge.

    @Arj: Yeah, you might want to look into that - a lot of things are hosted on S3 now. It's not as if it's a piracy-heavy destination like some of the "file hosting" services.

  13. Luis Lavena says:

    @Peter Cooper: Sometimes the libraries you look are not the ones that everybody uses.

    The whole win32utils project (driven by Daniel) is a CVS repository, all the mailing list and the bugs and patches are handle there.

    Or RubyInstaller (known as OneClick), which contains releases that can go back to Ruby 1.8.2.

    I've already expressed the concerns about the massive shift and shutdown of these sections, which led to segmentation more than making easy for people find tools that are not gems.

    (Taking in consideration that several Linux distribution repackage gems to work in their systems).

  14. Peter Cooper says:

    @Luis: I do realize that ;-) That's why I was asking the question. I'd still say, though, that those projects that do use RF features in anger are at least a tiny, tiny minority of all of the typically new projects I see. I'd guess the majority I see are using GitHub's equivalent features.

  15. Daniel Berger says:

    Peter, I'm not sure what you mean by "in anger". RF, and the majority of my projects, predate github by several years. It was better than anything else available for the Ruby community by far in 2003 when it went online.

  16. Peter Cooper says:

    Sorry, "in anger" is a colloquialism. By using it "in anger" I'm referring to projects that use the wiki, bug tracker, and mailing list features of RF with vigor in the present day. I'm not saying it doesn't happen; I just don't see it.

    I can't recall seeing a RF project where the forum wasn't something like "2 messages" - though I'm sure there must be some popular ones still.

  17. Daniel Berger says:

    Peter, indeed, there are some popular ones on RF. Such as Rubygems. :-)

  18. Peter Cooper says:

    Haha, touché! :)

Other Posts to Enjoy

Twitter Mentions