In the last section we finished up our pre-deployment checklist this list of four steps right here are
steps you'll have to repeat on any no J.S. project that you ever want to deploy to Roku.
And so it might be a good idea to print out this or save a copy of this diagram.
Remember you can access all the diagrams from this course on the Get Haab repo.
Matching up with the course and the link to that is inside of the Course resources document which you
can find in the very first lecture in this course now that we've gone through this pre-deployment checklist
we can start to go through the actual deployment process.
So we're going to go through this list of steps right here to handle our first time deployments and
then we'll go through the list of steps to figure out how we would do subsequent subsequent deployments
or redeploy our application after we make some changes.
At some point in future.
So step one is to create a Heroku account.
Easy enough.
Let's get to it now.
Inside my browser I'll open up a new tab and then navigate to Heroku dot com.
Now on the landing page that pops up you can find the sign up button on the very top right.
Go ahead and click it and then you can fill out the required information to create a new account.
Now Heroku might require you to access your e-mail and say like you know click on some verification
link or incisor e-mail.
So if it does make sure you hop over to your e-mail account and click that link once you've gone through
that process you can sign into your account.
Now I have already created an account myself.
Some is going to go ahead and log in like the now this is kind of a let's say hobby account of mine
so I don't really have a lot of serious projects inside of here.
It's a lot of test projects that I've worked on in the past and just kind of deployed throughout there
so I don't really have that much that's super important in here.
So all we have to do at this point is create the account and sign in to make sure that our account is
working.
The next step is to commit our codebase to get.
So by default Heroku uses a get based deployment procedure or a get based deployment workflow.
All we have to do is commit our code base to get.
Now when I say that I intentionally say it's somewhat ironically because just saying all we have to
do is come in our code base to get is actually at the end of the day a lot more confusing than you might
think.
So I am going to say that this is really not a course about get per se.
So we're not really going to cover in great detail but I going to give you at least the steps to do
this from scratch assuming that assuming that you've never used it in the past before.
So the first thing we're going to do is verify whether or not we have good already installed on our
local machines to do so.
I'll change back to my terminal and I'll run the command get dash vi like so now Daschle is not an actual
command.
My mistake we probably want dash dash version the much better.
OK.
Now when we run this command we should see something that says like hey here's the version of Get your
running.
If you get back something that says unrecognized command get.
That's totally fine.
It means that you have to install get before you can actually use it.
Now installing it is pretty straightforward.
I'm going to change back over to my browser.
I'm going to open up a new tab and then search for install get and then one of the first links that
you should see pop up should be good dash SVM dot com slash downloads.
We'll click on go to download and then you'll see some directions right on here for installing get.
No matter what operating system you're currently using.
And so at this point I'm going to kind of let you follow through this.
All right so if you do not have it installed please walk through the respective installation steps for
your operating system.
By the time you're done you should be able to run the command get dash dash version at the command line
and see a version be printed printed out to you.
Now if you're running a newer version of good that's totally fine.
Don't sweat it.
OK so now we have get installed.
We are going to create a new local repository and commit all of our server code to the repository.
So inside of my server directory we're going to run the command get in MIT.
Now when I run this command you're going to see initialize empty get repository and then the directory
that you're in.
At present we're then going to commit all of our code to this directory or Scuse me into this get repository
by running the command get ad dot and then get commit Dasch him and it will give it the message.
Initial comment like so after we do that we should see a short message telling us all the different
files and folders that we have committed.
Now if you set up the get ignore file correctly you should not see node modules on this list right here.
So at this point you should only see like three or four listings and you should not see mode modules
on this list.
OK.
So let's go back to our workflow to pull my diagram up.
So we have now created our hero Kroker account.
We have committed our code base using get the next step is going to be to install the Roku see a lie
and create a new Roku application.
So this step here is going to do just a little bit more involved.
But we do have a great installation guide for the Heroku CLID.
Now the purpose of this Rocha's Selye by the way it's a command line interface that we will use to generate
a brand new Heroku project.
So I'm going to open up another new browser tab.
I'm going to search for Heroku Seelye and then you should see one of the toppling some here will be
a help article on Heroku Seelye published at Heroku dot com.
So click on this.
And then it's going to give us some very detailed installation directions for each operating system
that you might be using.
So in my case I'm on Mac OS and so I on Mac OS can use homebrew to install Heroku.
Now to be clear this does assume that you are already using homebrewed.
So this is where we kind of go down like this rabbit hole of installation directions.
So I'm just going to say this one very quick thing.
If you are on Mac OS you might want to install homebrew.
There's a link to it right here.
I'll open it on a new tab and then I can copy this link right here and paste it at the terminal.
You can do that to install homebrew.
And then after running that you can run Brue install Heroku to actually install the Heroku see a lie.
Now if you're on Windows you can just go ahead and download the installer right here.
And also by the way if you don't want install homebrew you can grab the Mac OS install it right here
as well.
So totally up to you.
OK.
So after you go through that installation process we should then be able to run the command Heroku dash
via the command line and then see some version of the Selye printout like so.
OK so let's pause right here because I anticipate that installing the CLID might be a little bit troublesome
if you're having any issues installing the Seelye.
Feel free to pause the video right now.
Flip over to the human discussion boards and just ask me a question let me know.
Hey what are you getting.
Make sure you tell me what you see and I'll do my best to help you get this installed.
So at this point let's take a quick break and when we come back let's make sure that we have the Heroku
dash V command working.
So I'll see you in just a second.