Question

I’m developing a new gem (fork of nifty-generators).

Right now my “deployment” consists on the following:

1. I make changes on the gem’s source code
2. I commit to github
3. I update the gemspec lower numer (i.e. go from 0.1.1 to 0.1.2)
4. Build the gem and push it to gemcutter (gem build, gem push)
5. Install the new gem (sudo gem install mygem)
6. Then y try the new gem.

I’m sure there must be a more correct way of doing things. Right now, I’m uploading to gemcutter so that I can test my gem.. and that doesn’t feel right.

What is the best way to “test your gem before uploading to gemcutter”?

Answer 1

Once you have your gemspec, you can run gem build yourgem.gemspec. That will produce a .gem file for you to install….try the following commands out to verify it:

gem install --local
gem spec
gem unpack

You have to push a built gem to RubyGems.org anyway, so you’re pretty much there 🙂