Welcome everyone to this section of the course or we're going to focus on actually the point.
Our web site to the internet so anyone can then visit your website.
Or we're going to do just explore a couple of details that allow us to actually the Player Tango application,
and I want to start off by thinking about what are the key requirements that we need when having our
website up and running on the internet.
Well, we first want to make sure that anyone can visit our website online, which means we don't want
to concern ourselves with things like uptime or resiliency.
So, for example, throughout this entire course, we've technically been hosting the website, but
we've only hosted it locally and only let it be accessible locally.
If you were a really good programmer and had really good internet and really robust resources in terms
of servers and computers, you could technically host the website yourself.
However, that's actually super complex.
And pretty much if anything goes wrong with your local computer setup, then your website will be down.
So clearly, we want to use some sort of cloud service provider.
We also want to make sure that we're able to ourselves connect to that cloud server easily and that
that cloud server supports things like Python and Django.
The other part of this is that we need to be able to push updates to our code and have version control
when we want to add new features to our website.
So what we need to do is choose a cloud service provider.
And that's essentially a company that is going to host a computer or server with our single application
living on it along with the database.
And I should point out, there are many cloud service providers.
There's eight of us Google Cloud, Azure, Heroku, Lennart, and there's often a tradeoff between ease
of use and price.
And it doesn't really make sense for us to show an example through the dozens of cloud service providers.
Instead, we want to do is pick one that is ideal for someone who's just gone through this course and
then wants to launch their website.
And a cloud provider with a really nice balance between price and ease of use is Leonard.
And we can use Leno to set up an online server that contains or Jenga web application.
And what's really nice about Leno is it actually has what's known as a Leno app marketplace that essentially
allows us just to fill out a form, click a button and immediately launch a jingle project live to the
web.
It's super easy to use, and it's actually really affordable.
Speaking of affordability, we actually provide you a link for $100 in line note credit.
And I should point out that what we do throughout this section of the course, depending on how long
you run, your website shouldn't take up the full $100.
Now, let's talk about the fact that you will have to actually provide your credit card information
even with a link for the line of credit, and you should note that any major cloud service provider
is going to require your credit card information in case you go beyond the credit or free tier limits.
And by continuing with this section of the course, you understand that you may be charged if you exceed
the limits.
And again, what we show in this lecture, this section of the course should easily fall within the
$100 credit limit, but cloud services are going to be charging monthly, so eventually the credits
will be used up.
You can't just run this in perpetuity for free forever.
Now, if you have any questions on pricing information or charging information, please contact your
specific cloud hosting provider or check out your dashboard there.
US personally are not going to give you any advice regarding payments or credit limits, and if you
ask a question saying how much will this cost or how much will this charge me?
We're pretty much going to have to redirect you to the cloud hosting provider and their dashboard there
because we want to make sure that you get the most accurate information.
So just keep that in mind.
We can't really answer questions about pricing information.
You'll have to explore those yourselves depending on your situation, the instance you end up running
and creating and your cloud hosting provider.
Now that was the information on the cloud service provider.
Remember, we also need version control for the actual code underlying our website, and we want to
wait to be able to edit or website's code and keep track of those changes.
And for this, we're going to end up using a system called Get or I.T. and that keeps track of the actual
versions of your software.
So version one, version two, version three and so on, and we're going to end up using GitHub to actually
store our code.
So sometimes beginners are confused on this.
Git is the actual open source version control system and Gets Hub is technically a subsidiary of Microsoft,
which allows you to beyond a certain free tier, actually just host code for free.
So we'll be using that and then in turn will be using it to push and pull changes to our website.
Now, I want to quickly visualize our website hosting structure and version control structure so we
understand everything that's going on.
So we're essentially going to start up a server using Lennart and within that server.
You can think of this as just a really small computer or really large computer, depending on the actual
instance you and the purchasing.
And within that server, that little virtual computer, we end up creating our jungle web application.
This is essentially everything we've just did locally, except now we're doing it on a computer that's
being hosted by Lenovo.
And that way, the user browser can then access the server.
Hey, show me this Django web application at the specific IP address, which you could later redirect
to your own custom domain name.
And again, we're using Leno for this aspect of the cloud service provider.
Next, we also want to do is make sure that we actually are able to update our code, so we set up what's
known as it gets repository, which includes a copy of the website code that I can then make changes
to.
And when I'm ready to actually deploy those changes, I can connect them to the tangled web application.
This allows me to edit the code that's being hosted on GitHub without having to worry of breaking the
website if I'm trying to test out new features.
I can just mess around with what's being hosted on GitHub and then when I feel it's ready after testing
it locally, I can push it to the Django Web app that lives on the server.
And I should note that it's going to be slightly more complicated than what I show here in order for
our computer to actually connect to the server.
We need to use what's known as an SSA connection, and we'll talk about that later on when we actually
deploy our Django app using the Linux marketplace.
But just keep that in mind.
There is going to be a special, secure connection that we can make to our server in order to actually
edit things that are happening on that server, rather than just viewing the actual website.
OK, so we're going to start off by setting up our Jingle Web application, using what's known as Notes
Marketplace, I think you're really going to like how easy it is to use and this will do again, a lot
of setup work for us automatically.
It's actually going to automatically start a new jingle project and link it to an IP address on the
web at a port.
So it's super cool about this is pretty much thing like a few minutes.
You're going to have a jingle project already set up live on the web that you can visit from anybody's
browser.
It's super cool, so I'm excited to get started on it.
All right, I'll see you at the next lecture.