Allows the purge/clear/flush of the PHP OpCache via the CLI and Magento2 Backend
Allows to manage your cache hosts via the CLI. You can add for instance Varnish servers and remove them again in the configuration., (*1)
I believe this package is stable. Yet I want to warn you about using it in production:, (*2)
When you are in need of a tool like this, I assume you have somewhat decent knowledge the make the right calls ;), (*3)
Because the default CLI setting (config:set --http-cache-hosts)
is not usefull.
The config:set commands overrides all your hosts. Imagine a dynamic setup where you add a new server. The configuration (env.php) is shared via
a NFS (or whatever volume). You must know all hosts if you want to add your new host., (*4)
With this manager you can simply do bin/magento cachehosts:add {currenthost}
and it will append the server, rather than overriding all your servers, (*5)
I'm a DevOps engineer for a full service digital agency in the Netherlands. When possible I try to create opensource scripts / extentions and tools. If you appriciate my work, please be so kind to donate so I can keep drinking beer., (*6)
There are 2 commands:, (*8)
bin/magento cachehosts:add
, (*9)
bin/magento cachehosts:remove
, (*10)
Arguments are the host(s), comma seperated, (*11)
Add, (*12)
// Using default port bin/magento cachehosts:add 127.0.0.1 // Adding multiple hosts bin/magento cachehosts:add 127.0.0.1,127.0.0.2 // Adding with port bin/magento cachehosts:add 127.0.0.1:1337
Remove, (*13)
// Using default port bin/magento cachehosts:remove 127.0.0.1 // Removing multiple hosts bin/magento cachehosts:remove 127.0.0.1,127.0.0.2 // Removing with port bin/magento cachehosts:remove 127.0.0.1:1337
Mixing up, (*14)
bin/magento cachehosts:remove 127.0.0.1:1337,127.0.0.1
It is ok to have the same host on different ports., (*15)
composer require webfixit/cachehostsmanager