We were getting some spurious failures connecting to redis on initial…

… bring-up

The problem was recovered automatically, but it still was producing events for sentry.io.

app/scripts/start_app.sh

@@ -4,6 +4,9 @@ set -o errexit
 set -o pipefail
 set -o nounset
 
+wait-for-it --service redis:6379 -- echo "Redis available"
+# XXX We collectstatic in the docker image build step so we should probably
+#     remove this.
 /venv/bin/python /app/manage.py collectstatic --clear --no-input --verbosity 0
 /venv/bin/python /app/manage.py migrate
 /venv/bin/gunicorn config.asgi --bind 0.0.0.0:8000 --chdir=/app -w 4 -k uvicorn.workers.UvicornWorker

app/scripts/start_smtpd.sh

@@ -4,6 +4,8 @@ set -o errexit
 set -o pipefail
 set -o nounset
 
+wait-for-it --service redis:6379 -- echo "Redis available"
+
 echo "Running django migrations.."
 /venv/bin/python /app/manage.py migrate
 

app/scripts/start_worker.sh

@@ -4,5 +4,6 @@ set -o errexit
 set -o pipefail
 set -o nounset
 
+wait-for-it --service redis:6379 -- echo "Redis available"
 /venv/bin/python /app/manage.py migrate
 /venv/bin/python /app/manage.py run_huey

docker-compose.yml

@@ -69,7 +69,7 @@ services:
       - mailhog
     ports:
       - "11578:8000"
-    command: /app/manage.py runserver_plus --cert-file /mnt/ssl/ssl_crt.pem --key-file /mnt/ssl/ssl_key.pem 0.0.0.0:8000
+    command: wait-for-it --service redis:6379 -- /app/manage.py runserver_plus --cert-file /mnt/ssl/ssl_crt.pem --key-file /mnt/ssl/ssl_key.pem 0.0.0.0:8000
     restart: always
     env_file: .env
     volumes: