Publishing your gem to and via the commandline.

zdavatz's Avatar


13 Dec, 2010 04:50 PM


I was trying to publish my documents and gems to Rubyforge and Rubygems today. Rubygems worked with the command:

rake release VERSION= --trace

but what I do not understand is, if the documents are also being pushed to this site:

If you click on these two links:

both clicks will result in a white page and not in the download of the package. If I manually upload the package, then the download links do work.

Also if run

rake publish_docs

the documentation is not updated at

I ran the same command last Saturday and the documentation update worked.

Thank you for your help and Feedback.


  1. 1 Posted by zdavatz on 14 Dec, 2010 07:25 AM

    zdavatz's Avatar

    Ok, the documentation part seems to work now. does have new documentation.

    But: The whitepages still appear if I click on


    any hints what went wrong with the upload?

  2. Support Staff 2 Posted by Nick Quaranto on 15 Dec, 2010 03:24 PM

    Nick Quaranto's Avatar

    I'm not too sure about why the RubyForge upload isn't working, maybe Tom can provide some insight to that.

    That being said, is there any reason why you need to update the RubyForge stuff in the first place? Especially now that updates docs for every pushed gem automatically, it seems like a hassle to do things the old way. :)

  3. 3 Posted by zdavatz on 15 Dec, 2010 03:45 PM

    zdavatz's Avatar

    There is a new way?! I am more then happy to leave Rubyforge! The site is so outdated.

    But all of my projects are not found on


    They are found on Rubyforge though. All of the gems are also found with gem search name -r


  4. 4 Posted by zdavatz on 15 Dec, 2010 03:46 PM

    zdavatz's Avatar

    Ah, sorry, they are found. I hit the wrong button!

  5. 5 Posted by Tom Copeland on 15 Dec, 2010 03:48 PM

    Tom Copeland's Avatar

    Cool, and as Nick said, publishing right to is the way to go.

  6. 6 Posted by zdavatz on 15 Dec, 2010 03:52 PM

    zdavatz's Avatar

    Looks awesome! Nice work! Inspiring.

  7. 7 Posted by zdavatz on 15 Dec, 2010 03:55 PM

    zdavatz's Avatar

    So you guys are recommending not to publish any more stuff to - but only do "rake relase VERSION=" and that will update and release the gem?

    Sounds good to me.

  8. 8 Posted by zdavatz on 15 Dec, 2010 04:00 PM

    zdavatz's Avatar

    Are the documentation pages always built on the fly (processing circle turning on the screen)? That would mean that Google indexes them less. A google search for "spreadsheet ruby" still yields me the rubyforge-page. Until I get to see the documentation on it does take some time.

  9. Support Staff 9 Posted by Nick Quaranto on 18 Dec, 2010 04:09 PM

    Nick Quaranto's Avatar

    Yep, you can just gem build and gem push without any release tools like Hoe or Jeweler if you want to go barebones.

    I think the rubyinfo docs are only built once, not sure why they're taking forever to show up in google.

  10. Nick Quaranto closed this discussion on 18 Dec, 2010 04:09 PM.

  11. zdavatz re-opened this discussion on 18 Dec, 2010 04:26 PM

  12. 10 Posted by zdavatz on 18 Dec, 2010 04:26 PM

    zdavatz's Avatar

    I guess because yard builds the documents onthefly.

  13. Nick Quaranto closed this discussion on 18 Jan, 2011 03:19 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac