Improve static asset build process and cache headers #2560
Merged
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.
This PR improves the static asset build process by using the Mix build system to copy all static files instead of only those which are compiled or relocated. By making Mix aware of all of the static assets, the
mix()
helper function can be used to add cache busting extensions to all static asset file paths. This in turn allows an aggressive cache policy to be put in place. Although the caching policy only resulted in a marginal speedup in my local environment, I expect it to have a more significant impact in production environments where assets have to travel a greater distance.