Okay. So, let's finish setting up our application. We're going to use the actual example that was given here which is, we're going to set up our web application on glitch. So glitches, a system for creating new applications for free, and it's really easy to use, simply navigate to the docs that we specified that on the probot/probot/docs/deployment.md section, and then if you go down to the glitch, there's a nice link to create a new application on glitch. So, if we open up our glitch account and we sign in there and we use our Github credentials, then we can basically authorize them to access our account. So at this point what we're going to do is, we're going to let glitch initialize our application. So, at this point, we're going go to some advanced options and we're going to grant access so that they can import, export from our organization. We're going to grant them access to the Leo organization. So, we'll just choose that authorized them there. Whoops, I didn't mean to go that far. Okay. Go back here and then choose Advanced Options and let's import, and we're going to choose to import from LeoPoppy and the name of our repository and in this case, it was on, let's go back, github.com/leoPoppy. We're going to choose our repository. Let's copy that, and place this there, and say, okay. So, it's importing the LeoPoppy. So it imported it successfully, and now we see some of our code here. We see the package.json file and we see the index.js file. Now, just because we imported this, doesn't mean that we're completely done yet. We actually have to give some permissions here in the environment, and the first permission is the secret information. So, but one of the things that we can do is we can now see the URL for our app. So, this is trying to start up the URL. However, it's going to fail because we're going to see some errors here and we do see some errors that the Node JS application fell to start. That's okay. That just basically means that the application isn't fully configured. However, we do have our application URL now. So at this point, what we can do is we can copy that URL. If we go back to github.com and we choose our user account settings and we scroll down here to Developer and click on GitHub apps. Whoops, I'm actually in the wrong place. Let us go to github.com/LeoPoppy, and we choose settings, and we scroll down to the developer settings and choose GitHub apps, and we added the Probot Hello, the URL for our page is now this URL. The authorization callback will go to this URL and the web hook URL will go to that URL. So, we can save those settings, and if we now go back to our environment file, we need to configure the dot env file, and we also need to upload a secret file, which is a private key that's generated from our GitHub app. So, if we click on edit for our GitHub app and we choose, we scroll down here to the section called private keys, we're going to generate a private key, and it's downloading, this is the public version of it and is downloading a file that we can upload into our glitch applications. So, that should be in the download section now, and we see that as probot hello ended with a dot pem directory. You're going to want to save that file and secure it. So, now our application has a way to authorize with our GitHub application backend. So, next is going to arc lead shop and configuring the dot env file. So, in the third step we see there's a couple of settings that we want to set in the dot env file. First is the App ID, then the web hooks secret, then the path to the private key path, and then finally the node environment. So, let's highlight this section and copy it, and then we're going to go back to the environment section and we're going to replace it here. So, let's replace that there. Now, the App ID, where does that come from? If we go to the GitHub application and we scroll down to the end which check. Just like we did before, we go to github.com/LeoPoppy, and we choose settings, and we scroll down to the developer settings, click on GitHub apps. Choose the edit button, and if we look at the section, whoops, section down here under ID, our application ID is this number. So, we'll copy that application ID and paste it into your configuration file. The next is the web hooks secret. Now, this was the same secret new generated from the command prompt. So, as long as you stored that, we can copy that, and that web hook secret goes right into your application. Remember that setting, in your application is actually the web hook secret that's configured here. So, that when the web hook request is received we know that it came from our application and not somewhere else. Then the next setting is the private key and this allows us to communicate back with GitHub, and basically it's expected to live in a directory called.data/private-key.pem. Now, this was the same private key that was downloaded and it's in our downloads folder. So, we simply just need to create a new file, and we're going to add a file. Whoops, I didn't mean to do that. Delete that. We're going to create a new file, and we're going to call it.data/private-key.pem. Then we're going to choose Add. In this file, we basically want our download file copied into that. So, we'll just copy that in just like that, and we dragged it right in into there. So, we see, whoops, and it doesn't work right. Okay. So, we're going to go to this file. Actually, let's go to Adam, and we're going to add. We're going to choose File Open, and we're going to click on downloads and click on the file. Then we're going to highlight this text, copy it, go back to our web interface, and paste the contents of the private key there. Okay. Great. So, we have the private key and we have the environment configuration. We've set the NODE_ENV to production, and that should allow us to stop and start the application. So, all we have to do now is turn on the application by clicking the Show button. Now, it's that's waking up, we can go back here and take a look at the log, and see what kind of error messages we get. Oh, we called it private key instead of private dash key. So, that's not a big deal, we can just remove the slash here. Okay. So, I'm going to turn this back-off here, and since we've already changed that, let's just make sure it changed, and then we'll click on show again. This should give us a second instantiation. Hey, there's our probot app. Okay. Great. So, let's go look at the logs, and we should see some clean logs now, yep, sure enough. Okay. So, this is the basis for what we needed to start debugging.
