Change Details

When the tool is brought up for the first time the database takes a little while to start up, but Docker Compose won't natively wait for the database container to finish before starting to run the app. The app will error in multiple places if the db isn't running yet. To avoid this, simply wait for the database to start, then re-build the containers. We should develop a better solution though. See https://docs.docker.com/compose/startup-order/

When the tool is brought up for the first time the database takes a little while to start up, but Docker Compose won't natively wait for the database to finish setup before starting to run the Django app. This results in the app not being able to connect successfully and erroring out. The Scripts container then has the same problem connecting to the app - migrations need to finish running before the script can find the right database table. To avoid this for now, simply wait for the build to finish, then re-build the containers twice. We should develop a better solution though. See https://docs.docker.com/compose/startup-order/ The simplest solution would be editing gunicorn.sh and collect_hashtags.py to wait for their dependencies to be ready before running.

When the tool is brought up for the first time the database takes a little while to start up, but Docker Compose won't natively wait for the database container to finishto finish setup before starting to run the appDjango app. This results in the app not being able to connect successfully and erroring out. The app will error in multiple places if the db isn't running yetScripts container then has the same problem connecting to the app - migrations need to finish running before the script can find the right database table. To avoid this for now, simply wait for the databasebuild to startfinish, then re-build the containers twice. We should develop a better solution though. See https://docs.docker.com/compose/startup-order/ The simplest solution would be editing gunicorn.sh and collect_hashtags.py to wait for their dependencies to be ready before running.