The next logical step would be to deploy the website and this time using Google MCI and not from our
own computers.
So for that, I'm going to define a new stage.
I'm going to call this deeply.
Deployed to search.
I'm going to call it a job, but feel free to name it as you want, going to still use the note image
and now I have quite a few jobs that use the same image.
So what I can do right now is to take this out of here and put it right here on top so that by default,
no will be used for old jobs and all the other jobs that have noad.
I can simply remove it.
And the other jobs will have it by default.
So let's see how our script will look like.
Now, this time, we will not be working with Gatsby anymore and actually only need to see a tool from
search.
So for that reason we don't have to do NPM install.
We don't have to install Gatsby.
Seelie, we only need to install such as H.
So the comment to that is npm install, dash, dash, global search and that will be just enough to
install search.
Now we have installed search so we can call search.
They will need to specify our project dash dash project and this needs to be the path to our project.
So I'm going to say dot slash public because we are already inside.
The folder that contains the public folder and we only need to reference it, and now we need to specify
a domain as well.
So dishdasha domain and it needs to be something like something that surge that as age.
And this is something that you need to decide for yourself and of course, first to make sure that this
isn't taken anywhere and at the same time to make sure that this is unique enough so that nobody else
has taken it already.
Otherwise, of course, you will not be able to register it.
I have used this domain name generator just to find something unique or a bit more unusual, and I'll
be using the zone for my domain name.
But this is just because I don't have any better idea what to name my domain like, but feel free to
type in whatever you feel like.
So my domain will be installed on.
We don't need to specify any tokens because we already have them as environment variables, so search
will look for the variables that we have to find and will automatically use them to authenticate ourselves.
So that's about it, let's save it and give it a go.
There's one more thing we need to do now, we have to find a stage called deploy, but we haven't assigned
the job deployed to search to that one.
So by default, if you don't specify a stage for your job, then it will automatically go to the test
stage.
And this is something that we don't want at this step.
We first want to run our tests and then deploy.
So let's do that small change as well.
The stage.
And now our pipeline has three stages, a build stage, the test stage, which runs in parallel, and
only when both jobs with test have been executed and are successful will the deploy stage be executed.
So if any of the stages here fail, then the deploy will not be executed.
So it seems now that the pipeline has succeeded and let's look at the final stage to see how the logs
look like.
And you will see here, there's nothing very special, we have installed search and wit this command
surge.
This project was specifying the project and then with this domain, we are specifying the domain and
we are logging in.
And yes, success published in The Zone that Sociedad, that is.
And of course, in your case, it will be a different domain name.
So let's open this in the browser and see how it looks like.
So this is the website automatically being published using search as H and all done automatically through
catalepsy.