<br><br><div><span class="gmail_quote">On 10/9/06, <b class="gmail_sendername">Anton</b> <<a href="mailto:anton.list@gmail.com">anton.list@gmail.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;">
Hi Anisa,<br><br>Well done for going to the effort to better document this. Here's my<br>feedback based on supporting this process a lot...</blockquote><div><br>In that case, I can look forward to your concrete examples to use in the documentation! Right? :)
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I think the "pointing" part of the exercise should be the first step.
<br>And database/sites should come later.</blockquote><div><br>?<br>*winnethepooh*<br></div><br>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.
<br><br>It's not like we're stopping them from skipping to step 3. :)<br><br>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!
<br><br>;)<br><br>Anisa.<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">My reasons:<br><br>* It is the potentially most technically challenging part because it
<br>is an infrastructure task that varies from site to site, and it would<br>be better to hit any insurmountable issues at the first step before<br>they have altered their Drupal installation yet.<br><br>* It can be independently tested to be working properly before going
<br>further - ie if all the intended URLs of their "sites" serve up their<br>main Drupal site (ie /sites/default) then they know for sure this<br>pointing step is done properly. Then they can move on to actually
<br>configuring Drupal.<br><br>* It should be treated as a go/no-go step. If they can't get this<br>working, there is no point trying the other bits. This stops database<br>or sites directory configuration steps clouding the issue and adding
<br>confusion to the process. A lot of people don't understand its<br>importance at first, and spend ages banging their heads against the<br>sites subdirectory set up wondering why nothing is happening.<br><br>* It helps give a better understanding of the fundamental process. ie
<br>Drupal can't magically pluck requests for other sites out of the air -<br>the requests need to be funnelled through the Drupal index.php file.<br>Only then can Drupal figure out how to treat these sites differently.<br>
<br>Anyway, thanks again for your efforts :)<br><br>I'll read it in more detail and hopefully add some more feedback later.<br><br>--<br>Cheers<br>Anton (a.k.a styro)<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>*********************************