Registration view for User

Description

The packages to install in requirements.txt should be seperate for local deployment and production deployment.

Use fixtures to auto create superuser and other model objects.

Description

Add a Proper Django Admin view for the User model.
You can search user by first_name, last_name and email
list view presents necessary information
you can filter users based on user_types i.e is_staff, is_admin, is_buyer, is_seller

Description

Local, Production and test settings should be in different files.

Coming soon or a nice webpage telling about the project would be fine

Description

Add User model Create/Change Form class that has fieldsets and more organized information

Description

Currently when the user is created it is active by default.

Expected behavior:
Upon signing up, a code should be sent to his email that should be valid for a time period and if he enters that code before that period then his account should become active otherwise he would remain inactive and have to re generate the code in case of expiry.

Description

Currently we have boolean fields for is_seller and is_buyer
There needs to be a seperate model for that

Write Basic Tests for User model that check if user is successfully created.

Description

Add 📝 docstring for UserManager class.

A Basic Login view with email and password field using class based views

Description

(First time contrib here, please don't bite.)
Module 'registration' does not exist (yet) but is already included in settings.py and shopspot/shopspot/urls.py. Makes it impossible to use manage.py and test stuff.

Steps to Reproduce

1. Clone the repo
2. Run in terminal 'python manage.py makemigrations' or 'python manage.py runserver'
3. You will get an error 'module "registration" does not exist.'.

Expected behavior:
'registration' module should be already included in the repo, otherwise it shouldn't be referred to in other files.

Actual behavior:

Reproduces how often:
100%

Versions

Python 3.6.6
Django 2.1.2

Additional Information:

Seems like a partially implemented registration feature.

📝 Write Docs for User class

for guidelines reference this page

Create a custom django user model that has

• Email as default username field
• Has is_seller and is_buyer flag

Currently the user has all permissions set to True by default
Add the default permissions to the User as are provided by the django.contrib.auth.User Model.
We would have to add the permission mixin maybe make some adjustments.

Create Api layer for user model