You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think executing the python live code its a perfect idea but if we can implement a native script (bash) for implement another services that need to start first in the app maybe can replicate in other projects or services, maybe its only fork the script or the bash function.
Or maybe its only wait for the start of the service in a single file for wait until the database service is already started and exit.
The text was updated successfully, but these errors were encountered:
I honestly don't know why it's been done like this, maybe the original pull request has some details. Have you tried to search in the git history?
I personally don't really have an issue with the current solution, but simplifications are always welcome. I'd be happy to replace it with an off the shelves solution.
browniebroke
changed the title
Why preffer python than bash for wait the service start
Why prefer python than bash for wait the service start
Aug 31, 2023
Description
In this file
https://github.com/cookiecutter/cookiecutter-django/blob/master/%7B%7Bcookiecutter.project_slug%7D%7D/compose/production/django/entrypoint
Why don't use some tcp listener for docker like wait-for or wait-for-it.sh
Rationale
I think executing the python live code its a perfect idea but if we can implement a native script (bash) for implement another services that need to start first in the app maybe can replicate in other projects or services, maybe its only fork the script or the bash function.
Or maybe its only wait for the start of the service in a single file for wait until the database service is already started and exit.
The text was updated successfully, but these errors were encountered: