django-async-orm VS cookiecutter-django

I'm not sure if its official. Would love some more guidance/clarity/docs/funding from the django foundation on what it looks like to migrate legacy code to the new ways.

The rednaks repo works great for just giving the new async stuff a go. If everything else is also using async.

I did some experimentation with this. And its a pain trying to migrate a production application that uses gevent and psycogreen2.

The documentation on the code migration path is pretty sparse.

The main hiccup that I ran into was psycogreen2 not being supported.

https://stackoverflow.com/questions/67735453/django-async-or...

https://github.com/rednaks/django-async-orm/discussions/9

Consider taking a look at cookiecutter to generate projects from templates. There is also cookiecutter-django. As for your environment variables you should have an example .env file containing all the environment variables required by your project (without setting them) that can be safely pushed into your repository for you and other developers to copy into the actual .env file that'll be used by your project (add this file to .gitignore)

I'm obviously biased, so take what I say with a grain of salt, but I also probably know more about this space than ~anyone else. I'd say that your characterization is pretty accurate. There are many similar products to Pegasus (you can find a pretty comprehensive list here: https://github.com/smirnov-am/awesome-saas-boilerplates) but most of them are either more focused on infrastructure/setup (e.g. cookiecutter-django or - as you noted - far less mature/maintained (most of the others on that list).

Boilerplate is not in opposition to productivity. Especially when it’s all written for you, as it is in Django, Rails, etc. You can start with something like Cookiecutter Django.

Strongly recommend „CookieCutter“ for Django. You can build a boilerplate starter project out of it. Add your own Apps and deploy with Docker. I use GitHub Actions SSH to my Hetzner for upload the code and build the docker-images on the server. Very easy and fast.

to speed things up you could get a lot of the building blocks (environments, postgres, drf, redis, containers, etc) in place by starting with cookiecutter and then customize from there.

djangox definitely looks a bit less opinionated and lighter weight than what I normally use for a starter project, which is cookiecutter-django: https://github.com/cookiecutter/cookiecutter-django

It seems to include most everything that djangox does, and a little bit more, and with cookiecutter's setup process, you can strip out much of what you don't want/need.

the problem is that "email notification" is not something that you can easily implement as a builtin feature since you need an external service, however in my project I used multiple time email notifications without problems: have you tried to look at how for example cookiecutter django is using Anymail?

For what you're interested in using, I would suggest you look at [Django Cookiecutter](https://github.com/cookiecutter/cookiecutter-django). The original creator, u/pydanny is one of the wise and experienced Django devs who has created a lot of the literature that's become standard reading in the Django-verse. Even if you don't decide to use cookiecutter-django as your base going forward, almost everything in there is a best practice method and it simply works out of the box. It's my starting point for nearly every Django project I run.

python3 -m venv env source env/bin/activate pip install cookiecutter cookiecutter https://github.com/cookiecutter/cookiecutter-django docker-compose -f local.yml build docker-compose -f local.yml up -d docker-compose -f local.yml logs -f