1. Home
  2. Documentation
  3. Frontend
  4. Using a CDN
WARNING:

You are browsing the documentation for Symfony 4.3 which is not maintained anymore.

Consider upgrading your projects to Symfony 5.3.

Using a CDN

4.3 version
Maintained
4.4 5.2 5.3 current 5.4 dev 6.0
Unmaintained
3.3 3.4 4.0 4.1 4.2 4.3 5.0 5.1

Using a CDN

Are you deploying to a CDN? That’s awesome :) Once you’ve made sure that your built files are uploaded to the CDN, configure it in Encore:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
// webpack.config.js
// ...

Encore
    .setOutputPath('public/build/')
    // in dev mode, don't use the CDN
    .setPublicPath('/build');
    // ...
;

+ if (Encore.isProduction()) {
+     Encore.setPublicPath('https://my-cool-app.com.global.prod.fastly.net');
+
+     // guarantee that the keys in manifest.json are *still*
+     // prefixed with build/
+     // (e.g. "build/dashboard.js": "https://my-cool-app.com.global.prod.fastly.net/dashboard.js")
+     Encore.setManifestKeyPrefix('build/');
+ }

That’s it! Internally, Webpack will now know to load assets from your CDN - e.g. https://my-cool-app.com.global.prod.fastly.net/dashboard.js.

Note

It’s still your responsibility to put your assets on the CDN - e.g. by uploading them or by using “origin pull”, where your CDN pulls assets directly from your web server.

You do need to make sure that the script and link tags you include on your pages also use the CDN. Fortunately, the entrypoints.json paths are updated to include the full URL to the CDN.

If you are using Encore.enableIntegrityHashes() and your CDN and your domain are not the same-origin, you may need to set the crossorigin option in your webpack_encore.yaml configuration to anonymous or use-credentials to overcome CORS errors.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.