Skip to content

[Encore] Deploying to a CDN subdirectory #15044

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 21, 2021
+4 −0
Merged

[Encore] Deploying to a CDN subdirectory #15044

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions frontend/encore/cdn.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,10 @@ pages also use the CDN. Fortunately, the
:ref:`entrypoints.json <encore-entrypointsjson-simple-description>` paths are updated
to include the full URL to the CDN.

When deploying to a subdirectory of your CDN, you must add the path at the end of your URL -
e.g. ``Encore.setPublicPath('https://my-cool-app.com.global.prod.fastly.net/awesome-website')``
will generate assets URLs like ``https://my-cool-app.com.global.prod.fastly.net/awesome-website/dashboard.js``

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``
Expand Down