jjmcinto-0559, As I understand you’re leveraging AWS storage to service static files on Azure App Service. Thanks for detailed description and sharing the sample code.
While I’m still checking on this, here are few recommended configurations from App Service standpoint.
-Oryx attempts to build and run Django apps appropriately, but some configuration is not automated.
-Add whitenoise to your requirements.txt file.
(Whitenoise (whitenoise.evans.io) is a Python package that makes it simple for a production Django app to serve its own static files).
Whitenoise specifically serves those files that are found in the folder specified by the Django STATIC_ROOT variable.
--In your settings.py file, add the following line for Whitenoise:
STATICFILES_STORAGE = ('whitenoise.storage.CompressedManifestStaticFilesStorage')
Also, modify the MIDDLEWARE and INSTALLED_APPS lists to include Whitenoise. -Check the doc section Serve static files for Django apps (below) for more details.
-Oryx runs manage.py collectstatic on your behalf unless you specify the DISABLE_COLLECTSTATIC env var.
Try to also set STATIC_ROOT in settings.py:
// settings.py
STATIC_ROOT = './static/'
-To isolate the issue, firstly you may separately test this on Azure.
-Check this doc section Serve static files for Django apps for more details.
-App Service - Django Tips