Ever see the Winnie the Pooh show? When Pooh is thinking really hard, and he crosses one arm and taps his head with the other?<br><br>That's me right now. ;)<br><br>I have been thinking about this recently, because I am on vacation and I'd really like to get that multi site install up this week.
<br><br>It confused me that even though there are no files in <a href="http://sub1.example.com">sub1.example.com</a>, you could have a site.<br><br>In fact, it's all a great deception. All sites run off the same codebase because they all point to that code base.
<br><br>So the really difficult trick with a multisite is to get it all pointing to that codebase.<br>This seems to involve, for different people, apache configurations, symlinks, aliasing, etc.<br><br>But how does the URL stay the same? Does Drupal handle that as well? I've seen references to ReWrite rules....but I've also seen people who don't seem to need those.
<br><br>I think we can divide multi site install into 3 steps... 1. create the database. 2. configure settings. 3. pointing to the codebase.<br><br>Anisa.<br>my backup computer is soooooooooooo slow...<br><br><br><div><span class="gmail_quote">
On 6/25/06, <b class="gmail_sendername">sime</b> <<a href="mailto:info@urbits.com">info@urbits.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Anisa wrote:<br><br>><br>> On 6/25/06, *Angie Byron* <<a href="mailto:drupal-docs@webchick.net">drupal-docs@webchick.net</a><br>> <mailto:<a href="mailto:drupal-docs@webchick.net">drupal-docs@webchick.net</a>
>> wrote:<br>><br>><br>> Multisite can also mean different domains pointing to the same Drupal<br>> installation only using different modules, themes, and files but<br>> otherwise<br>> sharing the exact same codebase/database. For example:
<br>><br>> <a href="http://technology.example.com">technology.example.com</a> <<a href="http://technology.example.com">http://technology.example.com</a>><br>> <a href="http://news.example.com">news.example.com
</a> <<a href="http://news.example.com">http://news.example.com</a>><br>> <a href="http://kids.example.com">kids.example.com</a> <<a href="http://kids.example.com">http://kids.example.com</a>><br>><br>
> Multisite doesn't have to just mean completely separate domains/sites.<br>> Completely separate domains/sites probably would indeed want their<br>> own databases.<br>><br>> Why? how does that work? What happens if you make a node in
<br>> technology... does that same node show up in news? What's a case for<br>> this? I sorta see what you mean, it's all the same site, maybe like<br>> different sections of the same site, but my mind can't quite believe
<br>> it's that simple.<br>><br>The way the above works in a teeny-tiny nutshell.<br>1. Apache is set up so that <a href="http://one.com">one.com</a> and <a href="http://two.com">two.com</a> use exactly the same<br>
directory.<br>2. Drupal then looks at the appropriate settings.php, either in<br>sites/one.com, or sites/two.com (or sites/default/)<br>3. If<br> a) the db connection string is the same and<br> b) there is no db table prefix defined,
<br>then the two sites use the same database.<br><br>In the real world there are some tables you don't want to share, and<br>there is a solution for this also.<br><br>Yes, I couldn't believe how well it works. It is brilliant.
<br>--<br>Pending work: <a href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</a><br>List archives: <a href="http://lists.drupal.org/pipermail/documentation/">http://lists.drupal.org/pipermail/documentation/
</a><br></blockquote></div><br><br clear="all"><br>-- <br>*********************************<br><a href="http://www.AnimeCards.Org">www.AnimeCards.Org</a><br><br>16,000 scans and counting!<br>*********************************