My reply is particularly from the perspective of running multiple sites. I started using option two, with the public instance in the root webapp, and separate Tomcat virtual servers for each site. This ran into memory problems quite quickly.
I have changed to using a single pair of webapps, with the default names, and placing my sites under dummy root nodes as in option three. This enables the menus to be separate. URL rewriting I move outside using Apache as a reverse proxy (see my wiki write-up of this), because Magnolia doesn't know which site is being accessed. Inheritance works as I expect; but I don't have any sophisticated requirements. The main difficulties I have with this are: (1) the somewhat trivial matter that the obvious ways of dividing the sites in the templating trees (webapp and config) are different from each other and from the website and dms trees. (At least, those that work most easily with the URL rewriting are.) (2) there is no mechanism for dividing up roles and users according to sites, which limits the amount of separation of sites that can be achieved through the security system. Of course, as Magnolia isn't originally designed for doing this, I have no cause for complaint! Paul ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
