Users can log into the site, but they can't log out.

This is something they'll probably want at some time.

Thankfully, with all of Django's provided batteries,

this is as simple as a single function call.

Before a user can ever log in or log out though, they need to be able to sign up.

I think, we can tackle both of those things in this video,

logging out and signing up.

Join me in Workspaces to get started.

I actually already have a URL and a view for logging out.

Django provides me one in the URLs from the contrib package inside

these URLs right here, but let me show you what happens if I go there.

So, accounts/log out, kind of default standard name.

And I get this page, right?

It renders as admin template and not the template I like, right?

I would rather that the log-out view just redirect me back to the home page.

So, I'm gonna build that.

That's the nice thing, I can kinda just do the stuff I wanna do, right?

So, I'm gonna make a new url and

it'll be r"logout and

we go to views.LogoutView.as_view.

And the name will be logout.

All right, and then if I go over to views.py, I need to make the logout view.

Now that might seem backwards to some of you, making URL and making the view.

I guess, it kind of is, Django cares a little bit, I kind of complain, but

it doesn't really care.

You're just kind of do whatever you need to do.

So, I'm gonna import the logout function, which comes from the same place as login.

And then this is actually going to be a, Redirect view.

So, it's gonna be a view that just automatically redirects the user

at the end of it.

So, I'm gonna call this LogoutView and it's gonna be a RedirectView.

And redirect views require an argument named url,

which is where they redirect to.

So, I'm gonna redirect back to home.

And then in the get, which is what is fired when the get request comes in.

I'm gonna actually log the user out.

So, I'm gonna take the request, I'm gonna take the args and the kwargs.

I'm gonna call logout with the request, which since normally we

would login with the request, now we logout with the request.

So, same difference, I just called one request and

the other one got from the class.

And then we return super().get(request, *args, **kwargs).

Because I wanted to go ahead and do its normal return, right?

So, this view doesn't use a template or anything like that.

So, it's it's actually done.

So, If I don't typo.

So, I've been logged out.

So, that's awesome, and I can see the menu shows that I'm logged out and all of that.

Okay, so now what about signing up, right?

I need to be able to, I can log in, I can log out, that's great.

I can get in, I can get out, but I don't have any way of creating an account, so

I need to do that.

So, let's see, accounts/signup.

Now, and if I look here, there is no accounts like register or

create account or anything like that.

So, it must be that I need to make this view all by myself and it turns out, I do.

And that makes sense because creating an account is often very customized

to the site that it's on.

Okay, so I think, I can get by using a Django provided form for

creating a new user.

And I'll just write a create view for it.

It's worth a try, at least.

So, here in this, I'm only importing this AuthenticationForm, I'm also gonna import

UserCreationForm, and that's a form as you can probably guess for creating users.

So, then down here at the bottom, one two, I'm gonna make a SignUp view.

And I'm just gonna call this one SignUp.

So, this is going to be a CreateView because it's

creating a model and form_class = UserCreationForm.

The success_url should be

reverse_lazy("login").

That way they can go to the login page and

then template name is accounts/signup.html.

Okay, fairly straightforward and I'm gonna make that template.

So, signup.html, over here in accounts.

And I'm just gonna use this one, so I just paste it in the other one here.

So, it's gonna say, Sign Up and Sign Up, and

the form stays the same and then this would be Sign Up as well.

All right, I think that's everything.

So, different headline,

I bet you could think of a really good way to make it easier to change that headline.

Okay, so time to try this, all right?

Let's see, did I have a url for that?

I didn't, I need to add a URL.

All right, so, let's see, signup,

SignUp, signup, all right.

All right, so, here we go.

I've got my Username, I've got my Password and Password confirmation.

So, okay, let's try making a new one.

Let's say, testuser, And hit Sign Up.

That username already exists.

Okay, let's call it treehouse.

Okay, now I should be able to login with treehouse.

All right, not bad, I can log in, I can do all of this stuff.

But let me go back to this Sign Up form again, real quick.

So, one of the things that bugs me with this, is there's no email on here.

It says username, I know that is the username,

it's gonna show up as the username.

For right now though, I want this to say display name, right?

I don't know exactly what I want but for now that's what I want.

So, let's see, if I can change this form.

So, up here in accounts, I'm gonna make a new file, which is gonna be named

forms.py and then inside here I'm gonna import that same form, right?

So, I had this UserCreationForm here, so I'm gonna import that.

And while I'm at it, I'm gonna take it and then I'll leave it in the view for now.

Okay, so I've got that and then I need to import the model.

So, from django.contrib.auth.models import User, cuz that's the model, right?

So, I'm gonna make my own form here.

So, I'm gonna call this UserCreateForm instead of UserCreationForm.

But it's gonna extend the UserCreationForm.

And then I'm just gonna specify the class Meta,

and I'm gonna say the fields that I want it to add.

So, I wanna show the username field, I wanna show the email field and

then there's two fields named password1 and password2.

We should show both of those, so that's for

the password and the password validation.

And then the model will be User.

Okay, now I want to rename a couple of these fields,

I wanna change the label, at least.

So, I could redefine the fields in the form, but that's a lot of trouble,

cuz if you look, there's all this help text and stuff.

I don't wanna have to recreate all of that.

So, I'm just gonna override them here, inside the form.

So, self, *args, **kwargs.

And I'm gonna call super().__init, and that's gonna take *args and **kwargs.

And then I'm gonna say self.fields["username"].label

= "Display name".

And self.fields["email"].label = "Email address".

It may say something like that already but just to make sure.

Okay, so I think, it's gonna work, but

now I need to use this form in my view instead of the old one.

So, I'm gonna take that out and then we'll say, from .import forms.

And then down here at the bottom, forms.UserCreateForm.

Okay, so that should use my new form.

So, let me refresh this and yeah, look,

there's display name, email address, password and password, so, awesome.

There's the form that I want.

One thing, I didn't do that's a good idea,

is some sort of user validation on sign up.

I'm sure you've used a site where you had to click a link that was emailed to you to

verify, yep, I'm actually me, and I actually wanted to sign up.

That's a bit beyond the scope of this course, but I'll link to a library or

two in the teacher's notes that make it a lot simpler to implement.

Check those out before you put user registration on a live website.

I think, there's only one thing missing from the site as far as registration and

stuff is concerned.

What would your users do, if they forgot their password?