In any case, multisite is a good thing, I think. Updates are a piece of cake, but you should keep two codebases around. Put all of your multisites on codebase A and let them run for a while. When updates are available, pull the updates down on codebase B and move your site directories over one by one and run update.php. It's a good process, and it's easily scriptable. It also happens to be the same process that Aegir uses (more or less).<div>
<br clear="all">Thanks,<br>Cameron<br><br>
<br><br><div class="gmail_quote">On Sat, Nov 13, 2010 at 13:33, Chris Skene <span dir="ltr"><<a href="mailto:chris@xtfer.com">chris@xtfer.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><div>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.</div>
<div><br></div><div>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.</div>
<div><br></div><div>Either way, however, I would use git to manage the platform off a separate repository.</div><div><br></div><font color="#888888"><div>Chris Skene</div><div><a href="mailto:chris@xtfer.com" target="_blank">chris@xtfer.com</a></div>
</font><div><div></div><div class="h5"><div><br></div><br><div><div>On 14/11/2010, at 2:56 AM, <a href="mailto:jeff@ayendesigns.com" target="_blank">jeff@ayendesigns.com</a> wrote:</div><br><blockquote type="cite">
<div text="#000000" bgcolor="#ffffff">
I don't know. I'll try that out. In thinking this through, another
question sprung to mind:<br>
<br>
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?<br>
<br>
On 11/12/2010 09:38 PM, Christopher Skene wrote:
<blockquote type="cite"><p>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".</p>
<blockquote type="cite">On 13/11/2010 12:29 PM, <<a href="mailto:jeff@ayendesigns.com" target="_blank">jeff@ayendesigns.com</a>>
wrote:<br>
<br>
Right, so sub.domain/category_1 would run off the same code instance as
sub.domain/category_2, but separate db's
<p><font color="#500050"><br>
<br>
On 11/12/2010 08:23 PM, Christopher Skene wrote:<br>
><br>
><br>
> So you want different sites on each categor...</font></p>
</blockquote>
</blockquote>
</div>
</blockquote></div><br></div></div></div></blockquote></div><br></div>