debops VS cookiecutter-django

I'm planning on adding to the litany of tutorials on this soon. My process is to use debops to provision and secure a VPS and install the docker service. The app is spun up with docker-compose and the appropriate containers - if you use something like cookiecutter-django you can get a basis for the docker compose files you need. This uses traefik as the proxy for gunicorn instead of nginx, and then you'll need to serve static and media either with whitenoise or with S3.

I wrote a set of Ansible roles in DebOps that let you build and install LXD from source on Debian. You can check out the role itself and it's documentation. It's not a perfect solution, but it can enable you to use LXD without snaps on Debian.

If you are committed to Debian environment, perhaps DebOps would be an interesting alternative (disclaimer: I'm the maintainer of the project). DebOps is a set of Ansible playbooks and roles + some scripts that let you deploy and manage Debian-based clusters. It has extensive documentation, supports LDAP deployment and is actively maintained.

GitHub: https://github.com/debops/debops/releases/tag/v2.3.0

It's not strictly for Azure, but you can check out DebOps (disclaimer: I'm the maintainer). It's a set of Ansible playbooks and roles to manage Debian-based infrastructure, created completely in the open. You can use it as a base to build up your own infrastructure. Roles are designed to be reusable and can pass configuration between them using dependent variables, everything can be configured through Ansible inventory since you are not expected to modify the roles themselves.

Looks like that apt role has a Linuxmint dictionary key missing, somewhere where OS distributions are specified. You can look at the apt role defaults and add it in a few places where Debian, Devuan and Ubuntu are specified. The role's fact script could also be fixed to handle cases like that gracefully. I'll see what I can do.

DebOps has you covered - there are roles for slapd, nslcd, nscd, ldap role can be used to manage objects in the LDAP directory itself from other roles, and so on. Check the slapd role documentation for the server-side details, and the ldap role documentation for the client-side details.

Falco, in contrast to cookiecutter-django, aims to enhance the Django developer experience beyond project generation. It provides a CRUD generator and guides on various Django topics such as task queues, multitendency, deployment, realtime, etc.

It's not a tutorial but it's a resource to generate a Python+Django project with celery and Dockerfiles and other things you mentioned : https://github.com/cookiecutter/cookiecutter-django

There are very useful packages for bootstrapping your Django projects in minutes such as django-cookiecutter and djangox. If you are a seasoned developer I'd highly recommend using one of these instead of what I'm going to show here. But if you are struggling with the project structure of these packages as a beginner to intermediate Django developer and looking to structure your own Django projects in a better way, I have created a lightweight setup that deals with the basics of setting up a Django project with PostgreSQL as database and TailwindCSS as our styling library.

And so, the idea for cookiecutter-django-lite came into existence. I am an absolute fan of https://github.com/cookiecutter/cookiecutter-django - but for a lot of use cases this template is an overkill so I thought a barebones version of this will be superuseful - and that's how the idea of cookiecutter-django-lite was born.

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).

I followed a lot of the guidance found in this "template" here: https://github.com/cookiecutter/cookiecutter-django

If you understand all that and just want to get started as quickly as possible, use a project generator such as cookiecutter-django or API Bakery. Note that I'd avoid using these until you have a solid grasp of Django otherwise you'll have no idea what's going on.

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.