add a postdeploy step to purge surroage-keys for static files

python · Sep 25, 2024 · 4729534 · 4729534
1 parent 107f838
commit 4729534
Show file tree

Hide file tree

Showing 4 changed files with 15 additions and 0 deletions.
diff --git a/Procfile b/Procfile
@@ -2,3 +2,4 @@ release: python manage.py migrate --noinput
 web: bin/start-nginx gunicorn -c gunicorn.conf pydotorg.wsgi
 worker: celery -A pydotorg worker -l INFO
 worker-beat: celery -A pydotorg beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler
+postdeploy: python manage.py postdeploy
diff --git a/pydotorg/management/__init__.py b/pydotorg/management/__init__.py
diff --git a/pydotorg/management/commands/__init__.py b/pydotorg/management/commands/__init__.py
diff --git a/pydotorg/management/commands/postdeploy.py b/pydotorg/management/commands/postdeploy.py
@@ -0,0 +1,14 @@
+from django.core.management.base import BaseCommand
+from django.conf import settings
+
+from fastly.utils import purge_surrogate_key
+
+
+class Command(BaseCommand):
+    """ Do things after deployment is complete """
+
+    def handle(self, *args, **kwargs):
+        # If we have a STATIC_SURROGATE_KEY set, purge static files to ensure
+        # that anything cached mid-deploy is ignored (like 404s).
+        if settings.STATIC_SURROGATE_KEY:
+            purge_surrogate_key(settings.STATIC_SURROGATE_KEY)