Package: zopeskel.unis
IntroductionThis 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
<unis@ens-lyon.fr> and by Quadra Informatique <plone@quadra-informatique.fr>.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 UsageSkels 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 preparationcd /opt/python-envs
mkdir project
cd project
/opt/python/python-2.6/bin/virtualenv --distribute --no-site-packages .
source bin/activateAt this step verify that your Python interpreter is a python 2.6$pythonPython2.6.6(r266:84292,Nov92010,04:51:52)...Now you can install our architecture dependencies for Plone 4easy_installpython-ldapeasy_installpsycopg2easy_installlxml==2.2.8easy_installcelementtreeeasy_installzopeskel.unisYou can check if the new buildout template is well installed by typing the
following command:pastercreate--list-templatesAvailabletemplates:...unis_plone4_buildout:AbuildoutforPlone4.xYour new Plone easy installer is ready. You can create a new Plone 4 project.pastercreate-tunis_plone4_buildoutWhat can you configure in the easy mode:buildout directory name (‘builout’ or deployement)the main domain name use for the proxythe 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)Changelog1.14  2012-12-17Unpin old versions
[encolpe]Add a switch for plone IDE
[encolpe]1.13  2012-12-17Fix how customer name is added in the project path
[encolpe]Remove ploneIDE automatic installation
[encolpe]1.12  2012-05-04Fix collective.developermanual checkout using the readonly address for the git repository
[encolpe]1.11  2012-03-10synchronize with internal developments
[encolpe]Add PloneIDE
[encolpe]1.10  2011-10-27Force to use zopeskel<3.0a1 in setup.py
[edegoute]1.9   2011-07-28Fix HAProxy configuration
[encolpe]1.8   2011-05-02Add a test file for the Hudson server
[encolpe]Fix the typo in DSN condition
[encolpe]1.7   2011-04-20Update Plone default version to 4.0.5
[encolpe]Fix postgres and oracle DSN
[encolpe]1.6   2010-01-27Add 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-07Fix documentation errors
[encolpe]1.4   2010-12-23bugfix release
[encolpe]1.3   2010-12-23complete the easy mode
[encolpe]1.2   2010-12-22Complete installation documentation for Debian Lenny
[encolpe]1.1   2010-11-10Add usage documentation in the package description
[encolpe]1.0   2010-11-10Initial release
[encolpe]