So the Django project is now running on Heroku.

Has a robust database backing it, and

the configuration is all safely stored in environment variables.

What's left now is correctly configuring the static file setup, and

deciding what extra pieces we need to have before sharing our app with the world.

Let's start by getting our static files serving correctly on Heroku.

There's a couple of options here.

You can either serve the static assets directly from Heroku, or

you can move your static assets to a third party host like Amazon's S3 service.

Both have pros and cons, and if your app starts getting a ton of traffic,

moving static assets to something like S3 can have large performance benefits.

Since we're just starting out though,

starting from Haroku seems like a fine choice.

And that's what I'm gonna set up.

So in your terminal you need to install the white noise package and

we're going to save it to requirements.txt as well.

So let me get out of here cuz this is still

inside Haroku, pip install whitenoise.

3.2.1 double equals and then I'm gonna make sure and

add that into the requirements file.

There's that.

Now whitenoise is a Python package that's designed to make

serving static assets easier.

It's designed to work well with content delivery networks and it provides benefits

like compressing content and setting correct caching headers.

It's the Heroku recommended package for serving static content.

Now that we have it installed,

we need to link it to our application in two different places.

So in the settings file, the deploy settings.

We're gonna add one new line down at the bottom, which is STATICFILES_STORAGE.

Which is going to be equal to

whitenoise.django.GzipManifestStaticFiles- Storage.

This tells our project to use whitenoise as static file storage for

storing static files and finding static files and all of that stuff.

Next, I wanna open up the deploy.py and

if you remember this is our deploy ready wsgi file.

And I'm gonna add a line up here at the top and

I'm gonna say from white noise .django import DjangoWhiteNoise.

Then down here after the application equals get wsgi application I'm

gonna add a new line, where I'm gonna to wrap the application that I got

from the get wsgi application function.

With the DjangoWhiteNoise app so application

is going to equal DjangoWhiteNoise application.

And I just noticed that I misspelled import so

don't do that spell import correctly and then save your file.

So both those files are saved back in the terminal.

I need to go ahead and push those so git add dot,

git commit dash m add whitenoise to project and

git push heroku master.

Now once the project is done building and deploying, I'll be able to go to my

web apps URL in a browser and I should see that the site looks better.

So now that it's deployed, I like to test this by going and double checking

the admin, which before when I logged in looked like this and now when we refresh.

We get an exception.

And I got the exception because I have a typo in my deployed.py.

So let's go fix that.

So I go back over to my editor and I look at deploy.py,

I typed whitenaise instead of whitenoise.

And some going to git add dot git ci dash m typo.

Sorry git commit dash m typo and git push heroku master.

Typo's like that will bite you quite often.

They happen to me a lot so double check everything especially

when you're working with Heroku or any other host.

Okay, now, that's the deployed again, I'm gonna go and

double check the app and there we go.

Everything looks correct we have all the C.S.S.

that we're supposed to have in the admin.

So congratulations again.

You've successfully deployed your Django project to Heroku

with a good separation of configuration and code, a stable data base backend, and

proper serving of static assets.

Your site is now ready to use and share with the world.

Now, from here you have a whole world of operations of what to do next.

You can start using and sharing your site as is,

but you might want to add a custom domain to your site.

And you probably should add HTTPS if you're having users create accounts

and log in.

Every domain and HTTPS setup is slightly different, but

I can provide some general tips on getting this working for you.

With adding a custom domain, make sure to add that domain to your app,

either in the Heroku dashboard or the Heroku toolbelt.

So that Heroku knows how to route the domain to your app correctly.

You'll add a C name from your DNS provider to your Heroku app URL, and

Heroku will pass through traffic to your app.

One common gotcha is forgetting to add your new domain name

to your allowed hosts.

If we we were adding django.com to our site, our allowed host would

look something like this In the settings we'd have localhost, .herokuapp,

and then we'd also wanna have .djangoal.com.

That way any subdomain we added for djangoal would come through.

Now speaking of DNS providers, some DNS providers, or

domain registrars, will make it easy to get set up with HTTPS.

If your DNS provider, or registrar,

makes it easy to get an HTTPS certificate, then you can use the Heroku SSL add on.

Which I've linked to in the teacher's notes.

The Heroku SSL endpoint, it costs a bit of money,

it costs $20 per month, per Heroku app that you add it to.

But you get to use your own certificate and have that level of trust.

If you wanna get going quickly with HTTPS and you're okay with trusting your DNS

provider using Cloud Flare for DNS gives you free HTTPS on your domains.

The catch is that the HTTPS stops at Cloud Flare.

So the connection between Cloud Flare and Heroku is still regular HTTP.

This is probably okay for most apps especially if you're just getting started.

But it's something to be aware of.

Once you have domains and HTTPS set up, where do you go?

Well my next step is often using Heroku's Pipelines feature.

So that I can test against a staging.

Let me show you where that is, it's here in Deploy, there we go.

So that I can test against a staging.

Like a staging server, before pushing my project to production.

In the Heroku dashboard here in the deploy tab, there's a button for

this new pipeline.

You can click that button, and change the pipeline name if you want, you can leave

it as the name of your project anyway, and then you can click create pipeline.

And now you're gonna be taken to this pipeline overview screen

where you'll see that the app is listed here as the production app, and

the staging area is empty.

If you create a new app by following the instructions back from video one, and

so the what is it,

out here on the personal apps thing you'd have a thing here that says create app.

If you do that and you create your app.

Then you can add that here as the staging step of your pipeline.

So you probably name it like Djangoal staging.

You'll need to update your get remote to point to the staging server and so

now you deploy to staging instead of production and

you can test your app before your users see it.

Then when you're ready to deploy to production,

you can go to the pipeline overview screen which is this one here and

promote the build from staging to production.

Heroku will take the exact build that's on staging and deploy it to production so

you'll know exactly what you're getting.

From here, there's still so much you could do to give you peace of mind and

make your life easier like adding logging or error tracking or app metrics.

And you should definitely feel free to explore what Heroku and

their adon partners offer.

For now though I'm gonna leave the rest of that to you and

I'm gonna go get on to other stuff.

Thanks for watching the series and have fun deploying your Django apps to Heroku.