Varnish Cache Warmer Magento2 module by Lizard Media
Magento2 module for handling Varnish Cache cleaning and regenerating using admin panel and CLI. It uses multiple process to run the commands to minimize the time required to run.
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
- Magento 2.2
- PHP 7.1
- Magento 2.3
- PHP 7.1/7.2
- Magento 2.3
- PHP 7.1/7.2/7.3
- Magento 2.3/2.4
- PHP 7.1/7.2/7.3/7.4
composer require lizardmedia/module-varnish-warmer
Download a ZIP version of the module and unpack it into your project into
If you use ZIP file you will need to install the dependencies of the module manually
composer require react/http-client:^0.5.9
Run this command
bin/magento module:enable LizardMedia_VarnishWarmer bin/magento setup:upgrade
The commands can be run in backround from admin panel using
Lizard Media Varnish Warmer
The commands can be run using Magento built-in CLI:
lm-varnish:cache-purge-homepage- purges and regenerates homepage
lm-varnish:cache-purge-general- purges and regenerates homepage and categories
lm-varnish:cache-purge-wildcard- purges * and regenerates homepage, categories and products
lm-varnish:cache-purge-all- purges and regenerates homepage, categories and products
lm-varnish:cache-purge-force- purges * without regenerating. Omits lock check
lm-varnish:cache-purge-products- purges and regenerates products
lm-varnish:cache-refresh-url- purges and regenerates single URL given as argument
- store - sets store view ID to get a correct base URL, e.g.
php bin/magento lm-varnish:cache-refresh-url "*" --store=1
The number of process used for purging and regenerating Varnish cache can be customized
in the admin panel. The max number of processes is specified in
If you have a powerful server you can modify those numbers to use more resources.
Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.
See also the list of contributors who participated in this project.
This project is licensed under the MIT License - see the LICENSE.md file for details