zopeskel.unis 1.13

Different kind of buildout templates used by Quadra-Informatique

Introduction

This egg contains some paste templates to help to build a Plone architecture with as little knowledge as possible about Python and Plone. The first target is Debian Lenny up-to-date with the lenny-backports repository enabled. In a second time Debian Squeeze and Ubuntu LTS should be added. No ReadHat, Suse, Mandriva, or any RPM-based linux is on the roadmap.

The docs directory contains all necessary steps about server configuration before installing this egg. These documents can be distributed separately under the specified license in each of them.

These templates was initiated by the UNIS Team of the ENS de Lyon <[e-mail]> and by Quadra Informatique <[e-mail]>.

The CECILL-B license is a BSD like license. The english and the french version are available in this directory. If you want to make patch or to send us a success story you can use the mail addresses above.

UNIS Skels Usage

Skels allows you to quickly configure a new project following its need. For the next steps you only need a normal account user. The only steps you need to to as superuser are reconfiguring and restarting the proxy (apache or nginx) that runs on the port 80.

Project preparation

cd /opt/python-envs
mkdir project
cd project
/opt/python/python-2.6/bin/virtualenv --distribute --no-site-packages .
source bin/activate

At this step verify that your Python interpreter is a python 2.6

$ python
Python 2.6.6 (r266:84292, Nov  9 2010, 04:51:52)
...

Now you can install our architecture dependencies for Plone 4

easy_install python-ldap
easy_install psycopg2
easy_install lxml==2.2.8
easy_install celementtree
easy_install zopeskel.unis

You can check if the new buildout template is well installed by typing the following command:

paster create --list-templates

Available templates:
...
unis_plone4_buildout:  A buildout for Plone 4.x

Your new Plone easy installer is ready. You can create a new Plone 4 project.

paster create -t unis_plone4_buildout

What can you configure in the easy mode:

• buildout directory name (‘builout’ or deployement)

• the main domain name use for the proxy

• the id of the Plone site (‘site’ or ‘Plone’)

• the Plone version (above 4)

• shared blobs files between zope instances (you should say yes if all instances are on the same server)

• the ports starting value for all services (we reserve at least 15 ports)

• install LDAP aware products (python-ldap, PloneLDAP)

• install CAS aware products (CAS4PAS, collective.castle)

• install Metnav products (metnav, enslyon.existda)

Changelog

1.13 2012-12-17

• Fix how customer name is added in the project path [encolpe]

• Remove ploneIDE automatic installation [encolpe]

1.12 2012-05-04

• Fix collective.developermanual checkout using the readonly address for the git repository [encolpe]

1.11 2012-03-10

• synchronize with internal developments [encolpe]

• Add PloneIDE [encolpe]

1.10 2011-10-27

• Force to use zopeskel<3.0a1 in setup.py [edegoute]

1.9 2011-07-28

• Fix HAProxy configuration [encolpe]

1.8 2011-05-02

• Add a test file for the Hudson server [encolpe]

• Fix the typo in DSN condition [encolpe]

1.7 2011-04-20

• Update Plone default version to 4.0.5 [encolpe]

• Fix postgres and oracle DSN [encolpe]

1.6 2010-01-27

• Add zopepy, i18ndude, test and zopeskel parts from the new plone4_buildout template in ZopeSkel 1.19. [encolpe]

• Add ldap, cas and relstorage options [encolpe]

• Fix license in setup.py [encolpe]

• Add paster template usage in documentation [encolpe]

• Add correct classifiers for pypi [encolpe]

1.5 2010-01-07

• Fix documentation errors [encolpe]

1.4 2010-12-23

• bugfix release [encolpe]

1.3 2010-12-23

• complete the easy mode [encolpe]

1.2 2010-12-22

• Complete installation documentation for Debian Lenny [encolpe]

1.1 2010-11-10

• Add usage documentation in the package description [encolpe]

1.0 2010-11-10

• Initial release [encolpe]