Okay.
Back in the terminal where we left off.
I'm connected to my virtual machine running a boon too.
And the first installation method will cover is via the operating systems built in backage manager.
Before we start however note that whilst this is a quick and easy solution it's also very limited in
that it doesn't allow us to add any extra modules or functionality to engine X meaning it's almost never
going to be the best solution but still worth knowing a boon to ships with the A P T package manager.
So that's what we'll use.
Start by updating a p t worth apt get update.
Just good practice to make sure we have all the latest versions of the available packages all done.
All clear this and now with all the applegate packages being up to date we can install engine X by sane
at get install engine X..
Get informs us of some additional dependency packages that will also be installed.
Do you want to continue.
Yes.
And done with this particular package.
Engine X is now not only installed but also running.
We can confirm this by searching for an engine XT process.
I'll use the process command.
P. S..
All users listing detailed information and X include boot processors which we can then byp through grep
to only see the engine X results and there we have it the engine X master process and a single worker
process.
The last one being our grep command we can also test this in the browser get the IP address with i-f
config.
There it is.
I'll copy that.
Navigate to that IP in the browser.
Welcome to IN Genex.
We get that standard engineers holding page meaning our engine server is working and listening on HTP
port 80 with those configuration files residing in slash iti see slash engine X..
Next let's quickly see how to do the same on sentence as sent or ships with a different package manager.
Yum.
Are logout it over to the digital ocean dashboard and rebuild this machine with the latest version of
centrepiece.
Seven point four reybold confirm.
I'll fast forward through this droplet has been rebooked.
So back to the terminal.
But a side note here as this machine has been rebuilt but the IP address or hostname remains the same.
When I try and connect over a space age I get this error warning remote host ID has changed a standard.
It is an error in the scenario which you've probably encountered before.
So to fix this we can either remove that host entry from the known hosts file or much easier run the
following command to do it automatically.
S s h key Jane without our flag or remove the hostname or IP.
In this case whatever you used previously to connect year host found no host update at connect again.
And we get prompted as before.
Yes so we're connected this time running sent our seven point four and we'll attempt to install engine
X using the Yum package manager that comes with centos yum install engine X..
Yum looks for that package.
No package engineers available meaning young doesn't show up with engine x.
This is an easy fix however as we can provide young with a new package schorsch one that contains engine
x.
The most popular package repository for this is the EPL repository.
So added to Yum say YUM install it well release the name of that repository confirm.
Yes again and done that in your next package should now be available.
So try installing it again.
Yum install in Genex.
We see yum fetching their package from the EPL repository.
Confirm.
Another one.
Complete.
So this time it worked.
We can confirm by checking for the engine XT configuration files Alice see slash engine X which is there
but when we check for an engine x process as before P S A you x grip in X nothing only There's grep
command is found.
And when I reload my browser unable to connect.
This simply being as the young package doesn't automatically start engine X as well but it does add
engine X as a service.
So to start it is as easy as running servers.
Engine X start check the process again.
There we have it.
Same as before.
Head over to the browser reload and we get another holding page albeit a slightly different version
than that of the Buddha package.
That's all they use to using package managers for engine X installs as they're only really for very
quick and simple setups in the next lesson we'll see the preferred method of installing engine X by
boulding at from source.