This finally implements a global server for the assets used in the generated websites. It will substantially optimize storage requirements, page load times and required bandwidth, since all common assets will now (as) soon (as this is finished and merged) be shared across all builds and tags (branches or pull requests).
Additionally, we can now safely enable some aggressive caching configurations to the asset files, since the independent asset server will make sure that the invariant <name without extension> == sha1(<content>) is always respected, even if something goes wrong on a particular build.
The (so far) weird asset naming in the HTML was designed specifically with the goal of allowing such asset sharing...
This finally implements a global server for the assets used in the generated websites. It will substantially optimize storage requirements, page load times and required bandwidth, since all common assets will
now(as) soon (as this is finished and merged) be shared across all builds and tags (branches or pull requests).Additionally, we can now safely enable some aggressive caching configurations to the asset files, since the independent asset server will make sure that the invariant
<name without extension> == sha1(<content>)is always respected, even if something goes wrong on a particular build.The (so far) weird asset naming in the HTML was designed specifically with the goal of allowing such asset sharing...