WEBVTT

00:04.370 --> 00:07.440
Before we start installing our custom bulled of in genetics.

00:07.460 --> 00:13.220
Note that I've once again rebuilt my server with the latest version of a boon to seventeen point ten

00:13.710 --> 00:14.270
again.

00:14.300 --> 00:17.160
I'll show you the necessary changes for the installation.

00:17.210 --> 00:20.980
Should you want to use centos over to the terminal.

00:20.990 --> 00:25.090
I've already reset that host finger print so we can go ahead and connect.

00:25.310 --> 00:26.070
Yes.

00:26.800 --> 00:32.790
And in were 31 to welcome page confirming version seventeen point ten as before.

00:32.800 --> 00:39.100
I'll update AP t this time not in order to install engine X but rather to install a couple of dependencies

00:39.100 --> 00:41.240
will need to compile engine x.

00:41.380 --> 00:43.750
If you're on sentence you can do the same by running.

00:43.750 --> 00:44.370
Yum.

00:44.530 --> 00:46.030
Check update.

00:46.720 --> 00:49.030
With our app get packages updated.

00:49.060 --> 00:52.870
The next step is downloading the latest engineer sourcecode.

00:52.960 --> 00:59.100
Now before we start navigating the engine X websites know that we have both engine X dot org and engine

00:59.100 --> 01:05.620
X dot com engine X dot org is where we'll look for the majority of our documentation where s engine

01:05.620 --> 01:12.070
X dot com is the flashier product side of engine X although we'll also have to visit it for some resources

01:12.070 --> 01:13.110
later.

01:13.150 --> 01:18.730
Just important to be aware of these two and that engine X dot com also contains a lot of documentation

01:18.730 --> 01:25.000
on paid for products such as engine X plus which can be somewhat confusing at times and doesn't relate

01:25.000 --> 01:26.420
to this course.

01:26.470 --> 01:30.870
Again if you find any of the sites in the course look different than at the time of recording.

01:30.880 --> 01:34.090
Just check the list and resources for up to date links.

01:34.340 --> 01:36.120
Get over to engine X dot org.

01:37.700 --> 01:39.690
Navigate to this download link.

01:40.490 --> 01:46.700
And here we have sourcecode links to the main line version which is what we'll be using the stable version

01:46.730 --> 01:52.610
which is just a much more mature but slightly older version of engine x and some legacy versions.

01:52.700 --> 01:58.880
Each download version containing the change log for that version the sourcecode download itself and

01:58.880 --> 02:03.950
the windows binary for the version which we won't be covering in this course right.

02:03.950 --> 02:07.220
We'll be using this main line version so copy the link.

02:08.860 --> 02:12.470
Head back to the terminal and download the source code.

02:12.510 --> 02:16.140
You can do this using either curl or easier yet on a boon too.

02:16.140 --> 02:19.170
I'll say w get that link.

02:20.200 --> 02:21.290
All done.

02:21.370 --> 02:24.040
Check the contents of this directory.

02:24.040 --> 02:24.940
There we have it.

02:25.000 --> 02:29.520
Engine X one point thirteen point ten in tarball form at.

02:29.710 --> 02:33.950
So extract the tarball with tar zy X v. F..

02:36.220 --> 02:37.220
Clear this.

02:38.380 --> 02:39.660
List again.

02:39.970 --> 02:46.600
We have then extracted directory so change into it and step 1 is configuring our source code for the

02:46.600 --> 02:51.280
bold to do this we run the configure script in the sourcecode directory.

02:51.460 --> 02:57.440
Current directory slash configure enter C compiler not found.

02:57.670 --> 03:03.040
So in order to compile our source code we're going to have to install a compiler or more specifically

03:03.040 --> 03:11.280
some development tools to do this on a boon to using apt get run up get install build essential.

03:13.030 --> 03:16.990
Or if you're using yum on Santos you can do the same by running.

03:16.990 --> 03:17.740
Yum.

03:17.750 --> 03:20.660
Group install development tools.

03:22.140 --> 03:25.190
Enter confirm.

03:25.190 --> 03:25.490
Asked.

03:25.490 --> 03:27.030
Forward through this.

03:27.120 --> 03:28.100
And all done.

03:28.260 --> 03:32.370
Meaning we now have all the necessary tools to compile in Genex.

03:32.370 --> 03:36.600
Test this by running that configure script again and this time it works.

03:36.750 --> 03:41.460
Although we still need some dependency packages as per this configuration error.

03:41.790 --> 03:46.570
Now at this point whilst I can give you a list of probable dependencies you need for engine x.

03:46.710 --> 03:51.890
Each individual board of engine X will be different but it's as easy as running configure.

03:51.960 --> 03:58.770
Checking what's missing a p CRT or regex library in this case and then installing it using the systems

03:58.770 --> 04:00.060
package manager.

04:00.060 --> 04:04.920
A quick search will usually tell you exactly what the missing package is called and how to install it

04:05.550 --> 04:06.540
or a boon to then.

04:06.570 --> 04:08.690
We need that PCR free library.

04:08.700 --> 04:15.730
So say upt get install Le bcr 3 3 and look PCR re 3 dev.

04:17.120 --> 04:20.820
We're also going to need ze Loeb for Jesus being so add.

04:20.870 --> 04:25.270
ZE lab one G and C lab one G dev.

04:26.100 --> 04:31.770
And lib SSL dev for S S L or H T T P S Support later on.

04:32.070 --> 04:38.640
At this point if you're on sentence you can install the same packages by running yum install B C R E

04:39.090 --> 04:46.580
B C R E E devil zela up zilah Devil open SSL and open SSL Novell.

04:48.230 --> 04:54.390
Enter Isle again fast forward through this answering yes to all the confirmations along the way.

04:54.740 --> 04:59.060
That's done clear this run configure again.

05:00.790 --> 05:03.030
And this time it works without any problems.

05:03.100 --> 05:09.010
Meaning we could now go ahead and compile the source code but we still haven't actually added any custom

05:09.010 --> 05:13.120
configuration flags to find all the available configuration options.

05:13.120 --> 05:15.760
We can run that same configure script passing.

05:15.840 --> 05:17.060
A help flag.

05:17.200 --> 05:18.210
And there we have it.

05:18.310 --> 05:23.710
Although this way we don't get to see any information on the flags So it's a bit difficult to know exactly

05:23.710 --> 05:25.030
what they'll do.

05:25.030 --> 05:30.330
We can however find more information on the engine X dot org site over to the browser.

05:30.430 --> 05:36.850
Navigate to documentation in the sidebar and the second section years what we are looking for.

05:36.970 --> 05:43.030
Building engine X from source where we get a detailed description of each of those configuration options

05:43.330 --> 05:45.430
along with thier default values.

05:45.700 --> 05:49.960
So let's reconfigure the source and sit a few common flags.

05:50.600 --> 05:51.590
Configure.

05:52.450 --> 05:56.360
Setting the espin path flag to user.

05:56.420 --> 05:58.280
Then engine x.

05:58.330 --> 06:04.240
This being the location of the engine is executable which will use to start and stop then jinich service

06:04.650 --> 06:12.520
user Ben being a common location for and to executables conf path being the path of the engineer's configuration

06:12.520 --> 06:13.690
files.

06:13.690 --> 06:17.970
Make that iti see engine X engine X dot conf.

06:18.250 --> 06:23.700
Again a common location and the same as the location used by the package manager in the previous lesson.

06:24.440 --> 06:25.800
A Prologue path.

06:25.950 --> 06:36.720
Make that var log engine x error dot log HTP log path being our access logs the same var log in generics

06:36.990 --> 06:45.930
but access dot log with PCR re telling engine X to use the system speci our library for regular expressions

06:46.590 --> 06:52.350
and the process idae path which will need to know when configuring an engine X system service later

06:52.350 --> 06:56.840
on var run engine X dot P I D E.

06:57.180 --> 07:00.190
That's all we'll do in terms of customizing this install.

07:00.240 --> 07:06.180
But of course the absolute main benefit of boulding engine X from source is the ability to add custom

07:06.180 --> 07:10.540
modules or essentially extend the standard engine X functionality.

07:10.770 --> 07:13.320
Something you cannot do using a package manager.

07:13.320 --> 07:21.450
Note however that engine X modules exist in two forms bundled modules and third party modules third

07:21.450 --> 07:26.670
body modules being modules that's developed and maintained by third party developers and need to be

07:26.670 --> 07:29.820
downloaded and compiled with engine X to use.

07:29.820 --> 07:35.400
We'll see examples of these modules later in the course bundled modules on the other hand being modules

07:35.460 --> 07:37.350
that come with the engineer source.

07:37.500 --> 07:45.990
Like for example the H T T P S S L module will be adding here the flag being worth htb underscore SSL

07:46.050 --> 07:51.780
underscore module telling engine X to include this module in the bold and thus enabling us to use H

07:51.780 --> 07:53.160
T T P S.

07:53.160 --> 07:59.850
Also note here that this module being the reason we installed the loop SSL package via apt get to see

07:59.850 --> 08:03.100
a comprehensive list of modules available with the engine source.

08:03.250 --> 08:06.000
Navigate back to the documentation page.

08:06.000 --> 08:07.670
Scroll all the way down.

08:07.800 --> 08:15.030
And here we have it modules which if I select one like this HTP to module for example we get a complete

08:15.030 --> 08:19.770
reference to use this module and the configuration flag needed to install it.

08:20.830 --> 08:26.700
Again for now I'll add the SSL module only so back to the terminal and add that flag.

08:27.850 --> 08:36.160
With HTP underscore SSL underscore module enter late that custom configuration complete.

08:36.520 --> 08:38.190
All done without any issues.

08:38.200 --> 08:44.290
So next we can compile this configuration source by running make this one taking quite a bit of time

08:44.290 --> 08:46.130
so I'll forward through it again.

08:46.240 --> 08:51.330
And once that's done install the compile source with make install.

08:52.960 --> 08:53.610
Done.

08:53.830 --> 09:01.060
Check the configuration files exist in that location we configured Alice list utc in Genex.

09:01.240 --> 09:07.150
They're all there so we should now have the ingenius executable available as well tested by getting

09:07.150 --> 09:09.400
the installed engine X version.

09:09.400 --> 09:11.240
Engineer X v..

09:11.350 --> 09:17.590
Which tells us engine X one point thirteen point ten is installed with a breakdown of the configuration

09:17.590 --> 09:19.480
used to install it.

09:19.510 --> 09:27.250
We can start engine X by simply running engine x no errors check the processes running all good.

09:27.250 --> 09:30.550
Also check the browser navigate to that IP.

09:31.370 --> 09:37.090
And we get the holding page in the next lesson we'll create a system servers to manage our new engineers

09:37.190 --> 09:38.180
install.