Dear Squidex Support Team,
I am currently running Squidex on a Kubernetes cluster using the Helm chart from the official GitHub repository. I’ve already configured the assets to be stored in S3, but I want to use Squidex as a CDN.
Could you please clarify if additional configurations are required for this use case? Specifically, I would like to know:
-
Are there any specific configurations I should apply to optimize Squidex for use as a CDN?
-
Can Squidex handle this efficiently at scale when used as a CDN, and what performance considerations should I be aware of?
-
What are the constraints or limitations when using Squidex as a CDN in this setup?
Additionally, are there any other important details or information I should be aware of before using Squidex as a CDN?
I appreciate your guidance and any insights you can provide to ensure a smooth and efficient setup.
Best regards,
Asayil
I am not sure what you mean with “Squidex as a CDN”. You can put Squidex behind a CDN. Then you just have to point your CDN URL to Squidex Assets.
e.g.
"assets.mydomain.com" -> "squidex.mydomain.com/api/assets"
That’s basically it. But you also have to adjust asset URLs in your client then.
Alternative you can also put your full squidex domain behind a CDN, but I would only cache the assets endpoints. For example you can do that via a rule in cloudflare.
Thank you for the clarification. I currently use S3 to store the assets, and users interact with the Squidex UI to upload and retrieve them. Whenever they want to use the assets, they still contact the Squidex API.
Given this setup, I wanted to know if this is considered best practice and whether it will provide the expected efficiency. Alternatively, I’m considering whether creating a custom UI that returns the S3 URLs of the assets directly within the Squidex UI would improve client performance. Would this approach yield better performance, or is the current setup sufficient since Squidex can handle a high load?
I appreciate your insights on this!