Download the PHP package nepada/bust-cache without Composer
On this page you can find all versions of the php package nepada/bust-cache. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package bust-cache
Bust Cache Latte Tag
Installation
Via Composer:
Register the extension in config.neon:
Overview of available configuration options with their default values:
If you're using stand-alone Latte, install the Latte extension manually:
Usage
Basic example:
The resulting path depends on the (auto-)chosen cache busting strategy:
Usage in application with non-trivial base path:
Generating full absolute URL:
Revision manifest support
Revision manifest is a JSON file that contains mapping between original asset path and its revision path.
Example:
Configuration
With default configuration the path of manifest file is auto-detected by traversing up from asset directory and looking for manifest.json or rev-manifest.json. If a manifest file is found, the contained revision mapping is used instead of cache busting using query parameter.
You can completely disable the revision manifest support by setting manifest: false in your config.
You can also bypass the auto-detection and specify the manifest file path statically, e.g. manifest: "assets/my-manifest.json"
Caching
The caching is implemented on two levels - runtime and compile-time.
Runtime caching
The cache stores the computed cache busted path for each input path.
DI extension automatically enables this cache, if you have nette/caching configured. In production mode with default settings, asset files are not checked for modification to avoid unnecessary I/O, i.e. the cache is not automatically refreshed.
Compile time caching
When the file path is specified as literal string, the cache busted path is computed in compile time of Latte template and the cache busted path is directly dumped into the compiled code of template.
With the default settings, this is enabled only in production mode.
Cache busting of files that are modified in app runtime
If you want to use cache busting on files that are expected to be modified in app runtime, you can use dynamic keyword to opt-out of compile time caching and force auto refresh of cache even in production mode:
Handling of missing manifest or asset files
With default configuration, when a missing file (manifest or asset) is encountered a warning triggered and asset dummy path is generated. You can switch to strictMode: true to fail hard by throwing exception instead.
"Missing file" is one of the following cases:
- the static manifest file specified in configuration does not exist
- a manifest file points to a revision path that does not exist
- using cache busting by query parameter with asset path that does not exist
