postgres VS cookiecutter-django

EDIT: Somehow i managed to fix it right now (I struggled with this problem yesterday for hours). This github issue have helped: https://github.com/docker-library/postgres/issues/537 If anyone runs into this problem, those are crucial instructions that helped me: docker system prune docker-compose up --force-recreate --build --remove-orphans --always-recreate-deps --renew-anon-volumes

Tragedy of the commons - only need a few actors to ruin it all for us. Almost all distributors face this problem, from Docker Hub to PyPI. This also reminded me of official Postgres Docker image running a cryptominer in the background [1]

[1] - https://github.com/docker-library/postgres/issues/770

If you open the dockerfile of the desired container, you can determine exactly how and what was built. If not satisfied, you can always build your own container with the right postgresql build flags.

Ok according to The Dockerfile, postgres is running in /var/lib/postgresql/data so you will need enter the container and look at the log files in /var/lib/postgresql/data/pg_log/

I got started on trying to make a basic postgres image but I can't seem to figure out how to include a shell script in the same folder as my nix file (fetched from https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh and to be modified once I get it working) into the docker image as an entrypoint

See example here : https://github.com/docker-library/postgres/issues/601

cookiecutter https://github.com/pydanny/cookiecutter-django

"1" is definitely something I'd like the team to focus on. Cookie-cutter django aims at it (https://github.com/pydanny/cookiecutter-django) but IDK I think it goes a little too far, and we should have better out-of-the-box options. I think we have this situation because of the unwillingness to make backward incompatible changes.

Use Django Environ for secret keys etc, have a look at 12 factor https://12factor.net and https://github.com/pydanny/cookiecutter-django for a solid example of a best practise setup.

Have you seen https://github.com/pydanny/cookiecutter-django ?

I don't have production level examples but cookie cutter django covers setting up points 3,4,6 https://github.com/pydanny/cookiecutter-django for you. django-allauth for point 6

You really should take a look at cookiecutter it makes bootstrapping projects easier and more customizable. You can also peek at cookiecutter Django.