18F/open-data-maker

Set up continuous deployment for different branches/spaces

yozlet opened this issue · 1 comments

Committing to dev, staging and master should push to the dev, staging and production CF spaces respectively. This requires setting our CI service up to do those deployments.

This issue mirrors RTICWDT/college-scorecard#256

At present, Travis is set up to auto-deploy only to dev, but thanks to the manifest.yml it pushes the app with the name ccapi-staging. Both the space and the app name should depend on which branch is being pushed.