The built-in User model doesn't cut it for real-world. Have to decide whether to sub-class the AbstractUser or the AbstractBaseUser. The former is easier; the latter more flexible.
Everyone says you have to do this before your first migration. I feel like we should be able to do this now because we haven't done anything with users yet. We'll see. These sites say it can be done.
The built-in User model doesn't cut it for real-world. Have to decide whether to sub-class the AbstractUser or the AbstractBaseUser. The former is easier; the latter more flexible.
Tips on sub-classing AbstractUser: https://learndjango.com/tutorials/django-custom-user-model
Tips on either approach: https://testdriven.io/blog/django-custom-user-model/
Everyone says you have to do this before your first migration. I feel like we should be able to do this now because we haven't done anything with users yet. We'll see. These sites say it can be done.
More than that, we can easily just wipe and recreate the database.
Let's try the approach at https://testdriven.io/blog/django-custom-user-model/