Currently the AzureCDNToolKit uses a "origin push" approach so all assets to be served via CDN must be pushed to the storage account.
I would recommend that you use a grunt or gulp task to bundle and minify your css and js and then upload it to the storage container. If you use images within your css I would also recommend considering using a task to append cache busting variables to those paths. One example is grunt-asset-cachebuster
An alternative approach is to use a "origin pull" approach where the CDN could pull your bundles from the site. This approach is not currently supported by the toolkit although I am planning on adding it in the future.
ClientDependency compatiblilty
Hello.
The Umbraco sites I work with use ClientDependency for bundling out the css/js using an html helpler, for example:
Does the toolkit provide a similar helper?
Many thanks.
Hi Ismael,
Currently the AzureCDNToolKit uses a "origin push" approach so all assets to be served via CDN must be pushed to the storage account.
I would recommend that you use a grunt or gulp task to bundle and minify your css and js and then upload it to the storage container. If you use images within your css I would also recommend considering using a task to append cache busting variables to those paths. One example is grunt-asset-cachebuster
An alternative approach is to use a "origin pull" approach where the CDN could pull your bundles from the site. This approach is not currently supported by the toolkit although I am planning on adding it in the future.
Jeavon
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.