cookiecutter-django VS Hasura

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.

[4] https://github.com/hasura/graphql-engine/blob/master/architecture/live-queries.md

Another strategy is to model access control declaratively and enforce it in the application layer. ZenStack (built above Prisma ORM) and Hasura are good examples of this approach. The following code shows how access policies are defined with ZenStack and how a secured CRUD API can be derived automatically.

Today, this ecosystem is going strong with new providers like Hasura, AppWrite and Supabase powering millions of projects. There are a few reasons people choose this style of hosting, especially if they are more comfortable with frontend development. BaaS lets them set up a database in a secure way, expose some business logic on top of the data, and connect via a dev-friendly SDK from their app or website code to save data easily. These modern tools build a blend of managed database with curated plugins such as authentication, great admin dashboards, and function as a service type capability - all in one package, and often offered as a integrated hosted service.

Hi! If you’ve ever thought about something like using GraphQL for something like this.. You might like Hasura. (Obligatory I work for Hasura)

We’ve got an OpenAPI import and you can setup cron-jobs or one-off jobs and do things like load in headers from the environment variables to pass through. There isn’t currently an easy journey for chaining multiple calls together without writing any code at all, but you can wrap pretty much any API endpoint via OpenAPI import or a custom action, and you can even make minor edits to things like the API contract format to change aliases/naming.

Our goal is to join all the things, databases and API’s. Most people know us for instant GraphQL API’s that give you CRUD on your database, but we also wrap APIs.

Not sure if something like this would fit your use-case and do check out some of the other things mentioned, but depending what you are trying to do I think Hasura might potentially work.

You can find out more here: https://hasura.io

Nested Mutation - 113 thumbs up, and still open since 2019... another case of not listening to the users?

Hasura is an open-source real-time GraphQL API server with a strong authorization layer on your database. You can subscribe to database events via webhooks. It can combine multiple API servers into one unified graphQL API. Hasura is a great tool to build any CRUD GraphQL API. Hasura does not have any authentication mechanisms; e.g., you need an auth server to handle sign-up and sign-in.

7. Hasura