dj-stripe VS cookiecutter-django

If you don't want to use Pegasus or another paid product (presumably because of the cost), the packages I'd reach for are django-allauth for login/user stuff and dj-stripe for the Stripe integration. As for teams, there wasn't a library I was happy with so I rolled my own for Pegasus, but some people like django-tenants. It's too heavyweight for my taste as it requires a more complex dev/test/infrastructure setup with Postgres schemas, as opposed to having a single-database and handling multitenancy in the application layer. But there are pros and cons to both approaches.

dj-stripe, Django library for Stripe, released a long awaited version 2.7, which features full in-db management of webhook endpoints through the admin, multiple endpoints per install, and more.

I would also recommend using dj-stripe to help with syncing payment intents and setting foreign keys to the whole payment intent object since it also will handle updates via webhooks for you. https://github.com/dj-stripe/dj-stripe

Just gonna leave this here: dj-stripe

Add Stripe to your site via dj-stripe. That will help you manage customers and plans. I strongly recommend focusing on integrating Stripe Checkout, as you won't have to handle any cards or anything like that. Unfortunately, I did not yet write a guide about that :( And I haven't found a good one online that will go into details, step by step.

I make it a point to check the current status and state of issues and pull requests for djstripe before updating or modifying the surrounding codebase codebase for every project I have that uses the module itself.

Nice work. Why start from scratch, instead of building atop https://github.com/dj-stripe/dj-stripe?

Django 4.0 support has been added in the master-branch as stated in https://github.com/dj-stripe/dj-stripe/issues/1507 But… this has not been released to pypi yet.

You might also want to take a look at the dj-stripe library: https://github.com/dj-stripe/dj-stripe

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.