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