[development] Distilling distributions from configured sites.

Michelle Cox mcox at charter.net
Wed Aug 9 21:51:58 UTC 2006

Ah, I like that. I do have a few modules / themes that I want on every site 
I put in my multi site so I currently have those off the Drupal root. This 
is a nice alternative. I still would put most of my modules and themes under 
sites/domain/, though, as it keeps everything for that site in one spot. 
This is especially important because I have a tendency to muck around a bit 
with themes and not rename them... Keeps the changes to one site. ;)


On 8/9/2006 3:47:10 PM, Larry Garfield (larry at garfieldtech.com) wrote:
> sites/all is a new minor feature in current CVS that adds a 3rd place
> where modules and themes can be stored.  In addition to /modules/ and
> sites/sitename/modules/, they can also be placed in /sites/all/modules/.
> Modules in /modules/ and /sites/all/modules/ will be available to all
> sites, while modules in /sites/sitename/modules/ are site-specific.  It's
> primary purpose is that there is now no excuse to put modules in
> /modules/
> that don't come with the core system.  Leave that directory pure and
> pristine!  The same applies to theme directories.  ALL
> installation-specific stuff can now go under /sites/.
> (This was one of the decidedly few patches I had time to contribute myself
> recently, so I mention it where I can. <g>)
> --Larry Garfield, who wishes he had more time to work on Drupal

More information about the development mailing list