With all of the setup out of the way, we can update our CircleCI configuration to deploy code on our behalf. During the CI tasks, we utilized our various make targets to perform work that we were already doing manually. For deployments, we'll reuse another pre-existing make target that is already set up, make deploy.
Under the jobs key, we'll add another step named deploy, which comes after our build step. This new deploy job has the same configuration options available as the previous build step. Our goal in this deploy step is actually to perform the deployment out to our production environment. For that to work, there are different configuration options that we'll need to set up, the details of which you can see in ...
