1
00:00:01,010 --> 00:00:06,590
We just did some Cuban 80s set up on our expiration service but we did forget one little step we forgot

2
00:00:06,590 --> 00:00:10,060
to set up that file sinking inside of our scaffold e-mail file.

3
00:00:10,070 --> 00:00:12,170
I can open up my scaffold ammo file.

4
00:00:12,170 --> 00:00:16,780
I'm going to scroll down to the bottom the last entry instead of yours should be for orders.

5
00:00:16,790 --> 00:00:19,190
I'm going to copy paste that thing down.

6
00:00:19,190 --> 00:00:20,540
I'll fix up some indentation

7
00:00:23,720 --> 00:00:30,820
and then I'll change orders and orders to expiration instead of expiration and expiration.

8
00:00:30,840 --> 00:00:36,240
Now we should have all that file thinking stuff set up for the expiration service as well and then going

9
00:00:36,240 --> 00:00:41,100
to say this file and I'm going to go back over to my terminal and see what scaffold is doing.

10
00:00:41,100 --> 00:00:48,420
Now quick note if you go back over a scaffold you might see your image get rebuilt though something

11
00:00:48,420 --> 00:00:53,460
like this right here it might try to rebuild your image and you might eventually see something it says

12
00:00:53,520 --> 00:00:56,000
unknown response manifest for blah blah blah.

13
00:00:56,010 --> 00:00:57,930
UNKNOWN If you see that.

14
00:00:57,930 --> 00:00:59,220
No problem whatsoever.

15
00:00:59,220 --> 00:01:01,760
All you gotta do is restart scaffold.

16
00:01:01,980 --> 00:01:03,300
So I'm going to close scaffold down

17
00:01:06,390 --> 00:01:07,460
and they'll start it back up.

18
00:01:08,710 --> 00:01:09,790
Oh scaffold

19
00:01:13,130 --> 00:01:18,020
now when everything gets graded again we should see that expiration serve it seeing the expiration deployment

20
00:01:18,050 --> 00:01:19,760
or the pod start to get lunch

21
00:01:24,300 --> 00:01:28,350
I do eventually get my expiration service coming up which is great but you'll also notice I'm getting

22
00:01:28,350 --> 00:01:32,050
some errors inside of you're about unable to connect to the Internet service.

23
00:01:32,130 --> 00:01:32,970
That's totally fine.

24
00:01:32,970 --> 00:01:39,270
Essentially our tickets service and probably some others here are starting to boot up before the Natsumi

25
00:01:39,270 --> 00:01:41,740
server is live and we can connect to it.

26
00:01:41,820 --> 00:01:46,060
Those services should automatically restart eventually but just in case they don't.

27
00:01:46,080 --> 00:01:56,420
In order to fix that we can do a cube Seitel get pods and then manually restart our orders deployment

28
00:01:56,450 --> 00:01:59,290
tickets deployment and possibly expiration as well.

29
00:01:59,450 --> 00:02:05,720
So to manually restart those things I would copy the name and do a cube Seitel delete odd and then put

30
00:02:05,720 --> 00:02:08,880
the name in and I'll do the same for tickets as well.

31
00:02:11,050 --> 00:02:18,500
Though cubes EDL delete pod and then the name when those things automatically get relaunched we should

32
00:02:18,500 --> 00:02:20,340
then be able to connect to it and that's.

33
00:02:20,530 --> 00:02:24,860
Yep looks good looks good and it looks like the expiration service is connected as well.

34
00:02:25,770 --> 00:02:28,240
Yeah so looks like I'm small green across the board.

35
00:02:28,250 --> 00:02:32,130
Let's take a pause right here and continue with a bull J.S. in just a moment.