Instructor: In the last section,
we were able to successfully run our tests on Travis CI.
So now in theory, our application will be ready
to be deployed to some outside hosting provider
such as AWS or Windows Azure or DigitalOcean,
whatever it might be.
Now, in our case,
we're going to set up some automatic deployment over to AWS.
This is a point at which I'm hoping
you've got a AWS account already created.
Again, recall that in order to sign up for AWS,
you do need to have a credit card.
You won't be billed anything,
but you do have to enter some credit card details.
Now, if you don't have a credit card, that's totally fine.
You can always follow along,
just you won't go through the AWS part in particular.
So let's get to it.
The first thing that we're going to do
is to log onto AWS and create a new application
that is going to be used as the target for our deployment.
So I'm going to open up a new browser tab,
and I'll navigate to aws.amazon.com.
And then once here,
I'll sign in by going up to my account
and opening up the AWS Management console.
I'll then sign in,
and then I get redirected to the AWS dashboard.
And at this point, I'm going to scroll in
a pretty good amount just so you can see everything a-okay.
Now, to deploy our project,
we're going to be making use of Elastic Beanstalk,
which you can find
by searching for Elastic Beanstalk, like so.
Elastic Beanstalk, I'm going to tell you right now,
by far easiest way to get started
with production Docker instances.
Now, to be clear, Elastic Beanstalk is most appropriate
when you're running exactly one container at a time.
We can start up multiple copies of the same container,
but at the end of the day,
easiest way to run one single container.