1
00:00:00,590 --> 00:00:01,000
All right.

2
00:00:01,010 --> 00:00:01,730
So this is it.

3
00:00:01,730 --> 00:00:03,160
This is the moment of truth.

4
00:00:03,170 --> 00:00:08,300
We're going to restart scaffold at our terminal as soon as we do so scaffold should attempt to build

5
00:00:08,300 --> 00:00:13,670
this image that we listed inside of our scaffold config file using Google Cloud built it will then take

6
00:00:13,730 --> 00:00:19,010
our off deployment and the ingress service config and apply them to our remote cluster.

7
00:00:19,010 --> 00:00:20,460
So let's get to it.

8
00:00:20,690 --> 00:00:21,610
First I want to go backwards.

9
00:00:21,650 --> 00:00:22,360
My terminal.

10
00:00:22,370 --> 00:00:26,880
I got to make sure that I shut down any previous version of scaffold that might still be running.

11
00:00:26,980 --> 00:00:31,790
I'll then go to my uber Nettles or Docker window and just make sure I've got the correct context still

12
00:00:31,790 --> 00:00:41,530
selected and then after that I'll do a scaffold Dev inside of my root project directory so as soon as

13
00:00:41,530 --> 00:00:45,170
I do so scaffold is going to attempt to build our image remotely.

14
00:00:45,280 --> 00:00:48,090
It's going to try to build it using Google Cloud built.

15
00:00:48,250 --> 00:00:53,050
So again as a reminder all that building stuff is occurring using Google Cloud built.

16
00:00:53,230 --> 00:00:56,230
We should actually be able to see the image build in process.

17
00:00:56,260 --> 00:00:59,970
If we hop over to the Google cloud build dashboard really quickly.

18
00:01:00,130 --> 00:01:05,890
So if I go back over to Google Cloud find the menu on the top left hand side I can then scroll way down

19
00:01:05,890 --> 00:01:14,000
this menu to the tools section year tools right here and you'll see a cloud built I'll then select history

20
00:01:15,400 --> 00:01:21,330
and I'll see my build listed right on here if I click on the build itself you'll see a lot of output

21
00:01:21,330 --> 00:01:26,630
from the build process just about all the output you see right here probably looks identical to the

22
00:01:26,630 --> 00:01:29,430
details from when we were building these images locally.

23
00:01:29,570 --> 00:01:33,740
They'll see stuff inside of here like setting up that working directory copying over the package not

24
00:01:33,740 --> 00:01:39,740
just on file doing the NPM install and so on eventually the image gets built and then it's pushed off

25
00:01:40,190 --> 00:01:43,950
to our repository of images on Google Cloud.

26
00:01:44,030 --> 00:01:49,790
So all these images are now being pushed to a Google Cloud repository of images no longer are we making

27
00:01:49,790 --> 00:01:58,790
use of Docker Hub after this image is built scaffold is then going to attempt to create are off deployment

28
00:01:59,180 --> 00:02:04,940
the service and apply our ingress rules to this cluster on Google Cloud.

29
00:02:05,070 --> 00:02:08,050
So you'll see that the deployment inside of our logs over here was created.

30
00:02:08,050 --> 00:02:11,530
There's the all service created and the Ingress was created as well.

31
00:02:11,780 --> 00:02:17,600
And then eventually we get our console log so this logging information right here is coming out of our

32
00:02:17,600 --> 00:02:22,160
pod running on a remote virtual machine on Google Cloud.

33
00:02:22,190 --> 00:02:24,810
None of this stuff is running locally anymore.

34
00:02:24,810 --> 00:02:28,430
Now I don't know about you but it is pretty awesome.

35
00:02:28,430 --> 00:02:34,140
Pretty cool now in theory as we start to add in more pods more deployments more everything into our

36
00:02:34,140 --> 00:02:39,060
cluster we're not going to start slowing down our local machine anymore because all that stuff is going

37
00:02:39,060 --> 00:02:46,220
to be created on some local or cuse me some remote machine in Alaska we need to do is actually test

38
00:02:46,220 --> 00:02:49,240
this stuff out in a browser and see if we could still connect.

39
00:02:49,310 --> 00:02:53,960
So I'm going to once again try to visit are your l or our domain that we had set up inside of our host

40
00:02:53,960 --> 00:02:54,630
file.

41
00:02:54,660 --> 00:02:59,030
I'm going to try to get at our users slash current user route again.

42
00:02:59,030 --> 00:03:03,810
So API users current user that's the route that should retrieve.

43
00:03:03,820 --> 00:03:05,110
Hi there.

44
00:03:05,110 --> 00:03:10,360
So I'm going to just take that you are L paste instead of a new tab I'm going to see that same kind

45
00:03:10,360 --> 00:03:13,010
of your connection is not private again.

46
00:03:13,030 --> 00:03:15,130
So again we're just going to ignore this for right now.

47
00:03:15,130 --> 00:03:21,370
This is related to some nasty setup inside of ingress engine X if you go to advanced once again we cannot

48
00:03:21,380 --> 00:03:22,450
seem to get around this.

49
00:03:22,520 --> 00:03:26,700
So we're gonna use that kind of little work around command that we spoke about a little bit ago.

50
00:03:26,870 --> 00:03:28,260
You just type into that window.

51
00:03:28,280 --> 00:03:30,480
This is unsafe again.

52
00:03:30,590 --> 00:03:32,210
We know what we're doing.

53
00:03:32,270 --> 00:03:35,280
Rome really isn't happy what we're doing what we're doing here.

54
00:03:35,330 --> 00:03:38,020
We'll eventually fix this but right now let's just get around it.

55
00:03:38,060 --> 00:03:38,720
So I will type in.

56
00:03:38,750 --> 00:03:46,430
This is on safe and there we go I've got high there appearing on the screen all right.

57
00:03:46,500 --> 00:03:50,710
So this looks awesome Well we've got everything built.

58
00:03:50,710 --> 00:03:55,960
The last thing I want mentioned here is that moving forward in the course I am probably not going to

59
00:03:55,960 --> 00:03:58,910
be running all this stuff on the remote cluster.

60
00:03:58,930 --> 00:04:02,860
Again this is for people out there who are watching this course who might have a little bit of an older

61
00:04:02,890 --> 00:04:04,470
machine.

62
00:04:04,520 --> 00:04:08,630
The reason this is relevant is that in a little bit or in the coming videos you're going to see that

63
00:04:08,630 --> 00:04:13,010
my scaffolds e-mail file will revert back to its previous look.

64
00:04:13,220 --> 00:04:18,710
So incoming videos you are going to see that I do not have a Google Cloud built in there.

65
00:04:18,710 --> 00:04:21,650
You're going to see that I've got local push set to false.

66
00:04:21,710 --> 00:04:27,020
You're going to see that I have an image of Steven Greider switch off and so on.

67
00:04:27,050 --> 00:04:30,240
So in the coming videos it's really important for you.

68
00:04:30,350 --> 00:04:36,020
This is up to you to make sure that any time we come into the scaffolds e-mail file you put the appropriate

69
00:04:36,080 --> 00:04:37,910
image name in here.

70
00:04:37,910 --> 00:04:42,210
So the image name that you should be using is USGS yours.

71
00:04:42,890 --> 00:04:47,480
Then you're project I.D. and then the name of the directory or the image that we are building.

72
00:04:47,480 --> 00:04:48,700
So in this case simply off.

73
00:04:49,140 --> 00:04:54,890
So at some point in the future we are going to build an image called orders or an order service.

74
00:04:54,890 --> 00:05:03,200
When we do so you are going to add inside of here this block but it will be orders right there and orders

75
00:05:03,230 --> 00:05:04,250
right there instead.

76
00:05:04,400 --> 00:05:06,230
So again that is up to you.

77
00:05:06,290 --> 00:05:12,810
I may or may not recall or remember to tell you in the relevant videos to do that.

78
00:05:12,840 --> 00:05:17,460
The other thing I want you to remember is that when we start to put together some other deployment files.

79
00:05:17,460 --> 00:05:22,080
So if we put together say and orders deployment file you will need to enter in the appropriate image

80
00:05:22,080 --> 00:05:23,160
name right there as well.

81
00:05:23,520 --> 00:05:26,050
So you need to enter and USG OCR blah blah blah.

82
00:05:26,220 --> 00:05:30,210
Because what I'm going to be writing in is something like that because I'm going to be running the stuff

83
00:05:30,240 --> 00:05:31,420
on my local machine.

84
00:05:31,500 --> 00:05:36,120
So again I can't say it enough is up to you to remember to make these changes because I know that some

85
00:05:36,120 --> 00:05:39,480
people out there are going to unfortunately maybe not quite remember.

86
00:05:39,480 --> 00:05:42,040
So again please just keep that in mind.

87
00:05:42,060 --> 00:05:42,390
All right.

88
00:05:42,510 --> 00:05:44,390
Well looks like all this stuff is working.

89
00:05:44,520 --> 00:05:49,140
Now last thing I want to remind you is that at this point time you are now paying in theory you might

90
00:05:49,140 --> 00:05:54,430
be showing through some free credits but you are in theory paying for this running cluster.

91
00:05:54,480 --> 00:05:59,490
So if at some point time you decide to stop taking this course for any reason or if you say hey I'm

92
00:05:59,490 --> 00:06:04,980
going to come back to this in like a month or two then you need to open up the cluster on Google Cloud

93
00:06:05,820 --> 00:06:10,140
and click on delete right there and just delete this thing entirely because as long as this thing is

94
00:06:10,140 --> 00:06:12,720
running again you are paying money for it.

95
00:06:12,840 --> 00:06:17,170
So don't forget to hop on here and delete the cluster.

96
00:06:17,230 --> 00:06:18,430
Well that is pretty much it.

97
00:06:18,430 --> 00:06:22,540
So now that all this stuff is set up let's take a quick pause right here and we're going to continue

98
00:06:22,570 --> 00:06:25,060
building our actual application in the next video.