Deploying to Heroku

WARNING - THE INFORMATION BELOW IS OUT OF DATE - PLEASE see https://github.com/AgileVentures/LocalSupport/blob/develop/docs/heroku.md

First setup DEVISE_SECRET_KEY as an env variable on your heroku app configuration.

Deploying your build to heroku is a good way to share your work with others. Deploying to heroku with LocalSupport now requires an extra step because we use bower. For a ruby app to use bower on heroku, it needs run two installations: first a node.js installation, and then a ruby installation. To enable this, you need to tell your heroku remote to use multiple buildpacks BEFORE your first deployment.

heroku config:add BUILDPACK_URL=https://github.com/ddollar/heroku-buildpack-multi.git --app <your heroku remote name>

This will cause heroku to detect the buildpacks referenced in .buildpacks, and to run the node.js installation before the ruby installation.

If you accidentally deployed the app without modifying the setting of multiple buildpacks, you will need to use heroku buildpacks:clear after you use the above commands. If the build process on Heroku is not triggered, you may want to use heroku repo:reset to first empty the repo on Heroku and run git push heroku master again.

A list of deployed servers showcasing Local Support is at the Agile Ventures site:

• http://www.agileventures.org/projects/localsupport/documents/heroku-sites

---

Previous (Remote Pair Programming Strategy) ::: Next (Future Plans)

---

Return to Top (Project Overview)