So let's get started. So the first step for us is to stand up our Prometheus environment. Now, for that, you're going to need your Heroku credentials so don't forget to. If you lost your Heroku credentials, place the video on pause now and go get that user ID and password. Now, the Heroku credentials will allow you to log in Heroku, and hopefully, you still have your Probot app. It might be asleep. So, sometimes it's good to go ahead and go to your Probot app, click on the settings tab. Then scroll down here to where the URL is just in case you forgot it. By clicking on the URL, Heroku will automatically reawaken that application. So that is up and running and ready for us to make some changes to it. Now, if we're going to deploy a Prometheus server it can sometimes be really complicated. So it's good to take a repository that I've already prepared for us and use that repository to perform a deployment of the Prometheus server into our Heroku application or into our Heroku application account. Now, let's take a second to go find that repository. So if you open up your browser and you navigate to github.com/ucdavis and we click on repositories and we look for WEB1066-prom, that's just short for Prometheus. You'll find the repository is there. So in this repository, we have a few configuration settings, we have our grafana configuration, we also have a little bit of documentation on how we're going to program that Probot app. We're already set up for this application to be deployable to Travis so we have a Dockerfile here along with some scripts that are going to help us automate that step. So clone and download that repository. So we'll open that in our GitHub desktop. So just click on that, allow the GitHub desktop to be used and you'll be prompted for a user or a URL along with the directory where that can be cloned too. So let's go ahead and clone that repository. Then make sure that you have Docker up and running. So over here on the top right-hand corner, you'll see the little docker icon. If you have that available and you see that little green sign that says Docker is running, then that means that you do have Docker running. So most of this exercise we're going to perform in a command prompt. So choose the repositories section open-end terminal. Then that will open us a terminal session where we can work in. Now I'm going to make this a little larger for you so don't worry about having to zoom in. So give me a second here and we'll make that just a little larger and put that in a good place so that we can see it. Okay, so first command here is docker info just to make sure that our Docker subsystem is running and I'm running a little low on disk space but that's okay. That should be plenty of disk space for us to do this exercise. Now, if I look at the current directory, I'm in my home directory along with where I cloned the WEB1066-prom repository. We should see few files here including that Dockerfile. We'll just take a quick peek at that Dockerfile and it's really simple. We're using a published version from Prometheus of the Prometheus base image and we're pulling down some tools where we can use these tools to help us start up this Prometheus server on our Heroku account. The entry point script here is basically going to help us make some environment configuration settings so that we can point it to our particular Probot app. Now there is a directory here called scripts and if I show you what is in this directory, it's actually called script. There's a publish script, there's a build script, a bootstrap script, and server_local.sh for testing locally and also just a test script. So we're interested in the build script and if we, actually let's look at the bootstrap script real quick just to make sure we don't have to do that first. Yeah, so the bootstrap script just verifies that you have Docker and the Heroku client installed. So we can actually try that real quick and see if we get any errors. Yeah, it looks like I have the Heroku client not installed. Brew install Heroku, can be used to, oh, I don't have brew. That's right. So in previous lessons, we installed the Heroku client using a Docker container. In this particular exercise, we're going to install brew and then install this Heroku container. If you've done this before, you can skip over this portion of it. So I'm just going to do this real quick and then we can make this a breakout or something. So to install brew, we can go to brew.sh and brew.sh is a nice website that is an open source project to help us manage applications that we're installing on our Mac OS. So something similar on Windows system is a system called Chocolaty. So we'll just run that real quick. This script will install, that's great, and put in some credentials, oops. Okay, that's better. This will just take a second so we'll skip over this and then we'll be right back. Okay, brew is installed and it's ready to install additional packages. Now we need to Heroku CLI. So the Heroku CLI is actually really easy to install once you have Brew installed. You can learn how to install the Brew CLI by going to heroku.com, clicking on documentation link at the bottom and then clicking on the Heroku CLI instructions, there's a download and install section here and then a nice little command that we can highlight and copy and then install that in our command prompts. So that should take just a few seconds here and we'll pause the video and come right back. Okay, the Heroku client is installed. We should be able to run the Heroku --version command again and see a version. Okay, that looks good. So let's try to rerun that bootstrap script again to make sure that everything is okay there and it is. The next step will be to create ourselves a local Docker container. That Docker container will be used to actually start up the Heroku application or the Prometheus application on Heroku. So if we run script/build.sh, we're actually going to start by building a local Docker container. Now it uses the prom/Prometheus repository which is published on hub.docker.com to pull down an open source version of Prometheus and then it uses our Dockerfile to configure our new container that is going to be runnable on Heroku itself. So let's give that a few seconds to finish. Then we can go back here and type Heroku login. To login, we can open a browser or press any key to open a browser. Okay, looks like we're getting a login automatically. Great, So Heroku should be logged in. That generated a token for us automatically. So that's great.
