WEBVTT

00:05.830 --> 00:06.150
Okay.

00:06.160 --> 00:08.250
Back in the terminal where we left off.

00:08.290 --> 00:11.440
I'm connected to my virtual machine running a boon too.

00:11.440 --> 00:17.440
And the first installation method will cover is via the operating systems built in backage manager.

00:17.440 --> 00:22.780
Before we start however note that whilst this is a quick and easy solution it's also very limited in

00:22.780 --> 00:29.200
that it doesn't allow us to add any extra modules or functionality to engine X meaning it's almost never

00:29.200 --> 00:35.710
going to be the best solution but still worth knowing a boon to ships with the A P T package manager.

00:35.710 --> 00:37.530
So that's what we'll use.

00:37.540 --> 00:42.870
Start by updating a p t worth apt get update.

00:42.970 --> 00:49.510
Just good practice to make sure we have all the latest versions of the available packages all done.

00:49.510 --> 00:56.890
All clear this and now with all the applegate packages being up to date we can install engine X by sane

00:57.160 --> 01:00.670
at get install engine X..

01:02.030 --> 01:06.370
Get informs us of some additional dependency packages that will also be installed.

01:06.410 --> 01:07.980
Do you want to continue.

01:08.240 --> 01:09.200
Yes.

01:12.690 --> 01:14.970
And done with this particular package.

01:14.970 --> 01:18.220
Engine X is now not only installed but also running.

01:18.420 --> 01:22.320
We can confirm this by searching for an engine XT process.

01:22.320 --> 01:23.950
I'll use the process command.

01:23.970 --> 01:24.940
P. S..

01:24.990 --> 01:34.140
All users listing detailed information and X include boot processors which we can then byp through grep

01:34.230 --> 01:40.740
to only see the engine X results and there we have it the engine X master process and a single worker

01:40.740 --> 01:41.650
process.

01:41.700 --> 01:48.540
The last one being our grep command we can also test this in the browser get the IP address with i-f

01:48.690 --> 01:49.610
config.

01:49.890 --> 01:51.150
There it is.

01:51.150 --> 01:52.620
I'll copy that.

01:53.500 --> 01:56.290
Navigate to that IP in the browser.

01:58.550 --> 02:00.100
Welcome to IN Genex.

02:00.260 --> 02:06.730
We get that standard engineers holding page meaning our engine server is working and listening on HTP

02:06.740 --> 02:14.290
port 80 with those configuration files residing in slash iti see slash engine X..

02:14.330 --> 02:20.280
Next let's quickly see how to do the same on sentence as sent or ships with a different package manager.

02:20.300 --> 02:21.400
Yum.

02:21.480 --> 02:28.400
Are logout it over to the digital ocean dashboard and rebuild this machine with the latest version of

02:28.400 --> 02:29.190
centrepiece.

02:29.240 --> 02:33.660
Seven point four reybold confirm.

02:33.980 --> 02:38.200
I'll fast forward through this droplet has been rebooked.

02:38.240 --> 02:39.790
So back to the terminal.

02:40.010 --> 02:47.300
But a side note here as this machine has been rebuilt but the IP address or hostname remains the same.

02:47.300 --> 02:54.530
When I try and connect over a space age I get this error warning remote host ID has changed a standard.

02:54.530 --> 02:58.630
It is an error in the scenario which you've probably encountered before.

02:58.730 --> 03:05.750
So to fix this we can either remove that host entry from the known hosts file or much easier run the

03:05.750 --> 03:08.320
following command to do it automatically.

03:08.450 --> 03:15.420
S s h key Jane without our flag or remove the hostname or IP.

03:15.440 --> 03:24.070
In this case whatever you used previously to connect year host found no host update at connect again.

03:25.180 --> 03:26.850
And we get prompted as before.

03:26.980 --> 03:33.910
Yes so we're connected this time running sent our seven point four and we'll attempt to install engine

03:33.910 --> 03:40.000
X using the Yum package manager that comes with centos yum install engine X..

03:40.000 --> 03:41.720
Yum looks for that package.

03:43.270 --> 03:48.130
No package engineers available meaning young doesn't show up with engine x.

03:48.220 --> 03:53.870
This is an easy fix however as we can provide young with a new package schorsch one that contains engine

03:53.870 --> 03:54.600
x.

03:54.850 --> 03:59.060
The most popular package repository for this is the EPL repository.

03:59.260 --> 04:07.140
So added to Yum say YUM install it well release the name of that repository confirm.

04:07.890 --> 04:13.710
Yes again and done that in your next package should now be available.

04:13.710 --> 04:15.510
So try installing it again.

04:15.570 --> 04:17.670
Yum install in Genex.

04:18.520 --> 04:21.990
We see yum fetching their package from the EPL repository.

04:22.180 --> 04:23.220
Confirm.

04:25.560 --> 04:26.570
Another one.

04:27.900 --> 04:28.690
Complete.

04:28.710 --> 04:30.060
So this time it worked.

04:30.090 --> 04:38.100
We can confirm by checking for the engine XT configuration files Alice see slash engine X which is there

04:38.670 --> 04:48.360
but when we check for an engine x process as before P S A you x grip in X nothing only There's grep

04:48.350 --> 04:49.460
command is found.

04:49.680 --> 04:53.690
And when I reload my browser unable to connect.

04:53.880 --> 04:59.190
This simply being as the young package doesn't automatically start engine X as well but it does add

04:59.190 --> 05:00.840
engine X as a service.

05:01.020 --> 05:04.080
So to start it is as easy as running servers.

05:04.140 --> 05:07.790
Engine X start check the process again.

05:07.980 --> 05:08.750
There we have it.

05:08.820 --> 05:10.130
Same as before.

05:10.140 --> 05:16.410
Head over to the browser reload and we get another holding page albeit a slightly different version

05:16.410 --> 05:18.650
than that of the Buddha package.

05:18.720 --> 05:23.760
That's all they use to using package managers for engine X installs as they're only really for very

05:23.760 --> 05:29.100
quick and simple setups in the next lesson we'll see the preferred method of installing engine X by

05:29.100 --> 05:30.900
boulding at from source.
