[documentation] multi site docs

[Anisa]

Hihi!  I am glad you like my picture Gaele, it's quite horribly done, but
simple is good too right?

With regards to terminology, I want to consistently use the same
terminology.

Normally people talk about main and sub, but actually, multisites are just
different sites, there isn't really a parent child relationship.

So, how about the 'main' site be the 'codebase site', and any baby sites be
'multi-sites'?

Also, how about, 'a MySQL database is a place to store tables' a drupal
database is 'a collection of tables'?  Does that matter, is it confusing?

Can we make tip boxes?  I'd like to be able to make a tip visually different
from the rest of the text.

When you share tables, don't you have to put them all in the same database,
since drupal only connects to one?

I think I would avoid mentioning words like database layer.  ;)  But it is
important to know that only completely separate sites are supported.

I will change the illustration for 3 different cases.  What's the real
difference between supported and unsupported anyway?  That it may not work?
That you may break something horrible?

With regards to step 3, there are many ways, as Gaele and Boris (whose name
always reminds me of rocky and bullwinkle...) pointed out.  I personally
can't do anything about the document root, I had to ask my host to make a
symlink.  But it did sound like just changing the docroot was the most ideal
way.  There are many methods and I would like to have step by steps for each
of them.  But they should go in the order you recommend.

So, first, are there any methods in addition to the 3 I listed (change doc
root in apache http.conf, create a symlink, configure .htaccess)?

Also, there is also the case of completely different servers?

Anisa.

On 10/5/06, Boris Mann <boris at bryght.com> wrote:
>
> On 10/5/06, Gaele Strootman <eindgebruiker at gmail.com> wrote:
>
> > Step 1:
> > It would be clearer if you order it:
> > - COMPLETELY separate sites
> > - SHARE users ONLY
> > - MIRROR sites
> > What about the option of using a different database for each site? No
> > need for prefixes.
>
> Yep. You only need prefixing if you are limited in the number of MySQL
> DBs you can run.
>
> > Step 2:
> > I would supply a table here to make it clearer:
> > site:                            directory:
> > www.example.com    /sites/default/settings.php
> > sub1.example.com   /sites/sub1.example.com/settings.php
> > etc.
> >
> > Step 3:
> > What I do is: let Apache point to a different document root for every
> > hostname, and let each document root be a symlink to the drupal
> > directory. This is quite easy and gives you enough flexibility.
>
> You definitely don't need to do this. This is the "hard" part that
> Drupal handles automatically. Point all your hostnames at the same
> DocRoot. One Drupal codebase. Create a folder in at /sites/domain1.com
> that represents your http://domain1.com URL. Done. (still have to
> create a separate database or do prefixing)
>
> A general note: sharing users or other tables is difficult stuff. I
> applaud attempts to document, BUT it should come with big bold letters
> like "You should know what you're doing, this is powerful stuff, it is
> trickery at the DB layer, and it is a trick that is essentially
> unsupported". As opposed to separate multisite, which we have core
> support for and "just works".
>
> --
> Boris Mann
> --
> 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/20061006/2d8c7473/attachment-0001.htm