[opencms-dev] import/export index configuration

[Jonathan Woods]

I guess the set-up process could cope with this, though, by kind of sawing
off the branch it sits on: "after you complete this step, you will need to
configure Apache <thus> and then revisit <this URL>".

I avoided renaming OpenCms to ROOT.war because that didn't feel like The
Right Thing, so as you imply I'm left with a two-stage set-up, with the
first (manual) stage carried out before I turn on Apache's RewriteEngine.
I'm using mod_jk rather than mod_proxy, and the only case this doesn't cope
with is (predictably) the case of an HTTP redirect from OpenCms - the
OpenCms JSP example in which sendRedirect is used tries to send the browser
to /opencms/opencms/... regardless of my configuration - which feels like a
bug to me.  Maybe I'm not getting it, but it feels as though OpenCms should
behave the same in the redirect case as it does when generating any other
kind of URI/URL.

Jon

-----Original Message-----
From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Nigel Kersten
Sent: 17 February 2006 20:31
To: The OpenCms mailing list
Subject: Re: [opencms-dev] import/export index configuration


On 18/02/2006, at 3:52 AM, Jonathan Woods wrote:

> I know it's
> possible to delve into OpenCms config and Apache 
> mod_rewrite/mod_proxy/mod_jk config, but the getting rid of the 
> "/opencms/opencms" prefix is (i) very fiddly, and (ii) a very common 
> requirement.  It would be lovely if the set-up wizard said "What URI 
> prefix would you like dynamic resources to have?  What URI prefix 
> would you like exported resources to have?", combining this with the 
> ability to configure multiple sites both at set-up time and later 
> through the Workplace.

part of the problem however is that while you could do that with the second
prefix in /opencms/opencms, the first one depends upon the Tomcat context in
which you're deploying it, *prior* to the setup wizard actually running.

The docs do mention how you can rename opencms.war to ROOT.war and remove
your existing ROOT context if you wish to deploy it at that context, so you
can effectively rename it to whatever you want to deploy it.

It's not particularly fiddly to get rid of the second prefix altogether
using apache2 and ProxyPass, the only problem I ran into was how to make
sure the 404 handler was working properly in order to export content that
had yet to be exported.


--
Nigel Kersten [Senior Technical Officer] College of Fine Arts, University of
NSW, Australia.
CRICOS Provider Code: 00098G



_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev