Okay, so let's go on to our next steps, and that's back in the Atom ID. The next step after this, will require a command line prompt. So let's use the GitHub desktop to open up a command line prompt to the location that we need to go to. So open up the GitHub desktop, and choose repositories. Open-end terminal, and the terminal window should launch. Okay we should have our terminal window. Let's expand the terminal window a little bit so that we can see it. Now for this command or for the following commands we're going to need a Docker Engine. We can type the command, Docker version. To look at the current running version of Docker, and then we can see that it's running if we get a client version, and a server version, you can also use the Docker info command to see if your Docker Engine communicating or your dark a client is communicating with your Docker Server which in this case we are. Now I'm going to use a Docker container from hub dot docker dot com that I created for this exercise is called, win-loss slash Heroku, CLI, and if I do a Docker pull command on that container I can download it off of hub dot docker dot com to my local desktop. This will just take a few seconds. This is a way for me to extract the Heroku CLI, and all of its requirements so that I don't have to install our Heroku CLI everywhere. We can just use it from within a Docker container to work within our repository. So once this is done, I'm also going to need some information from my Heroku App to connect my Heroku App with my local git repository so that I can interact with that git repository. If I click on that application, and I click on the deploy section, we'll see some instructions here for how to deploy Heroku. We're really only interested in the connection between the Git repository, and Heroku App. So for that we can highlight this Heroku Git remote command, and we're going to run that on our local terminal here, and that'll connect our App to Heroku. So first I can see that the download is finished here. So let's just make sure our Heroku CLI is working, and I'll use the Heroku, minus-minus help command. Let's try that again. Oh! Actually one step back. I don't have the Heroku alias setup yet. So I need to set up the alias by using the docker run command, and if I use minus-minus RM, and we specify the container, Heroku CLI, and we use the init command. We'll see that the init command executed some aliases that we can use to source into our current directory or into command prompt, and I can use the ENV commands to sources commands. So if I repeat this command ENV dollar, and put it into a sub-shell Docker run, and it's minus RM, Wenlock, Heroku CLI, and then, then it. We'll see that we now have a Heroku command, and we can see that it pulls the latest version of the container. Makes sure that we're using the latest, and we should get some help output. So just running that twice, can show us that? So the first step here in connecting our local repository where Heroku is to use the Heroku Command with the Gate Colon Remote, and if you remember I get that from the dashboard, and then pulling it from the deploy section. Deploy section has some documentation on how to set up an empty repository. We already have a repository. So we don't have to reinitialize anything. So if I use that, I will be able to connect. Now I don't have a login yet, and that's okay, I can use my user ID that I set up my Heroku account with. So for me that was when logCA at Gmail dot com. So this should be your email address for your Heroku account. Now you can create a temporary password for your command prompt. If you're paranoid, you can go back to Heroku, click on your user account, and click on Account Settings. In the application section, there's a section under authorizations. If you click on create authorization, and we call this Heroku CLI. We can authorize a login for let's say 3,000 seconds. That'll give me a temporary authorization token that I can then use to paste into the password section here for the Heroku CLI. So now you can see this Heroku Git colon remote command connected my local repository with Heroku. So I can type Git remote minus V, and see that I now have a Heroku origin that's connected to the Git repository on Heroku, and that should be enough for me to start to configure the Heroku App for my GitHub App. Now if we go back to the GitHub App configuration, remember that was under your user accounts settings or your org settings, and if you go to developers settings, GitHub apps, and navigate to your app by clicking Edit on it. You can find your application ID which is the first thing we're going to configure for your GitHub app, and so if we copy this value here, and that'll be different for for your GitHub app, and we use the command, Heroku again, and we use config colon set app underscore ID. In our application we'll look for App ID in the config, and we'll configure our App ID on the Heroku website. So this is being done but with the Heroku CLI. The next command that would be useful is to configure this web secret. Remember we had set the web's secret already. However I don't have that right here so I'm just going to reset that to a new value, and if you remember correctly we use the OpenSSL Command to generate that, and so if I go back to the terminal, we'll generate a new value for that. So there's my new value. I'm going to copy this, and actually make it a setting for Heroku App. So Heroku, config, colon set. Webhook secret, equals the value, and this could really be any string, that's acceptable. Is just it needs to be something secret that guarantees the webhook that is communicating from the GitHub App to your Heroku App is actually coming from your app. So in here I'm going to just replace that, and save those changes. Will say not now, and we'll go back to edit here. So the next thing that might be useful for me is some debug settings. I'm going to use the Heroku, config, colon set. Command again, and set the log level. Two equals debug. You might use info or error later on if you were writing a production app, and then the webhook proxy is the URL that our Heroku App will be configured to listen to. So we'll use webhook underscore, proxy underscore, URL, equals, and then the URL actually comes from our Heroku App configuration. So if we go back to the Heroku App dashboard, and we click on our application settings. So there we go, settings. So there's our URL. So we're going to copy that. Now that should be the same URL that we used in the webhook URL down here. So if we go back to the terminal, and we paste in that value, the webhook proxy URL will be configured to that. Now the next setting is the private key, and for this setting is to little trickier. Remember we went to the GitHub App, and we generate a private key by clicking on the GitHub App, and choosing generate key. You can generate a new one by clicking on generate a private key that was downloaded into the Downloads folder. Now since we're using a container, I need to have a way to generate this from within the Heroku App container. So I'm going to copy the downloaded key from the Downloads directory into a local relative directory in Temp. So now that should be copied into the temp folder and the Heroku CLI container actually contains sub-command called Shell, and if I use the Heroku's shell command that will put place be within the container, and I can actually see that Temp fall in that container. I can use to Heroku command from within the Docker containers. So I'll use Heroku config set again, and this time I'm setting the private key. So I want to use private underscore key, and we're going to cut the contents of the file in the Temp directory, and close paren , close quote, and that so we'll use the Heroku config set. That key should now be set into Heroku CLI.