All right.
So this is it.
This is the moment of truth.
We're going to restart scaffold at our terminal as soon as we do so scaffold should attempt to build
this image that we listed inside of our scaffold config file using Google Cloud built it will then take
our off deployment and the ingress service config and apply them to our remote cluster.
So let's get to it.
First I want to go backwards.
My terminal.
I got to make sure that I shut down any previous version of scaffold that might still be running.
I'll then go to my uber Nettles or Docker window and just make sure I've got the correct context still
selected and then after that I'll do a scaffold Dev inside of my root project directory so as soon as
I do so scaffold is going to attempt to build our image remotely.
It's going to try to build it using Google Cloud built.
So again as a reminder all that building stuff is occurring using Google Cloud built.
We should actually be able to see the image build in process.
If we hop over to the Google cloud build dashboard really quickly.
So if I go back over to Google Cloud find the menu on the top left hand side I can then scroll way down
this menu to the tools section year tools right here and you'll see a cloud built I'll then select history
and I'll see my build listed right on here if I click on the build itself you'll see a lot of output
from the build process just about all the output you see right here probably looks identical to the
details from when we were building these images locally.
They'll see stuff inside of here like setting up that working directory copying over the package not
just on file doing the NPM install and so on eventually the image gets built and then it's pushed off
to our repository of images on Google Cloud.
So all these images are now being pushed to a Google Cloud repository of images no longer are we making
use of Docker Hub after this image is built scaffold is then going to attempt to create are off deployment
the service and apply our ingress rules to this cluster on Google Cloud.
So you'll see that the deployment inside of our logs over here was created.
There's the all service created and the Ingress was created as well.
And then eventually we get our console log so this logging information right here is coming out of our
pod running on a remote virtual machine on Google Cloud.
None of this stuff is running locally anymore.
Now I don't know about you but it is pretty awesome.
Pretty cool now in theory as we start to add in more pods more deployments more everything into our
cluster we're not going to start slowing down our local machine anymore because all that stuff is going
to be created on some local or cuse me some remote machine in Alaska we need to do is actually test
this stuff out in a browser and see if we could still connect.
So I'm going to once again try to visit are your l or our domain that we had set up inside of our host
file.
I'm going to try to get at our users slash current user route again.
So API users current user that's the route that should retrieve.
Hi there.
So I'm going to just take that you are L paste instead of a new tab I'm going to see that same kind
of your connection is not private again.
So again we're just going to ignore this for right now.
This is related to some nasty setup inside of ingress engine X if you go to advanced once again we cannot
seem to get around this.
So we're gonna use that kind of little work around command that we spoke about a little bit ago.
You just type into that window.
This is unsafe again.
We know what we're doing.
Rome really isn't happy what we're doing what we're doing here.
We'll eventually fix this but right now let's just get around it.
So I will type in.
This is on safe and there we go I've got high there appearing on the screen all right.
So this looks awesome Well we've got everything built.
The last thing I want mentioned here is that moving forward in the course I am probably not going to
be running all this stuff on the remote cluster.
Again this is for people out there who are watching this course who might have a little bit of an older
machine.
The reason this is relevant is that in a little bit or in the coming videos you're going to see that
my scaffolds e-mail file will revert back to its previous look.
So incoming videos you are going to see that I do not have a Google Cloud built in there.
You're going to see that I've got local push set to false.
You're going to see that I have an image of Steven Greider switch off and so on.
So in the coming videos it's really important for you.
This is up to you to make sure that any time we come into the scaffolds e-mail file you put the appropriate
image name in here.
So the image name that you should be using is USGS yours.
Then you're project I.D. and then the name of the directory or the image that we are building.
So in this case simply off.
So at some point in the future we are going to build an image called orders or an order service.
When we do so you are going to add inside of here this block but it will be orders right there and orders
right there instead.
So again that is up to you.
I may or may not recall or remember to tell you in the relevant videos to do that.
The other thing I want you to remember is that when we start to put together some other deployment files.
So if we put together say and orders deployment file you will need to enter in the appropriate image
name right there as well.
So you need to enter and USG OCR blah blah blah.
Because what I'm going to be writing in is something like that because I'm going to be running the stuff
on my local machine.
So again I can't say it enough is up to you to remember to make these changes because I know that some
people out there are going to unfortunately maybe not quite remember.
So again please just keep that in mind.
All right.
Well looks like all this stuff is working.
Now last thing I want to remind you is that at this point time you are now paying in theory you might
be showing through some free credits but you are in theory paying for this running cluster.
So if at some point time you decide to stop taking this course for any reason or if you say hey I'm
going to come back to this in like a month or two then you need to open up the cluster on Google Cloud
and click on delete right there and just delete this thing entirely because as long as this thing is
running again you are paying money for it.
So don't forget to hop on here and delete the cluster.
Well that is pretty much it.
So now that all this stuff is set up let's take a quick pause right here and we're going to continue
building our actual application in the next video.