Our next step is we're basically complete on configuring the Heroku CLI. I hit Exit there to exit the subshell of that container. We can actually go look at our probot app now in Heroku, and look at the settings under, if you click on Heroku, your app, and then choose Settings, and choose Reveal Configs. These are the config values that we set up from the command lines, so this could have been done from here as well. However, if you are trying to automate this, this is a good way to automate that as well using those commands. Now, the next step is for us to configure the secrets, so that we have an access token that can be used for deploying our application using Heroku, the Heroku deployment plug-in on Travis CI, and communicating with Heroku to deploy our application as a live application whenever we have a continuous integration job. So for that step, we're going to follow the following steps. All right. So we'll need to have our terminal open again. The first thing we want to do is make sure that we have another Docker image. I have a Docker image called the Travis CLI image, under my account on hub.docker.com. So we can pull that image with docker pull, wenlock, and then Travis CLI. That will pull down the wenlock/traviscli image. Now, the travel CLI image can be used to encrypt settings with the.travis.yml. There's a few other features available with the Travis CLI to validate your Travis configuration file before you committed as well, so that it can be a handy tool to have. Now, encapsulating this in a container, gives us the ability to do just like we did with their Heroku CLI and evaluate an alias that's available with the container, and then use that as an actual command line tool for editing and manipulating our travis.yml file. So we'll use the eval command again. Actually, before we eval, let's take a look at what we're about to eval. So we'll run the Docker RM. RM basically says, "Hey, don't leave the container around after it exits." We'll use that wenlock/traviscli init command, and you'll see an alias there for running the Travis CLI with the current working directory. So if we run the eval command and put that into a subshell, well, I'll just copy and paste the command that we just ran there. Then, if I type Travis minus minus help, it should pull the latest version of that and give us a command line settings. So that looks really good. We're ready to use the Travis CLI. If we use the Travis CLI to run the command, Travis encrypt and provide some help for that. We can see that the Travis encrypt command allows us a lot of options to encrypt keys and to store those values for those keys into our travis.yml. This is going to help us take a Heruko API token that is required during the Travis deployment for the Heroku deployment provider, so that it can communicate with Heroku and publish our application. Now, we're going to use our Heroku container alias again. So let's make sure that the Heroku containers available. I'll do Heroku help, and if you don't have that just like before, download the Heroku CLI container from my wenlock repository on hub.docker.com, and use the init command to alias that command into your subshell. We're going to use the subcommand here called authorizations:create. Let's use the help for that. So I mistyped that, so let's try that again, authorizations:create. So we can see the options here. There is a short options so that we just output the container key or the API key for our Heroku applications. So let's just try that as an example. So I've been doing this a couple of times now. If you get prompted and asked if this is for your repository, just say yes. Run that a couple times, and it should generate some keys. If you go back to your Heroku account, on the Heroku website, and let's just do that real quick so that we can see something with how these keys are managed. So go to heroku.com, and make sure you log into your Heroku account. Go to your Account settings. Under your account, there should be a section here for your keys. I think that might be under Applications. So you can see all of those authorizations that I did. Now, you can delete these authorizations from the actual dashboard here by clicking on the authorization and clicking on Delete authorization. That way, anything that you're not using, it's always good to clean up. So I'm just deleting all my authorizations here. We're going to try this one more time so that we can see how that gets created. So we'll run that one more time. We can see a new key is generated and that shows up as a long-lived user authorization. So this is great. We can generate these authorizations from the command line, and that's because we're logged into the Heroku CLI. So if we use that ability in conjunction with the Travis CLI container and use the authorizations create, we can create an authorization in our travis.yml that is encrypted. So we have everything that we need to check out and encrypt our credentials. So let's start by making sure that we're logged in to the dot-com side of the Travis websites. So if we run Travis minus minus help, we should see with the encrypt command, some helped options here. So let's take a look at that. What's important here is the dash dash com and dash dash org. There's two parts to the Travis back in. One is the dot-com side. The other is a dot-org side. We want to make sure that we're using the dot-com side. So in order to encrypt our credentials, we have to make sure that we're logged in. So for this exercise, we're going to use the Travis login command to make sure that we're logged into Travis. So I'm going to execute Travis login minus minus com, we'll use auto here. So what happens is Travis will authenticate your credentials with GitHub. So we'll use our user account that we set up under Travis for GitHub authentication, and place your password here to authenticate with GitHub and Travis. Great. So we're authenticated there. So next step is to make sure that we can generate a token with the Heroku CLI, and we'll use the authorizations:create option again to generate a new token for us that we'll use to encrypt. So let's generate that right now with the Heroku authorizations create minus minus short. Oops, I misspelled that. Let me go back here and correct that. Then copy this string. We're going to use that as one of the arguments to the Travis encrypt command. So let's run Travis encrypt and paste the token that was generated from the Heroku authorization calling create command, use minus minus add, and we'll add the key to the deployment section. We'll call the key API underscore key because that's what the provider expects. Remember to use the minus minus com options so that we're talking to the dot-com side of the Travis API.