title: Working on gem within a Rails app
body: <p>What's the easiest way to work on a plain-ole Ruby gem, and then quickly turn around and run it in a Rails app?</p>
  
  <p>I like to keep application logic out of Rails. Encourages code reuse across projects, and keeps my Rails app clean. It produces, however, an ugly workflow:</p>
  
  <ol>
  <li>Test my gem. <code>rake test</code></li>
  <li>Build my gem. <code>gem build ...</code></li>
  <li>Upload gem to private repository (currently using Gemfury). <code>fury push ...</code></li>
  <li>Update my gem from within Rails (bundle update ...)</li>
  <li>Run my Rails code.</li>
  </ol>
  
  <p>Yuck. I'd like to simply save my file in the library, and then watch it work in the Rails project.</p>
  
  <p>Clojure's <a href="https://github.com/technomancy/leiningen" rel="nofollow noreferrer">Leiningen</a> has a concept called <a href="https://stackoverflow.com/questions/8335709/how-can-i-set-up-leiningen-to-work-with-multiple-projects">"checkouts"</a>, allowing you to work on several libraries within one.</p>
  
  <p>Techniques, anyone?</p>