django-resonant-settings 0.33.1__tar.gz → 0.40.0__tar.gz

{django_resonant_settings-0.33.1 → django_resonant_settings-0.40.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: django-resonant-settings
-Version: 0.33.1
+Version: 0.40.0
 Summary: Shared Django settings for Resonant applications.
 Project-URL: Repository, https://github.com/kitware-resonant/cookiecutter-resonant
 Project-URL: Bug Reports, https://github.com/kitware-resonant/cookiecutter-resonant/issues

{django_resonant_settings-0.33.1 → django_resonant_settings-0.40.0}/resonant_settings/production/https.py

@@ -12,7 +12,7 @@ SESSION_COOKIE_SECURE = True
 CSRF_COOKIE_SECURE = True
 
 # Enable HSTS
-SECURE_HSTS_SECONDS = timedelta(days=365).total_seconds()
+SECURE_HSTS_SECONDS = int(timedelta(days=365).total_seconds())
 # This is already False by default, but it's important to ensure HSTS is not forced on other
 # subdomains which may have different HTTPS practices.
 SECURE_HSTS_INCLUDE_SUBDOMAINS = False

{django_resonant_settings-0.33.1 → django_resonant_settings-0.40.0}/resonant_settings/production/s3_storage.py

@@ -27,5 +27,9 @@ AWS_STORAGE_BUCKET_NAME: str = env.str("DJANGO_STORAGE_BUCKET_NAME")
 AWS_S3_SIGNATURE_VERSION = "s3v4"
 
 AWS_S3_MAX_MEMORY_SIZE = 5 * 1024 * 1024
-AWS_S3_FILE_OVERWRITE = False
+
+# Although overwriting existing files can be dangerous, it's the application's responsibility
+# (not the Storage layer) to handle. Setting this to `False` allows file names to be mutated in
+# the event of a collision, which can be confusing.
+AWS_S3_FILE_OVERWRITE = True
 AWS_QUERYSTRING_EXPIRE = int(timedelta(hours=6).total_seconds())