I currently have in place several sites using Drupal with immediate plans to do more in the near future. Because of the way I have configured my server, most of those sites have their own installations. I have thought many times about moving them all into a single installation for ease of maintenance, but I have not done so for one reason: what happens if I have a site that is using a module that gets abandoned or doesn't get upgraded in a timely manner? And with multi-sites and the potential to have several sites on a single installation (like > 20), there's a good likelihood that on a major upgrade (like from 4.6 to 4.7 or 4.7 to 5.0), I will have more than one such module.
I really see only three options: 1) don't upgrade any site until the modules are all current -- not really practical for abandoned modules, 2) uninstall the offending module(s) and live without it(them) -- also not practical if it turns out that it(they) are key to the site, and 3) upgrade and/or maintain the module(s) myself -- also not necessarily practical if we're talking several modules and free time being at a premium. I think for me the only option that makes any sense (other than not combining all the sites into a single installation, which may turn out to be the best option) is option #3. Does anyone else have any words of wisdom to offer?
On 11/10/06, Jason Flatt drupal@oadae.net wrote:
Does anyone else have any words of wisdom to offer?
This is a good question and one that most people skip over when they are in the phase of "these modules are all great I'm going to install 350 of them!"
Ideally I like to verify that a module is high quality and will be around for a while, but things change so you have to adjust. If you have 19 sites that are ready to upgrade to 5.x but there's one or two that have legacy modules only available for 4.7 you can then leave those sites in 4.7 and upgrade the first 19 to a new home (in the directory structure) that is the 5.x installation. Then as the modules that were holding you back get updated, or you update them, or you find replacement functionality you can merge the 4.7 sites back into the 5.x location.
That is the system I've been using for the sites that are under my direct control - it works fairly well.
Greg