Re: [support] Multi Site Question . . .
On 11/10/2006 7:39:19 AM, Jason Flatt (drupal@oadae.net) wrote:
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.
Upgrading is one reason that I'm considering splitting up my multi site. I have 3 sites running off a multi site. One of them I want to bring to 5.x within a few months after release. The other two really don't need to be upgraded as long as 4.7 is still supported. The only real advantage I've found to multi site is security updates only need to be applied in one place. I'm not sure that benefit outweighs the pain of being forced to upgrade all sites at once. If you do decide to do multi site, and you only have one or two out of the 20 that you don't want to upgrade because you're waiting on a module, you could always split those off of the multi site until they are ready to be upgraded. Michelle
On 11/10/06, Michelle Cox <mcox@charter.net> wrote:
The only real advantage I've found to multi site is security updates only need to be applied in one place. I'm not sure that benefit outweighs the pain of being forced to upgrade all sites at once.
I agree and would just point out that for me, at 3 sites I said "why bother with multisite, it's not worth it" and then at 10 sites I said "security and general updates suck, I need multisite". So, there are different strategies for different situations. If you have or are going to have lots of sites, multisite becomes a smart decision. Greg
On Friday 10 November 2006 06:52, Greg Knaddison - GVS wrote:
I agree and would just point out that for me, at 3 sites I said "why bother with multisite, it's not worth it" and then at 10 sites I said "security and general updates suck, I need multisite".
:^)) Yeah, that's kind of where I am. -- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 13; Cramer, 11; Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005) Linux User: http://www.sourcemage.org/ Drupal Fanatic: http://drupal.org/
I'm wondering how high Drupal can go. I am reviewing it for an installation where it could be installed on 140 sites (departments within a company). I really can't afford to get to some odd number and see serious performance issues. The traffic most likely won't be an issue, but huge amounts of content will go in the database. Upgrading all of these as separate sites would be a nightmare, so multi-site is my only solution at this time. On 11/10/06, Greg Knaddison - GVS <Greg@growingventuresolutions.com> wrote:
On 11/10/06, Michelle Cox <mcox@charter.net> wrote:
The only real advantage I've found to multi site is security updates only need to be applied in one place. I'm not sure that benefit outweighs the pain of being forced to upgrade all sites at once.
I agree and would just point out that for me, at 3 sites I said "why bother with multisite, it's not worth it" and then at 10 sites I said "security and general updates suck, I need multisite".
So, there are different strategies for different situations. If you have or are going to have lots of sites, multisite becomes a smart decision.
Greg -- [ Drupal support list | http://lists.drupal.org/ ]
-- Aaron Green Web Content Coordinator University of Southern Mississippi
Bryght is running over 1000 sites off of one code base:http://drupal.org/node/72328#comment-134751 Paul Aaron Green wrote:
I'm wondering how high Drupal can go. I am reviewing it for an installation where it could be installed on 140 sites (departments within a company). I really can't afford to get to some odd number and see serious performance issues. The traffic most likely won't be an issue, but huge amounts of content will go in the database. Upgrading all of these as separate sites would be a nightmare, so multi-site is my only solution at this time.
On 11/10/06, Greg Knaddison - GVS <Greg@growingventuresolutions.com> wrote:
On 11/10/06, Michelle Cox <mcox@charter.net> wrote:
The only real advantage I've found to multi site is security updates only need to be applied in one place. I'm not sure that benefit outweighs the pain of being forced to upgrade all sites at once. I agree and would just point out that for me, at 3 sites I said "why bother with multisite, it's not worth it" and then at 10 sites I said "security and general updates suck, I need multisite".
So, there are different strategies for different situations. If you have or are going to have lots of sites, multisite becomes a smart decision.
Greg -- [ Drupal support list | http://lists.drupal.org/ ]
Thanks for that link, and if this is hijacking this thread, I apologize. The situation described is a lot like mine, the one thing I never saw answered was updating all databases during an upgrade if your using separate databases and one multi-site installation. Any ideas there? On 11/10/06, Paul Rooney <paul@f5sitedesign.com> wrote:
Bryght is running over 1000 sites off of one code base:http://drupal.org/node/72328#comment-134751
Paul
Aaron Green wrote:
I'm wondering how high Drupal can go. I am reviewing it for an installation where it could be installed on 140 sites (departments within a company). I really can't afford to get to some odd number and see serious performance issues. The traffic most likely won't be an issue, but huge amounts of content will go in the database. Upgrading all of these as separate sites would be a nightmare, so multi-site is my only solution at this time.
On 11/10/06, Greg Knaddison - GVS <Greg@growingventuresolutions.com> wrote:
On 11/10/06, Michelle Cox <mcox@charter.net> wrote:
The only real advantage I've found to multi site is security updates only need to be applied in one place. I'm not sure that benefit outweighs the pain of being forced to upgrade all sites at once. I agree and would just point out that for me, at 3 sites I said "why bother with multisite, it's not worth it" and then at 10 sites I said "security and general updates suck, I need multisite".
So, there are different strategies for different situations. If you have or are going to have lots of sites, multisite becomes a smart decision.
Greg -- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- Aaron Green Web Content Coordinator University of Southern Mississippi
On Friday 10 November 2006 07:13, Aaron Green wrote:
I'm wondering how high Drupal can go. I am reviewing it for an installation where it could be installed on 140 sites (departments within a company). I really can't afford to get to some odd number and see serious performance issues. The traffic most likely won't be an issue, but huge amounts of content will go in the database. Upgrading all of these as separate sites would be a nightmare, so multi-site is my only solution at this time.
If they are not sharing a database, that part of the update will have to be done for each site. In the case of security updates, that's likely to be nil. In the case of major version upgrades, each site /will/ need to run /update.php. For your situation, if all the sites are similarly configured and use the same contrib modules and/or themes, that might be possible by running a script (once you've tested it in a couple of sites). YMMV. -- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 13; Cramer, 11; Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005) Linux User: http://www.sourcemage.org/ Drupal Fanatic: http://drupal.org/
Ok, thanks for the information. On 11/10/06, Jason Flatt <drupal@oadae.net> wrote:
On Friday 10 November 2006 07:13, Aaron Green wrote:
I'm wondering how high Drupal can go. I am reviewing it for an installation where it could be installed on 140 sites (departments within a company). I really can't afford to get to some odd number and see serious performance issues. The traffic most likely won't be an issue, but huge amounts of content will go in the database. Upgrading all of these as separate sites would be a nightmare, so multi-site is my only solution at this time.
If they are not sharing a database, that part of the update will have to be done for each site. In the case of security updates, that's likely to be nil. In the case of major version upgrades, each site /will/ need to run /update.php. For your situation, if all the sites are similarly configured and use the same contrib modules and/or themes, that might be possible by running a script (once you've tested it in a couple of sites). YMMV.
-- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 13; Cramer, 11; Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005) Linux User: http://www.sourcemage.org/ Drupal Fanatic: http://drupal.org/ -- [ Drupal support list | http://lists.drupal.org/ ]
-- Aaron Green Web Content Coordinator University of Southern Mississippi
participants (5)
-
Aaron Green -
Greg Knaddison - GVS -
Jason Flatt -
Michelle Cox -
Paul Rooney