1 00:00:00,780 --> 00:00:04,300 In the last video, we discussed how this singular property right here really needs to be different, 2 00:00:04,300 --> 00:00:07,360 depending upon whether we are on the development or production that cluster. 3 00:00:07,960 --> 00:00:09,910 There are a couple of different ways for handling this. 4 00:00:10,140 --> 00:00:12,220 I'm gonna show you a very simple, straightforward way. 5 00:00:13,230 --> 00:00:17,280 To solve this, we're going to create a couple of additional directories inside sidebar in for a folder. 6 00:00:17,830 --> 00:00:22,890 I'm going to create another folder inside of infra called AIDS Dash Prod. 7 00:00:24,410 --> 00:00:28,250 And then another one called AIDS Dash Death. 8 00:00:29,340 --> 00:00:34,170 The idea here is that we are going to have summit number of manifests or Yamal files split between all 9 00:00:34,170 --> 00:00:37,170 three directories inside of our K Eights directory. 10 00:00:37,260 --> 00:00:42,150 We're going to have a series of manifest files that can be applied to any cluster that we connect to. 11 00:00:42,450 --> 00:00:44,760 So either a production or deployment cluster. 12 00:00:45,790 --> 00:00:50,380 Inside of the AIDS death directory, as you would guess, we're gonna play some config files inside 13 00:00:50,380 --> 00:00:55,780 of here that are only supposed to be applied to a development cluster and an inside of Cades prod are 14 00:00:55,780 --> 00:00:59,440 going to be manifest that are suppose to be applied to a production cluster. 15 00:01:00,450 --> 00:01:07,470 So now I'm going to take my ingress service file and I'm going to move it into the Kate's dev folder. 16 00:01:09,540 --> 00:01:14,430 Because this file, as it stands right now, should be only applied to a development cluster. 17 00:01:14,460 --> 00:01:19,350 I do not want to use this on my production cluster because that will expose or make use of a host of 18 00:01:19,350 --> 00:01:20,100 ticketing def. 19 00:01:21,430 --> 00:01:27,520 Then inside of Kate's broad, I'm going to make a new file, also called Ingress Savi Dot Yamal. 20 00:01:28,480 --> 00:01:34,720 I'm going to copy everything from the existing Ingress service file and pasted over here and now in 21 00:01:34,720 --> 00:01:39,640 theory, we will change this hostname right here to whatever our final domain name is. 22 00:01:40,000 --> 00:01:43,960 We have not yet purchased a domain name for our application, so we don't have anything to change that 23 00:01:43,960 --> 00:01:44,680 to just yet. 24 00:01:45,010 --> 00:01:49,300 But as soon as we do purchase a domain name for our app, we will come back to the broad file right 25 00:01:49,300 --> 00:01:51,100 here and update that most property. 26 00:01:54,730 --> 00:01:55,210 That's it. 27 00:01:55,270 --> 00:01:57,110 We now have these three different directories. 28 00:01:57,160 --> 00:02:02,440 And again, Cates is going to hold everything that as related to any given Cluster B at development 29 00:02:02,470 --> 00:02:03,130 or production. 30 00:02:03,480 --> 00:02:05,800 Devore's for just development and product is very broad. 31 00:02:06,680 --> 00:02:09,360 Now, by just moving these folders around and moving these files around. 32 00:02:09,400 --> 00:02:14,170 Well, we do have to fix up a couple of other things that are making use of these config files. 33 00:02:15,020 --> 00:02:18,490 So first off, we do have to make sure that we open up our scaffold YAML file. 34 00:02:20,400 --> 00:02:24,840 So whenever you run scaffold, we're gonna tell it that in addition to some config files we place inside 35 00:02:24,840 --> 00:02:25,890 that Kades directory. 36 00:02:26,130 --> 00:02:32,520 We also wanted to use some config files that are going to be inside of the K AIt's dev directory. 37 00:02:32,710 --> 00:02:34,350 So I can add in that line right there. 38 00:02:36,560 --> 00:02:40,400 We're also going to go back over to our get hub repository. 39 00:02:41,580 --> 00:02:47,340 We're gonna find the deploy manifest config file that we just put together and we were going to adjust 40 00:02:47,340 --> 00:02:51,630 that command right there and make sure that in addition to applying everything from the case folder, 41 00:02:51,840 --> 00:02:55,260 we also apply everything from the eights prod folder as well. 42 00:02:56,100 --> 00:02:57,330 So I'm going to edit this file. 43 00:02:59,180 --> 00:03:00,060 And I'll put in a little. 44 00:03:00,150 --> 00:03:01,290 And step right here. 45 00:03:02,760 --> 00:03:07,910 You've CDL apply dash f infra slash eights dashboard. 46 00:03:08,760 --> 00:03:13,620 I think that you might possibly be able to put in multiple directories to a dash F reference. 47 00:03:13,970 --> 00:03:15,450 I'm actually not one percent sure. 48 00:03:15,510 --> 00:03:16,830 Now that I'd say it out loud. 49 00:03:17,160 --> 00:03:20,820 So that would actually be a pretty good place to look at the documentation for that. 50 00:03:20,820 --> 00:03:24,240 You might be able to simplify this to just something that looks like that right there. 51 00:03:24,630 --> 00:03:27,260 But again, you might look at the documentation on your own. 52 00:03:29,430 --> 00:03:30,450 All committees file again. 53 00:03:32,870 --> 00:03:33,000 OK. 54 00:03:33,090 --> 00:03:36,390 So now we should be good to go once we buy a domain name. 55 00:03:36,510 --> 00:03:39,920 We're going to come back to that broad ingress service file, update the host. 56 00:03:40,080 --> 00:03:41,460 And that should pretty much be at. 57 00:03:42,500 --> 00:03:45,860 Well, I think that we're just about ready for an actual test run here. 58 00:03:46,210 --> 00:03:50,630 Now, before we do a test run, there's a little bit more setup we have to do specifically around our 59 00:03:50,630 --> 00:03:51,080 cluster. 60 00:03:51,470 --> 00:03:57,080 You might recall that our cluster expect there to be one or two secrets to find, such as the Jason 61 00:03:57,080 --> 00:03:58,450 Webb token key secret. 62 00:03:59,270 --> 00:04:04,060 So we define that a very long time ago and we made use of it inside of our off deployment. 63 00:04:04,760 --> 00:04:05,570 But here it is right here. 64 00:04:06,050 --> 00:04:10,060 Right now, our digital ocean cluster does not have a secret called JWT key. 65 00:04:10,730 --> 00:04:13,460 I think there might be one other secret somewhere inside of here as well. 66 00:04:13,610 --> 00:04:15,710 We have to mainly create inside of our cluster as well. 67 00:04:16,400 --> 00:04:21,290 So once we create those two secrets, one or two secrets will then be able to test out this entire float 68 00:04:21,470 --> 00:04:22,910 and then start to finish things up.