Chapter 4. Release, deployment, and monitoring

 

This chapter covers

  • Understanding release flow and predeployment tasks
  • Deploying to Heroku
  • Using Travis for continuous integration
  • Understanding continuous deployments

We’ve covered the build process, common build tasks you can perform (and how to do that using Grunt), and, at a high level, environments and configuration. We discussed the development environment extensively, but that’s only half the story. The development environment is where you’ll spend most of your time working, because you’ll have a system in place, so you can prepare your application for a release, deploy it to a platform that humans can access, and then monitor the application state. Thanks to the Build First mentality, you’ll be automating the workflows I’ve just mentioned, avoiding repetition, human error, and running tests, all while saving time, as I promised in chapter 1.

4.1. Releasing your application

4.2. Predeployment operations

4.3. Deploying to Heroku

4.4. Continuous integration

4.5. Monitoring and diagnostics

4.6. Summary