Make default debug settings runable

[MyPyDavid]

No description provided.

[jochenklar]

Do we need this? I had a similar idea a year ago or so and then thought that development setups will differ anyway. I ended up creating my own dev app (https://github.com/jochenklar/rdmo-dev/blob/main/rdmo_dev/settings.py), which I include in my local.py.

I will also switch of DEBUG in development now and then and use postgres all the time.

What we could do, is to ship the devlopment.py by default, but this depends on what concrete problem you actually want to solve.

[jochenklar]

What I usually do for "my" RDMO instances nowadays is to create:

config/settings/environments/development.py
config/settings/environments/production.py

with the different setups, and copy them to config/settings/local.py or link them and use https://github.com/AGWA/git-crypt to encrypt the files (which I would not suggest for the beginner setup).

[jochenklar]

We could do the same here (not the crypt stuff) and remove config/settings/sample.local.py which I never liked anyway. But maybe we should discuss this on Zoom.

[MyPyDavid]

Yeah, the main problem, from the experience of the last hackathon(s), is that when new users/developers want to start up the rdmo-app it can take a lot of time (and effort) following all the steps in the development docs to get the runserver to run.

I think that the easier Dev Experience would be to just have it to run (with minimal configuration effort after cloning) and start working/changing things from there. For deployment it will always be different and has to be adjusted anyways.