cookiecutter-django

cookiecutter-django copied to clipboard

Description

It would be great if django-allauth became an option instead of a default.

Rationale

A lot of sites I create are for internal users and don't need all the features that come with django-allauth. It is not trivial removing all the references from it in my projects without breaking something.

Huge upvote!!

Anyone? :D

In a month time, there seems to be some interest.

Trying to evaluate how difficult such an option would be to maintain... Doing a quick search in the code, it doesn't seem too difficult, however, I see in base.html that several views are currently provided by allauth:

https://github.com/pydanny/cookiecutter-django/blob/bf2d5370be5334f7037aead9f544aed8d5416cf2/%7B%7Bcookiecutter.project_slug%7D%7D/%7B%7Bcookiecutter.project_slug%7D%7D/templates/base.html#L54-L72

Should the template provide these if allauth is opted-out? If so, I guess we would need to have another account app that we would delete in post gen hook if allauth is opted-in...

Imo if you don't need allauth, then I don't find it necessary for cookiecutter-django to create its own account app to make up for the registration. I think people are simply asking to not have a signup and stuff in the first place. So having the option to remove django-allauth is basically asking cookiecutter django to not have registration integrated with the UI.

@Andrew-Chen-Wang I think there is also the scenario where you want to use something else, specially if you are not interested by the social apps, for instance I like to use https://github.com/macropin/django-registration in my Django projects. My 2 cents :)

Hi, is this feature up for consideration? I can start working on it if it is. Thanks!