WEBVTT 00:00.480 --> 00:01.120 Welcome back. 00:01.200 --> 00:06.680 In this video, I want to quickly show you how to update your local N810 instance. 00:06.840 --> 00:12.040 If you are self-hosting a n810 on your own machine using NodeJS. 00:12.280 --> 00:17.280 So this is super important because the N810 team pushes updates all the time. 00:17.680 --> 00:20.120 New features, improvements, bug fixes. 00:20.560 --> 00:26.920 So they roll out updates regularly and keeping your local version of N810 up to date means you don't 00:26.960 --> 00:27.480 need you. 00:27.480 --> 00:32.080 Don't miss out anything and your N810 instance will work perfectly fine. 00:32.840 --> 00:35.040 So let me show you how to how simple it is. 00:35.080 --> 00:38.200 First thing first we need to check if an update is available. 00:38.200 --> 00:42.000 So open up your local N810 instance in the browser. 00:42.200 --> 00:51.680 And now if you go to the right bottom corner and click on your name on this on this three dots and then 00:51.680 --> 00:52.800 go to settings. 00:53.920 --> 00:56.600 You might see a red dot at the bottom. 00:57.560 --> 01:03.240 So currently my version is up to date so I don't need to update my instance. 01:03.290 --> 01:09.490 But if you see the red dot, that means there is an update available, and it's probably a good idea 01:09.490 --> 01:11.370 to to update your instance. 01:11.410 --> 01:15.530 Now, before updating, we need to shut down the current instance of N810. 01:16.050 --> 01:20.250 So just simply go back to your Node.js command prompt. 01:20.810 --> 01:22.450 So open this terminal window. 01:22.810 --> 01:26.570 So the one you use to start n810 and close that window. 01:30.330 --> 01:36.330 Now if you try refreshing your browser tab when it was running. 01:38.810 --> 01:45.290 It won't load anymore because that was expected because the server just shut down. 01:45.290 --> 01:46.570 It runs over the node. 01:46.610 --> 01:52.130 Now if you visit the GitHub page you will see just how often they push updates. 01:52.130 --> 01:54.450 So sometimes multiple times a week. 01:55.050 --> 02:01.570 And for example, you might see that the last update was committed to GitHub a 54 minutes ago. 02:02.690 --> 02:06.090 We have some 14 hours ago four days this last month. 02:06.090 --> 02:06.890 Last week? 02:08.930 --> 02:09.370 Yep. 02:09.890 --> 02:16.370 So as you can see, the team shipping features and fixed boxes all the time. 02:16.810 --> 02:18.450 So this is very active. 02:18.450 --> 02:22.370 And we need and we need to keep our N810 instance up to date. 02:22.370 --> 02:30.170 So you don't need to update your N810 instance every day, but doing it from time to time is strongly 02:30.170 --> 02:34.170 recommended to keep your setup running smoothly. 02:35.450 --> 02:41.970 There is also a dedicated page for tracking all the updates and releasing notes. 02:42.170 --> 02:49.490 I'm going to leave the link to this web page in the resources section, so you can keep an eye on the 02:49.490 --> 02:50.370 new updates. 02:52.690 --> 02:53.130 All right. 02:53.130 --> 02:53.410 Great. 02:53.450 --> 02:56.050 Now let's actually update our instance. 02:56.130 --> 02:59.090 So let's open the Node.js command prompt again. 03:04.410 --> 03:09.620 This time let's type The n pm. 03:12.100 --> 03:12.860 Update. 03:15.620 --> 03:18.500 Dash G and a10. 03:19.980 --> 03:21.300 And then press enter. 03:24.940 --> 03:31.620 So this will take a couple of minutes depending on your internet speed and what's being updated. 03:34.740 --> 03:43.460 So behind the scenes it's removing all the packages, adding new files and synchronizing everything. 03:48.460 --> 03:49.460 Alright, here we go. 03:49.580 --> 03:53.100 As you can see, in my case it changed to packages in one minute. 03:54.700 --> 04:02.100 So it wasn't a big update because I just installed the N810 locally for the sake of this tutorial review. 04:03.540 --> 04:04.420 Alright, great. 04:04.820 --> 04:13.980 Now as soon as the updating process is completed, you can simply type in N810 to start running N810 04:14.140 --> 04:14.980 instance again. 04:17.420 --> 04:19.020 Just wait a moment. 04:21.500 --> 04:27.940 Okay, so as you can see, we are not able to run our local instance yet because the process has not 04:27.940 --> 04:28.700 completed. 04:31.460 --> 04:33.500 So let's just wait a few more seconds. 04:34.660 --> 04:35.020 Okay. 04:35.060 --> 04:36.100 Everything is ready. 04:39.500 --> 04:43.980 So now when I reload this page to reset our instance. 05:00.580 --> 05:01.940 Now we get access back. 05:02.740 --> 05:03.420 Brilliant. 05:03.860 --> 05:09.060 So, yeah, there are two ways to start your local N810 instance. 05:09.580 --> 05:18.150 Just copy and paste the URL from the terminal to the browser, or just simply refresh the old tab if 05:18.150 --> 05:19.430 you still have it open. 05:19.470 --> 05:23.150 Now your local N810 is now fully updated and ready to go. 05:23.710 --> 05:30.310 Just to let you know, you can absolutely continue working locally for most things like building and 05:30.310 --> 05:32.030 testing and experimenting. 05:32.510 --> 05:39.430 But for certain use cases like triggering telegram, WhatsApp or hosting workflows you want to share 05:39.430 --> 05:43.030 or sell a local setup will be not enough. 05:43.790 --> 05:47.350 That's when you need to move to a cloud hosted version. 05:47.870 --> 05:54.390 I already showed you how to use the N810 cloud version and pay for the subscription. 05:55.110 --> 06:01.670 And also the second option was to self-hosting on the virtual private server. 06:01.870 --> 06:04.350 So these are three ways of using N810. 06:04.750 --> 06:07.550 So each method has its own pros and cons. 06:07.870 --> 06:13.070 So yeah this is how you can update your local N810 node instance. 06:13.110 --> 06:14.230 Thanks for listening. 06:14.350 --> 06:15.390 See you in the next lesson.