In a sharp left-turn for the danwalmsley.com ouvre, what follows is instructions for virtualising Magnolia CMS. Magnolia is an open-source Content Management system available in both community and enterprise versions, and is elegant and easy-to-use.
If you want to deploy Magnolia for multiple clients across multiple virtual domains hosted through a single instance of Apache HTTPD and a single instance of Apache Tomcat, read on.
Virtualises magnolia for an apache virtual host under / for root and /admin for admin stuff
What you get:
- myclient.com: magnolia public content (i.e. everything normally under /magnoliaPublic)
- myclient.com/admin: magnolia authoring interface (i.e. everything normally under /magnoliaAuthor)
$CLIENT = client name, e.g. myclient
$CLIENT_HOSTNAME = client host name to be proxied, e.g. myclient.com
$CLIENT_PORT = selected port on which Tomcat should host the site, e.g. 8082.
$TOMCAT_HOME = installation directory of TOMCAT
unzip magnoliaPublic.war to webapps_$CLIENT/ROOT
unzip magnoliaAuthor.war to webapps_$CLIENT/admin
(e.g. mkdir myclient.com)
edit $TOMCAT_HOME/conf/server.xml to include the following elements:
Create a config, $CLIENT.conf:
ServerName $CLIENT_HOSTNAME ProxyRequests Off
Order deny,allow Allow from allProxyPass / http://localhost:$CLIENT_PORT/ ProxyPassReverse / http://localhost:$CLIENT_PORT/ Order allow,deny Allow from all ]]>