1
00:00:00,600 --> 00:00:03,900
In the last section we finished up our first time deployment process.

2
00:00:03,900 --> 00:00:07,100
Now at the end of the video I know I said that we're going to start working on our first feature.

3
00:00:07,140 --> 00:00:11,850
But you know what I realized we might as well just talk right now how we do additional deployments in

4
00:00:11,850 --> 00:00:12,620
the future.

5
00:00:12,630 --> 00:00:17,310
So now that we've committed and deployed for the very first time how do we deploy again after we've

6
00:00:17,310 --> 00:00:19,170
made some changes to our code base.

7
00:00:19,170 --> 00:00:23,060
So in practice it ends up being pretty straight forward.

8
00:00:23,070 --> 00:00:28,470
Let's make some arbitrary change sure codebase just to say hey we changed something song and flip back

9
00:00:28,470 --> 00:00:31,660
over to my index dot Jay has filed inside my code editor.

10
00:00:31,830 --> 00:00:34,330
I'm going to find the line that says red dot send.

11
00:00:34,620 --> 00:00:40,460
And I'm going to change the contents of this object to be by buddy.

12
00:00:40,530 --> 00:00:42,680
You know what the heck you change it to whatever you want.

13
00:00:42,780 --> 00:00:45,850
Absolutely anything doesn't matter just change it to something else.

14
00:00:46,080 --> 00:00:51,050
After we make that change we will then go through the process to deploy our application again.

15
00:00:51,270 --> 00:00:56,250
So from here on out this is what you will do in the future to redeploy your application.

16
00:00:56,520 --> 00:01:01,350
First we're going to make sure that every single file inside of our code editor is completely saved

17
00:01:01,860 --> 00:01:02,910
if you're using Adam.

18
00:01:02,940 --> 00:01:06,410
You can always check by looking up at the top tab at the top.

19
00:01:06,510 --> 00:01:11,010
You'll notice if I have not saved the file you'll see that little blue circle right there.

20
00:01:11,010 --> 00:01:16,710
And so when I save the file it changes back to next so that it works the same way on sublime.

21
00:01:16,710 --> 00:01:19,140
And I think it works the same way on vs code well.

22
00:01:19,470 --> 00:01:23,220
But anyways just make sure that every single file is saved.

23
00:01:23,310 --> 00:01:25,920
Next we'll change back over to our code editor.

24
00:01:25,950 --> 00:01:29,290
We're going to make sure that we are still inside of our server directory.

25
00:01:29,310 --> 00:01:35,460
We will then inspect all the different files that we have waiting to be committed to get it's all run

26
00:01:35,460 --> 00:01:41,460
the commands get status and I should see all the different files that I've changed appear on the screen.

27
00:01:41,690 --> 00:01:44,230
And so right now I've changed the index file.

28
00:01:44,340 --> 00:01:46,760
And so it's listing as being modified.

29
00:01:46,830 --> 00:01:50,330
I will then add that file by writing get add Daut.

30
00:01:50,550 --> 00:01:57,990
I will commit the file by running get ad commit dash him and then a commit message of which I will use

31
00:01:58,860 --> 00:02:04,410
changed greeting and then I should see something that says okay commit complete.

32
00:02:04,440 --> 00:02:05,470
We're good to go.

33
00:02:05,820 --> 00:02:13,620
Now we will actually do that deployment over to Roku by running the command get push Heroku master just

34
00:02:13,620 --> 00:02:17,250
like we did the first time so we'll run this command.

35
00:02:17,500 --> 00:02:21,480
And when we do we'll then see all the same output that we had seen previously.

36
00:02:21,670 --> 00:02:29,350
So the caching build installing node modules node version is blah blah blah all that kind of stuff.

37
00:02:29,440 --> 00:02:34,510
And then after everything is done we can again verify that there were no errors deployed during deployment

38
00:02:34,780 --> 00:02:37,600
by running the command Heroku logs.

39
00:02:37,840 --> 00:02:39,250
Now running Heroku logs.

40
00:02:39,250 --> 00:02:44,860
Remember this is not a required step is just something we can run to say hey did anything go wrong.

41
00:02:44,890 --> 00:02:47,730
So when I run that you'll see something that says like ok.

42
00:02:47,740 --> 00:02:50,200
Starting command with NPM start.

43
00:02:50,290 --> 00:02:51,970
Here's the command we executed.

44
00:02:52,150 --> 00:02:54,950
And it looks like we are now up and running.

45
00:02:55,150 --> 00:03:00,700
So I can then run Heroku open again and verify that the deployment was successful.

46
00:03:00,850 --> 00:03:05,090
And so I can now see on the screen by Buddy or essentially whatever my change was.

47
00:03:05,430 --> 00:03:05,750
OK.

48
00:03:05,770 --> 00:03:06,600
So that's pretty much it.

49
00:03:06,610 --> 00:03:09,240
That's how we do follow up deployments in the future.

50
00:03:09,250 --> 00:03:17,430
Remember you make your change you save your files you run get add Daut get commit and then get push.

51
00:03:17,500 --> 00:03:22,900
So now that we know how to do follow up deployments in the future let's take a pause and actually start

52
00:03:22,900 --> 00:03:24,410
working on the next feature.

53
00:03:24,430 --> 00:03:28,700
I promise this time inside the next section so I'll see you in just a second.