Like I've said many times before, Django loves us and

wants to save us time and trouble, so it's made it easy to log users in.

You've logged in to your Django admin panel before but that only works for

users that are marked as being staff members.

You don't want to make every user of your web app a staff user though.

And you don't want them all to log in to your admin panel either, but

all of that functionality exists, so you can probably use it.

There's obviously some code somewhere for

logging users in because the admin doesn't.

Let me show you how to use that log-in function and

a few other tools to make your very own log-in view for your users.

Django actually has a few different ways of handling log-in forms,

views, the whole log-in process.

So needless to say there's, you know, been a lot of approaches to this.

The approach that I actually always used is this one that's here in the docs you

would call authenticate and then you would call this login method to log the user in,

or this login function rather.

You don't have to do all that anymore.

You still have to call log in.

Well sorta.

We don't have to do authenticate and so

like that Django provides some tools for that.

So that's pretty cool.

So let me use Django's provided goodies to save myself some work.

So before I do that though, I'm going to create a new app

named accounts, and this app is going to hold just

any sort of stuff I'm doing that's dealing with accounts.

So if I made a user model or just whatever.

So I'm gonna create that and then I'm going to add that to my installed apps.

And I'm gonna add it above communities just in case

communities need to rely on accounts.

And then here inside of url.pie I'm gonna add a new URL for accounts.

I'm gonna include accounts.urls,

namespace=accounts.

All right, cool.

So there's that.

So now if I refresh my tree over here then I should see accounts and

I'm gonna go ahead and create the templates folder and

inside of there I'm gonna go ahead and

create accounts cuz I better have some templates.

And then I'm also going to create the urls.py file because and

we gonna have some urls and in fact I'm gonna go ahead and

get that started so from django.com.url from .url

import view and then urlpatterns is an empty list.

All right cool.

I mean it's just it's just a blank shell for now.

Okay so I think I'm ready to start creating my view.

Now this view is going to be a form view it's not a creative you or

an update view but they're very similar.

So I'm gonna go ahead and do from django.views import generic so

that I can use form view I have a couple of other imports I need to do, though.

So I need to do from django.contrib.auth.forms

import AuthenticationForm, and

this very appropriately named form is the form that handles authenticating the user.

So authenticating means Is there an account that has this username and

this password?

It's not actually logging the user in,

it's just making sure they are an authentic user.

I'm going to need to do a redirect when the form view is complete, so

I'm going to do an import for

reverse lazy, so that I can get that URL without having to have like a method

that does that, and then like I said I still need to use the login function.

So I'm going to do from Django.contrib.log and forward login.

Okay, pretty sure I'm all ready to do this view.

Now this isn't the simplest view ever, so stick with me to get through this one.

So LoginView(generic.FormView) and

then the form_class is going to be AuthenticationForm.

The success URL is going to be

reverse lazy post going all.

Because I want to go to all the posts once you're logged in and

the template name is going to be accountslogin.html.

So far, pretty basic.

But now I need to override get_form,

and it takes two arguments which is self and form_class.

Form_class by default is none.

You should be used to this kind of thing with our mix-ins.

We set something to none and then we check to see if it's none.

So if one class is none, then the form

class is equal to self-Git form class.

And then we're gonna to return the form class.

Now the default view just or

the default class rather just does this get form cards and that's it.

But the authentication form of the first argument to it has to be the request.

So I need to send back self.request and then **self.get_form_kwargs.

And then, if the form is valid, so they've successfully submitted and

the user is a real user then I'm gonna call log in, and

I'm gonna pass it self.request, because that's where it creates the session and

all the data that actually validates the request as being from the user.

and then I'm going to call form.get_user, and this is a method provided by

the authentication form for getting the user that's been authenticated.

Then all return super( )_form_valid(form).

All right, so not the easiest, simplest view ever but it's not terrible either.

Okay, so

I do need a template though cuz I said I was gonna have this login.html template.

So I'm gonna need that.

And this is going to extend the layout.html template

which is my template that just kind of covers everything.

And then I'm gonna load the bootstrap3 library.

So bootstrap3 is a library that lets you automatically create some bootstrap3

things in your templates and

the template that I'm using the,

the design to build that I got uses bootstrap3.

So that's why I'm using the bootstrap3 library here.

So inside of here I'm going to make a div which is a container.

Apparently it automatically creates an extra div for me, thanks.

And then I'm going to try on that just as log in.

I make a form where the method is post.

I'm going to enter the CSRF token, or print that out at least.

And then I'm gonna use the bootstrap form template tag to render my form.

And then I'm gonna do an input type = "submit" value =

"Login" class = "btn btn-default".

Alright.

So that should handle all the template work that I need to do.

Basically I'm just printing out a form, right?

This is equivalent to doing like form.asp,

but the fields will get some special CSS, and or

some special html wrapped around them so they take advantage of the bootstrap3 CSS.

Okay, last thing I should have to do is to make a URL for this.

So url and

I'm just gonna say login and

views.LoginView.as_view() and name='login'.

All right, so now you will to go and test this out.

So, if I go to accounts login.

And restart my server here.

And there we go, okay?

And I should have to log in with my usual username and

password, and if this worked, this menu should change.

Yep, there we go so now I have post communities.

I can see the thing, where I can make new communities.

And, I can delete my post.

So, that's pretty cool, it works.

Now, I told you earlier though, that there were multiple approaches.

And, there just happens to be an easier way.

Honestly, I think this one's pretty easy.

It's not that bad, but what if you could do all of this, and

even a little bit more in a single line of code?

Well, a single line of code and a copy of the template that I just made.

Yeah? Okay.

So back over here in my MSD urls.py, I'm going to add a new line Of URL's.

Now I'm gonna put it below this one because django looks from top to bottom.

I have a feeling I'm wanna override some accounts URL's later.

So that way I can kind of put one here, take one out whatever.

So we're gonna accounts again, and

I'm going to include django.contrib.auth.urls.

Now I'm not going to give this one a namespace,

because these are Django's URLs.

I don't want to, I just don't want to namespace them.

And then I'm going to go over here and

I'm going to comment out this one, because I don't want to use it anymore.

All right, I want the Django provided one for login to work.

If I refresh this URL accounts log in, I get a template doesn't exist.

And it's looking for a registration login.html.

And that's true.

That template does not exist.

So I'm gonna come down here to my global templates directory.

I want to make a new folder called registration and then inside there.

I'm gonna make a new file.

That's called login.html cuz that's what it's looking for and

then I'm gonna to take this login, copy, paste, save, refresh.

Hey look it's the same form.

It looks exactly the same.

All right. So now I should be able to log in

here as well.

So if I do kennethlove, test password.

Then I should still see but I got a 404 something's not found what's not found?

It's trying to go to accounts profile, why is it?

Why is trying to go there?

Well I don't have that view and I don't want.

I'm not going to make that right now.

So I need to deal with this and the way that I deal with this is

by changing it inside of msg's settings.py.

Then at the bottom, I'm gonna add a new setting and

the setting is named log-in redirect URL.

And so this can actually be a URL like /hello.

Or this can be a URL name.

I want this to be the name posts all, so I'm going to redirect to there.

So now if I go back and

I log in.

Then I should, now I get taken to the Post page.

Cool, there it is.

Thanks to code already provided by Django,

you didn't have to write a lot of new code.

That's exactly how Frameworks was supposed to work.

You'll see that as a common pattern throughout this course.

I'll be using Django's tools as often as possible.

Now though, users can log in, but then they're trapped and can't log out.

Take care of that with me in the next video.