Chapter 13. Deployment
This chapter covers
- Setting up Heroku for deployment
- The twelve-factor methodology for building and serving web applications
- Setting up Travis CI for continuous integration and automatic deployment
- Setting up Mailgun for sending emails in production
Developing applications is fun, but using them is more fun. Nobody can use your application until you deploy it to the public internet somewhere. In this chapter, we’ll get you started on learning how to deploy Rails, and we’ll talk about how to deploy your app when your tests are green.
Deployment is a big topic, enough for dedicated books on the subject alone.[1] This book can’t possibly explain everything there is to know about deployment, so please think of this as an introduction.
1Books such as Deploying Rails by Tom Copeland and Anthony Burns (http://mng.bz/QwSU), or Reliably Deploying Rails Applications by Ben Dixon (https://leanpub.com/deploying_rails_applications).
One of the difficult things about deployment is that the process often relies on the details of how you’ve built your application. That means different projects have slightly different deployment processes. This book will show you what’s needed to deploy Ticketee, but more complicated applications may have additional needs that we won’t cover here.