Added gems for Heroku and specified the Ruby version as 1.9.3 (the latest stable Ruby that runs on Windows)
Removed staging. It's the same as production.
Added Heroku required gems, but added them to a production group in the Gemfile. Documentation updated to tell developers to ignore that group (it doesn't build cleanly on Windows).
Explicitly versioned dependencies. Reasons: 1) Underlying dependencies don't quietly change and break things, 2) Make deployments repeatable, 3) Allow Gemfile.lock to be disposed, so that different gems can be used for different groups (i.e. development and production)
 Gemfile.lock is deleted/ignored, so that different gems can be used for different groups (i.e. development and production). However, since the Gemfile has static dependencies the Gemfile.lock will be recreated consistently upon installation.
Revert " Gemfile.lock is deleted/ignored, so that different gems can be used for different groups (i.e. development and production). However, since the Gemfile has static dependencies the Gemfile.lock will be recreated consistently upon installation."

This reverts commit 865c48e0aeb9f60a47e99aa14deb6b37a0a35782.
Removed staging references.
Added unicorn capability for production deployment.
Added instructions on deploying to Heroku.
Added note to production setup instructions to see Heroku instructions if deploying there.
Merge pull request #237 from codeforamerica/heroku-deploy

"When I Get [on the Web]" or got ready for Heroku deployment