In the last two tutorials we've built a gem and added tests and documentation.
We're going carry on working with the same gem, first publishing it on and Github, and then finishing it off by adding an executable.
If you've been following along, you should already have a package sitting on your computer and ready for upload to
You'll need to sign up for an account if you don't already have one, keeping a note of your username and password.
At Engine Yard, we advocate for the use of Bundler in users’ applications, mainly because it makes dependency management very easy.
Avrohom Katz wrote a post with pro tips for Bundler and Evan Machnic wrote a post about some issues with Bundler and Rails 3.1.
Beneath is an example of just this happening, and an argument as to why you should run it, but carefully.
Sure, it's a trivial and not-very-useful example, but hopefully it illustrates the important steps nicely enough : ) Go to the root of the Gem directory and create a .My preferred method is to first locate them gem on and use the convenient clipboard utility to grab the version number.Alternatively you could run It’s worth the time to read the Bundler documentation on Gemfile setup, as you can get a little fancier than what I’ve shown if you’d like., that will update all the specified gems but there is more risk of breaking dependencies.Sometimes, you want to keep your gems with your application so that you don’t have to call out to to install the gems.