Before we start installing our custom bulled of in genetics.
Note that I've once again rebuilt my server with the latest version of a boon to seventeen point ten
again.
I'll show you the necessary changes for the installation.
Should you want to use centos over to the terminal.
I've already reset that host finger print so we can go ahead and connect.
Yes.
And in were 31 to welcome page confirming version seventeen point ten as before.
I'll update AP t this time not in order to install engine X but rather to install a couple of dependencies
will need to compile engine x.
If you're on sentence you can do the same by running.
Yum.
Check update.
With our app get packages updated.
The next step is downloading the latest engineer sourcecode.
Now before we start navigating the engine X websites know that we have both engine X dot org and engine
X dot com engine X dot org is where we'll look for the majority of our documentation where s engine
X dot com is the flashier product side of engine X although we'll also have to visit it for some resources
later.
Just important to be aware of these two and that engine X dot com also contains a lot of documentation
on paid for products such as engine X plus which can be somewhat confusing at times and doesn't relate
to this course.
Again if you find any of the sites in the course look different than at the time of recording.
Just check the list and resources for up to date links.
Get over to engine X dot org.
Navigate to this download link.
And here we have sourcecode links to the main line version which is what we'll be using the stable version
which is just a much more mature but slightly older version of engine x and some legacy versions.
Each download version containing the change log for that version the sourcecode download itself and
the windows binary for the version which we won't be covering in this course right.
We'll be using this main line version so copy the link.
Head back to the terminal and download the source code.
You can do this using either curl or easier yet on a boon too.
I'll say w get that link.
All done.
Check the contents of this directory.
There we have it.
Engine X one point thirteen point ten in tarball form at.
So extract the tarball with tar zy X v. F..
Clear this.
List again.
We have then extracted directory so change into it and step 1 is configuring our source code for the
bold to do this we run the configure script in the sourcecode directory.
Current directory slash configure enter C compiler not found.
So in order to compile our source code we're going to have to install a compiler or more specifically
some development tools to do this on a boon to using apt get run up get install build essential.
Or if you're using yum on Santos you can do the same by running.
Yum.
Group install development tools.
Enter confirm.
Asked.
Forward through this.
And all done.
Meaning we now have all the necessary tools to compile in Genex.
Test this by running that configure script again and this time it works.
Although we still need some dependency packages as per this configuration error.
Now at this point whilst I can give you a list of probable dependencies you need for engine x.
Each individual board of engine X will be different but it's as easy as running configure.
Checking what's missing a p CRT or regex library in this case and then installing it using the systems
package manager.
A quick search will usually tell you exactly what the missing package is called and how to install it
or a boon to then.
We need that PCR free library.
So say upt get install Le bcr 3 3 and look PCR re 3 dev.
We're also going to need ze Loeb for Jesus being so add.
ZE lab one G and C lab one G dev.
And lib SSL dev for S S L or H T T P S Support later on.
At this point if you're on sentence you can install the same packages by running yum install B C R E
B C R E E devil zela up zilah Devil open SSL and open SSL Novell.
Enter Isle again fast forward through this answering yes to all the confirmations along the way.
That's done clear this run configure again.
And this time it works without any problems.
Meaning we could now go ahead and compile the source code but we still haven't actually added any custom
configuration flags to find all the available configuration options.
We can run that same configure script passing.
A help flag.
And there we have it.
Although this way we don't get to see any information on the flags So it's a bit difficult to know exactly
what they'll do.
We can however find more information on the engine X dot org site over to the browser.
Navigate to documentation in the sidebar and the second section years what we are looking for.
Building engine X from source where we get a detailed description of each of those configuration options
along with thier default values.
So let's reconfigure the source and sit a few common flags.
Configure.
Setting the espin path flag to user.
Then engine x.
This being the location of the engine is executable which will use to start and stop then jinich service
user Ben being a common location for and to executables conf path being the path of the engineer's configuration
files.
Make that iti see engine X engine X dot conf.
Again a common location and the same as the location used by the package manager in the previous lesson.
A Prologue path.
Make that var log engine x error dot log HTP log path being our access logs the same var log in generics
but access dot log with PCR re telling engine X to use the system speci our library for regular expressions
and the process idae path which will need to know when configuring an engine X system service later
on var run engine X dot P I D E.
That's all we'll do in terms of customizing this install.
But of course the absolute main benefit of boulding engine X from source is the ability to add custom
modules or essentially extend the standard engine X functionality.
Something you cannot do using a package manager.
Note however that engine X modules exist in two forms bundled modules and third party modules third
body modules being modules that's developed and maintained by third party developers and need to be
downloaded and compiled with engine X to use.
We'll see examples of these modules later in the course bundled modules on the other hand being modules
that come with the engineer source.
Like for example the H T T P S S L module will be adding here the flag being worth htb underscore SSL
underscore module telling engine X to include this module in the bold and thus enabling us to use H
T T P S.
Also note here that this module being the reason we installed the loop SSL package via apt get to see
a comprehensive list of modules available with the engine source.
Navigate back to the documentation page.
Scroll all the way down.
And here we have it modules which if I select one like this HTP to module for example we get a complete
reference to use this module and the configuration flag needed to install it.
Again for now I'll add the SSL module only so back to the terminal and add that flag.
With HTP underscore SSL underscore module enter late that custom configuration complete.
All done without any issues.
So next we can compile this configuration source by running make this one taking quite a bit of time
so I'll forward through it again.
And once that's done install the compile source with make install.
Done.
Check the configuration files exist in that location we configured Alice list utc in Genex.
They're all there so we should now have the ingenius executable available as well tested by getting
the installed engine X version.
Engineer X v..
Which tells us engine X one point thirteen point ten is installed with a breakdown of the configuration
used to install it.
We can start engine X by simply running engine x no errors check the processes running all good.
Also check the browser navigate to that IP.
And we get the holding page in the next lesson we'll create a system servers to manage our new engineers
install.