[documentation] Multi site docs feedback

Anisa mystavash at animecards.org
Sun Oct 8 23:00:55 UTC 2006


On 10/9/06, Anton <anton.list at gmail.com> wrote:
>
> Hi Anisa,
>
> Well done for going to the effort to better document this. Here's my
> feedback based on supporting this process a lot...


In that case, I can look forward to your concrete examples to use in the
documentation!  Right?  :)

I think the "pointing" part of the exercise should be the first step.
> And database/sites should come later.


?
*winnethepooh*

OK, I got it!  But, I don't know that I agree.  Well, I agree that Step 3 is
the crucial hard part, and not many people know there IS a step 3 (since
it's not mentioned in the install.txt *ahem!*).  But there's a bit of trial
and error involved, whereas the database is (for your average install)
straightforward, and you don't have too many places to go wrong in the
settings.php file.  I think it would confuse the issue more to go backwards.

It's not like we're stopping them from skipping to step 3.  :)

Feel free to discuss some more, but my hearing gets a lot better when people
contribute examples *strong hint*  Especially apache conf examples, my
hearing is really good then!

;)

Anisa.

My reasons:
>
> * It is the potentially most technically challenging part because it
> is an infrastructure task that varies from site to site, and it would
> be better to hit any insurmountable issues at the first step before
> they have altered their Drupal installation yet.
>
> * It can be independently tested to be working properly before going
> further - ie if all the intended URLs of their "sites" serve up their
> main Drupal site (ie /sites/default) then they know for sure this
> pointing step is done properly. Then they can move on to actually
> configuring Drupal.
>
> * It should be treated as a go/no-go step. If they can't get this
> working, there is no point trying the other bits. This stops database
> or sites directory configuration steps clouding the issue and adding
> confusion to the process. A lot of people don't understand its
> importance at first, and spend ages banging their heads against the
> sites subdirectory set up wondering why nothing is happening.
>
> * It helps give a better understanding of the fundamental process. ie
> Drupal can't magically pluck requests for other sites out of the air -
> the requests need to be funnelled through the Drupal index.php file.
> Only then can Drupal figure out how to treat these sites differently.
>
> Anyway, thanks again for your efforts :)
>
> I'll read it in more detail and hopefully add some more feedback later.
>
> --
> Cheers
> Anton (a.k.a styro)
> --
> 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/20061009/ac1faaff/attachment.htm 


More information about the documentation mailing list