Hi I'm Ken and I'm a Django teacher for treehouse.

Building applications in Django isn't the most difficult thing in the world, and

you probably built a couple by now, either with treehouse or on your own.

Once you build your project though you'll want the world to see it.

Years ago deploying python and Django sites, well it wasn't fun.

I remember keeping a very long text file of all of the steps I needed to do

to get updates deployed on a site I built with a very early version of Django.

Those days are far behind us now though with platforms like Heroku.

Heroku provides all of the supporting tools your Django site needs,

like a database and web server, and

makes deploying updates a simple as pushing changes to a git repository.

Stick around and I'll show you how to get your Django site live on Heroku.

So I'm gonna start by creating a Heroku app.

So, you should go to Heroku.com and sign up or log in if you haven't already.

And what you're currently seeing is the Heroku Dashboard.

Now, this may look different when you get there.

I have sadly no control over what Heroku does,

but this is how Heroku looks right now.

So this dashboard is an overview of all the apps you have on Heroku,

as well as ways of adjusting settings for those apps.

Ar Heroku app is kind of like a container for your Django project code.

It's where you put the code that you want to Heroku to run, by creating an app

on the Heroku dashboard you're effectively reserving space in Heroku for your app.

So I'm going to click the new button up here in the top right corner, and

I'm going to choose new app from the drop down,

I could also click create a new app right there.

Now in the app name field I'm going to put in a name for

my Heroku app, so I'll call it djanoal.

In the run time selection here

I'm just going to leave this as United States because where I'm based.

If you are based in Europe or Asia, you might want to choose Europe.

So, I'm going to hit create app.

And now I'm looking at the dashboard with a Heroku app selected.

So you'll probably be taken directly to this Deploy tab, but

let's take a minute to talk about what each of these tabs on the dashboard does.

If we click Overview, then we get this Overview screen for our Heroku app.

We can see all of our configured add-ons we can see all of our dynos, and

see the activity, what we've done,

what our collaborators have done, all that kind of stuff.

This becomes more and more useful as you do more and more stuff.

If I click on resources, then I see two sections, I see Dynos, and I see Add-ons.

Now Dynos are a central concept to deploying with Heroku,

you're going to see this word a lot.

The number of Dynos that you have roughly correlates to how much computing power and

memory your app has.

With the Heroku free tier, which is what I'm gonna be using for

all of this workshop.

I'm limited to Heroku's smallest dyno sizes, and

I'm limited in the number of hours the dynos can be active.

Roughly though it equates to being able to run the app, run the project on a single

machine with about 512 megs of RAM, and I can run it for about 500 hours per month.

Exact details are in the teacher's notes, but

this free tier is more than enough to get things started and just play around.

You'll notice that there is no diners right now though because

I haven't deployed anything to the Heroku app.

Once I deploy an app with a proc file which will get to in a bit,

this section will have a lot more information.

So I'll talk more about proc files and

this section in a future video, the add-ons section right down here,

is where we can add external sources and services to the Heroku app.

Part of the benefit of deploying with Heroku is a huge range of third party

services like logging tools and data stores and all sorts of stuff.

These add-ons are specially configured to work well with Heroku app

with a very little configuration for you.

A lot of them have free tiers,

some of them do cost money, you'll investigate them each as you need them.

We're gonna add an add-on right now though, and what I wanna do is here in

this add-ons bar I'm gonna search for Heroku Postgres, and look there it is.

I'm gonna select that and

then notice these are the different price tiers, right?

So if I want just the hobby one which is what I want, that's free But

it goes all the way up to $7,000 per month for

this Private 7 database, that's just amazing.

So I'm gonna choose the Hobby Dev-Free and I'm gonna hit Provision, and

that's going to provision this database for me.

And now you can see it's down here, all right, there's that.

In creating and

developing this django project I've been using SQL lite as a data store.

SQL lite is great for local development, but it doesn't work on a Heroku.

Heroku dynos provide computing power and memory, but they have no disk space.

Only the things that are bundled into your project are available to tje Heroku app,

and you can't expect changes to files to stick,

only if they change in your GitHub repo and

your Git repo they'll stick, if they change anywhere else they will not stick.

Since we don't have a permanent file system SQLite out of the question.

And so because of that I'll be connecting the Django project

to this Postgres database, and I'll do that in the future video.

So let's move on to the tabs, let's go back to the deploy tab and here we see

the methods that Heroku offers for getting your project deployed to Heroku app.

We'll focus on this a bit more in a future video, but

if you want to scroll through here and read stuff over go for it.

The metrics tab unfortunately only displays metrics for

paid apps, which will not be covered in this workshop.

But if you upgrade it's a cool thing to check out.

The activity tab here gives me a log of all of the app specific

actions that have been taken by me or my collaborators for this app.

Right now it doesn't show a whole lot,

it shows that we created an initial release of the app down here.

We enabled Logplex, which is done by default and we attached the database.

So yeah, that's the stuff I've don.

The first two actions are done automatically when we created the app,

the third is the database we just created out of the resources tab.

I know you all picked that up, this tab will also display our deploys

once we start deploying as well as in the other settings changes.

The access tab here lets us add collaborators, which is helpful if we want

other developers to be able to deploy and manage our application.

For now though the only collaborative that's listed should be

your Heroku account, and in my case it's this one.

And the last tab over here settings controls a whole range of configurations

for the Heroku app.

Here you can change the name of your app.

You can show config variables, you can change them as well.

You can add domains and you can even delete the app entirely,

if you come all the way down here.

You wanna delete it?

You can throw it away.

The part of this page that's relevant for this workshop is up here at the top,

this config variables section.

If you select the reveal config vars you'll see that Heroku added a URL,

it added this database URL in this string over here.

That's the connection string for the database.

Most of the secret configuration for

projects that get deployed on Heroku happens to reconfigure variables.

We'll be covering those more as this workshop goes on too.

There's one last thing to notice about the Heroku dashboard.

If you click open app, up in the top right corner the page,

you'll taken to a page showing your new empty app.

In the next video I'm gonna replace this placeholder page

with the actual Django project.