[documentation] Sharing content/users between Drupal sites (was Re: multi site docs)

[Anisa]

On 10/7/06, Boris Mann <boris at bryght.com> wrote:
>
> As wel as comments inline, I've also pasted in the "tree walking"
> rules from settings.php at the end.


Question!  In the docs for this, I've just linked Installing Drupal a few
times, rather than repeat what has already been said.  I don't like
repeating in the handbook, but I will say the install text is not the
easiest.  Still, just linking OK?

On 10/6/06, Larry Garfield <larry at garfieldtech.com> wrote:
>
> > Using Drupal 4.7.3 on my Apache2/PHP5 Linux desktop:
> >
> > Code installed in:
> > /var/www/mysite/
> >
> > Main url:
> > http://myserver/mysite
> >
> > Intended location of sub-site:
> > http://myserver/mysite/foo
> >
> > .htaccess file's RewriteBase set to:
> > /mysite
> >
> > sites directory has the following entries:
> > default (used for the main site)
>
> Try actually putting in an myserver.mysite entry, rather than default
> (you should be able to just rename default). It seems to be walking up
> the path and "Defaulting" to default when it shouldn't be. In general,
> I don't use default unless I am only running one site OR I actually
> will symlink myserver --> default....just so it's clear what I
> *expect* the default to be.
>
> Also, set base_url's for both in settings.php. That's sort of a
> general troubleshooting tip if you're having difficulties getting the
> proper domain to resolve.


Question!  Is there any reason to NOT set base url?  I think I would like to
add it to the advice.

(will have to add this line to the troubleshooting section)

> myserver.mysite.foo
> >
> > Both sites exist and have basic configuration done.  They are using
> different
> > themes so that I can tell them apart.  I do not have a base url set for
> > either one.
>
> > If I symlink /var/www/mysite/foo to /var/www/mysite:
>
> There should be no /var/www/mysite/foo at all. If this does not work,
> it's a bug.
>
> I'm being anal about this, because documenting this the wrong way
> is...well, wrong.
>
> It is complicated by the fact that a combination of shared hosting DNS
> and webserver set ups can make this look completely..well, different,
> and again, really hard to troubleshoot and get working correctly.


Well, accuracy is important if that will reduce confusion later.  So please,
by all means, be picky.  But please also provide the explanations so that I
and others who write this understand.  I find when I understand something
really well, I can summarize it better.

So, we can actually only document very specific combinations if
> hosting has things set up strangely -- "If your host uses cpanel, and
> subdomains are created as directories, then you need to symlink".


Well, let's say if your host creates subdomains as directories, you need to
symlink.  Is this more bad or less bad than editing the apache file (which
as far as I can understand, is roughly the same?).

Additionally, let me be absolutely clear, you are saying this whole step 3
thing of pointing when you have a sub directory of the *codebase* site is
not necessary because the domain is already pointed at the site, and Drupal
handles the rest.  Drupal can handle the rest effectively because actually,
as listed in the instructions you mentioned, it checks for directories
first.

So, a check needs to be added to the end of Step 2, and the start of Step 3.

Anisa.

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

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