Page 1 of 1

Apache and folder structure for multi hosting with CMS

Posted: Thu May 11, 2006 3:02 pm
by Donoss
Hi,

I've downloaded CMSMS for windows and think its fantastic!  However I'm now trying to set it up on SuSE Linux so that I can have CMS to manage Multiple hosts.  At the moment I want to use domains (alias) on my local network but was wondering how to set up my file structure in Apache and CMS so that I can manage and test two domain names before I open up my webserver to the open world.  Eventually I want to host two domains (www.donoss.com and www.bramptonhall.com).  I'm new to Apache, PHP and CMSMS so please treat me gently!  I was thinking of making the document root /home as I already have a backup solution for this.  Do I have to install CMSMS in each domains folder or can I have just one installation and use this to manage to domains?  Any tips would be much appreciated.

Many thanks

Andy

Re: Apache and folder structure for multi hosting with CMS

Posted: Thu May 11, 2006 3:05 pm
by Dr.CSS
install CMSMS in each domains folder,,

  mark

Re: Apache and folder structure for multi hosting with CMS

Posted: Thu May 11, 2006 9:15 pm
by Ted
I've only ever done this on Debian, but I assume it's the same thing.  I have a /var/www.  From there, I usually have a directory for each domain (/var/www/cmsmadesimple.org).  From there, I usually have 1 for each subdomain (/var/www/cmsmadesimple.org/www /var/www/cmsmadesimple.org/forums).  Then for each, you install a separate instance of cmsms.

CMSMS doesn't handle a multiple hosting sitation, so each one is going to be a disconnected instance.

Does that help at all?

Re: Apache and folder structure for multi hosting with CMS

Posted: Fri May 12, 2006 9:26 am
by Donoss
Many thanks for your input, I'll giveit a try and let you know how I get on.

Regards

Andy

Re: Apache and folder structure for multi hosting with CMS

Posted: Fri May 12, 2006 12:06 pm
by Russ
Andy, I've also done it this way in Debian and would add, if possible, it might also be better to have different databases for each CMS instance, otherwise relying on differing extensions in a single database can get a bit confusing ;-) Plus if you are not managing them there are potential client conflicts...

Also I colour code or add some extra text to each install admin header so I know where I am, but I guess this is really only important if you are managing them yourself.

Russ