You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 22, 2024. It is now read-only.
Currently the deploy-hashed-assets task will send files from the configured local directory (./public/ by default) to a folder named hashed-assets/app-name (app-name being inferred from the application's pkg.name).
With the Core UI project we intend to deploy all hashed assets to a shared folder. This is because we will be splitting our JS bundle into more granular parts with the intention that this will increase cache-ability, reduce the amount we bust the cache, and enable greater reuse of assets between our user facing applications.
The text was updated successfully, but these errors were encountered:
Currently the
deploy-hashed-assets
task will send files from the configured local directory (./public/
by default) to a folder namedhashed-assets/app-name
(app-name
being inferred from the application'spkg.name
).https://github.com/Financial-Times/n-heroku-tools/blob/master/tasks/deploy-hashed-assets.js#L66
With the Core UI project we intend to deploy all hashed assets to a shared folder. This is because we will be splitting our JS bundle into more granular parts with the intention that this will increase cache-ability, reduce the amount we bust the cache, and enable greater reuse of assets between our user facing applications.
The text was updated successfully, but these errors were encountered: