[Encore] Deploying to a CDN subdirectory #15044
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I agree this will be useful for some readers. Let's merge it. Thanks Thibault. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When deploying to a CDN, you might want to deploy your whole public directory to also include bundles assets for example.
This would result in the CDN containing two folders
bundlesandbuildwhen using Encore.This may also be the case if using a shared CDN for multiple applications where each project lives in a given folder.
This PR tries to document this and it seems the only solution is to add the path of the subdirectory at the end of the URL.
It's even showcased in the code comments here.