This module ensures that optimized CSS and JavaScript assets are available by storing them in the database and restoring them to disk if they are missing. This is particularly useful in multi-server environments where assets generated on one server might not be present on others, preventing errors and ensuring assets are served correctly.
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.
Ask your assistant about CSS/JS Optimized Assets Proxy
Check compatibility with your Drupal and PHP version, maintenance and security coverage, from current release data. How it works
Depends on
Dependencies of the latest stable release
No dependencies recorded for this project.
Required by
Tracked projects that depend on this one
No tracked projects depend on this one yet.