One single WebGUI Instance you can use for multiple sites with different domains, e.g.:
www.server.xx (Path /home )
----- www.subserver01.xx (Path /sub01)
|
---- www.subserver02.xx (Path /sub02)
After installing of WebGUI, you'll have to make the pages /home, /sub01 and /sub02. Depending on your navigation-assets, it will be possible to jump to every site or not.
The next step is the configuring of Apache. Here you`ll need two instances (a proxy and one for WebGUI)
A proxy will analyse your requests and proxie it to the webgui-server on another port (e.g.81) or rewrites the hostnames
That's the trick!
# Proxy config
<VirtualHost _default_:80>
#...
RewriteEngine On
# redirect to domain, from other internal webgui site
RewriteCond %{HTTP_HOST} "sub01\."
RewriteRule ^/$ /sub01
# back from sub to master (on link /home)
RewriteCond %{HTTP_HOST} "sub01\."
RewriteRule ^/home$ http://www.server.xx/home [R]
# from master to sub (on link /sub01)
RewriteCond %{HTTP_HOST} "www.server\."
RewriteRule ^/sub01$ http://www.subserver01.xx/sub01 [R]
#same per subserver
#....
# get answers back with clients Hostname
ProxyPreserveHost On
RewriteRule ^/(.*) http://www.server.xx:81/$1 [P]
</VirtualHost>
# WebGUI-Server, normal but on port 81
<VirtualHost Adresse:81>
...
</VirtualHost>
With this type of installation with more apache-instances, it's no problem to run two or more different versions of WebGUI on one system.
If you configure the proxy also for php, you also might use phpMyAdmin (which is _still_ not possible with wre).
To configure Apache, you may copy and use your standard config and control-files, as long as you change the pid-file in the new control file and add a PidFile-Statement in your config like
"PidFile /var/run/httpd2_proxy" and "PidFile /var/run/httpd2_webgui"
Keywords: multi-sites multiple sites proxy redirect one-site_more-versions