Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

As per the tutorial at : https://www.digitalocean.com/community/tutorials/how-to-set-up-a-scalable-django-app-with-digitalocean-managed-databases-and-spaces
The guidance to setup CDN access via Spaces from the above is:
AWS_S3_ENDPOINT_URL = ‘spaces_endpoint_URL’ AWS_S3_CUSTOM_DOMAIN = ‘spaces_edge_endpoint_URL’
replace the spaces_edge_endpoint_URL with the Edge endpoint you just noted down, truncating the https:// prefix. For example, if the Edge endpoint URL is https://example.sfo2.cdn.digitaloceanspaces.com, AWS_S3_CUSTOM_DOMAIN should be set to example.sfo2.cdn.digitaloceanspaces.com.
With the above config, the edge path is not used - instead the path links only to the standard spaces endpoint and not the CDN endpoint.
Can you please advise if there is any further guidance on this issue? Thanks!
009fd274aeae48f2bfbda6ef568676
009fd274aeae48f2bfbda6ef568676
SarkariResultht
Arne van Hoorn
4287c71658bd4ea39bef277d491b1c
4287c71658bd4ea39bef277d491b1c
Demanix
Demanix
Henry Mui
Prakash Hinduja
f60f754977ec49e1b2cad3cf42286e
anonymouse1