- 2015-08-21: 50% less server load with MongoDB on the Drupal 7 site factory at France Télévisions
- 2015-07-15: Our first Drupal 8 production site at France Télévisions is live
- 2014-08-18: 400% speedup in 3 weeks for http://france3-regions.francetvinfo.fr/ : who said Drupal back-offices had to be slow ?
- 2014-02-07: Sotchi Olympics traffic not a problem for http://www.francetvsport.fr/ , which I rearchitected on Drupal 7 in 2013
- 2011-09-14: Completed migration of FranceInfo.FR from SPIP to Drupal
- 2011-07-13: The new social network features of Le Figaro are now powered by an OSInet-designed MongoDB implementation
- 2010-12-21: Madame Figaro brand new site by OSInet and others
- 2010-08-16: France.FR is back online with OSInet and Typhon
- 2010-06-15: the new France Culture, which OSInet helped reach its performance goals, is now online
I hit ⌘D⌘R, you won't believe what happened next!
Keep calm and flush cache
If you've done any Drupal development in the last ten years or so, you have probably noticed that the single most often used command in your work process is clearing the cache, be it in the Drupal UI at
admin/config/development/performance (or its earlier incarnations), or hopefully with
drush cr in Drupal 8 or
drush cc all in earlier versions.
The thing is, while you probably switched from the web UI to Drush years ago, it's still a minor annoyance to have switch to a terminal, press the
▲ / ↵ combo and switch back to PhpStorm. Or switch view from the editor to the Terminal view. Isn't there a better way ?
You bet there is: as soon as I asked myself I knew it had to be easy, so let's see how it's done in PhpStorm in three steps:
- create an external tool
- map a key to it
- trick: there's no third step, it's already done
drush cr in PhpStorm 2016.3
Here is in detailed form how to implement the two steps above. Note that these instructions assume that (a) you are working in a Drupal 8 project opened one level above the Drupal docroot, as is typical in Composer-built projects, (b) Drush is local to the project, as it probably should. Adjust according to your actual situation.
|Open tool dialog||
||...fits your fancy|
||Although the widget looks like a selector, you needn't stick to existing groups, but may create one just by typing its label.|
|Synchronize files after execution||Checked||If you haven't excluded
|Open console||Checked||You normally want to see if something happens during the flush. Don't worry: only one console gets used for all calls to the tool.|
|Show in||As you prefer||Probably at least in editor views|
||Assuming you are working on a Composer-built project|
||Especially important for projects built on
|Open keymap dialog||
|Search for your tool||
||Or whatever you typed in the
|Map a key||Your choice: I used
||Now you know what happened when I hit