On 4/21/06, <b class="gmail_sendername">njivy</b> <<a href="mailto:drupal-docs@drupal.org">drupal-docs@drupal.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>The descriptions of the filesystem layouts confuse me. Could we show<br>excerpts from the results of ls -al to describe how sub-directory<br>installations relate to the primary codebase?</blockquote><div><br><br>Hi njivy,
<br><br>I updated the text as follows (below), but I haven't taken the time yet to update <a href="http://www.amstercad.com">www.amstercad.com</a> or readied another release. Before I do that, is this revised text helpful to you? (This revised text appears just before the .htaccess section of the multi-site docs.)
<br><br>I am afraid this instruction differs from your installation, as I understand both your installation and Dries' original text. But I may just as easily be mistaken, I really am no expert, I'm just someone trying to clarify the written instructions.
<br><br>My understanding is that modules, themes, and the favicon are made unique the way I've tried to clarify. <br><br>Now I also wonder... Are unique, site-specific directories for 'files', 'includes', and 'misc', also configured this way? If someone clarifies this for me, I'll adjust the instruction accordingly.
<br><br>I hope this text is an improvement, and I plan to incorporate it into the multi-site versions of the install doc. Please let me know if this helps you. If I'm really off-the-mark, please help clarify the setup anyway you can.
<br><br>Thanks,<br>SpzToid<br><br><br><span style="font-weight: bold;"><span style="font-weight: bold;"></span>Site-specific Themes, Modules, or Favicons<br></span>Each website configuration can be configured with unique themes, modules, and favicons, that are not shared by the other sites of your multi-site installation.
<br><br>To introduce site-specific themes, or modules, you must create a new 'modules' or a new 'themes' directory. The location of this new directory is inside the 'sites' directory that is receiving unique treatment from the other sites sharing the codebase.
<br><br>For example, if the site 'sub.example.com' has a custom theme or a custom module, that should not shared with, or even be accessible to, other sites sharing the codebase, then the structure for either unique theme or module directory is as follows:
<br><br> sites/sub.example.com/settings.php<br> sites/sub.example.com/themes/unique_theme_directory<br> sites/sub.example.com/modules/unique_module_directory<br><br>To configure a unique site favicon with 'sub.example.com', the file should be located at:
<br><br> sites/sub.example.com/favicon.ico</div></div><br>