[support] Install and configure modules only once for all
websites running the same drupal install?
Casper Labuschagne
casperl at krooninfo.co.za
Mon Aug 21 08:46:58 UTC 2006
Hi,
On Mon, 21 Aug 2006 00:37:15 +0200, Larry Garfield
<larry at garfieldtech.com> wrote:
> Actually the answer is "mostly". If you put a module in the /modules
> directory instead of /sites/foo/modules, then it becomes available to all
> sites.
Correct
> Any configuration you have to do, however, is per-site
That is the way I am doing it per - site
> In most cases, you probably don't want to have configuration shared
> between two sites. Think very hard before you do so.
I have played with this and it is a bigger headache sharing configurations
than redoing manual configurations. What I am investigating is to
selectively export specific tables from one site to another such as the
user file.
Due to restrictions by my hosting co I am forced to use a rigid control
panel and all hosted sites out of my account are fixed dirs directly below
public_html/ , thus the Drupal scheme of shared code could not work for
me. What I have done is to create symlinks to the appropriate dirs (I
even have a bash script to instantly create the links for new sites) Thus
I have ~/public_html/mysite/ with symlinks to
~/public_html/drupal_47/database ./includes etc. Only ./files and ./sites
and ./modules/xtra (for contributed modules) are unique dirs for any
shared site. This works like a charm with a single codebase shared
between all sites. Security updates for Drupal means a single set of
files copied to drupal_47 . The contributed modules in ./modules/xtra are
also manual symlinks to ./drupal_47/modules/xtra/my_module or whatever
appropriate module is required.
Hope this helps someone
--
Casper Labuschagne
+27827054416
www.krooninfo.co.za www.boerboel.co.za
Visit http://www.ubuntu.com for a highly recommended open source
alternative to Windows!
More information about the support
mailing list