| Topic | Presenter | Summary | Duration | Tags | Quiz | Captions |
| ----------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------------------------------------------------------------------------------------------------------------------------- | ---- | -------- |
| CEF Updates | James Gray | In this video, James discusses recent changes (as of Aug. 2020) to the CEF platform, how to set the configs and where those changes occur | 27:41 | #DevTraining, #FridayTraining, #CEF, #ClarityTraining, #CEFUpdates, #CEF2020.1, #DeveloperTrainingVideos, #TrainingVideos | | N/A |00:00:00.090 --> 00:00:04.724 - OK well thank you guys a James and not to turn the floor over 00:00:04.724 --> 00:00:09.358 - to you. Uh, to talk about recent stuff updates and how to set the 00:00:09.358 --> 00:00:12.999 - the config's and where those changes a Kurd and will be 00:00:12.999 --> 00:00:16.640 - looking to do this more often. And thanks again for the 00:00:16.640 --> 00:00:20.943 - feedback from the team so we can kind of queue up things that 00:00:20.943 --> 00:00:22.929 - makes sense. James over to you. 00:00:23.630 --> 00:00:29.818 - OK, so higher grounds in DFO is the example of what the site 00:00:29.818 --> 00:00:32.198 - looks like when you have. 00:00:32.820 --> 00:00:36.351 - Just about everything turned on. You'll notice there's a lot more 00:00:36.351 --> 00:00:39.882 - at pools, and this is a Coors website that's using multiple 00:00:39.882 --> 00:00:43.413 - domains, so again, it's like the most complicated version of a 00:00:43.413 --> 00:00:47.265 - setup that we can do a regular website who's just doing one 00:00:47.265 --> 00:00:49.512 - domain does not need to do as 00:00:49.512 --> 00:00:53.620 - much stuff. Um involved in this uhm, so don't think that every 00:00:53.620 --> 00:00:57.940 - client has to do a lot of extra stuff every time now and you can 00:00:57.940 --> 00:01:01.684 - avoid doing all these API tools and just use one if you want. 00:01:01.684 --> 00:01:03.412 - Just be aware that you're going 00:01:03.412 --> 00:01:08.136 - to use. A single app pool that's going to take longer to spin up 00:01:08.136 --> 00:01:11.592 - every time, and that was the reason for part of the reason 00:01:11.592 --> 00:01:14.760 - for the branch office was the performance of them starting up 00:01:14.760 --> 00:01:18.216 - so that you can get back to work more quickly on individual 00:01:18.216 --> 00:01:20.808 - things. Other reasons include, like security of only loading 00:01:20.808 --> 00:01:23.688 - end points that matter to the vendor. Admin portal doesn't 00:01:23.688 --> 00:01:26.568 - need information about the brand stuff, it doesn't need stuff 00:01:26.568 --> 00:01:30.024 - that the admin portal would have access to, or even as checkout 00:01:30.024 --> 00:01:32.904 - process at the storefront has 'cause the vendor admin should 00:01:32.904 --> 00:01:34.344 - just be dealing with managing 00:01:34.344 --> 00:01:36.690 - vendor products. A man manipulating products 00:01:36.690 --> 00:01:39.930 - automatically injecting like the vendors record to the vendors 00:01:39.930 --> 00:01:43.530 - list of the product, etc. Auto filtering queries that are 00:01:43.530 --> 00:01:45.330 - coming back. Things like that. 00:01:46.200 --> 00:01:50.017 - Uh, so there's stuff like that. It's baked into these separate 00:01:50.017 --> 00:01:54.181 - portals that is not baked into the main API that literally just 00:01:54.181 --> 00:01:58.520 - loads everything. And that you know where this one might take 3 00:01:58.520 --> 00:02:02.252 - minutes to spin up. This one takes 45 seconds. This one takes 00:02:02.252 --> 00:02:06.295 - 30. This one takes 20. This one takes about 15. This one takes 00:02:06.295 --> 00:02:09.950 - about 10. Um second spin up. So if you're having directly work 00:02:09.950 --> 00:02:12.878 - on something and manipulate it, you know these will be your best 00:02:12.878 --> 00:02:15.562 - bet as far as actually, like, you know, turning Apple off, 00:02:15.562 --> 00:02:18.246 - rebuilding, running what you need to do, and dealing with it, 00:02:18.246 --> 00:02:20.686 - and then you can also individually just turn one if 00:02:20.686 --> 00:02:22.882 - you're only working in storefront right now and you 00:02:22.882 --> 00:02:26.298 - don't need to hop into admin at all, you could just turn the API 00:02:26.298 --> 00:02:28.738 - storefront on the other ones off, save yourself some cycles 00:02:28.738 --> 00:02:30.202 - and CPU and stuff if you're 00:02:30.202 --> 00:02:35.176 - limited. Um? There's also a couple of everything. 00:02:35.180 --> 00:02:41.646 - One there. So I will show that in just a second here, but this 00:02:41.646 --> 00:02:47.498 - MVC one is the NBC host that we built for IA, though it does 00:02:47.498 --> 00:02:52.514 - have the. The ODC part turned off. It's commented out of the 00:02:52.514 --> 00:02:57.112 - code so that I don't require a PC to run it. 00:02:57.160 --> 00:03:01.242 - In there and I need to expand this and show you what the 00:03:01.242 --> 00:03:06.148 - setups involve. Uh, OK. So First things first, you have your 00:03:06.148 --> 00:03:10.570 - check out. It is stuff. You'll notice that there's all these 00:03:10.570 --> 00:03:14.992 - service folders in here and they all correspond directly with the 00:03:14.992 --> 00:03:19.414 - same API. Once we got store admin storefront vendor at and 00:03:19.414 --> 00:03:23.434 - Brent Admin Admin and these these other apps are just 00:03:23.434 --> 00:03:27.454 - basically wrappers around what the main service one does and 00:03:27.454 --> 00:03:32.680 - then they filter by an attribute that is on the the end points. 00:03:32.740 --> 00:03:36.705 - Uh, that says that it is has to have a particular attribute on 00:03:36.705 --> 00:03:40.975 - it like this and I was in that energy can see it better. So 00:03:40.975 --> 00:03:44.940 - it'll say used in admin or used in store admin or using brand 00:03:44.940 --> 00:03:47.685 - admin using vendor admin using storefront. One attribute on 00:03:47.685 --> 00:03:51.650 - that end point route class that says that it should be loaded in 00:03:51.650 --> 00:03:55.615 - with that particular API. An example of that if I run over to 00:03:55.615 --> 00:03:58.970 - the service project I'll open a Visual Studio in the background 00:03:58.970 --> 00:04:02.935 - here so we can get that running, but I'll keep going with text. 00:04:02.990 --> 00:04:05.120 - Until then, uhm. 00:04:05.770 --> 00:04:10.320 - So products. Antoinette routes 00:04:13.330 --> 00:04:15.580 - Here. 00:04:17.600 --> 00:04:21.740 - Um, here there's get product by ID we're adding in that it's 00:04:21.740 --> 00:04:25.190 - used in storefront Houston store admin using brand admin and 00:04:25.190 --> 00:04:29.675 - using vendor admin. Notice how this one is not used in the full 00:04:29.675 --> 00:04:33.125 - admin because the full admin actually uses a different end 00:04:33.125 --> 00:04:34.505 - point to call it's. 00:04:34.550 --> 00:04:36.720 - Relevant information that's forward the self administration 00:04:36.720 --> 00:04:39.510 - portal that loads more data and doesn't require information 00:04:39.510 --> 00:04:42.920 - about the quantity and whatever is going on here. All that 00:04:42.920 --> 00:04:46.640 - subject is ignoring. It's all part of the product key is used 00:04:46.640 --> 00:04:50.360 - by Serpent alone. These other guys don't call it so it doesn't 00:04:50.360 --> 00:04:51.910 - load that information into that 00:04:51.910 --> 00:04:56.998 - API. Uh, another piece of what happens with that stuff is our 00:04:56.998 --> 00:05:01.414 - another reason that we were trimming that down is when I run 00:05:01.414 --> 00:05:05.462 - the key for that generates the typescript of the API. It 00:05:05.462 --> 00:05:09.878 - filters them out there as well, so we have far less typescript 00:05:09.878 --> 00:05:13.558 - going into that one big JavaScript file that that gets 00:05:13.558 --> 00:05:18.342 - output at the end in the UI projects. So I would go into 00:05:18.342 --> 00:05:23.494 - framework and if I look at store he ran out of the API folder. 00:05:24.140 --> 00:05:27.146 - There's the T4 here that was running clarity Congress 00:05:27.146 --> 00:05:30.486 - service. It generates all these files, but if it's only 00:05:30.486 --> 00:05:33.826 - generating files that include contents of end points that have 00:05:33.826 --> 00:05:37.500 - the use in storefront attribute, that's far less total that it 00:05:37.500 --> 00:05:41.174 - creates throughout this process. And if I look at like vendor 00:05:41.174 --> 00:05:45.182 - admin here, you'll notice it's got way fewer to it because it's 00:05:45.182 --> 00:05:48.856 - using the only ones that are loaded in vendor admin, so 00:05:48.856 --> 00:05:52.864 - there's a lot less going on here. And like the DTO classes 00:05:52.864 --> 00:05:56.760 - file is. 5000 lines instead of 00:05:56.760 --> 00:06:00.360 - 20,000 lines. 54137, so that's significantly less. JavaScript 00:06:00.360 --> 00:06:04.045 - is being generated on these things in order to reduce those 00:06:04.045 --> 00:06:07.395 - file sizes, which helps with the performance of the website 00:06:07.395 --> 00:06:10.410 - loading and all that stuff even after magnification and 00:06:10.410 --> 00:06:16.200 - everything. OK, so I know I'm driving around a little bit 00:06:16.200 --> 00:06:20.856 - here, but. So we have the admin, the brand admin store app in the 00:06:20.856 --> 00:06:24.860 - store front Fender and these are the break off ones and then the 00:06:24.860 --> 00:06:27.324 - service one just loads everything like it does 00:06:27.324 --> 00:06:29.788 - normally. There are individual endpoints like classes or 00:06:29.788 --> 00:06:32.868 - anything loaded inside. This is basically just a rapper that 00:06:32.868 --> 00:06:34.716 - says to load only that section. 00:06:34.730 --> 00:06:37.844 - Only rolled quote Unquote duplicating codes in here is 00:06:37.844 --> 00:06:41.304 - just you have the service application class and then it 00:06:41.304 --> 00:06:45.802 - will be appended. The name of the type that's on here so it's 00:06:45.802 --> 00:06:48.224 - admin and then we also have the. 00:06:48.250 --> 00:06:53.288 - The global asax file basically goes in and loads just about 00:06:53.288 --> 00:06:56.036 - everything or has all the same 00:06:56.036 --> 00:06:59.824 - content. In it, although we do strip out like a couple of these 00:06:59.824 --> 00:07:02.594 - global filters that are just, you know, specific around to 00:07:02.594 --> 00:07:05.087 - those particular domains like there's a vendor Brant Alterna 00:07:05.087 --> 00:07:08.411 - brand filter that don't get used in admin, but they would get 00:07:08.411 --> 00:07:11.458 - used in their brand filter or they might get used in 00:07:11.458 --> 00:07:14.228 - storefront stuff in there, but otherwise this file is identical 00:07:14.228 --> 00:07:17.829 - and I can use this like a simple winmerge to compare the two 00:07:17.829 --> 00:07:21.153 - files real quickly to make sure if there's any updates that can 00:07:21.153 --> 00:07:22.538 - propagate those out to these 00:07:22.538 --> 00:07:27.672 - copies. But when you go in and you said all that stuff up, 00:07:27.672 --> 00:07:31.132 - there's all these API domains that are involved. There's also 00:07:31.132 --> 00:07:34.592 - if you look in the user interface folder, there's this 00:07:34.592 --> 00:07:39.870 - image. This, like I said earlier, this came out of IA. 00:07:39.870 --> 00:07:44.457 - The idea was to make something host the staff admin portal 00:07:44.457 --> 00:07:50.295 - without the need to use DNN so it can run and now also deep 00:07:50.295 --> 00:07:51.963 - link into this stuff. 00:07:52.900 --> 00:07:58.170 - With, uh, without the need for tenants do anything, um. 00:07:59.000 --> 00:08:06.189 - Dallas uhm so it's an NBC app, but it basically has one route 00:08:06.189 --> 00:08:13.378 - in the one route is basically to load this index dot HTML file 00:08:13.378 --> 00:08:16.143 - that mimics what this admin. 00:08:16.150 --> 00:08:19.039 - The clarity admin skin did Indianen, which was to 00:08:19.039 --> 00:08:22.570 - basically just have the root here and load the stuff admin 00:08:22.570 --> 00:08:26.743 - body in the stuff admin site menu in the same way and load 00:08:26.743 --> 00:08:31.237 - those files. So when I publish this to a folder and I do have 00:08:31.237 --> 00:08:35.089 - the option here. So if I right click this and say publish. 00:08:38.120 --> 00:08:39.820 - What it will do? 00:08:40.550 --> 00:08:45.038 - Is I have a folder here that says MVC. This one should 00:08:45.038 --> 00:08:46.908 - actually not point to that. 00:08:47.700 --> 00:08:48.580 - I think. 00:08:50.540 --> 00:08:53.420 - Yeah, that should point to embassy admin, NBC vendor 00:08:53.420 --> 00:08:56.300 - admin so I have two deployments here, one for 00:08:56.300 --> 00:09:00.140 - admin and one for vendor admin in order to make those two 00:09:00.140 --> 00:09:03.660 - portals as MVC apps and then inside them I just replaced 00:09:03.660 --> 00:09:06.860 - the index dot HTML with values that are inside these. 00:09:08.030 --> 00:09:12.398 - And I apologize, some of this is going to make more sense if I'm 00:09:12.398 --> 00:09:16.142 - actually running through the full set up of what it does, and 00:09:16.142 --> 00:09:19.574 - all of those individual pieces, but in this backup Contacts here 00:09:19.574 --> 00:09:21.758 - I have a web config that is 00:09:21.758 --> 00:09:25.187 - enabling. Directory browse to, turn it off. Putting in rewrite 00:09:25.187 --> 00:09:28.960 - rules, enabling URL compression and these parts. I have to be 00:09:28.960 --> 00:09:32.390 - added to the web config that puts out by itself. 00:09:32.410 --> 00:09:35.926 - Not doing that on its own when it makes its deployments with 00:09:35.926 --> 00:09:39.149 - that published process and then inside this index dot HTML I'm 00:09:39.149 --> 00:09:42.958 - just swapping out like where the URLs are to read stuff from. So 00:09:42.958 --> 00:09:46.767 - one of the big things here because of this is a core site. 00:09:46.767 --> 00:09:51.162 - Is I needed? All of the API stuff to kind of come out of the 00:09:51.162 --> 00:09:54.092 - same place, including like where templates were going to be 00:09:54.092 --> 00:09:57.315 - loaded from, so I didn't have like different full domain names 00:09:57.315 --> 00:09:59.952 - trying to happen for the template caches because the 00:09:59.952 --> 00:10:03.761 - template caches all need to be one domain URL in order to load 00:10:03.761 --> 00:10:06.282 - correctly. Uh, that's the JavaScript HTML angular 00:10:06.282 --> 00:10:10.728 - template. Cash on it. So I had to create this API website here 00:10:10.728 --> 00:10:14.832 - and at the root here. Basically the API site itself has nothing. 00:10:14.832 --> 00:10:18.594 - It actually has an empty directory with two files in it 00:10:18.594 --> 00:10:22.356 - just says this is intentionally empty and do not delete it. 00:10:23.520 --> 00:10:27.680 - Um in all caps. So this folder here exists and it doesn't do 00:10:27.680 --> 00:10:30.880 - anything on its own. It's all about putting these virtual 00:10:30.880 --> 00:10:33.760 - directories and virtual applications that are all of our 00:10:33.760 --> 00:10:37.280 - APIs. Now, this APIs that full one, there's the API Admin, 00:10:37.280 --> 00:10:39.840 - Brand, Admin, Store Admin, Storefronts, vendor admin. We 00:10:39.840 --> 00:10:43.360 - also have the reporting the scheduler here and I have the 00:10:43.360 --> 00:10:46.560 - URL that links in the virtual directory for the images. 00:10:47.410 --> 00:10:50.479 - And the UI folder, which also includes the API reference that 00:10:50.479 --> 00:10:53.269 - gets documentation inside there and then I included the skins 00:10:53.269 --> 00:10:56.617 - folder, right have access to it. My hope though is to actually 00:10:56.617 --> 00:11:00.244 - remove the need for this one. I'm just using it as a temporary 00:11:00.244 --> 00:11:03.871 - work around for some CSS loading right now, but I do. I'm going 00:11:03.871 --> 00:11:07.777 - to do how to remove the need to have this one here from it. 00:11:08.470 --> 00:11:12.461 - But with this API domain, you're able to load all this stuff and 00:11:12.461 --> 00:11:15.531 - then the other websites that are actually hosting websites like 00:11:15.531 --> 00:11:18.601 - the admin portal, the Vendor Admin Portal, and the individual 00:11:18.601 --> 00:11:21.671 - store like storefronts. Those actually what I'll point at this 00:11:21.671 --> 00:11:25.048 - singular place to grab all of the information that it would 00:11:25.048 --> 00:11:26.890 - need better. What is trying to 00:11:26.890 --> 00:11:31.830 - do. That's the goal there. So we set up all these things here. 00:11:32.000 --> 00:11:35.648 - I have a website here that's vendor admin. It is pointed at 00:11:35.648 --> 00:11:38.992 - that MVC dash vendor admin site here thisis.net core MVC. That's 00:11:38.992 --> 00:11:42.944 - basically just acting as a rapper so that all he has to do 00:11:42.944 --> 00:11:46.896 - is load the index file at the index file starts to spa of 00:11:46.896 --> 00:11:50.240 - angular. Same thing for this stuff admin here which is the 00:11:50.240 --> 00:11:54.496 - main admin stuff here is just an index file that loads all of the 00:11:54.496 --> 00:11:58.752 - stuff admin parts in the browser and if I click on this let's see 00:11:58.752 --> 00:12:00.880 - if I can get it to load. 00:12:02.970 --> 00:12:05.078 - In my browser here. 00:12:06.420 --> 00:12:08.940 - So here's a vendor admin Anne. It's been too like mimic what 00:12:08.940 --> 00:12:11.670 - the stuff had been looks like, but it's very pared down to just 00:12:11.670 --> 00:12:16.607 - the product's part. Uhm, you see that it spun up really quickly 00:12:16.607 --> 00:12:21.040 - there and it should get into the page contents fairly quickly. 00:12:25.070 --> 00:12:26.330 - Take it in sweet time though. 00:12:27.120 --> 00:12:29.479 - And Meanwhile I will actually duplicate this 00:12:29.479 --> 00:12:31.164 - page and open the admin. 00:12:33.780 --> 00:12:35.916 - Anne, I will also open the. 00:12:36.560 --> 00:12:41.900 - A www.sitewhichistheirmainsite Which is running indianen and 00:12:41.900 --> 00:12:43.790 - then like a store 1. 00:12:49.770 --> 00:12:53.830 - OK, so since I'm not logged in anywhere it wants me to log in, 00:12:53.830 --> 00:12:57.310 - go ahead and log in with the clarity admin account which now 00:12:57.310 --> 00:12:58.470 - has access to everything. 00:13:03.330 --> 00:13:06.192 - And you'll notice that my login is actually shared 00:13:06.192 --> 00:13:09.372 - across all these domains that Sadie. I don't want that. 00:13:12.740 --> 00:13:16.874 - I need to redeploy this one so it has the deeply deep linking 00:13:16.874 --> 00:13:21.008 - fix on the NBC. OK so here is the vendor admin portal this 00:13:21.008 --> 00:13:23.870 - year. There's basically nothing in it, it's just managed 00:13:23.870 --> 00:13:28.004 - products. So I go to manage products and I can see you know 00:13:28.004 --> 00:13:31.502 - the vendor has been assigned to all these products. These are 00:13:31.502 --> 00:13:35.636 - the ones that it can see 194 but there's 195 Toyota prices. One 00:13:35.636 --> 00:13:39.452 - this was not assigned to. I thought about details page and I 00:13:39.452 --> 00:13:42.632 - can do all this stuff and immigration, but the important 00:13:42.632 --> 00:13:46.876 - part really is. That all of this information is running across 00:13:46.876 --> 00:13:51.298 - the wire from the API, higher ground step com API, vendor 00:13:51.298 --> 00:13:56.524 - admin. So it's using the cores and talking to this one API and 00:13:56.524 --> 00:13:59.740 - it doesn't matter which website I'm looking at. 00:14:00.920 --> 00:14:03.206 - It's going to the correct one. 00:14:04.150 --> 00:14:05.438 - For all this stuff. 00:14:06.180 --> 00:14:10.164 - They're all pointing at the same place in able to load template 00:14:10.164 --> 00:14:12.820 - caching everything all correctly from that one location. 00:14:13.340 --> 00:14:14.480 - Got mine refresh. 00:14:15.370 --> 00:14:20.296 - There we go. So here's the full staff admin view which has 00:14:20.296 --> 00:14:25.289 - everything. A man I can go jump around between web pages. Here 00:14:25.289 --> 00:14:30.455 - is like if I go to products view and then I filter the products. 00:14:30.455 --> 00:14:34.145 - I still have access to every product. Nothing is getting 00:14:34.145 --> 00:14:38.942 - filtered out here as a self admin I have access to all this 00:14:38.942 --> 00:14:42.263 - stuff and I can manipulate everything but the main 00:14:42.263 --> 00:14:45.215 - storefront website here www.site. This is where higher 00:14:45.215 --> 00:14:50.012 - grounds is is going to on board vendors to come and sell their 00:14:50.012 --> 00:14:51.488 - products also on board 00:14:51.488 --> 00:14:55.440 - companies. Like you know that would come in and sell those 00:14:55.440 --> 00:14:58.140 - products that would be have their own individual branded 00:14:58.140 --> 00:15:01.140 - websites to run their stuff throughout this thing. But at 00:15:01.140 --> 00:15:04.740 - the moment right here it's very simple. It isn't really know if 00:15:04.740 --> 00:15:08.040 - anything beyond the basic info would be going and doing more 00:15:08.040 --> 00:15:11.340 - work with that client to make this website more unique, but 00:15:11.340 --> 00:15:14.340 - then have the storefront ones be actual like websites with 00:15:14.340 --> 00:15:17.040 - catalogs in them that are limited to their individual 00:15:17.040 --> 00:15:20.040 - branding. All that stuff in there that's blue versus pink 00:15:20.040 --> 00:15:22.740 - that's being loaded through dynamic data that's attached to 00:15:22.740 --> 00:15:25.990 - the brands records. And the brand site domains records. 00:15:26.750 --> 00:15:30.225 - For filtering things on that 00:15:30.225 --> 00:15:33.230 - stuff. So they kind of all points back to keep clicking on 00:15:33.230 --> 00:15:34.490 - that Anita pin. That says stop 00:15:34.490 --> 00:15:38.434 - clicking it. Not all these tabs are here are the ones that I 00:15:38.434 --> 00:15:40.974 - care about, so vendor in everything they be able to 00:15:40.974 --> 00:15:43.768 - manipulate their stuff here and do that stuff there. And that 00:15:43.768 --> 00:15:46.816 - goes through this one which is pointed to an empty site. The 00:15:46.816 --> 00:15:49.864 - admin which is pointing to an NBC site that separate it has 00:15:49.864 --> 00:15:52.912 - its own index file to index files may be late talking weird 00:15:52.912 --> 00:15:55.706 - appointed stuff. The API domain has all of these up applications 00:15:55.706 --> 00:15:58.500 - inside it for what all these different things do. And then 00:15:58.500 --> 00:16:01.548 - there's the main stores website which you'll notice if I go down 00:16:01.548 --> 00:16:04.596 - in here we don't have any of that stuff here, 'cause it's 00:16:04.596 --> 00:16:06.374 - better to point at the API site 00:16:06.374 --> 00:16:09.254 - instead. A man, even the images directory. I don't 00:16:09.254 --> 00:16:11.162 - have that E Commerce one inch. 00:16:12.300 --> 00:16:15.556 - Here, because I'm telling it with settings to read it all 00:16:15.556 --> 00:16:19.404 - through the main site. Now the other aspect of this is I only 00:16:19.404 --> 00:16:20.588 - have one step checkout. 00:16:21.710 --> 00:16:24.916 - Um and this one step checkout is able to drive the data for all 00:16:24.916 --> 00:16:28.698 - of these separate things. With one set of settings, which is 00:16:28.698 --> 00:16:31.932 - really nice. Now if I had a situation where an individual 00:16:31.932 --> 00:16:35.166 - site need to be handled differently, I would have to set 00:16:35.166 --> 00:16:38.988 - up a second copy with its own settings setup and then a point 00:16:38.988 --> 00:16:42.810 - at any particular one of these, like these API ones like it was 00:16:42.810 --> 00:16:45.750 - supposed to be the storefront one that supposed to act 00:16:45.750 --> 00:16:48.396 - differently. I might point to a different directory that's 00:16:48.396 --> 00:16:51.336 - underneath that other copy of stuff, or admin or whatever. 00:16:51.336 --> 00:16:53.982 - Whichever one needs to be functioning differently in order 00:16:53.982 --> 00:16:56.334 - to do that. But if I look at 00:16:56.334 --> 00:17:00.034 - these apps settings. File, this is where a lot of the 00:17:00.034 --> 00:17:03.514 - complexities come from is. I'm telling it for the API 00:17:03.514 --> 00:17:06.994 - requests called this one slash API for API admin request, 00:17:06.994 --> 00:17:10.822 - school API admin telling it what the domain is and what 00:17:10.822 --> 00:17:14.302 - the relative URL is. If this was embedded under something 00:17:14.302 --> 00:17:17.086 - else, like excuse me under desktop modules, clarity, 00:17:17.086 --> 00:17:17.434 - Commerce. 00:17:18.570 --> 00:17:21.937 - Well, this would be the default value for it, so I wouldn't get 00:17:21.937 --> 00:17:24.527 - message with it, but I could specify, you know kumquat. 00:17:25.220 --> 00:17:29.462 - You know, as my custom path or whatever I need to do here, I 00:17:29.462 --> 00:17:33.098 - could do whatever I need to do inside the space. Those places 00:17:33.098 --> 00:17:36.431 - in specify where that stuff is coming from. On these things, 00:17:36.431 --> 00:17:39.764 - the UI is going to come from there. There is actually, 00:17:39.764 --> 00:17:42.491 - template overrides are going to be coming from the 00:17:42.491 --> 00:17:44.915 - individual skins and everything, and then it says 00:17:44.915 --> 00:17:47.945 - that goes by brand, which means that it's allowed to 00:17:47.945 --> 00:17:50.975 - look at the individual brands domain for something on those 00:17:50.975 --> 00:17:52.793 - individual pieces if it needs to. 00:17:54.030 --> 00:17:57.640 - From December Sinatras little squish, all of these routes that 00:17:57.640 --> 00:18:01.250 - happened throughout the website, like where the terms pages where 00:18:01.250 --> 00:18:05.221 - the login is, where, where your registration path is, where the 00:18:05.221 --> 00:18:08.831 - checkout is, those are all generated by brand, so whenever 00:18:08.831 --> 00:18:13.524 - he generates the link, go ahead. Just what is not by look up 00:18:13.524 --> 00:18:16.773 - method host look up method, not by look up. 00:18:17.500 --> 00:18:22.090 - Now I look at means it it's your tending to to give it the value 00:18:22.090 --> 00:18:25.456 - you're intentionally selling it at the root URL. Is this by 00:18:25.456 --> 00:18:29.740 - brand? It means that this URL is dynamic and it's going to be fed 00:18:29.740 --> 00:18:31.270 - by data from the database. 00:18:33.550 --> 00:18:38.520 - Just wait, yeah. So basically if I had the same thing here and I 00:18:38.520 --> 00:18:43.135 - said that site dot root URL, I would expect that this would be 00:18:43.135 --> 00:18:44.200 - dynamic from DB. 00:18:45.040 --> 00:18:47.200 - And you wouldn't actually fill this in because it's 00:18:47.200 --> 00:18:50.320 - being told to be do it. Be doing it by the brands of 00:18:50.320 --> 00:18:52.720 - site domain record. So by brand. So I would not 00:18:52.720 --> 00:18:55.360 - actually have this and I would like at most I would 00:18:55.360 --> 00:18:58.000 - have like a note here that said that this was dynamic. 00:18:59.520 --> 00:19:00.270 - Like that? 00:19:02.240 --> 00:19:05.256 - A dynamic from DB, whereas this version it says not by look up 00:19:05.256 --> 00:19:08.040 - and I'm intending to actually tell it or I would specify this 00:19:08.040 --> 00:19:10.824 - null mean that's always going to be relative to what I'm actually 00:19:10.824 --> 00:19:15.020 - looking at right now. Um on stuff. So I would just get rid 00:19:15.020 --> 00:19:19.030 - of this. But all these you know, these are pages within the 00:19:19.030 --> 00:19:21.740 - website that are part of the storefront. Like where's the 00:19:21.740 --> 00:19:24.721 - dashboard? Where is the store locator? Where is the check out? 00:19:24.721 --> 00:19:28.244 - Where is the cart? Was the quote cart all of these things would 00:19:28.244 --> 00:19:31.767 - be specified by data that's in the brand, so that it knows that 00:19:31.767 --> 00:19:34.477 - it's going to be reading that individual websites URL for 00:19:34.477 --> 00:19:37.458 - where stuff supposed to go. Now there's a secondary piece of 00:19:37.458 --> 00:19:40.981 - this that we used to use in towel that was also like there 00:19:40.981 --> 00:19:42.336 - was a witch on it. 00:19:42.880 --> 00:19:47.220 - And I'm going to say which right here, but I don't know the exact 00:19:47.220 --> 00:19:50.940 - name. You could say primary, which is the main URL that's on 00:19:50.940 --> 00:19:54.040 - the site domain or and then there's alternate one through 00:19:54.040 --> 00:19:57.760 - three, in which case, like if you had a bunch of separate 00:19:57.760 --> 00:20:01.170 - store websites that all wanted to redirect to one check out 00:20:01.170 --> 00:20:04.580 - page that had like an SSL certificate on it, the other 00:20:04.580 --> 00:20:08.300 - sides didn't have some websites to decide to do this kind of 00:20:08.300 --> 00:20:12.330 - thing, so they don't have to pay for like a multidomain wild card 00:20:12.330 --> 00:20:16.070 - SSL cert. They redirect all the checkouts to one check out 00:20:16.070 --> 00:20:19.700 - website. You could specify that there's a. There's the main URL, 00:20:19.700 --> 00:20:23.990 - which is the like store 1 higher ground, stab com, but then they 00:20:23.990 --> 00:20:26.630 - might have checkouts all point to check out.highergrounds.com 00:20:26.630 --> 00:20:30.920 - and that check out one is the one that has the SSL cert. 00:20:30.950 --> 00:20:32.290 - And it's singular fashion. 00:20:32.990 --> 00:20:35.537 - And you specify with the alternate one that checkout 00:20:35.537 --> 00:20:38.933 - URL and say that for the check out one which I would 00:20:38.933 --> 00:20:40.065 - do for down here. 00:20:42.410 --> 00:20:45.270 - That's the check out. One needs to use the alternate 00:20:45.270 --> 00:20:48.416 - one value inside that site domain record so that when it 00:20:48.416 --> 00:20:51.276 - goes to generate the checkout domain it's going to domain 00:20:51.276 --> 00:20:54.708 - links like when you're on the cart page and he says proceed 00:20:54.708 --> 00:20:57.854 - to check out that link would actually point over to check 00:20:57.854 --> 00:20:59.284 - out website instead on stuff. 00:21:01.870 --> 00:21:05.705 - And then I also have some other settings here that turns on like 00:21:05.705 --> 00:21:08.950 - brands turning on like this that has price rules. It's using 00:21:08.950 --> 00:21:11.900 - individual stores because not only is the brand itself the 00:21:11.900 --> 00:21:15.145 - branding of Home Depot versus Lowe's, they also have brick and 00:21:15.145 --> 00:21:18.685 - mortar stores that are on site locations that would need to go 00:21:18.685 --> 00:21:22.520 - where you could use indoor pick up or you know those kinds of 00:21:22.520 --> 00:21:26.650 - things so you want to make sure that you have the stores as well 00:21:26.650 --> 00:21:29.895 - and then this site also has vendors defenders going to be 00:21:29.895 --> 00:21:31.075 - able to come in. 00:21:31.720 --> 00:21:34.810 - Upload their products for the brains to pick from and 00:21:34.810 --> 00:21:37.282 - choose to sell as part of their environment. 00:21:38.780 --> 00:21:39.728 - For different things. 00:21:41.050 --> 00:21:46.538 - So all those pieces get gets up there. We're kind of at a time, 00:21:46.538 --> 00:21:51.242 - so that's the I would say. The highlights of the setup changes 00:21:51.242 --> 00:21:57.122 - and when it comes down to like if you want to just use like one 00:21:57.122 --> 00:21:59.474 - API, you could have it where. 00:21:59.510 --> 00:22:02.238 - You would basically you would need to include these, but you 00:22:02.238 --> 00:22:05.214 - would set the relative path to slash API just like this one 00:22:05.214 --> 00:22:07.446 - with all of these other settings. So the API 00:22:07.446 --> 00:22:09.926 - storefront, the API brand admin, you would just make him 00:22:09.926 --> 00:22:13.150 - all say slash API and then you have one API that you could 00:22:13.150 --> 00:22:16.126 - use. Any would just put them all in the same place. That 00:22:16.126 --> 00:22:19.102 - would be your local. You could have that config set up like 00:22:19.102 --> 00:22:21.086 - that so I would do something like this. 00:22:22.180 --> 00:22:26.856 - Uh, if James just as a side note, I think it would be really 00:22:26.856 --> 00:22:30.864 - helpful in the deployment tool if we could have like a planning 00:22:30.864 --> 00:22:34.872 - session with you and Taylor and go over how we could automate 00:22:34.872 --> 00:22:36.542 - this in the deployment tool. 00:22:37.130 --> 00:22:41.264 - And then I also think we should have just a standard for this 00:22:41.264 --> 00:22:44.444 - version. I'm guessing you're planning on that. That's in the 00:22:44.444 --> 00:22:48.578 - South Configs and maybe like to the right of each of them. A 00:22:48.578 --> 00:22:52.703 - little comment. Uh, that just kind of states what the options 00:22:52.703 --> 00:22:56.824 - are. Or maybe a separate Readme file. What do you guys say to 00:22:56.824 --> 00:22:59.994 - that? Do any of those sound helpful or not helpful? 00:23:01.380 --> 00:23:05.648 - That does sound very helpful. To better you know defaults have 00:23:05.648 --> 00:23:06.812 - config app settings. 00:23:07.420 --> 00:23:11.630 - Yeah, sorry. I was on mute. That sounds insanely helpful. 00:23:12.770 --> 00:23:18.722 - Awesome and so great. Is that sound reasonable on your end? An 00:23:18.722 --> 00:23:20.706 - Sir Duncan as well. 00:23:21.520 --> 00:23:22.960 - Yeah, I think that sounds fine. 00:23:23.710 --> 00:23:25.198 - Cool so grey. 00:23:25.860 --> 00:23:32.696 - Thank you. Yes and no. Pressing that their pieces and. 00:23:32.700 --> 00:23:35.060 - There's pieces of this. It's like like regular website. You 00:23:35.060 --> 00:23:36.476 - wouldn't even have any of this 00:23:36.476 --> 00:23:41.290 - stuff. With all that being the file default for with and 00:23:41.290 --> 00:23:45.230 - without and then it has the documentation for the variable 00:23:45.230 --> 00:23:50.352 - options and then we just need to coordinate so we can include it 00:23:50.352 --> 00:23:54.686 - into the deployment tool. Yeah, I mean, I was already planning 00:23:54.686 --> 00:23:59.020 - to use to at some point generate a T4 off of. 00:23:59.870 --> 00:24:01.958 - The properties file here. 00:24:02.960 --> 00:24:07.490 - It's all this stuff out that is such a good idea. I was about to 00:24:07.490 --> 00:24:11.114 - say that making all the notes and everything that are on this 00:24:11.114 --> 00:24:15.040 - great I just, I just haven't gotten to it yet. 'cause of high 00:24:15.040 --> 00:24:17.620 - priority client work? Um? 00:24:18.620 --> 00:24:21.870 - So all that stuff would be all like all this like these notes 00:24:21.870 --> 00:24:24.870 - and everything there will be into a file that would be inside 00:24:24.870 --> 00:24:25.620 - the Abbey reference 00:24:25.620 --> 00:24:27.710 - documentation, just like. Um? 00:24:28.260 --> 00:24:30.642 - See, this should see this page 00:24:30.642 --> 00:24:32.660 - loads. Go away. 00:24:33.510 --> 00:24:37.200 - Not sure this will load. 00:24:39.190 --> 00:24:43.105 - I don't think it will. Maybe I can do. 00:24:50.170 --> 00:24:55.300 - Maybe Master. 00:24:59.040 --> 00:25:02.280 - Yeah, so it would be embedded inside this page. 00:25:03.030 --> 00:25:05.284 - It's too bad you don't have an 00:25:05.284 --> 00:25:09.094 - amazing memory. Um, and I'll have like AA settings reference 00:25:09.094 --> 00:25:13.090 - at the top here for that page. And then we basically would 00:25:13.090 --> 00:25:17.086 - split out info similar to this for like each property can have 00:25:17.086 --> 00:25:21.082 - a section that you able to open up another look at different 00:25:21.082 --> 00:25:22.747 - settings. It therefore on a. 00:25:22.780 --> 00:25:26.663 - Be great, yeah. And obviously this the last government was run 00:25:26.663 --> 00:25:31.252 - did not work well because of this, so I need to fix that. 00:25:33.620 --> 00:25:35.622 - But any clothes I was playing I 00:25:35.622 --> 00:25:37.830 - was playing. Um? 00:25:38.390 --> 00:25:42.290 - Call let's. I mean it's it seems a lot more complicated than it 00:25:42.290 --> 00:25:46.490 - is, and you don't have to do any of this extra crap and less 00:25:46.490 --> 00:25:50.390 - you're actually trying to set up a site that needs all of that 00:25:50.390 --> 00:25:54.038 - stuff. Your website you can just run it up. 00:25:55.090 --> 00:25:59.192 - Pretty much like he used to, but we do have these extra things so 00:25:59.192 --> 00:26:02.415 - like the API storefront got broken off so that you could 00:26:02.415 --> 00:26:06.517 - have a faster load time. We just have a few more of those that 00:26:06.517 --> 00:26:10.619 - you can set up and then if you choose not to use them, that's 00:26:10.619 --> 00:26:14.135 - your choice, but then you have to add those couple of settings 00:26:14.135 --> 00:26:17.065 - which this is a recorded video so you'll have that 00:26:17.065 --> 00:26:19.702 - documentation and the are wonderful. New Mount guys will 00:26:19.702 --> 00:26:22.632 - come in and turn this into physical documentation for our 00:26:22.632 --> 00:26:26.441 - we key that will show you those changes that I just did inside 00:26:26.441 --> 00:26:29.050 - the screen here. Um? 00:26:29.600 --> 00:26:33.884 - For specifying that if you want to, that's it. Well, thank you 00:26:33.884 --> 00:26:37.811 - to the intern team members. We really appreciate that guys and 00:26:37.811 --> 00:26:42.095 - thank you James. Anne will look forward to the next round next 00:26:42.095 --> 00:26:46.022 - week if any. If anyone else has anything, feel free. Otherwise, 00:26:46.022 --> 00:26:49.949 - I hope you guys have a great weekend. Happy Friday. Yeah, 00:26:49.949 --> 00:26:53.876 - thanks so much. Everybody. I do have one minor thing about 00:26:53.876 --> 00:26:54.947 - updating app settings. 00:26:54.990 --> 00:26:58.796 - About changing the default or listing all of these. Rather at 00:26:58.796 --> 00:27:01.910 - listing everything in the app settings. Sometimes the default 00:27:01.910 --> 00:27:05.024 - change and what it's expecting is completely different than 00:27:05.024 --> 00:27:08.830 - what was in the app settings. Like what happened on Atlas. 00:27:08.830 --> 00:27:12.636 - Even if the other day. Just something from core was merged 00:27:12.636 --> 00:27:17.134 - in that didn't agree with one of the old app settings in it. 00:27:17.134 --> 00:27:20.940 - Wrecked stuff up, so having everything listed out in the app 00:27:20.940 --> 00:27:26.130 - settings is A and not relying on any of the defaults is kind of a 00:27:26.130 --> 00:27:28.110 - bad idea. Anyway, that's it. 00:27:29.050 --> 00:27:30.640 - Thanks, thank you. 00:27:31.480 --> 00:27:34.063 - Appreciate it. Feel free if anyone else has comments. 00:27:34.880 --> 00:27:37.139 - That that one alone. Yes, you probably saved someone 00:27:37.139 --> 00:27:39.649 - or multiple people a lot of time, so thank you.