When using django-s3-storage together with Cloudflare R2 there are no public buckets. You'll need a so-called Worker to proxy the public requests to the private bucket.
In this setup, you'll need to set AWS_S3_PUBLIC_URL = <your_worker_route> and AWS_S3_BUCKET_AUTH = True. This works perfectly fine but issues a warning each time a django-admin command is used:
Using AWS_S3_BUCKET_AUTH with AWS_S3_PUBLIC_URL. Private files on S3 may be inaccessible via the public URL. See #114
I'd like to silence this particular log message and it seems to me that Django's Sytem Check Framework would be the ideal use case for this scenario. SILENCED_SYSTEM_CHECKS could then be used to silence the check for those who don't need to be reminded of it.
If you agree that this would be useful, I'd write a patch for it.
When using django-s3-storage together with Cloudflare R2 there are no public buckets. You'll need a so-called Worker to proxy the public requests to the private bucket.
In this setup, you'll need to set
AWS_S3_PUBLIC_URL = <your_worker_route>andAWS_S3_BUCKET_AUTH = True. This works perfectly fine but issues a warning each time a django-admin command is used:I'd like to silence this particular log message and it seems to me that Django's Sytem Check Framework would be the ideal use case for this scenario. SILENCED_SYSTEM_CHECKS could then be used to silence the check for those who don't need to be reminded of it.
If you agree that this would be useful, I'd write a patch for it.