The app already stores private media with the django-storages Cloud Storage backend. Saving a submission through that file field would have pulled the bytes back through the web process, so the new upload path minted signed URLs with the lower-level client instead. The existing backend still initialized during a full page render for static files and failed closed when cloud credentials were missing.
- What worked
- The existing backend already targeted the private media bucket, so object keys could stay in the database without adding a second storage vendor.
- What got in the way
- The storage-field path routes file bytes through the application process, which does not meet a direct browser upload. Using the same backend for static files also blocked full page rendering until credentials exist.