[support] multiple site, on database confusion

[will hall]

hi everyone, thanks for the prompt replies.

this is helpful but i am a drupal newbie and it's a bit hard for me to 
follow; i hope you can be patient as i ask some more newbie questions.

i have 2 separate domains www.myoriginalsite.com and www.mynewsite.com.

i create a sites/www.mynewpodcastsite.com directory.

i register the domain www.mynewsite.com and have the namerserver point 
to -- where -- to make this work? is there an apache config file that 
will make requests for www.mynewsite.com go to the sub-directory?

so now i have two settings.php files, one in /sites/default and one in 
/sites/www.mynewpodcastsite.com? and drupal will only use 
/sites/www.mynewpodcastsite.com when www.mynewpodcastsite.com is the url 
prefix being accessed?

then in this new settings.php file i can change the base_url value, but 
leave the database info the same.

How does drupal know how to use a completely different template and 
configuration for the new site?

if there is an article on drupal.org or somewhere that walks me through 
this that would be ideal, i'm a bit beyond my skillset here and on a 
steep learning curve.

thanks for help!

-- will



Michael Prasuhn wrote:
> On Jan 20, 2008, at 1:55 AM, Xavier Bestel wrote:
>> I have done something like that: a main site with much content, and
>> another site with only a few static pages and a part of the main  
>> site's
>> content.
>> I created a sites/mynewsite.com directory, and added a new  
>> settings.php
>> file in which I modified a few variables at the end to have a new  
>> name,
>> a new theme and a new frontpage for the site. I then arranged blocks  
>> for
>> this theme to display a new menu, and changed the theme to not display
>> the primary and seconday links.
>> And voilà ! But I'm not an Drupal expert, so there may be a better way
>> to do this.
>>
>> 	Xav
> 
> 
> 
> I have done the same thing before as well. A little more advice:
> 
> * Make sure $base_url is set, and then you can check against this in  
> php code for block visibility, it also makes sure that all the links  
> on that site, link to that site only. Any links back to the main site  
> with all content will have to include the full href.
> 
> * Use the $conf array to set things such as the front page of the new  
> site. e.g.
> 
> $conf = array(
>    'site_frontpage' => 'path_alias_for_your_view',
> );
> 
> A couple of downsides to this is that all content is available on  
> either side. Even if there are no links to it, one could poke around  
> and all the same paths will be valid on both sites. So you'll have to  
> watch your menus and blocks to make sure that the same links do not  
> appear on both sites. I managed this by having two versions of my  
> primary menu, and putting it into a block and then using PHP to  
> control which site got which block/menu. YMMV
> 
> -Mike
> 
> 
> __________________
> Michael Prasuhn
> mike at mikeyp.net
> http://mikeyp.net
> 949.200.7595
> 714.356.0168 cell
> 949.200.7670 fax
> 
>