[support] Multiple Drupal Sites Errors

[Metzler, David]

IMHO, the web server configuration for how to "get the web browser to
connect your URL with the drupal executables" is a little bit difficult
to get in the docs.  The options are numerous based on how much control
you have on your web configuration evironment, and what web server
you're using. Symbolic links are one way to do this; apache aliases are
another; in IIS you set up virtual directories.  I like using the
symbolic links the best, but others have a different interpretation on
this issue. 

You do have gist of the trade-offs in multi-site configuration.  Yes if
you just created a directory, you'd have to copy all of the code there
and then you'd have two drupal code tree's to maintain, upload modules
to etc.  Symbolic links, apache aliases, or IIS virtual directories let
you use one. The durpal "multi-site" install also lets you use common
database elements as well, although I don't do that cause I don't really
want to share any of the tables between my sites.  I keep track of one
database per site, and have written cloning scripts to copy one site to
another, create new sites based on a skeleton, etc. 

Dave


-----Original Message-----
From: support-bounces at drupal.org [mailto:support-bounces at drupal.org] On
Behalf Of lists at southernohio.net
Sent: Thursday, March 16, 2006 5:59 AM
To: support at drupal.org
Subject: Re: [support] Multiple Drupal Sites Errors

Thanks Jason, it appears that that was the "missing link." :)  I did not
realize, perhaps I missed it in the installation instructions somewhere,
that you should create a symlink to the drupal install as I had assumed
that it would by virtue of creating the settings folder, set up the site
to generate content based upon the base install.

I am now curious, why is this required?  And what are the possibilities
of having such an arrangement?  If for example, I created the folder
instead of symlinking it, what could be done in  
such a case?  Would I have to set up another drupal installation   
therein in order to utilize it?  I thought that the primary purpose of
this was simply to not have to worry about upgrading multiple drupal
installs and modifying multiple code bases as required.


Thanks again,

-George




On Mar 16, 2006, at 12:59 AM, Jason Flatt wrote:

On Wednesday 15 March 2006 08:49 pm, lists at southernohio.net wrote:
> I'm trying to set up the following scenario:
> mydomain.com/main is the primary Drupal installation.
>
> I am wanting users to be able to access a new Drupal site at:
> mydomain.com/main/NewSite
>
> In order to accomplish this, I have the following already in place 
> (I'm on a linux server with plesk):
> ~/httpdocs/main/sites/default/settings.php
> ~/httpdocs/main/sites/mydomain.com.main.NewSite/settings.php
>
> I set the files in ~/httpdocs/main/sites/mydomain.com.main.NewSite/
> settings.php up to the new database for that site, however each time I

> go to "www.mydomain.com/main/NewSite" I get the default Drupal site
> error: "Page not found"
>
> I've been pouring over documentation I can find on multiple sites on 
> one Drupal install, but am not having any luck.  Could someone please 
> offer some suggestions or help to ascertain what might be going wrong 
> here?
>
> Thanks so much.
>
> -George

And you put something in ~/httpdocs/main/NewSite/ or created a symlink
to ~/httpdocs/main/ and you changed the $base_url in
~/httpdocs/main/sites/mydomain.com.main.NewSite/settings.php to reflect
the correct address of http://www.mydomain.com/main/NewSite and you
verified your letter case in all places, since you have mixed case
directories?

--
Jason Flatt
http://www.oadae.net/
Father of Six:  http://www.flattfamily.com/ (Joseph, 13; Cramer, 11;
Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005)
Linux User:     http://www.sourcemage.org/
Drupal Fanatic: http://drupal.org/
--
[ Drupal support list | http://lists.drupal.org/ ]

-- 
[ Drupal support list | http://lists.drupal.org/ ]