1
00:00:01,100 --> 00:00:02,640
My project has started up.

2
00:00:02,690 --> 00:00:07,190
I don't see any distinct areas inside of here or anything like that so I can't go back over my browser

3
00:00:07,190 --> 00:00:09,740
and do a quick test.

4
00:00:09,790 --> 00:00:12,470
I still have my original window open at ticketing dot Dev.

5
00:00:12,490 --> 00:00:18,400
Remember that's how we access our application so I'm going to refresh this and I should still see content

6
00:00:18,430 --> 00:00:19,160
up here.

7
00:00:19,210 --> 00:00:19,650
Looks good.

8
00:00:21,230 --> 00:00:24,240
All right so that definitely means that everything is working as expected.

9
00:00:24,240 --> 00:00:28,590
Now at this point I would like to very quickly show you how we can very easily make a change to something

10
00:00:28,590 --> 00:00:34,260
inside of our common module and then reflect those changes inside of our off project.

11
00:00:34,350 --> 00:00:39,900
Let's imagine that we need to make a change to the common module maybe inside the index TSA file.

12
00:00:40,050 --> 00:00:40,520
Maybe.

13
00:00:40,530 --> 00:00:43,380
I don't know we need to add just a simple comment at the top.

14
00:00:43,510 --> 00:00:53,780
Opening the coming up here that says something like re export stuff from errors and Middleware is simple

15
00:00:53,780 --> 00:00:55,070
enough.

16
00:00:55,110 --> 00:01:00,000
Now if you wanted to get this change reflected or this update over to our auth project here's what we

17
00:01:00,000 --> 00:01:00,660
would do.

18
00:01:00,800 --> 00:01:07,510
We'd save these changes we would go back over to our terminal we would change into our off directory

19
00:01:07,540 --> 00:01:08,160
or not OK.

20
00:01:08,190 --> 00:01:11,020
What common we eventually want to be enough.

21
00:01:11,050 --> 00:01:12,960
Right now we want to be inside a common.

22
00:01:12,970 --> 00:01:15,700
So we're going to rebuild and publish our project.

23
00:01:15,880 --> 00:01:20,380
Recall that we put together a little script to automate that entire process for a real project.

24
00:01:20,380 --> 00:01:24,460
We don't really wanted that script but again for this course it's going to save us a decent amount of

25
00:01:24,460 --> 00:01:25,490
time.

26
00:01:25,690 --> 00:01:32,370
We'll do an NPM run hub that'll do the commit the version the build and then publish

27
00:01:35,870 --> 00:01:36,710
and there we go.

28
00:01:37,370 --> 00:01:39,890
So I'm up to version 1 point 0 9.

29
00:01:39,890 --> 00:01:42,750
Chances are you're not at version 1.0 0 9.

30
00:01:42,800 --> 00:01:47,420
I had to record some of the videos before this several times to get everything kind of working just

31
00:01:47,420 --> 00:01:48,090
right.

32
00:01:48,090 --> 00:01:51,050
And that's why I've got this higher version number here.

33
00:01:51,050 --> 00:01:53,270
So latest version is 1 point 0 9.

34
00:01:53,270 --> 00:01:57,800
We need to make sure that our auth project now uses Version 1.0 0 9 as well.

35
00:01:58,490 --> 00:02:09,020
So we'll change over to r and then all we really have to do is an NPM update SGI ticket slash comment.

36
00:02:09,020 --> 00:02:14,400
And of course you'll replace as free tickets with your organization name so I'll run that

37
00:02:17,200 --> 00:02:19,630
and very quickly we will see.

38
00:02:19,630 --> 00:02:20,290
There we go.

39
00:02:20,290 --> 00:02:26,250
Version 1.0 0 9 now that makes a change as usual to our packages on file.

40
00:02:26,580 --> 00:02:30,960
So if we go back over to scaffolds we're going to see that our image is being rebuilt.

41
00:02:30,960 --> 00:02:34,620
We're going to be installing all of our dependencies again which means that we should be getting at

42
00:02:34,650 --> 00:02:40,740
the latest version of that common module not going to let this just do its thing.

43
00:02:40,760 --> 00:02:41,390
You're really quick.

44
00:02:41,390 --> 00:02:46,000
Just so I can verify that this actually all occurred actually no reason.

45
00:02:46,030 --> 00:02:46,660
Well OK.

46
00:02:46,660 --> 00:02:48,250
There it goes.

47
00:02:48,250 --> 00:02:51,960
It always seems like sometimes it takes forever sometimes it doesn't take any time.

48
00:02:51,960 --> 00:02:52,100
OK.

49
00:02:52,120 --> 00:02:54,340
Simple enough looks like everything's restarting.

50
00:02:54,400 --> 00:02:59,350
But how do we actually know that our container is running the correct version of that dependency.

51
00:02:59,350 --> 00:03:04,690
Well we could actually kind of go into the container and just verify that everything worked as expected.

52
00:03:04,690 --> 00:03:08,130
Let me show you how I can open up another terminal window.

53
00:03:08,170 --> 00:03:10,820
I'm going to do a cube Seitel get pods.

54
00:03:11,110 --> 00:03:17,020
I'm going to find the pod running our authentication project and I'm going to try to start up a shell

55
00:03:17,020 --> 00:03:18,250
inside of that pod.

56
00:03:18,730 --> 00:03:22,750
So we're going to access the container inside there and tried to take a look at some of the different

57
00:03:22,750 --> 00:03:27,760
files inside of that container directly just to make sure we're running the latest version of our common

58
00:03:27,760 --> 00:03:28,970
project.

59
00:03:28,970 --> 00:03:35,680
It's going to copy that pod name and do a cube Seitel exact dash I.T. then the pod name and then SDH

60
00:03:35,740 --> 00:03:43,970
at the very end so I've now got a shell running inside of that container there is the node modules directory

61
00:03:44,030 --> 00:03:45,020
inside there.

62
00:03:45,050 --> 00:03:47,890
So I want to try to open up that node modules folder.

63
00:03:47,930 --> 00:03:50,960
I want to find our common module inside there.

64
00:03:50,970 --> 00:03:56,090
Now I just want to print out the package not just on file and make sure that we got version 1.0 0 9

65
00:03:56,090 --> 00:03:57,080
side there.

66
00:03:57,110 --> 00:03:59,710
So I will change into a node modules.

67
00:03:59,950 --> 00:04:05,450
I'll then change into my organization inside there which is SMG tickets.

68
00:04:05,570 --> 00:04:12,520
Again you'll need to update that organization name inside of there is the common folder.

69
00:04:12,660 --> 00:04:17,010
There's the packages on file and something is kind of interesting that you'll notice when we install

70
00:04:17,010 --> 00:04:19,310
this thing as a dependency.

71
00:04:19,380 --> 00:04:21,740
We didn't get the SRT folder or anything like that.

72
00:04:21,750 --> 00:04:25,740
All we got was the build directory and all the files inside there because remember we had sent that

73
00:04:25,740 --> 00:04:30,470
files property inside of our common modules packages on file.

74
00:04:30,480 --> 00:04:37,270
Now I will cut the package J some file just a printout all the information side there and if I scroll

75
00:04:37,270 --> 00:04:44,540
up a little bit I should be able to verify that I've got version 1.0 0 9.

76
00:04:44,690 --> 00:04:48,240
That means that my container is running the correct version of this module.

77
00:04:48,430 --> 00:04:51,520
The updated version 1.0 night right there OK.

78
00:04:51,550 --> 00:04:52,200
So that's it.

79
00:04:52,200 --> 00:04:53,520
That's how we do an update.

80
00:04:53,520 --> 00:04:56,780
Now of course you don't actually have to go to the process of verifying that package.

81
00:04:56,790 --> 00:04:57,850
It's on file.

82
00:04:57,870 --> 00:05:02,760
All we really have to do is run some changes inside of our common module.

83
00:05:02,760 --> 00:05:05,430
We're going to run that NPM run pub command.

84
00:05:05,430 --> 00:05:09,880
We'll do it in NPM updates inside of our project.

85
00:05:09,930 --> 00:05:10,880
And that's pretty much it.

86
00:05:10,920 --> 00:05:12,900
That's all we have to do.

87
00:05:12,930 --> 00:05:14,040
So it looks pretty good.

88
00:05:14,040 --> 00:05:18,780
We've got this common module that's going to make it really easy to create some additional services

89
00:05:18,780 --> 00:05:22,340
in the future such as the ticketing one they're we're gonna start here in just a second.

90
00:05:22,560 --> 00:05:26,930
And any time we need to make changes to the thing well we've got a strategy for it.

91
00:05:26,940 --> 00:05:29,520
All right enough with lecturing from me I'm kind of rattling on now.

92
00:05:29,520 --> 00:05:30,750
So pause right here.

93
00:05:30,750 --> 00:05:34,410
Let's kick off our ticketing service in the next video.