In the last section we finished up our first time deployment process.
Now at the end of the video I know I said that we're going to start working on our first feature.
But you know what I realized we might as well just talk right now how we do additional deployments in
the future.
So now that we've committed and deployed for the very first time how do we deploy again after we've
made some changes to our code base.
So in practice it ends up being pretty straight forward.
Let's make some arbitrary change sure codebase just to say hey we changed something song and flip back
over to my index dot Jay has filed inside my code editor.
I'm going to find the line that says red dot send.
And I'm going to change the contents of this object to be by buddy.
You know what the heck you change it to whatever you want.
Absolutely anything doesn't matter just change it to something else.
After we make that change we will then go through the process to deploy our application again.
So from here on out this is what you will do in the future to redeploy your application.
First we're going to make sure that every single file inside of our code editor is completely saved
if you're using Adam.
You can always check by looking up at the top tab at the top.
You'll notice if I have not saved the file you'll see that little blue circle right there.
And so when I save the file it changes back to next so that it works the same way on sublime.
And I think it works the same way on vs code well.
But anyways just make sure that every single file is saved.
Next we'll change back over to our code editor.
We're going to make sure that we are still inside of our server directory.
We will then inspect all the different files that we have waiting to be committed to get it's all run
the commands get status and I should see all the different files that I've changed appear on the screen.
And so right now I've changed the index file.
And so it's listing as being modified.
I will then add that file by writing get add Daut.
I will commit the file by running get ad commit dash him and then a commit message of which I will use
changed greeting and then I should see something that says okay commit complete.
We're good to go.
Now we will actually do that deployment over to Roku by running the command get push Heroku master just
like we did the first time so we'll run this command.
And when we do we'll then see all the same output that we had seen previously.
So the caching build installing node modules node version is blah blah blah all that kind of stuff.
And then after everything is done we can again verify that there were no errors deployed during deployment
by running the command Heroku logs.
Now running Heroku logs.
Remember this is not a required step is just something we can run to say hey did anything go wrong.
So when I run that you'll see something that says like ok.
Starting command with NPM start.
Here's the command we executed.
And it looks like we are now up and running.
So I can then run Heroku open again and verify that the deployment was successful.
And so I can now see on the screen by Buddy or essentially whatever my change was.
OK.
So that's pretty much it.
That's how we do follow up deployments in the future.
Remember you make your change you save your files you run get add Daut get commit and then get push.
So now that we know how to do follow up deployments in the future let's take a pause and actually start
working on the next feature.
I promise this time inside the next section so I'll see you in just a second.