cookiecutter-django VS wait-for-it

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.

python:3.10.5-slim-buster is a Debian GNU/Linux 10 (buster). Follow the Debian package link given by wait-for-it, we'll eventually find this link https://packages.debian.org/source/oldoldstable/wait-for-it, I downloaded the wait-for-it_0.0~git20160501.orig.tar.gz file and extracted wait-for-it.sh out to the project root directory where setup.py, app.py, .dockerignore, Dockerfile and docker-compose.yml are.

Using countless variations of the wait for it script (they all get ignored (yes i did chmod +x)). another candidate or using it like this

I haven’t done it, but maybe you can use something like this in an ExecStartPre on the nginx systemd service, or if that doesnt work, as a separate service that nginx’s systemd service starts after

I’ve used wait-for-it with success.

https://github.com/vishnubob/wait-for-it

When start to build docker-compose, it tried to connect db first, but it seems that db didn't become reachable yet. Even added wait-for-it doesn't work.

executes 'wait-for-it.sh' to wait on the availability of port 3306 before running 'air'--using wait-for-it.sh is just an example and this shell script has to be installed as part of the Dockerfilehttps://github.com/vishnubob/wait-for-it

Yeah dockerize seems to achieve your second suggestion, someone also suggested my wait-for-it https://github.com/vishnubob/wait-for-it which seems to be similar but a bit more popular and also used in the official documentation https://docs.docker.com/compose/startup-order/ I think I'll go this route, the first option doesn't quite match what I need as all compose aren't necessarily to be started simultaneously.

Can't you use something like this? : https://github.com/vishnubob/wait-for-it . Essentially wait until you can ping redis port and then run wsgi runserver for django. However, are you sure that you can resolve redis host on swarm? Redis starts so fast that it makes me think it might be something else.