Whenever I deploy an app, I always use cookiecutter-django. I’m pretty sure there is an option lying somewhere in the settings that let you disable username. If not, I believe the BaseUser model has the option of the unique identifier or username be set to the email itself.
Otherwise, you can do what you said, which is abstractbaseuser model. Or you can setup a manager class. Check the Django source code for a little more insight. On Wednesday, November 20, 2019 at 6:50:01 AM UTC-5, mmk mmk wrote: > I want to replace django default username and password authentication with > email and password authentication, > i have many solution like extends Abstractbaseuser or using 3rd part like > django-allauth . > My question now which is best practice to using to do this? -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e9dbd28e-3fc0-4954-bdd4-12938f80e24d%40googlegroups.com.
