cookiecutter-django VS frambozenapp

cookiecutter https://github.com/pydanny/cookiecutter-django

"1" is definitely something I'd like the team to focus on. Cookie-cutter django aims at it (https://github.com/pydanny/cookiecutter-django) but IDK I think it goes a little too far, and we should have better out-of-the-box options. I think we have this situation because of the unwillingness to make backward incompatible changes.

Use Django Environ for secret keys etc, have a look at 12 factor https://12factor.net and https://github.com/pydanny/cookiecutter-django for a solid example of a best practise setup.

Have you seen https://github.com/pydanny/cookiecutter-django ?

I don't have production level examples but cookie cutter django covers setting up points 3,4,6 https://github.com/pydanny/cookiecutter-django for you. django-allauth for point 6

You really should take a look at cookiecutter it makes bootstrapping projects easier and more customizable. You can also peek at cookiecutter Django.

> What about complex validation rules?

I wpould use my server-side form and database library, Bozen[1] to do this.

>

[1]: https://github.com/cabalamat/frambozenapp

Is it possible to give run-time types to `title` and `yearPublished`, in a way that works with mypy and the Python typing ecosystem? If so, is there a tutorial on this, as I'd like to add the feature to my ORM.

1: https://github.com/cabalamat/frambozenapp

There's a predefined table called User that holds user accounts: https://github.com/cabalamat/frambozenapp/blob/master/app/us...

There are also predefined web pages for logging in and out, and listing users. A real aspp might want ot customise the pages: https://github.com/cabalamat/frambozenapp/blob/master/app/lo...