Now put together some configuration for ingress engine x.
We're now going to open up the host file on our local machine and make sure that any time we tried to
navigate to ticketing dot Dev rather than going to the real ticketing dot dev that might be somewhere
online or on the Internet will instead redirect back to our local machine and access our ingress engine
X server.
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
host file is at Etsy slash hosts and that is the actual file that is not a domain right there.
And if you're on Windows it's going to be at that path right there.
As a quick reminder you need to open up this file with a Ed in administrator mode especially if you're
on Windows.
So I'm on Mac OS so I got to open up inside my code.
Ed the Etsy slash hosts file you'll see the change we made for our last application.
We're going to add in another entry just like it.
So I'll put in 1 2 7 0 0 1.
I'll make sure I put in the domain name right there equal to whatever I put back inside of my ingress
config file which is ticketing dot dev so now any time we try to go to ticketing dot Dev we're going
to instead connect back to our local machine will then save this file.
I get a little permissions there.
No problem.
And there we go.
So now to test this out we should be able to navigate to ticketing dot Dev inside of our browser when
we go to ticketing got Dev.
However that's just going to reach out to our ingress engine X server.
We don't really want to reach to the server directly.
We want to go to the root handler.
We had put together just a moment to go inside of our auth project.
So we specifically want to go to a route of ticketing dot Dev slash API users current user and that's
how we're going to access this row handler right here.
So let's go over to our browser and try that out right away inside of a new tab.
I'll go to ticketing dot Dev flash API users int user.
Now when you come to this your l you might see an error message like this right here.
Something it says your connection is not private.
I know this looks like a very scary error but this is just because of some of the default behavior inside
of ingress engine X you see by default ingress engine X is a web server that's going to try to use an
H2 CPS connection.
Unfortunately by default it uses what is called a self signed certificate.
Long story short chrome does not trust servers that use self signed certificates.
As a matter of fact if we come up to not secure right here and click on it and then click on certificate
it's going to say divinities ingress controller fake certificate and as you can guess yeah.
Chrome doesn't really like that.
Usually we could get around this message by clicking on advanced and then there would be a little link
down here.
But unfortunately kind of a double unfortunate thing.
The ingress server uses some configuration options that are going to prevent you from trying to circumvent
this warning screen.
And so right now it seems like we just can not reach out to that root handler at all.
Well again remember this is an area that's really only affecting us in this development environment.
And it's something that our users are never going to see once we properly can figure all this stuff.
So for right now we're just going to get this error message to go away because Chrome is just doing
something that we don't want it to do.
So to get that message to go away we are going to type this text right here into that tab.
We're going to type literally on your keyboard.
This is unsafe.
You don't have to select any inputs or anything like that you're just going to go over to this tab click
anywhere inside of it and then type out.
This is on safe and then that's gonna get that were error message to be dismissed and we should then
see.
Hi there.
Actually up here OK.
So now we are able to see some content on the screen.
That means we can reach out to our off server directly which is fantastic because now we can start to
put together some this authentication stuff test it manually for right now and eventually write some
automated tests.
Well let's take a pause right here and we'll continue in just a minute.