[documentation] multi site documentation?

[Anisa]

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?

That's me right now.  ;)

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.

It confused me that even though there are no files in sub1.example.com, you
could have a site.

In fact, it's all a great deception.  All sites run off the same codebase
because they all point to that code base.

So the really difficult trick with a multisite is to get it all pointing to
that codebase.
This seems to involve, for different people, apache configurations,
symlinks, aliasing, etc.

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.

I think we can divide multi site install into 3 steps... 1. create the
database.  2. configure settings.  3. pointing to the codebase.

Anisa.
my backup computer is soooooooooooo slow...


On 6/25/06, sime <info at urbits.com> wrote:
>
> Anisa wrote:
>
> >
> > On 6/25/06, *Angie Byron* <drupal-docs at webchick.net
> > <mailto:drupal-docs at webchick.net>> wrote:
> >
> >
> >     Multisite can also mean different domains pointing to the same
> Drupal
> >     installation only using different modules, themes, and files but
> >     otherwise
> >     sharing the exact same codebase/database. For example:
> >
> >     technology.example.com <http://technology.example.com>
> >     news.example.com <http://news.example.com>
> >     kids.example.com <http://kids.example.com>
> >
> >     Multisite doesn't have to just mean completely separate
> domains/sites.
> >     Completely separate domains/sites probably would indeed want their
> >     own databases.
> >
> > Why?  how does that work?  What happens if you make a node in
> > technology...  does that same node show up in news?  What's a case for
> > this?  I sorta see what you mean, it's all the same site, maybe like
> > different sections of the same site, but my mind can't quite believe
> > it's that simple.
> >
> The way the above works in a teeny-tiny nutshell.
> 1. Apache is set up so that one.com and two.com use exactly the same
> directory.
> 2. Drupal then looks at the appropriate settings.php, either in
> sites/one.com, or sites/two.com (or sites/default/)
> 3. If
>   a) the db connection string is the same and
>   b) there is no db table prefix defined,
> then the two sites use the same database.
>
> In the real world there are some tables you don't want to share, and
> there is a solution for this also.
>
> Yes, I couldn't believe how well it works. It is brilliant.
> --
> Pending work: http://drupal.org/project/issues/documentation/
> List archives: http://lists.drupal.org/pipermail/documentation/
>



-- 
*********************************
www.AnimeCards.Org

16,000 scans and counting!
*********************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/documentation/attachments/20061004/63fce45c/attachment-0001.htm