I run several sites with one Magnolia installation.
For example the site:
Just start the sites with dedicated handles
1. workers.properties: define two workers: author and publish.
workers.java_home=/usr/java/j2sdk1.4.2_03
ps=/
worker.list=author,public
worker.author.port=8019
worker.author.host=localhost
worker.author.type=ajp13
worker.public.port=8020
worker.public.host=localhost
worker.public.type=ajp13
2. httpd.conf: Define virtual hosts for each site. For Example:
# O'Connell
<VirtualHost *>
DocumentRoot /home/o/oconnell.de/public_html/
ServerName www.oconnell.de
ServerAlias oconnell.de
RewriteEngine on
RewriteRule ^/$ /oconnell.html [R]
JkMount /* public
</VirtualHost>
3. httpd.conf: Define virtual host for author instance:
# Magnolia Authoring
<VirtualHost *>
DocumentRoot /srv/www/htdocs/ccstuttgart
ServerName author.hirning.de
ServerAlias author.oconnell.de
ServerAlias author.ccstuttgart.de
JkMount /* author
</VirtualHost>
In its previous incarnation on JspWiki, this page was last edited on Feb 9, 2007 10:26:13 AM
What are your experiences with running multiple websites within one Magnolia instance? In my opinion Magnolia is not really suited for this. Magnolia is built around a single website, or at least a single customer. For example the user management module is notsomething where you want to store multiple customers in. I would be interested to hear your experiences.