In normal Drupal practice it is necessary to put the site into maintenance mode before upgrading anything, even a module, if I have understood correctly. Is this still true with Drush? and is there a Drush command to do this?
In normal Drupal practice it is necessary to put the site into maintenance mode before upgrading anything, even a module, if I have understood correctly. Is this still true with Drush? and is there a Drush command to do this?
Comments
Comment #1
moshe weitzman commenteddrush does not do that, nor do the maintainers think thats needed. if you want to do it yourself, run drush vset site_offline 1
Comment #2
AFowleThanks for this important clarification. This seems to puzzle people - I have amended the documentation at http://drupal.org/node/477684. Could you please consider adding it to the readme.txt and other places where Drush is documented?
Comment #3
greg.1.anderson commentedWhat if we added a lot of examples to
drush help variable-set? I could whip up a quick list later...Comment #4
izkreny commented+1 for examples a.k.a. time savers. :)
Comment #5
clemens.tolboomxref #804754: HTML documentation through drush where the drush documentation help page is generated through drush.
The same way we could generate the examples.
Comment #6
moshe weitzman commentedI think the existing examples are sufficient. site_offline is there.
Comment #7
greg.1.anderson commentedI agree; I did go trolling through the variables table, and didn't really see anything useful and generic enough to add...
Comment #9
roball commentedHere is a one-liner that puts all sites of a multisite environment into sites maintenance mode:
Putting them all back online works with that code:
Working great for me :-)