1 00:00:01,490 --> 00:00:04,550 Now put together some configuration for ingress engine x. 2 00:00:04,550 --> 00:00:08,300 We're now going to open up the host file on our local machine and make sure that any time we tried to 3 00:00:08,300 --> 00:00:13,040 navigate to ticketing dot Dev rather than going to the real ticketing dot dev that might be somewhere 4 00:00:13,040 --> 00:00:18,560 online or on the Internet will instead redirect back to our local machine and access our ingress engine 5 00:00:18,560 --> 00:00:19,740 X server. 6 00:00:20,110 --> 00:00:25,310 So to do so we're going to open up our host file as a quick reminder if you're on Mac OS or Linux your 7 00:00:25,310 --> 00:00:30,420 host file is at Etsy slash hosts and that is the actual file that is not a domain right there. 8 00:00:30,530 --> 00:00:34,610 And if you're on Windows it's going to be at that path right there. 9 00:00:34,610 --> 00:00:40,070 As a quick reminder you need to open up this file with a Ed in administrator mode especially if you're 10 00:00:40,070 --> 00:00:40,840 on Windows. 11 00:00:41,510 --> 00:00:44,110 So I'm on Mac OS so I got to open up inside my code. 12 00:00:44,130 --> 00:00:50,510 Ed the Etsy slash hosts file you'll see the change we made for our last application. 13 00:00:50,510 --> 00:00:53,010 We're going to add in another entry just like it. 14 00:00:53,010 --> 00:00:55,820 So I'll put in 1 2 7 0 0 1. 15 00:00:55,850 --> 00:01:00,800 I'll make sure I put in the domain name right there equal to whatever I put back inside of my ingress 16 00:01:00,800 --> 00:01:08,030 config file which is ticketing dot dev so now any time we try to go to ticketing dot Dev we're going 17 00:01:08,030 --> 00:01:12,060 to instead connect back to our local machine will then save this file. 18 00:01:12,060 --> 00:01:13,320 I get a little permissions there. 19 00:01:13,350 --> 00:01:14,310 No problem. 20 00:01:16,090 --> 00:01:18,160 And there we go. 21 00:01:18,190 --> 00:01:23,980 So now to test this out we should be able to navigate to ticketing dot Dev inside of our browser when 22 00:01:23,980 --> 00:01:24,940 we go to ticketing got Dev. 23 00:01:24,940 --> 00:01:28,990 However that's just going to reach out to our ingress engine X server. 24 00:01:29,050 --> 00:01:31,150 We don't really want to reach to the server directly. 25 00:01:31,150 --> 00:01:33,090 We want to go to the root handler. 26 00:01:33,130 --> 00:01:35,920 We had put together just a moment to go inside of our auth project. 27 00:01:36,250 --> 00:01:43,360 So we specifically want to go to a route of ticketing dot Dev slash API users current user and that's 28 00:01:43,360 --> 00:01:46,000 how we're going to access this row handler right here. 29 00:01:46,380 --> 00:01:51,060 So let's go over to our browser and try that out right away inside of a new tab. 30 00:01:51,060 --> 00:01:58,920 I'll go to ticketing dot Dev flash API users int user. 31 00:01:58,930 --> 00:02:03,400 Now when you come to this your l you might see an error message like this right here. 32 00:02:03,400 --> 00:02:06,160 Something it says your connection is not private. 33 00:02:06,190 --> 00:02:11,200 I know this looks like a very scary error but this is just because of some of the default behavior inside 34 00:02:11,200 --> 00:02:16,780 of ingress engine X you see by default ingress engine X is a web server that's going to try to use an 35 00:02:16,870 --> 00:02:19,030 H2 CPS connection. 36 00:02:19,030 --> 00:02:23,360 Unfortunately by default it uses what is called a self signed certificate. 37 00:02:23,380 --> 00:02:28,630 Long story short chrome does not trust servers that use self signed certificates. 38 00:02:28,630 --> 00:02:33,460 As a matter of fact if we come up to not secure right here and click on it and then click on certificate 39 00:02:34,240 --> 00:02:39,580 it's going to say divinities ingress controller fake certificate and as you can guess yeah. 40 00:02:39,580 --> 00:02:41,290 Chrome doesn't really like that. 41 00:02:41,530 --> 00:02:45,850 Usually we could get around this message by clicking on advanced and then there would be a little link 42 00:02:45,850 --> 00:02:46,570 down here. 43 00:02:46,750 --> 00:02:51,070 But unfortunately kind of a double unfortunate thing. 44 00:02:51,070 --> 00:02:56,410 The ingress server uses some configuration options that are going to prevent you from trying to circumvent 45 00:02:56,410 --> 00:02:57,310 this warning screen. 46 00:02:57,630 --> 00:03:01,720 And so right now it seems like we just can not reach out to that root handler at all. 47 00:03:01,720 --> 00:03:07,750 Well again remember this is an area that's really only affecting us in this development environment. 48 00:03:07,900 --> 00:03:12,190 And it's something that our users are never going to see once we properly can figure all this stuff. 49 00:03:12,190 --> 00:03:17,170 So for right now we're just going to get this error message to go away because Chrome is just doing 50 00:03:17,170 --> 00:03:19,770 something that we don't want it to do. 51 00:03:19,810 --> 00:03:26,710 So to get that message to go away we are going to type this text right here into that tab. 52 00:03:26,710 --> 00:03:28,530 We're going to type literally on your keyboard. 53 00:03:28,600 --> 00:03:29,800 This is unsafe. 54 00:03:29,800 --> 00:03:33,910 You don't have to select any inputs or anything like that you're just going to go over to this tab click 55 00:03:33,910 --> 00:03:35,800 anywhere inside of it and then type out. 56 00:03:35,800 --> 00:03:43,290 This is on safe and then that's gonna get that were error message to be dismissed and we should then 57 00:03:43,290 --> 00:03:43,630 see. 58 00:03:43,650 --> 00:03:44,160 Hi there. 59 00:03:44,160 --> 00:03:48,050 Actually up here OK. 60 00:03:48,090 --> 00:03:50,770 So now we are able to see some content on the screen. 61 00:03:50,790 --> 00:03:56,310 That means we can reach out to our off server directly which is fantastic because now we can start to 62 00:03:56,310 --> 00:04:00,930 put together some this authentication stuff test it manually for right now and eventually write some 63 00:04:00,990 --> 00:04:02,780 automated tests. 64 00:04:02,840 --> 00:04:05,580 Well let's take a pause right here and we'll continue in just a minute.