This page lists what caches or directories you will need to clear to apply various types of changes. It is consolidated and adapted from the complete official documentation on directories and caches.
💁 If your development environment supports it, you are better off using Vinai's automatic cache cleaner. As of this writing, the primary reason why it might not work is if your code is hosted on a NFS share (common with Vagrant).
| <?php | |
| /** | |
| * This rewrite modifies the caching behavior so that the layout cache key references a SHA1 | |
| * hash of the layout XML instead of the XML itself to avoid duplication. The layout XML must | |
| * still be generated once for each layout key, but it will not be saved if the identical | |
| * contents already exist, saving considerable cache backend storage. | |
| */ | |
| class Template_Core_Model_Layout_Update extends Mage_Core_Model_Layout_Update | |
| { |
| <?php | |
| require_once 'abstract.php'; | |
| /** | |
| * Generate a CSV of modules with admin routes that haven't implemented _isAllowed() | |
| */ | |
| class Mpchadwick_Missing_Acl_Checker extends Mage_Shell_Abstract | |
| { | |
| const MODULES_PATH = 'modules'; |
| #!/bin/bash | |
| # Generate sample data and trigger Magento2 performance toolkit jMeter test plan. | |
| HOST="magento2.loc" | |
| BASE_PATH="/" | |
| USERS=100 | |
| RAMP_PERIOD=300 | |
| LOOPS=1 | |
| ADMIN_USER="magento2" | |
| ADMIN_PASSWORD="magento2" |
| #!/bin/sh | |
| wget http://dev.mysql.com/get/Downloads/MySQL-5.6/mysql-5.6.24-osx10.9-x86_64.tar.gz | |
| tar xfvz mysql-5.6* | |
| echo "stopping mamp" | |
| sudo /Applications/MAMP/bin/stop.sh | |
| sudo killall httpd mysqld | |
| echo "creating backup" |
| <?xml version="1.0"?> | |
| <config> | |
| <global> | |
| <skip_process_modules_updates>1</skip_process_modules_updates> | |
| </global> | |
| </config> |
| <?php | |
| // I almost never use $installer = $this; instead I prefer to use the following | |
| $installer = Mage::getResourceModel('catalog/setup', 'catalog_setup'); | |
| // This is just an example of instantiating the setup class in the script. Of | |
| // course I choose the appropriate setup class and resource on a case by case basis. | |
| // That way it is very visible what setup class is being used. It can also be | |
| // switched within a single setup script, for example to add attributes to |
| <script type="text/javascript"> | |
| (function () { | |
| "use strict"; | |
| // once cached, the css file is stored on the client forever unless | |
| // the URL below is changed. Any change will invalidate the cache | |
| var css_href = './index_files/web-fonts.css'; | |
| // a simple event handler wrapper | |
| function on(el, ev, callback) { | |
| if (el.addEventListener) { | |
| el.addEventListener(ev, callback, false); |
This simple script will take a picture of a whiteboard and use parts of the ImageMagick library with sane defaults to clean it up tremendously.
The script is here:
#!/bin/bash
convert "$1" -morphology Convolve DoG:15,100,0 -negate -normalize -blur 0x1 -channel RBG -level 60%,91%,0.1 "$2"
