WEBVTT 00:06.630 --> 00:12.030 In this video we'll see how to add our newly built in Genex install as a linnik Service and how to update 00:12.030 --> 00:18.040 engine X without any downtime whether this be did change change in its core or simply to add extra modules. 00:18.060 --> 00:23.310 We could of course simply stop and start engine X were things in X executable but running it as a linnik 00:23.310 --> 00:28.950 service means other programs can interact with it much easier and make for an all round more standard 00:28.950 --> 00:30.030 experience. 00:30.940 --> 00:36.140 I'm back on a custom board of engine X. one point nine point two on a boon to fourteen point in exactly 00:36.140 --> 00:37.480 as in the previous video. 00:37.730 --> 00:44.300 And obviously when we try and run service engine start we get unrecognized service as engine hasn't 00:44.300 --> 00:46.470 yet been added as a clinic service. 00:46.850 --> 00:51.860 To add this we need to create an initial script for engine X which we can simply download from Engine 00:51.860 --> 00:58.070 X Weeki site so we'll head over to weeky dot engineers dot in its scripts where you'll see a list of 00:58.070 --> 01:02.810 in its script for different operating systems and even variations of those scripts. 01:03.080 --> 01:08.330 I'm going to go to the Ubuntu section and just navigate to this standard in its script. 01:08.330 --> 01:11.430 On the main page we can see the actual script Shaw Stonier. 01:11.450 --> 01:16.180 But I'm going to go ahead to the project page and like many Google Code projects. 01:16.190 --> 01:17.860 This one has moved to get hub. 01:20.210 --> 01:21.590 And here we are. 01:21.800 --> 01:27.410 So the project rebo contains some docs here which will look at in a minute but first we want to go and 01:27.410 --> 01:29.890 get the actual in its script year. 01:35.270 --> 01:38.750 And I'll copy this link and head back over to my terminal. 01:39.920 --> 01:45.700 We want to put this file in see init don't die as this is where all the initial scripts for different 01:45.700 --> 01:47.130 linnik services live. 01:48.400 --> 01:50.230 Just download the script here. 01:50.270 --> 01:57.820 And for Linux to know about this new script we need to load it by running update dash our C dot B and 01:57.820 --> 01:59.130 then a f flag. 01:59.260 --> 02:01.310 Engine X defaults. 02:02.240 --> 02:06.820 We have a permissions error though so we'll fix that by making the script executable. 02:15.510 --> 02:17.120 And try again. 02:19.270 --> 02:20.410 And this time we get. 02:20.410 --> 02:23.600 You don't have permissions to execute in generics. 02:23.680 --> 02:28.630 Now this might again seem like a permissions error but what's actually happening here is that the init 02:28.630 --> 02:33.930 script expect so engine X installed to be located in all the default bold locations. 02:34.240 --> 02:37.300 Of course we made some changes when configuring our board. 02:37.450 --> 02:40.630 So we need to tell them in a script about those changes. 02:40.630 --> 02:44.310 If we look at they need script read me on get how we'll see this section. 02:44.310 --> 02:51.770 Weird mentions that any script variables can be overridden by sitting them in ATC default engine X.. 02:51.910 --> 02:57.030 These variables get set in a separate file so we don't need to directly edit them in a script. 02:57.070 --> 03:03.010 Right now this file doesn't exist but will simply created by adding our first configuration variable. 03:03.010 --> 03:09.840 Engine X conf file which correspond to the conf path option we set and our bold configuration. 03:10.740 --> 03:16.740 And will also append to that file the Daim in variable which corresponds to our espin path configuration 03:16.760 --> 03:17.410 option. 03:18.270 --> 03:18.590 OK. 03:18.630 --> 03:23.520 The engineered script should now know where to load change in x configuration from and also where to 03:23.520 --> 03:25.720 find the engine X executable. 03:25.890 --> 03:31.740 We'll try running that service again and this time it works as expected so we can go ahead and start 03:31.740 --> 03:32.560 engineer X.. 03:32.640 --> 03:34.290 Head over to the browser. 03:36.370 --> 03:38.310 And we get that welcome page. 03:38.320 --> 03:43.440 Likewise if we stop our service that works to add a refresh confirms this. 03:47.850 --> 03:53.580 Next we'll very quickly look at updating our engineers install without any downtime to demonstrate this. 03:53.580 --> 03:58.950 I'll simply be changing my install from that main line version 1 point nine point two to the stable 03:58.950 --> 04:00.430 version one point eight. 04:01.170 --> 04:06.420 And we can see here we are on one point nine point two and I'll just start that service before starting 04:06.420 --> 04:06.860 the update. 04:06.860 --> 04:08.740 Two we know in Genesis running. 04:13.690 --> 04:18.140 Okay I am going to speed through this install as we've done this in the previous video. 04:18.140 --> 04:23.500 But basically I'm just copying the link to that stable version of engine X download it. 04:25.680 --> 04:26.690 Extract. 04:26.790 --> 04:32.020 Move into the Directory and run configure just as before with all the same options. 04:33.810 --> 04:35.050 And will make. 04:38.660 --> 04:40.910 Then make install. 04:40.910 --> 04:46.640 And once this is all done we can again check that engine X version number to see we are now in fact 04:46.640 --> 04:48.890 running version 1 point eight. 04:48.890 --> 04:55.850 But if I perform ahead a request for the IP address just using coal we still see version one point nine 04:55.850 --> 04:57.110 point two running. 04:57.210 --> 05:02.180 And this is because the engine X master process is still from the previous install and isn't aware of 05:02.180 --> 05:08.210 the changes but we can very easily update this by running servers in generics reload which will simply 05:08.210 --> 05:13.540 send a kill signal to the mast engine and process and immediately launch a new one. 05:13.580 --> 05:19.280 Now if we check those headers again we do in fact see version one point eight running and this all happened 05:19.280 --> 05:22.490 gracefully without any need for downtime. 05:22.520 --> 05:27.240 That's it for this video and in the next We'll very briefly look at engine X on Windows.