cookiecutter-django VS redwood

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.

Frameworks are a theme with this month's Release Radar, so here's another. Redwood is a full-stack, JavaScript/TypeScript web application, designed to scale with you. It uses React frontend for the frontend and links to a custom GraphQL API for the backend. The latest version includes a bunch of breaking changes such as moving to Node 20.0, the Redwood Studio, and highly requested GraphQL features such as Realtime, Fragments, and Trusted Documents, the server file, new router hooks, and heaps more. If you've previously used Redwood, you'll probably want to upgrade to version 7.0. The team have put together a handy migration guide for you to follow.

The other piece of important information to acknowledge here is that when we say RSCs need a framework, “framework” effectively just means “Next.js.” There are some smaller frameworks (like Waku) that support RSCs. There are also some larger and more established frameworks (like Redwood) that have plans to support RSCs or (like Gatsby) only support RSCs in beta. We will likely see this change once we get React 19 and RSCs are part of the Stable version. However, for now, Next.js is currently the only framework recommended in the official React docs that supports server components.

Although there are quite a few opinionated battery-included frameworks that have picked up everything for you like RedwoodJS, Blitz, and Create-T3-App, you still need to choose between them and hope that they will remain mainstream and well-maintained in the future. So how should we choose?

Web development frameworks in JavaScript, such as NextJS and RedwoodJS, have gained popularity among developers. Choosing the right framework, library, or tool for a project is crucial for efficient development. Developers often seek the best tools to save time and avoid reinventing the wheel.

The community here is pretty friendly. https://redwoodjs.com/

Next.js 13 ignited the first wave of attention to React Server Components (RSC) around the end of last year. Over time, other frameworks, like Remix and RedwoodJS, have also started to put RSC into their future road maps. However, the entire "moving computation to the server-side" direction of React/Next.js has been highly controversial from the very beginning.

I'm currently experimenting with the fantastic Redwood framework. However, while going through the excellent tutorial, I didn't find any guidance on using data validation libraries like Yup, Zod, Vest, etc. So, I had to do some investigation and came up with a solution. This article describes the implementation of validation with Zod in a fresh Redwood app. You can find the sources at this github repository.

RBAC is one of the most common authorization models - users are assigned different roles, and resource access privileges are controlled at the role level. Despite its limitations, RBAC is a popular choice for simple applications, and some frameworks (like RedwoodJS) have built-in support for it.

Check it out here: https://redwoodjs.com/