Narrator: All right, we just about got everything set up.
The very last thing we have to do
is add on the deploy section
to our Travis dot EML file.
So let's get to it.
Now the deploy section that we're gonna add on here
is going to be just about identical
to the one that we did on our previous project,
the single container deployment.
So a lot of these options are gonna be very similar
and so we're gonna go through them rather quickly.
So at the bottom of Travis dot EML
I'll add on the deploy section.
I'll add a provider of Elastic Beanstock.
A quick reminder here, we do not put any dashes in here
because these are not array entries.
It's all one single configuration object.
Next up, we'll add on the region.
For the region,
I'm gonna flip back over to my
dashboard for Elastic Beanstock,
which I still have open.
And remember, you can get your region very easily
by looking at the subdomain on your URL.
So that subdomain right there,
that's the region that we're talking about.
So I'm gonna copy that
and put it over as my region entry.
For my app entry.
My app name is Multi dash Docker.
That's the first part of the kind of header up here.
The env is going to be, or environment will be
the multi docker dash env right here.
So I'll put that in as the environment.
Next up, we have to do our bucket name and the bucket path.
And this is going to be where
Travis zips up our entire project
and where it stashes it inside of some S3 bucket.
So remember we are probably going to want to go over
to S3 really quickly
and make sure that there's some bucket over there
that we can use.
So I'm going to flip back over to my dashboard.
I'll go to services and then S3.
And then on here, I'm gonna find my bucket
for the region that I'm currently in.
So for me, it's Elastic Beanstock, US West one, right here.
I'll click on that
and then I'm gonna get the bucket name, if I can copy it.
I don't think I can copy it up at the top.
I feel like I copied it.
Yeah, there we go.
That's better.
So I'm gonna copy the bucket name
and I'll put in here as the bucket name.
And then we have to do a bucket half as well.
And for this one, I'll again just call it Docker multi.
Now, previously we had said
only try to deploy this thing on Branchmaster.
We're gonna do the same thing this time round.
So only try to run this deployment
when the branch that we are pushing
or building up on Travis is the master branch.
In other words, if we push up some feature branch,
don't try to build and deploy this thing.
And then finally, we're gonna do our access key ID
as AWS
access key.
Again, remember there are two Cs in the word access
and we'll do secret access key
and we'll say this is going to be a secret...
Oh, not secret, but secure.
AWS secret key,
like so.
All right. So that's pretty much it.
That's all we have to do for our Travis dot EML file.
So then the last thing we have to do is actually
deploy this thing and test it out.
So I'm gonna make sure I save this file.
We'll take a quick break right here
and we'll continue in the next section.