2020-02-10 Asset and Content CDN BETA

Introducing CDNs for the Cloud version

Hello together,

we started to integrate an asset and content CDN into Squidex Cloud.

The two URLs are

  • https://assets.squidex.io and (you guess it)
  • https://contents.squidex.io

How to use it

The two URLs are restricted for contents and API endpoint for now. So instead of

https://cloud.squidex.io/api/assets/eabbc4a0-afa5-40bb-ad32-4d07e1795770

for an asset you use

https://assets.squidex.io/eabbc4a0-afa5-40bb-ad32-4d07e1795770

And similarly instead of

https://cloud.squidex.io/api/content/squidex-website/blog

for contents you use

https://contents.squidex.io/squidex-website/blog

What is the status?

We are still working on it, especially the caching invalidation is not easy to get right.

And don’t forget: It is an CDN, your contents and updates are not available immediately in all cases.

The Squidex Client library has been updated as well to support this. You can enter CDN endpoints now to query your assets and contents from CDN instead of from the normal endpoint.

Who can use it?

For now it is available for anybody, but because of the additional costs on our side it will be only available for professional plans and above.

We also plan to make a few changes to the pricing model, but more about this later in an official blog post and newsletter.

2 Likes

Great!
Which CDN are you using? I’d like to see if they have servers in my country. Thanks!

We use fastly: https://www.fastly.com/network-map

This is an exciting feature! Curious how you are handling the authentication with Fastly? After a valid authenticated response, is it then cached for that IP?

I have not everything sorted, but basically it would be cache per authentication header value.

1 Like

Are there environment variables we can use to force asset URLs on a CDN we host?

Our setup:

  • Squidex Management: https://my-squidex-intance.com/
  • CDN For assets only: https://my-squidex-assets-cdn.com/ which forwards to https://my-squidex-intance.com/api/assets/ (which feels much the same as the way you’ve structured the cloud instance)

I’m hoping for an environment variable or two that I can specify so that all assets are referenced from that CDN.

Thanks!

Hi,
the CDNs has dedicated endpoints:

https://docs.squidex.io/02-documentation/developer-guides/api-overview#cloud-cdn-beta