The following is what I used and it seemed to work. It presumes that you are going to have two Plone sites - one public facing and an intranet site for local staff. If you are not going to have the intranet site, forget about the extra i-bay and don't bother creating the second Plone Site instance.
Also, I found that if I set up Plone against my Primary i-bay, I couldn't get at my server-manager panel. So I have an i-bay called 'main' and set up a domain (e.g., 'mydomain.ca') for that (the SME server's domain I call 'primary.mydomain.ca' to avoid confusion).
Here's my How-To
Install PloneBefore you start, ensure that none of the domains to be served by Plone are the Primary. Set up an I-bay for the main web site and one for the intranet site; and set up virtual domains for each.
Download Des Dougan’s rpmslogin as root
Create a directory for the downloads
# mkdir –p /root/downloads/smeplone
# cd /root/downloads/smeplone
Download the files
# wget –nc http://mirror.contribs.org/smeserver/contribs/ddougan/Plone/Plone2-2.0.2-sme.04.i386.rpm
# wget –nc http://mirror.contribs.org/smeserver/contribs/ddougan/Plone/Plone2-2.0.2-sme.04.src.rpm
# wget –nc http://mirror.contribs.org/smeserver/contribs/ddougan/Plone/db4-4.1.25-0.rh73.3.1.i386.rpm
# wget –nc http://mirror.contribs.org/smeserver/contribs/ddougan/Plone/db4-devel-4.1.25-0.rh73.3.1.i386.rpm
# wget –nc http://mirror.contribs.org/smeserver/contribs/ddougan/Plone/expat-1.95.5-2.i386.rpm
# wget –nc http://mirror.contribs.org/smeserver/contribs/ddougan/Plone/python2.3-2.3.3-2pydotorg.i386.rpm
# wget –nc http://mirror.contribs.org/smeserver/contribs/ddougan/Plone/python2.3-2.3.3-2pydotorg.src.rpm
# wget –nc http://mirror.contribs.org/smeserver/contribs/ddougan/Plone/python2.3-devel-2.3.3-2pydotorg.i386.rpm
# wget –nc http://mirror.contribs.org/smeserver/contribs/ddougan/Plone/python2.3-docs-2.3.3-2pydotorg.i386.rpm
# wget –nc http://mirror.contribs.org/smeserver/contribs/ddougan/Plone/python2.3-tools-2.3.3-2pydotorg.i386.rpm
Install Plone# rpm –Uvh db4*
# rpm –Uvh python*
# rpm –Uvh expat*
# rpm –Uvh Plone*
Start Plone# /etc/rc.d/init.d/plone2 start
Test Plone# lynx “http://localhost:9080/Plone”
You should see the Plone main page in text browser mode.
Setup ‘Virtual Host Monster’The Des Dougan rpms seem to set the initial administrative Plone/Zope userid to 'plone' with a password of 'plone'.
From a network attached Windows computer, open a ssh tunnel with the target server
using PuTTY:
On the ‘Session’ pane, enter the ip address of the server and on the SSH>Tunnels pane, enter ‘9080’ as the Source Port and ‘127.0.0.1:9080’ as the Destination, the push the ‘Add’ button. This information should then appear in the Forwarded Ports box. Click the Open button at the bottom to open a session on the server.
Login as ‘root’ with the root password
OR
From a Linux workstation, open a ssh tunnel using the ssh command
in a terminal window enter
ssh -L 9080:localhost:9080 -C 192.168.0.1 -f sleep 100000
Be sure to replace the ‘192.168.0.1’ with the ip address of the server.
Then:
Open a web browser with the address ‘127.0.0.1:9080/manage’
The Zope main page should display. On the upper right of the screen, select “Virtual Host Monster” from the Add pull-down list, and push the Add button. In the form that opens, enter an id (use ‘vhm’).
Then, setup a second Plone instance for the intranet site.
On the upper right of the Zope main page, select “Plone Site” from the Add pull-down list and push the Add button. In the form that opens, enter an id (use ‘Intranet’); add a Title (e.g., ‘Company Intranet Site’); keep the default Membership source and provide a Description (e.g., ‘The Company intranet site.’) Then click Add Plone Site and wait for the site to be created.
Close the browser and the ssh tunnel.
Setup Apache virtual host routing to the VHMEnsure that this directory path exists
/etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/VirtualHosts
and if not, create it.
# mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/VirtualHosts
Change to that directory.
# cd /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/VirtualHosts
create an empty file
# pico
add the following lines to the file:
#
# RewriteRule directives for Zope/Plone Virtual Host Monster
#
RewriteEngine on
{
return “” unless $virtualHost eq “mainhost.ca”;
‘RewriteRule ^/(.*) http://localhost:9080/VirtualHostBase/http/[ip]:80/Plone/VirtualHostRoot/$1 [L.P]’;
}
{
return “” unless $virtualHost eq “intranet.mainhost.ca”;
‘RewriteRule ^/(.*) http://localhost:9080/VirtualHostBase/http/[ip]:80/Intranet/VirtualHostRoot/$1 [L.P]’;
}
Replace the ‘[ip]’ portion with the relevant domain name (e.g.,
www.mainhost.ca) and save with the file name ‘35Rewrite’
N.B. ensure that each RewriteRule directive is only on one line before saving and enclosed in single quotes.
then regenerate the Apache configuration file
# /sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf
then restart Apache to have the new configuration take effect
# service httpd restart
Get Plone to start automatically on boot.# cd /etc/rc.d
# pico rc.local
add to the bottom of the file
# start Plone2
/etc/rc.d/init.d/plone2 start
save and exit
And that's it. Using a browser go to your Plone domain and try it.
Best of luck.
John