Clarification for using whitenoise with CDN on digital ocean about whitenoise HOT 2 CLOSED

I think I did not pay close attention to the Origin Domain Name part of the documentation. If I understand correctly, whitenoise + CDN works like this

1. white noise continues to serve static files through https://mycompany.com/static/. This is why STATICFILE_STORAGE should not be changed.
2. The website tells the client to retrieve static files through CDN, say, https://d4663kmspf1sqa.cloudfront.net/static.
3. If the file has never been accessed before, the CDN server will grab its content from origin domain name, which is https://mycompany.com/static/. After the first attempt, the file will be cached so subsequent access to static file will be handled by the CDN.

The problem with digital ocean, in my case, is that https://myspace.sfo2.cdn.digitaloceanspaces.com/myfolder/static/ will only serve files stored on https://myspace.sfo2.digitaloceanspaces.com/myfolder/static/, so whitenoise will not work with my configuration. If I want to serve static files to CDN, I will have to use a boto3 storage to store static files to the bucket, or use cloudfront to point to the https://mycompany.com/static/.

from whitenoise.

Yes, that is correct, thank you for your clear issue report and self-solve!

from whitenoise.