Ronin has moved to GitHub.

Ronin has moved it’s development repository from rubyforge.org to github.com. Since we are using GitHub to host Ronin’s development repositories, you will need to install git in order to access them. If your new to git, you might want to checkout Everyday Git With 20 Commands Or So.

To clone the new development repositories, simply run the following commands:

git clone git://github.com/postmodern/ronin.git
git clone git://github.com/postmodern/ronin-exploits.git
git clone git://github.com/postmodern/ronin-sql.git
git clone git://github.com/postmodern/ronin-php.git
git clone git://github.com/postmodern/ronin-dorks.git

Note: Ronin is only moving it’s development repositories to GitHub and will continue to publish RubyGems to rubyforge.org.

Yes, I have finally jumped on the GitHub band wagon, and I have to say there is a reason why GitHub is so popular. Even though Ronin and it’s sub-projects were hosted on a single RubyForge SVN repository, GitHub was able to effortlessly import each sub-project into separate git repositories via their web-interface. Since playing around with the DataMapper repository on GitHub, I’ve grown fond of a few git features and started to feel like SVN was not letting me exercise the magnitude of rapid-development (read: refactoring with occasional thrashing) that Ronin requires.

Another reason to look into free-hosting on GitHub for large projects (under 100M, above that you have to pay), was a comment made by Ezra at the end of his Merb talk at MountainWest RubyConf 2008. He made the point that GitHub made it really easy for users to fork and share branches via the web-interface, giving developers an incentive to create their own specialized branches, instead of bloating up the main branch.

Advertisements

About this entry