• Pre-Requisites
• Build & Setup
• Option 1: Installing using the online package index
• Option 2: Installing using the local package index
• Configure the Installation
• Create a plone site
• Import demo structure
• Updating a Plone installation
• Folder Structure
• Starting and Stopping plone
• Next Steps
• Manual Install
• Pre-requisites
• SSL support for Python
• Setup
• Core Installation

Pre-Requisites

You should have completed the following steps :

• How to setup the Pre-requisites
• How to setup Bungeni Parliamentary Information System

1. The Plone build is an optional deployment configuration which adds a content management system into Bungeni.
2. The Plone build currently works only on Ubuntu 10.04

Build & Setup

Option 1: Installing using the online package index

fab -H <host-name-or-ip> plone_install config_ini:plone

See also Executing Fabric actions

Option 2: Installing using the local package index

Use this option only if you have a Bungeni package index running on your local network. Set the fabric parameters for the cached buildout by setting the local_cache parameters appropriately See Using the local_cache parameter

fab -H <host-name-or-ip> plone_install config_ini:plone 

See also Executing Fabric actions

Configure the Installation

Log in as the admin user into plone. The default username and password is 'ploneadmin'

Create a plone site

In the Zope ZMI create a new plone site. Enter "plone" as the value of the path identifier and the title of the site.

Under the add ons section select the following products:

• Bungeni CMS Workspaces
• Bungeni CMS policy
• Bungeni CMS theme
• BungeniHelpCenter
• PloneHelpCenter

Click on site-setup -> Add on products.

• LinguaPlone and click activate.

Import demo structure

• Once the buildout is complete there will be an 'import' folder on the filesystem found in the root plone folder.

• Copy and unzip the contents of http://dist.bungeni.org/plone/import/import-0.1.tar.gz into that folder

• Run the python script 'import_data' in the root plone directory (using the plone python). Before running the script, edit the file appropriately and put in the necessary values for username, password (ploneadmin, ploneadmin) and the plone site that you want to import to.

Updating a Plone installation

It is standard procedure to re-install a product when any changes have been made to it. This done in the zmi->portal_setup. Import the profile of the product that has changed. Or alternatively use the zmi-portal_quickinstaller to reinstall said product.

Folder Structure

Plone gets installed within the Bungeni folder

./bungeni
|-- bin
|-- buildconf
|-- cache
|-- data
|-- develop-eggs
|-- eggs
|-- locales
|-- logs
|-- parts
|-- patch
|-- plone
|   |-- Products
|   |-- bin
|   |-- develop-eggs
|   |-- downloads
|   |-- eggs
|   |-- import
|   |-- parts
|   |-- Products
|   |-- src
|   `-- var
|-- src
|-- templates
`-- testdatadmp

Starting and Stopping plone

See using supervisor to start / stop Plone

Next Steps

• How to setup Deliverance Portal

Manual Install

This documents manual installation of plone without using assistive scripts like Fabric. The following steps have been tested on Ubuntu 8.04.

Pre-requisites

• Build environment (on ubunutu do a sudo apt-get install build-essentials )
• user Python 2.4 built from source. (on ubuntu /debian you will need to install development libaries/headers for imaging (libjpeg62-dev, libfreetype6-dev, libpng12-dev) and bz2 (libbz2-dev) libraries) and for ssl support openssl and libssl (openssl, libssl-dev) (Oct 15 2010 build : libldap2-dev libsasl2-dev libssl-dev )
• A working bungeni parlimentary information system installation

SSL support for Python

In ubuntu installing openssl and libssl-dev does not result in Python getting built with ssl support as the default ssl paths for include/ lib referenced by the Python build are different in Ubuntu. To build ssl support into Python on Ubuntu set the CPPFLAGS and LDFLAGS environment variables as follows :

 CPPFLAGS=-I/usr/include/openssl LDFLAGS=-L/usr/lib/ssl

now run ./configure ; make ; make install

To test if python has ssl support run this in the python shell :

import urllib
f = urllib.urlopen('https://svn.openplans.org')
# if it returns no errors ... the ssl support works.. 

Setup

Note: the python setuptools package (a python egg) is used by buildout, if you have an older version of setuptools, you might need to update it manually first (from http://cheeseshop.python.org/pypi/setuptools/) in the python used for zope. Update instructions at: http://peak.telecommunity.com/DevCenter/EasyInstall#installation-instructions

If you dont have setuptools installed, buildout downloads and installs it automatically.

Core Installation

In order to install it, use buildout. Plone for Bungeni is always installed within the Bungeni Buildout folder and resides in a sub-folder called plone:

$ cd bungeni_buildout_folder
$ svn co https://bungeni-portal.googlecode.com/svn/plone.buildout/trunk/ --username <username> plone
$ cd plone
$ python bootstrap.py # not the system python! The one you use with Plone, i.e. 2.4.x. 
## prefix the buildout command with the path to Bungeni's postgresql bin so that
## the plone buildout finds the correct pg_config
$ PATH=../parts/postgresql/bin:$PATH ./bin/buildout  # wait a while..

Once this has successfully completed. Add the 1st user to plone - the admin user :

./bin/addzope2user admin password

Now edit the zope instance home variable to an absolute path pointing to the plone buildout folder :

## was %define INSTANCE .
%define INSTANCE /home/undesa/bungeni_portal/current/plone

Create a folder called var/filestorage :

mkdir -p ./var/filestorage

Now you can start plone :

./bin/paster serve etc/deploy.ini

Now run the configuration steps as described in Configure the Installation