Timeline for Use Drush to update multi-site setup
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 30, 2013 at 1:34 | vote | accept | jsheffers | ||
| Sep 28, 2013 at 5:01 | comment | added | greg_1_anderson | This is the correct answer, presuming that you have the same modules enabled in each site. If some of the other sites have additional modules enabled, you might miss those unless you pm-updatecode each site individually. Also, it would be a good idea to copy the sites to dev, run the update there, test (!), then take the production sites offline, copy the code from dev, and run updatedb on all of the prod sites. Sometimes, an innocuous-looking update can take down a site, and there is no "undo" for updatedb! | |
| Sep 27, 2013 at 17:17 | history | answered | jsheffers | CC BY-SA 3.0 |