Deploying Through Seed
Now, we are ready to make our first deployment. You can either Git push a new change to master to trigger it. Or we can just go into the dev stage and hit the Trigger Deploy button.
Let’s do it through Git.
Go back to your project root and run the following.
$ npm version patch
This is simply updating the NPM version for your project. It is a good way to keep track of the changes you are making to your project. And it also creates a quick Git commit for us.
Push the change using.
$ git push
Now if you head into the dev stage in Seed, you should see a build in progress. Now to see the build logs, you can hit Build v1.
Here you’ll see the build taking place live. Click on the service that is being deployed. In this case, we only have one service.
You’ll see the build logs for the in progress build here.
Notice the tests are being run as a part of the build.
Once the build is complete, take a look at the build log and make a note of the following:
- Region:
region
- Cognito User Pool Id:
UserPoolId
- Cognito App Client Id:
UserPoolClientId
- Cognito Identity Pool Id:
IdentityPoolId
- S3 File Uploads Bucket:
AttachmentsBucketName
- API Gateway URL:
ServiceEndpoint
We’ll be needing these later in our frontend and when we test our APIs.
Now head over to the app home page. You’ll notice that we are ready to promote to production.
We have a manual promotion step so that you get a chance to review the changes and ensure that you are ready to push to production.
Hit the Promote button.
This brings up a dialog that will generate a Change Set. It compares the resources that are being updated with respect to what you have in production. It’s a great way to compare the infrastructure changes that are being promoted.
Scroll down and hit Promote to Production.
You’ll notice that the build is being promoted to the prod stage.
And if you head over to the prod stage, you should see your prod deployment in action. It should take a second to deploy to production. And just like before, make a note of the following.
- Region:
region
- Cognito User Pool Id:
UserPoolId
- Cognito App Client Id:
UserPoolClientId
- Cognito Identity Pool Id:
IdentityPoolId
- S3 File Uploads Bucket:
AttachmentsBucketName
- API Gateway URL:
ServiceEndpoint
Next let’s configure our serverless API with a custom domain.
For help and discussion
Comments on this chapterIf you liked this post, please subscribe to our newsletter, give us a star on GitHub, and follow us on Twitter.