-: In the last section,
we finished up a couple of changes to our travis.yml file,
and then pushed those changes up to GitHub.
Once we pushed the changes up,
Travis CI automatically woke up, pulled down our files,
and ran the directions we added to the travis.yml file.
It looks like the build was successful,
but let's take a look at some of the output
and just see what happened.
If you scroll down a little bit, you'll see that Docker,
or excuse me, Travis,
successfully built our image using the client directory,
and then ran some tests using that image.
All the tests ran successfully, and after they did,
we then attempted to build our four different images
using the production dockerfile
in each of those sub-directories.
We then successfully logged into the Docker CLI,
and then successfully pushed
all four images up to Docker Hub.
So we can now open up a new browser tab
and navigate to hub.docker.com.
And once you go there,
you'll see four brand new repositories appear right here.
Each of these represents one of those different images
that we just pushed up.
So we could look at say, how about multi-nginx right here?
And we can look at our tags.
And right now we have just the latest tag,
cause remember, by default,
whenever we tag an image with a name,
the default version used on the very end is latest.
So cool, that's pretty much it.
We now have a rock solid process
to take our GitHub repository
and build Docker images out of each of those sub-projects,
and then push them up to Docker Hub.
So let's take a quick pause right here.
We're gonna continue in the next section,
and start thinking about deploying this app
over to Amazon Elastic Beanstalk.
So quick break, and I'll see you in just a minute.