There's an old implementation of asset cache busting via process_assets.js and alwaysload.php in the controllers. They generate a file at fuel/app/config/asset_hash.json that includes hashes for every asset served. As far as we can tell, these hashes are not put into practice: static assets served to the page do not include the hashes located in asset_hash.json. Their inclusion messes with the docker image build and release process, so they should probably be removed and eventually replaced with a different implementation of cache busting.
Note that for the purposes of the react branch, at least initially, the replacement solution is not expected.
There's an old implementation of asset cache busting via
process_assets.js
andalwaysload.php
in the controllers. They generate a file atfuel/app/config/asset_hash.json
that includes hashes for every asset served. As far as we can tell, these hashes are not put into practice: static assets served to the page do not include the hashes located inasset_hash.json
. Their inclusion messes with the docker image build and release process, so they should probably be removed and eventually replaced with a different implementation of cache busting.Note that for the purposes of the react branch, at least initially, the replacement solution is not expected.