My unpopular opinion is that multisite is completely unnecessary for the vast majority of installs and has major drawbacks. The only fundamental advantage of multisite is that that it saves some disk space (does that matter?). But it has fundamental downsides:<br>
<ul><li>It closely couples the database updates of many sites. (When you do a module or minor version update, you have to do the update and test on all the sites at that exact time. If you're doing it "right" it means that many sites may be offline until you're done.</li>
<li>It takes your filesystem risk and instead of having one site at risk at one time, they're all at risk. So if you have a new module you're introducing or an upgrade that has a bug it unfortunately affects all sites.</li>
<li>The files directory has to be managed exactly right; and it better not be sites/default/files.<br></li></ul>IMO, multisite and database prefixing were for the old days before we had unlimited accounts and disk space was free.<br>
<br>That said, if you know exactly *why* you're doing multisite and you want to tie sites together, then that's fine. But "because Drupal does it and it seems cool" is not a good reason. <br><br>Aegir is fundamentally a multisite idea, and it deals with all these problems. It's a maturing approach to doing multisite quite well, and many people are very happy with it. That's a good reason for doing multisite, and it has all the issues above dealt with. <br>
<br>-Randy<br><br><div class="gmail_quote">On Sat, Nov 13, 2010 at 8:56 AM, <span dir="ltr"><<a href="mailto:jeff@ayendesigns.com">jeff@ayendesigns.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<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><br clear="all"><br>-- <br>Randy Fay<br>Drupal Module and Site Development<br><a href="mailto:randy@randyfay.com">randy@randyfay.com</a><br>+1 970.462.7450<br><br>