This module stores optimized css/js assets in the database, and if missing from disk upon request, restores them back.
It is intended to supplement the core patch Make css/js optimized assets path configurable in a multi-webhead architecture (see also the issue for adding support to advagg).
Why?
In a brief way: Drupal core generates css/js optimized assets only in the first page render after a cache rebuild. So, if an asset is missing on disk after generation, Drupal is unable to regenerate it unless a cache rebuild is performed again.
What is this useful for?
Let's consider a Drupal site deployed to a multi-webhead architecture and configured to store css/js optimized asset to a local filesystem.
In such scenario, css/js are stored to the filesystem of the instance serving the first request after a cache-rebuild. Further requests arriving to other instances will not find the assets in its local filesystem. In this event, this module intervenes to copy the file from database to disk and resolve the situation.
Supporting organizations:
sponsors the development
Project information
Maintenance fixes only
Considered feature-complete by its maintainers.- Project categories: Performance, Developer tools
9 sites report using this module- Created by jonhattan on , updated
Stable releases for this project are covered by the security advisory policy.
Look for the shield icon below.
