low-code-backend-dockered VS django-extensions

> 1. Hasura - DB + Basic APIS, 2. Ory.sh for Auth/Authz

Great choices!

3. React on the frontend

Here I'd go with Elm, and a generated GraphL API client. Here an example to play with (which btw also includes ZomboDB for ElasticSearch integration into Postgres)

https://github.com/cies/low-code-backend-dockered

> 4. Windmill.dev

Look awesome, never heard of it. Tnx

> If you like code-focused solution: Rails, Laravel and Django are good options.

I think Kotlin/KTor, while not as full featured, is a much better alternative due to the strong typing discipline.

I was a big Rails, Ruby and dynamic typing fanboy. But then my project grew in size and I changed my beliefs.

I'd not start a big project in any language without: null-safety, proper sum-types, type inference.

Hence I like Kotlin, and KTor seems to be a good Sinatra/Flask like in that arena.

Another interesting development I find no-code/low-code tools for the backend, like Hasura. This allows me to "just expose Postgres over GraphQL" with very little code (mainly configuration). That combined with type-safe client library generation for a typesafe frontend language like Elm gives me all the power I need in a very different paradigm. Something worth considering.

Small example Hasura+Elm project: https://github.com/cies/low-code-backend-dockered

My plug: https://github.com/cies/elm-hasura-dockered

I agreed. Then did a project[1] with Hasura and a generated client lib in Elm and I'm no longer looking back. If I can get away with "no backend code" I'll do it again in a heart beat.

[1] https://github.com/cies/elm-hasura-dockered

django_extensions/utils/dia2django.py: https://github.com/django-extensions/django-extensions/blob/...

django_extensions/management/modelviz.py:

I often perform operational tasks such as modifying data or debugging failures using the Django shell. In fact, anything I can't do through the admin or through management commands I use the shell for. The package django-extensions provides a shell on steroids that I much prefer over the built in shell. It allows you to run a custom REPL such as IPython or Ptpython and has autocomplete, command history, automatic model class imports and a myriad of other dev tools. shell_plus is for a Django programmer what a scalpel is for a surgeon.

It currently has a bug with the latest django update I think; so if it it isn't fixed by the time you try it, remember to check it out later, because django-extensions is genuinely useful.

alias m='exit_if_not_in_python_virtual_env && ./manage.py' alias mcs='exit_if_not_in_python_virtual_env && ./manage.py collectstatic' alias mcsu='exit_if_not_in_python_virtual_env && ./manage.py createsuperuser' alias mm='exit_if_not_in_python_virtual_env && ./manage.py migrate' alias mmm='exit_if_not_in_python_virtual_env && ./manage.py makemigrations' alias mrs='exit_if_not_in_python_virtual_env && ./manage.py runserver' alias ms='exit_if_not_in_python_virtual_env && ./manage.py shell' alias msa='exit_if_not_in_python_virtual_env && ./manage.py startapp' alias mt='exit_if_not_in_python_virtual_env && ./manage.py test' alias mts='exit_if_not_in_python_virtual_env && ./manage.py testserver' # [django-extension](https://github.com/django-extensions/django-extensions): alias msu="exit_if_not_in_python_virtual_env && ./manage.py show_urls" alias mvt="exit_if_not_in_python_virtual_env && ./manage.py validate_templates" alias msp="exit_if_not_in_python_virtual_env && ./manage.py shell_plus" alias mrsp="exit_if_not_in_python_virtual_env && ./manage.py runserver_plus"

I use https://github.com/django-extensions/django-extensions

If you just want a list of all the available urls & paths in your app, take a look at the django-extensions package. It has a django management command show_urls, which will list them all out nicely.

https://github.com/django-extensions/django-extensions has a command, show_urls which outputs the URLs rendered for a project along with the name of their view handler

# 1 million lines of logic and who knows how many queries

I've actually seen this pattern in every Django project :(

Regarding urls, instead of enforcing a flat file, I'd highly recommend always using django_extensions[0]. You'll get `shell_plus` that auto imports model and `show_urls` that you can grep for endpoint and gives you the handler.

[0] https://github.com/django-extensions/django-extensions

A common mistake in django is to make a model change but forget to run makemigrations to generate a migration for the model change. Sometimes it is not entirely obvious when this need to happen. For example, let's say I'm using the django-extensions library and I define a model like:

Django Extensions has a shell_plus with notebook mode.