Well, the easy way would be to change the name of the public app to
something that suites you better, e.g. "cms" or "pages" or whatever.
You only have to change the name of the app and the subscription paths
in the author instance and restart tomcat. Did I miss something?
The other thing is a bit more complex. Of course you could use an
apache rewrite rule to change all URLs to contain the app name, but
then you would have to change the way magnolia produces it's links too.
Both is feasible but gives you a headache because you would then end up
with broken links and missing images in the author instance... Not
good.
Finally you could cripple Tomcat to serve your magnolia public instance
at the root context (i.e. at "/", as it was with Magnolia 1). But this
is a headache too, because first of all it's a hack (IMO) and secondly
you would have to have the author instance in a separate Tomcat since
you can only have one app at the root context of course.
I strongly suggest method 1 - changing "magnoliaPublic" to what ever
suites you better.
-Will
On 21.10.2005, at 08:32, bholey ram wrote:
I dont want magnoliaPublic to appear on the deployed web site.
e.g I want something like www.mysite.com.
Is this something that I would have to do within magnolia or is this
a tomcat configuration.
thanks
bholey
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
