I've got to update Drupal 7 core 7.14 to 7.28 for my multisite implementation. I'm currently running about 30 or so sites with a shared code base. I've read the Core Update and the process seems pretty straightforward if I'm doing a single site update. But I've got a few questions for multisite updates:
-- I'm supposed to put my site in 'maintenance' mode prior to copying in the new code base. Does that mean that I have to place each of my 30+ sites in maintenance mode prior to applying the update or is that only required when I run the update.php script for each site?
-- If I copy the new code base into my production site, what happens to an individual site from the time I copy in the new code base until I run update.php for that site?
-- I use the "Boost" module to cache pages for many of my sites. If a site is in maintenance mode, will the cached pages still be served or will the user just receive the site unavailable message?
Thanks for any help that can be provided.
Comments
Yes. put all 30 in to
Best practice.
Take a snapshot of your multisite, and move it to a staging / test environment, and do all of your work there, to make sure it doesn't break anything. Then, do your work on production, after your sure nothing will explode in the process :)
Learning how to use Drush will probably be a HUGE help with this.
Cheers.
I've been running the new release on my dev system
for a month or so now, so I'm comfortable that the release shouldn't cause any problems. Are you talking about that or going through the update process on a non-production server before trying it on the production?
Thanks for your other comments. They were very helpful.
Dev -> Staging -> Prod
I use pantheon for most of my hosting needs, so there's a built in workflow that I can use to test things.
But best practices is to set it up in the SAME APACHE/PHP/MYSQL versioned configuration as your production environment, to minimize as many variables as possible...
a significant point release of MODULE X might all of a sudden require a new PHP version you weren't aware of...
But, if you're comfortable with your process, and have tested in a DEV environment, I think you should be good to go.
(have your clients tested the new versions?)