[opencms-dev] understanding that Site listbox

Christoph P. Kukulies kuku at physik.rwth-aachen.de
Sat Nov 26 15:35:47 CET 2005

On Sat, Nov 26, 2005 at 04:20:38PM +1100, Nigel Kersten wrote:
> On 26/11/2005, at 12:37 AM, Christoph P. Kukulies wrote:
> >But it seems that its initial design or default settings are made
> >as if OpenCMS would be just the backend for a single site.
> >Why would it then be so difficult to add another site beside default?
> >
> >>sites in one OpenCms installation. So you can configure different
> >>vritual hosts in your apache, and let then point to the different  
> >>sites
> >>within OpenCms. Those sited could be edited by different groups of
> >
> >This sounds as I would like to use it. For a multilanguage site
> >like .de and .com on the same host/server it would be ideal to  
> >separate
> >the sites into two.
> Christopher, if you go through and set up the multi-site config with  
> Apache and Tomcat according to the alkacon-documentation, the whole  
> concept of 'sites' begins to make more sense.  I agree that OpenCMS  

Thanks. Will study this.

> could do with a simple document that said "This is what a project is  
> for, this is what a site is for" (much like one of the mails in this  
> thread... :) as I was also confused at first.

This gives me hope that I'm not all too stupid :-)

> I find it a little frustrating sometimes when I'm working on /sites/ 
> cofa, and have to either switch to /sites/default to view the alkacon- 
> documentation, or open up a different browser that isn't logged into  
> the OpenCMS workplace to view it, but I can kind of see why it is  
> like this.

Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de

More information about the opencms-dev mailing list