WEBVTT 00:00.080 --> 00:03.050 Okay, so we've now published our application onto the internet. 00:03.050 --> 00:09.650 And hopefully for yourselves, it's working and running on Azure, which means now our fake e-commerce 00:09.650 --> 00:16.160 store is accessible to anyone on the planet that has an internet connection, should they know the URL 00:16.190 --> 00:18.050 of how to get to our application? 00:18.050 --> 00:18.710 Of course. 00:18.710 --> 00:25.790 So in this section, what we've taken a look at is we've created a production version of our react application. 00:25.790 --> 00:32.810 Very simple to do using the tooling that we are using in terms of vite, we finally switched out our 00:32.810 --> 00:37.250 non production usage SQLite server for something that is production worthy. 00:37.280 --> 00:44.570 SQL server and all future development now would be taken on the SQL server itself, as we've got that 00:44.570 --> 00:50.030 running on our computer either via Docker or if you're on windows, possibly you're running that natively 00:50.060 --> 00:51.470 on your operating system. 00:51.470 --> 00:56.690 Either way, it's a development SQL server instance that we can then use to further add features to 00:56.720 --> 00:57.560 our application. 00:57.560 --> 01:04.160 There's no point in going back and switching between SQLite and SQL server now, SQLite being useful 01:04.160 --> 01:08.070 for the early stages of development, but now we've got our application deployed. 01:08.070 --> 01:12.660 We really do want to just stick with SQL server for future updates. 01:12.660 --> 01:18.270 So we've published our application onto Azure, and we've also taken a look at continuous integration 01:18.270 --> 01:19.890 and continuous deployment. 01:19.890 --> 01:26.580 So updating our production application is as simple as writing the code and then saving those changes 01:26.580 --> 01:31.020 into source control by deploying our changes onto the main branch. 01:31.020 --> 01:33.360 So just one frequently asked question. 01:33.360 --> 01:34.110 I get this a lot. 01:34.140 --> 01:39.990 By the way, can I demonstrate how to deploy to insert your favorite platform here? 01:39.990 --> 01:45.930 And there are many, many, many different platforms cloud platforms that we could deploy this to Amazon 01:45.930 --> 01:53.190 being the favorite request Google Cloud, Heroku, DigitalOcean, linode, Vultr, IBM cloud, Oracle 01:53.190 --> 01:53.490 cloud. 01:53.490 --> 01:57.420 All of these are options where you could deploy this application to. 01:57.450 --> 01:59.760 Clearly, I can't demonstrate how to do that. 01:59.760 --> 02:00.210 Otherwise. 02:00.210 --> 02:04.020 This would just be a publishing course about different options for publishing a. 02:04.200 --> 02:05.340 Net application. 02:05.340 --> 02:06.630 So I have to pick one. 02:06.630 --> 02:12.690 And sticking with a theme that we're mostly using Microsoft technologies Azure made the most sense? 02:12.690 --> 02:15.930 And Azure do give us a way to deploy it free of charge. 02:15.930 --> 02:18.840 Regarding can I demonstrate other platforms? 02:18.840 --> 02:22.620 This is kind of tricky to support because I do not control the platforms. 02:22.620 --> 02:28.170 They can change their terms of service, their user interface, their process for deployment at any 02:28.170 --> 02:28.890 point. 02:28.890 --> 02:35.040 And if I had five different options for deployment on here that were designed to be follow along, then 02:35.040 --> 02:41.280 it's very tricky to keep track of what those platforms are doing with regards to net deployments. 02:41.280 --> 02:47.130 So I can only pick one, but the concepts are really pretty much the same across different platforms. 02:47.130 --> 02:53.220 We deploy our code, we're given a URL, our application is then accessible, and we just need to provide 02:53.220 --> 02:59.700 the configuration values as we did with Azure, things like our connection string and any secrets that 02:59.700 --> 03:00.390 we need to add. 03:00.390 --> 03:04.440 We use the same approach just on a different platform. 03:04.440 --> 03:11.160 So our application is now published and we do have one more thing to go, because we didn't really take 03:11.160 --> 03:14.760 a look at Crud operations or role management in our application. 03:14.760 --> 03:17.850 So that is coming up next.