What your name your repository is up to you, but you should keep rubygems naming conventions in mind: Click the big green, " New Repository" button to add a repository. Once logged into your Github account, when you go to, you'll see two columns, the left hand column is an activity stream while the right column lists repository. If you don't have a Github account, set one up by signing up at. We use and I'd recommend it because other services are likely to have Github integration before support for the other source control service like Gitorious or Bitbucket. Your gem will be open source, so you're going to want to host your source control server on one of the free source control services.
As we've made more and more gems, we've gotten a repeatable process for making new gems, but we thought our process might we useful for other developers in the community that are looking for a newer guide on how to setup ruby gems from scratch and get the most out of all the free tools available to open source projects. These smaller projects take the form of Ruby gems and Rails::Engines. As Metasploit adopts community best practices related to testing and code structure, we've started breaking up our new (and part of our old) work into separate projects that can developed and tested independently.
0 kommentar(er)
