1 00:00:05,830 --> 00:00:06,150 Okay. 2 00:00:06,160 --> 00:00:08,250 Back in the terminal where we left off. 3 00:00:08,290 --> 00:00:11,440 I'm connected to my virtual machine running a boon too. 4 00:00:11,440 --> 00:00:17,440 And the first installation method will cover is via the operating systems built in backage manager. 5 00:00:17,440 --> 00:00:22,780 Before we start however note that whilst this is a quick and easy solution it's also very limited in 6 00:00:22,780 --> 00:00:29,200 that it doesn't allow us to add any extra modules or functionality to engine X meaning it's almost never 7 00:00:29,200 --> 00:00:35,710 going to be the best solution but still worth knowing a boon to ships with the A P T package manager. 8 00:00:35,710 --> 00:00:37,530 So that's what we'll use. 9 00:00:37,540 --> 00:00:42,870 Start by updating a p t worth apt get update. 10 00:00:42,970 --> 00:00:49,510 Just good practice to make sure we have all the latest versions of the available packages all done. 11 00:00:49,510 --> 00:00:56,890 All clear this and now with all the applegate packages being up to date we can install engine X by sane 12 00:00:57,160 --> 00:01:00,670 at get install engine X.. 13 00:01:02,030 --> 00:01:06,370 Get informs us of some additional dependency packages that will also be installed. 14 00:01:06,410 --> 00:01:07,980 Do you want to continue. 15 00:01:08,240 --> 00:01:09,200 Yes. 16 00:01:12,690 --> 00:01:14,970 And done with this particular package. 17 00:01:14,970 --> 00:01:18,220 Engine X is now not only installed but also running. 18 00:01:18,420 --> 00:01:22,320 We can confirm this by searching for an engine XT process. 19 00:01:22,320 --> 00:01:23,950 I'll use the process command. 20 00:01:23,970 --> 00:01:24,940 P. S.. 21 00:01:24,990 --> 00:01:34,140 All users listing detailed information and X include boot processors which we can then byp through grep 22 00:01:34,230 --> 00:01:40,740 to only see the engine X results and there we have it the engine X master process and a single worker 23 00:01:40,740 --> 00:01:41,650 process. 24 00:01:41,700 --> 00: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 25 00:01:48,690 --> 00:01:49,610 config. 26 00:01:49,890 --> 00:01:51,150 There it is. 27 00:01:51,150 --> 00:01:52,620 I'll copy that. 28 00:01:53,500 --> 00:01:56,290 Navigate to that IP in the browser. 29 00:01:58,550 --> 00:02:00,100 Welcome to IN Genex. 30 00:02:00,260 --> 00:02:06,730 We get that standard engineers holding page meaning our engine server is working and listening on HTP 31 00:02:06,740 --> 00:02:14,290 port 80 with those configuration files residing in slash iti see slash engine X.. 32 00:02:14,330 --> 00:02:20,280 Next let's quickly see how to do the same on sentence as sent or ships with a different package manager. 33 00:02:20,300 --> 00:02:21,400 Yum. 34 00:02:21,480 --> 00:02:28,400 Are logout it over to the digital ocean dashboard and rebuild this machine with the latest version of 35 00:02:28,400 --> 00:02:29,190 centrepiece. 36 00:02:29,240 --> 00:02:33,660 Seven point four reybold confirm. 37 00:02:33,980 --> 00:02:38,200 I'll fast forward through this droplet has been rebooked. 38 00:02:38,240 --> 00:02:39,790 So back to the terminal. 39 00:02:40,010 --> 00:02:47,300 But a side note here as this machine has been rebuilt but the IP address or hostname remains the same. 40 00:02:47,300 --> 00:02:54,530 When I try and connect over a space age I get this error warning remote host ID has changed a standard. 41 00:02:54,530 --> 00:02:58,630 It is an error in the scenario which you've probably encountered before. 42 00:02:58,730 --> 00:03:05,750 So to fix this we can either remove that host entry from the known hosts file or much easier run the 43 00:03:05,750 --> 00:03:08,320 following command to do it automatically. 44 00:03:08,450 --> 00:03:15,420 S s h key Jane without our flag or remove the hostname or IP. 45 00:03:15,440 --> 00:03:24,070 In this case whatever you used previously to connect year host found no host update at connect again. 46 00:03:25,180 --> 00:03:26,850 And we get prompted as before. 47 00:03:26,980 --> 00:03:33,910 Yes so we're connected this time running sent our seven point four and we'll attempt to install engine 48 00:03:33,910 --> 00:03:40,000 X using the Yum package manager that comes with centos yum install engine X.. 49 00:03:40,000 --> 00:03:41,720 Yum looks for that package. 50 00:03:43,270 --> 00:03:48,130 No package engineers available meaning young doesn't show up with engine x. 51 00:03:48,220 --> 00:03:53,870 This is an easy fix however as we can provide young with a new package schorsch one that contains engine 52 00:03:53,870 --> 00:03:54,600 x. 53 00:03:54,850 --> 00:03:59,060 The most popular package repository for this is the EPL repository. 54 00:03:59,260 --> 00:04:07,140 So added to Yum say YUM install it well release the name of that repository confirm. 55 00:04:07,890 --> 00:04:13,710 Yes again and done that in your next package should now be available. 56 00:04:13,710 --> 00:04:15,510 So try installing it again. 57 00:04:15,570 --> 00:04:17,670 Yum install in Genex. 58 00:04:18,520 --> 00:04:21,990 We see yum fetching their package from the EPL repository. 59 00:04:22,180 --> 00:04:23,220 Confirm. 60 00:04:25,560 --> 00:04:26,570 Another one. 61 00:04:27,900 --> 00:04:28,690 Complete. 62 00:04:28,710 --> 00:04:30,060 So this time it worked. 63 00:04:30,090 --> 00:04:38,100 We can confirm by checking for the engine XT configuration files Alice see slash engine X which is there 64 00:04:38,670 --> 00: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 65 00:04:48,350 --> 00:04:49,460 command is found. 66 00:04:49,680 --> 00:04:53,690 And when I reload my browser unable to connect. 67 00:04:53,880 --> 00:04:59,190 This simply being as the young package doesn't automatically start engine X as well but it does add 68 00:04:59,190 --> 00:05:00,840 engine X as a service. 69 00:05:01,020 --> 00:05:04,080 So to start it is as easy as running servers. 70 00:05:04,140 --> 00:05:07,790 Engine X start check the process again. 71 00:05:07,980 --> 00:05:08,750 There we have it. 72 00:05:08,820 --> 00:05:10,130 Same as before. 73 00:05:10,140 --> 00:05:16,410 Head over to the browser reload and we get another holding page albeit a slightly different version 74 00:05:16,410 --> 00:05:18,650 than that of the Buddha package. 75 00:05:18,720 --> 00:05:23,760 That's all they use to using package managers for engine X installs as they're only really for very 76 00:05:23,760 --> 00:05:29,100 quick and simple setups in the next lesson we'll see the preferred method of installing engine X by 77 00:05:29,100 --> 00:05:30,900 boulding at from source.