WEBVTT 00:00.000 --> 00:00.300 Okay. 00:00.300 --> 00:05.400 Welcome to section 12 and it's finally time to publish our hard work onto the big, bad world of the 00:05.400 --> 00:12.450 internet so that our application can be accessed from anywhere and anyone on the planet can effectively 00:12.570 --> 00:18.840 add some fake products into their fake shopping cart and create a fake order using a fake payment card 00:18.960 --> 00:21.360 to not be delivered their fake products. 00:21.360 --> 00:23.250 And that's our goal of this section. 00:23.250 --> 00:29.280 So what's coming up in this section is we're going to take a look at finalizing our react application, 00:29.280 --> 00:35.340 creating things like a home page, and creating a production version of our react application. 00:35.730 --> 00:40.650 Then it's going to be time to say goodbye to SQLite, and we're going to replace it with a production 00:40.650 --> 00:42.390 worthy database server. 00:42.390 --> 00:47.820 And the one that we're going to replace it with is SQL server as the platform that we're going to publish 00:47.850 --> 00:55.380 our application onto is Azure a Microsoft platform and SQL server being a Microsoft database server 00:55.380 --> 00:59.460 technology, it all makes sense that we stick with the same technology stack. 00:59.460 --> 01:00.060 We don't have to. 01:00.090 --> 01:07.020 We could use other database servers on Azure, but because it's Azure I'm going for SQL server. 01:07.020 --> 01:11.730 And another reason for SQL server is that there is a free option. 01:11.730 --> 01:18.030 You get one free SQL server database to use in Azure, and it comes with significant limitations, but 01:18.030 --> 01:24.810 it does allow us to test our application in production with a production SQL server without incurring 01:24.810 --> 01:25.560 any charges. 01:25.560 --> 01:29.630 Now when it comes to deployment onto cloud platforms. 01:29.630 --> 01:32.660 Once upon a time, there used to be three options. 01:33.140 --> 01:34.760 There was a platform called Heroku. 01:34.790 --> 01:40.130 Heroku still exists, but nowadays they charge a fee to use their services. 01:40.160 --> 01:46.310 A few years ago we would be able to sign up for Heroku, just verify our email address and then deploy 01:46.310 --> 01:53.480 our application onto Heroku with a database server and our application deployed all free of charge. 01:53.480 --> 01:58.940 It would come with limitations about performance, etc., but it was completely free and no credit card 01:58.940 --> 02:00.320 was necessary. 02:00.350 --> 02:07.190 Those days have now gone thanks to crypto miners that signed up and used many free cloud provider services. 02:07.190 --> 02:09.200 So now they're all pretty much charging. 02:09.230 --> 02:14.030 Azure still does give us a way to do this free of charge though, so that's the reason for selecting 02:14.030 --> 02:15.050 that platform. 02:15.050 --> 02:20.180 The free options do come with some heavy limitations that I'll explain as we go through the deployment 02:20.180 --> 02:22.280 process to get it onto Azure. 02:22.400 --> 02:28.190 Something else we're going to take a look at in this section as well, is continuous integration and 02:28.190 --> 02:34.400 continuous deployment a way of automating our deployment so that when we do commit our changes into 02:34.400 --> 02:39.980 GitHub, then a workflow kicks off on GitHub side which is going to build our react application, build 02:39.980 --> 02:45.650 Our.net application, and then deploy all of that updated code to Azure. 02:45.650 --> 02:51.560 And then any of our code changes are automatically going to be deployed to our production application. 02:51.560 --> 02:53.480 So that's what's coming up in this section. 02:53.480 --> 02:54.980 And let's begin.