[development] Multisite risks (formerly multisite complication)

[Chris Skene]

All the previous points about Multisite and its advantages/disadvantages are valid, however in your case, as you plan to zap the database regularly and it doesn't sound like data integrity is important, I would probably start with multisite as well.

I will add, that if you are using APC to improve performance, multisite has big performance benefits over separate codebases, as APC will reuse all the files. The benefits are partly lost with separate code bases.

Either way, however, I would use git to manage the platform off a separate repository.

Chris Skene
chris at xtfer.com


On 14/11/2010, at 2:56 AM, jeff at ayendesigns.com wrote:

> I don't know. I'll try that out. In thinking this through, another question sprung to mind:
> 
> If these categories are going to be various demos, with the intent of pushing a database overwrite hourly to repair any pummeling done via users playing with the admin panel, are there risks in them sharing the same code base with production multisite sites?
> 
> On 11/12/2010 09:38 PM, Christopher Skene wrote:
>> 
>> Does having a site folder called sub.domain.category_1 work? You may need a symlink in your root folder to this folder, called "category_1".
>> 
>>> On 13/11/2010 12:29 PM, <jeff at ayendesigns.com> wrote:
>>> 
>>> Right, so sub.domain/category_1 would run off the same code instance as sub.domain/category_2, but separate db's
>>> 
>>> 
>>> On 11/12/2010 08:23 PM, Christopher Skene wrote:
>>> >
>>> >
>>> > So you want different sites on each categor...
>>> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20101114/ad686f20/attachment.html