Documentation from Rome! (Edited in Houston)

Document Actions

Submitted by kclarks. on 2006-07-12 08:44. Development | Documentation

A quick attempt at instructions for how to do a "Rhaptos Site" install, so that Chuck has something to work from in Vietnam. Jenn added 4.5. Ross edited with abandon, since the original is archived in email.

Here are my steps/notes on the Zope installation of a RhaptosSite.

Zope Installation Steps:

Install Zope from distribution packages or Zope.org tarball:
1. configure --prefix=/opt/zope --with-python=/usr/bin/python2.3
2. install into /opt/zope
run /opt/zope/bin/mkzopeinstance.py answer questions:
- directory: /opt/instances/demo
- set an admin username and password
(optional) Run /opt/zope/bin/mkzeoinstance.py /opt/instances/demo portnum (ex. 8888)
edit /opt/instances/demo/etc/zope.conf
- set port-base (instance will be at port-base + 8080: i.e. 1000 = 9080)
- set effective-user www-data
- (optional, if using zeo) Comment out filestorage, uncomment zeoclient, change port to match zeo
chown -R www-data:www-data /opt/instances/demo
(optional) /opt/instances/demo/bin/runzeo
if that worked, then ^C, /opt/instances/demo/bin/zeoctl start
/opt/instances/demo/bin/runzope

Rhaptos Installation Steps:

Install the Rhaptos Products

Log into the ZMI using http://<hostname>:<port>/manage (you'll need the frames for logout)
Go to the Control Panel
Demo Product List
Shutdown from Control Panel
Back at root prompt, untar Products directly into /opt/instances/demo/Products
```
/opt/instances/demo/Products# tar zxf ~/storage-dispatch-tree.tar.gz
```
/opt/instances/demo/bin/runzope
Back in the browser, refresh the Control Panel
Demo the full Products list: look for broken products

Create the Rhaptos Site

Go to the root folder in the ZMI.
From the add dropdown box, select "Rhaptos Site" and click the "Add" button.
You will now be at the RhaptosSite configuration form. Do the following:
1. Id - chose a unique ID that doesn't exist at the root level
2. Title- Can be anything
3. Membership source - Leave at the default: "Create a new user folder in the portal"
4. Description - Can by anything
5. DBA username - The name of a postgres super user (and password, if necessary) (Use 'postgres', no password)
6. DB username - the name of the user that should own the database (Will be created if doesn't exist; enter the password if necessary) (leave as 'rhaptos')
7. DB name - a name for the new database that is unique and doesn't already exist if you do a psql -l. (and enter the server and port if neccesary) (enter 'repository-demo')
Click the "Add Rhaptos Site"

Configure the VirtualHostMonster to point to the new site (by Jenn)

At the top level of the ZMI, click the "virtual_hosting" object
Click the "Mappings" tab (there aren't any actual controls on the default page)
Enter [hostname]/[new site object name], and Save Changes.
example: tachi.cnx.rice.edu/rhaptos

Log out of the ZMI (using the top frame dropdown) so that you are also logged out of the new rhaptos site

Go back to the top of the new site (delete /manage from the URL in the location bar)

Click on "Join" link to create a new user at the Plone level, so that you don't use the Zope user folder. This requires a functional email setup. (current setup works, but is blocked by several ISPs including Rice: can deliver to cnx.org addresses)

Test and demo

Known issues:

Multiple instances default to same cvs storage: configure portal_cvs
Doesn't like absolutely no content. Make some.
Issue w/ EIP for published content and storage-dispatch. Don't.