In this video we'll see how to add our newly built in Genex install as a linnik Service and how to update
engine X without any downtime whether this be did change change in its core or simply to add extra modules.
We could of course simply stop and start engine X were things in X executable but running it as a linnik
service means other programs can interact with it much easier and make for an all round more standard
experience.
I'm back on a custom board of engine X. one point nine point two on a boon to fourteen point in exactly
as in the previous video.
And obviously when we try and run service engine start we get unrecognized service as engine hasn't
yet been added as a clinic service.
To add this we need to create an initial script for engine X which we can simply download from Engine
X Weeki site so we'll head over to weeky dot engineers dot in its scripts where you'll see a list of
in its script for different operating systems and even variations of those scripts.
I'm going to go to the Ubuntu section and just navigate to this standard in its script.
On the main page we can see the actual script Shaw Stonier.
But I'm going to go ahead to the project page and like many Google Code projects.
This one has moved to get hub.
And here we are.
So the project rebo contains some docs here which will look at in a minute but first we want to go and
get the actual in its script year.
And I'll copy this link and head back over to my terminal.
We want to put this file in see init don't die as this is where all the initial scripts for different
linnik services live.
Just download the script here.
And for Linux to know about this new script we need to load it by running update dash our C dot B and
then a f flag.
Engine X defaults.
We have a permissions error though so we'll fix that by making the script executable.
And try again.
And this time we get.
You don't have permissions to execute in generics.
Now this might again seem like a permissions error but what's actually happening here is that the init
script expect so engine X installed to be located in all the default bold locations.
Of course we made some changes when configuring our board.
So we need to tell them in a script about those changes.
If we look at they need script read me on get how we'll see this section.
Weird mentions that any script variables can be overridden by sitting them in ATC default engine X..
These variables get set in a separate file so we don't need to directly edit them in a script.
Right now this file doesn't exist but will simply created by adding our first configuration variable.
Engine X conf file which correspond to the conf path option we set and our bold configuration.
And will also append to that file the Daim in variable which corresponds to our espin path configuration
option.
OK.
The engineered script should now know where to load change in x configuration from and also where to
find the engine X executable.
We'll try running that service again and this time it works as expected so we can go ahead and start
engineer X..
Head over to the browser.
And we get that welcome page.
Likewise if we stop our service that works to add a refresh confirms this.
Next we'll very quickly look at updating our engineers install without any downtime to demonstrate this.
I'll simply be changing my install from that main line version 1 point nine point two to the stable
version one point eight.
And we can see here we are on one point nine point two and I'll just start that service before starting
the update.
Two we know in Genesis running.
Okay I am going to speed through this install as we've done this in the previous video.
But basically I'm just copying the link to that stable version of engine X download it.
Extract.
Move into the Directory and run configure just as before with all the same options.
And will make.
Then make install.
And once this is all done we can again check that engine X version number to see we are now in fact
running version 1 point eight.
But if I perform ahead a request for the IP address just using coal we still see version one point nine
point two running.
And this is because the engine X master process is still from the previous install and isn't aware of
the changes but we can very easily update this by running servers in generics reload which will simply
send a kill signal to the mast engine and process and immediately launch a new one.
Now if we check those headers again we do in fact see version one point eight running and this all happened
gracefully without any need for downtime.
That's it for this video and in the next We'll very briefly look at engine X on Windows.