Re: PloneLDAP Install

############################################
#
# Buildout Configuration File for ZEO Plone 
# -----------------------------------------
# $LastChangedDate: 2010-03-06 09:04:51 -0800 (Sat, 06 Mar 2010) $ $LastChangedRevision: 33462M $
# 
# After making changes in this configuration file,
# you should run bin/buildout to update the components.
#
# ALWAYS back up all Plone/Zope data and components
# before changing configuration.
#                     
# Running "bin/buildout" will update your installation,
# installing missing components as necessary.
#
# Use "bin/buildout -n" to update many components here to the newest
# available releases.
# This will update the add-on products you've added in the eggs= lines.
# This will not, however, upgrade Plone itself (or anything else you've
# pinned with a version specification). To upgrade Plone itself, see the
# comments in "Plone Component Versions".
#     
# Tutorial instructions for using zc.buildout for
# configuration management are available at:
# http://plone.org/documentation/tutorial/buildout
# Full details at http://pypi.python.org/pypi/zc.buildout
# 
############################################             


[buildout]                                  

############################################
# Plone Component Versions
# ------------------------
# This version of the Unified Installer has the components
# of Plone 3.3.5 preloaded so that it can install without
# an Internet connection.
# If you want to update, uncomment the "extends = http://..." below,
# edit it to point to the current version URL,
# comment out the "extends = versions.cfg" line
# and run "bin/buildout -n" while attached to the Internet.
# Generally, you only want to do that as part
# of a planned migration.         
# 
# extends = http://dist.plone.org/release/3.3.5/versions.cfg
extends = versions.cfg
versions = versions

# This extension will dump a list of unpinned versions
# each time you run buildout.
extensions = buildout.dumppickedversions


############################################
# Ports
# -----
# Specify the ports on which your Zope installation
# will listen.
# ZEO Server
zeo-address = 127.0.0.1:8100
# Zope client 1
client1-address = 8080          
# Zope client 2
client2-address = 8081


############################################
# Eggs               
# ----
# Add an indented line to the eggs section for any Python              
# eggs or packages you wish to include.
# 
eggs =
      Plone
      Products.Ploneboard
# 
# Optional Functionality
# ----------------------
# Uncomment the indented lines to include these products.
# Documentation on all of them, along with many more products,
# is available at
# http://plone.org/products/
#
# Commonly used products:
# * LinguaPlone provides tools for building multi-lingual sites
# * Products.CacheSetup adds the "CacheFu" Plone speedup kit
# * PloneHelpCenter is a simple knowledge base            
# * PloneFormGen provides through-the-web form building  
# 
#    Products.LinguaPlone
#    Products.CacheSetup
#    Products.PloneHelpCenter                  
#    Products.PloneFormGen
# 
# Commonly used development tools:
# * Clouseau uses AJAX to provide a Python prompt inside Plone
# * DocFinderTab puts an object documentation inspector in the Zope Management Interface
# * Gloworm is a Firebug-like viewlet inspector and customizer
# * plone.reload allows you to refresh Python code and ZCML configuration
#   without restarting Zope. Note that to use plone.reload, you'll also
#   need to uncomment the "zcml" entry for it below.  
# 
#    Products.Clouseau                  
#    Products.DocFinderTab
#    Products.Gloworm
#    Products.DocFinderTab
#    Products.Gloworm
#    plone.reload


############################################       
# ZCML Slugs  
# ----------
# Some eggs need ZCML slugs to tell Zope to
# use them. Eggs with names beginning with "Products."
# usually don't need this.      
zcml =         
#    plone.reload     


############################################
# Development Eggs   
# ----------------
# You can use paster to create "development eggs" to                   
# develop new products/themes. Put these in the src/
# directory.
# You will also need to add the egg names in the
# eggs section above, and may also need to add them
# to the zcml section.   
# 
# Provide the *paths* to the eggs you are developing here:
develop =               
#    src/my.package


############################################
# Debug Mode
# ----------             
# Change debug-mode to "on" to run in development mode.        
# 
debug-mode = off
# Add-on developers should turn deprecation warnings on  
deprecation-warnings = off
# change verbose-security to "on" for useful security errors while developing
verbose-security = off  


############################################
# Backup Directory                
# ----------------
# Sets the target directory for the bin/backup and bin/snapshotbackup
# commands. Default is inside this project's var directory, but ideally
# this should be on a separate volume or backup server.                  
#   
backups-dir=${buildout:directory}/var                 



############################################
############################################
############################################
# Buildout instructions beyond this point are
# usually only changed by experienced developers.
#
# Beyond here there be dragons!


eggs-directory=/usr/local/Plone/buildout-cache/eggs   
download-cache=/usr/local/Plone/buildout-cache/downloads
newest = false 
parts =               
    zope2
    productdistros
    zeoserver
    client1          
    client2       
    zopepy
    zopeskel
    precompile
    chown
    unifiedinstaller
    backup               
    python-ldap

# Add additional egg download sources here. dist.plone.org contains archives
# of Plone packages.
find-links =
    http://dist.plone.org
    http://download.zope.org/ppix/          
    http://download.zope.org/distribution/
    http://effbot.org/downloads


# unzip all eggs for easier debugging
unzip = true

# let's share our Zope install
zope-directory = /usr/local/Plone


# This section installs the components of Zope 2.
# Zope operating instances are created elsewhere.
# For options see http://pypi.python.org/pypi/plone.recipe.zope2instance


[python-ldap]
recipe = zc.recipe.egg:custom
eggs = python-ldap == 2.3.8                           
find-links =
include-dirs = /usr/include /usr/lib/sasl2
library-dirs = /usr/lib

[zope2]
recipe = plone.recipe.zope2install
# update zope by updating this URL:
url = ${versions:zope2-url}
# fake eggs are required to satisfy Zope dependencies while
# zope is not yet eggified.
fake-zope-eggs = true
additional-fake-eggs =
    ZConfig           
    pytz 


# Use this section to download additional old-style products.
# List any number of URLs for product tarballs under URLs (separate
# with whitespace, or break over several lines, with subsequent lines
# indented). If any archives contain several products inside a top-level
# directory, list the archive file name (i.e. the last part of the URL,
# normally with a .tar.gz suffix or similar) under 'nested-packages'.
# If any archives extract to a product directory with a version suffix, list
# the archive name under 'version-suffix-packages'.
# For options see http://pypi.python.org/pypi/plone.recipe.distros
[productdistros]
recipe = plone.recipe.distros
urls =              
nested-packages =
version-suffix-packages =


# Use this section to install and configure a Zope
# Enterprise Objects server.
# For options see http://pypi.python.org/pypi/plone.recipe.zope2zeoserver
[zeoserver]
recipe = plone.recipe.zope2zeoserver
zope2-location = ${zope2:location}
zeo-address = ${buildout:zeo-address}
effective-user = zeo             
# Put the log, pid and socket files in var/zeoserver
zeo-log     = ${buildout:directory}/var/zeoserver/zeoserver.log
pid-file    = ${buildout:directory}/var/zeoserver/zeoserver.pid
socket-name = ${buildout:directory}/var/zeoserver/zeo.zdsock


# Use this section to install and configure a Zope
# client instance.
# For options see http://pypi.python.org/pypi/plone.recipe.zope2instance
[client1]
recipe = plone.recipe.zope2instance
zope2-location = ${zope2:location}
zeo-client = true      
zeo-address = ${zeoserver:zeo-address}

zeo-client = true      
zeo-address = ${zeoserver:zeo-address}
# The line below sets only the initial password. It will not change an
# existing password.
user = admin:aqx7Kpf6
http-address = ${buildout:client1-address}
effective-user = plone             
# change debug-mode to "on" to run in development mode
debug-mode = ${buildout:debug-mode}
# change verbose-security to "on" for detailed security
# errors while developing
verbose-security = ${buildout:verbose-security}
deprecation-warnings = ${buildout:deprecation-warnings}
# Put the log, pid, lock files in var/client1
event-log = ${buildout:directory}/var/client1/event.log
z2-log    = ${buildout:directory}/var/client1/Z2.log
pid-file  = ${buildout:directory}/var/client1/client1.pid    
lock-file = ${buildout:directory}/var/client1/client1.lock         


# If you want Zope to know about any additional eggs, list them here.  
# e.g. eggs = ${buildout:eggs} my.package
eggs =
    ${buildout:eggs}

# If you want to register ZCML slugs for any packages, list them here.
# e.g. zcml = my.package my.other.package
zcml =              
    ${buildout:zcml}


products =
    ${buildout:directory}/products                
    ${productdistros:location}


# You may also control the environment variables for the instance.
environment-vars =                
    PYTHON_EGG_CACHE ${buildout:directory}/var/.python-eggs

# client2 picks up nearly all its configuration     
# from client1. If you need to create a new client             
# stanza, you should be able to copy this (with a new part name),
# changing only the parts with "client2" in them.           
# For options see http://pypi.python.org/pypi/collective.recipe.zope2cluster
[client2]
recipe = collective.recipe.zope2cluster           
instance-clone = client1
# we only need to specify what's different from the clone instance.     
http-address = ${buildout:client2-address}
# Put the log, pid, lock files in var/client2
event-log = ${buildout:directory}/var/client2/event.log
z2-log    = ${buildout:directory}/var/client2/Z2.log
pid-file  = ${buildout:directory}/var/client2/client2.pid
z2-log    = ${buildout:directory}/var/client2/Z2.log
pid-file  = ${buildout:directory}/var/client2/client2.pid
lock-file = ${buildout:directory}/var/client2/client2.lock            


# installs a zopepy python interpreter that runs with your
# full Zope environment            
[zopepy]
recipe = zc.recipe.egg             
eggs = ${client1:eggs}
interpreter = zopepy     
extra-paths = ${zeoserver:zope2-location}/lib/python
scripts = zopepy


# installs paster and Zopeskel
[zopeskel]
recipe = zc.recipe.egg
eggs =
    PasteScript
    ZopeSkel


# compiles .py files in ./parts and ./products so that they don't
# need to be compiled by the daemon
# For options see http://pypi.python.org/pypi/plone.recipe.precompiler
[precompile]
recipe = plone.recipe.precompiler


# This recipe is used to set permissions -- and ownership for root mode installs
# For options see http://pypi.python.org/pypi/plone.recipe.command
[chown]
recipe = plone.recipe.command 
command =
    chmod 600 .installed.cfg
    touch ${buildout:directory}/var/zeoserver/zeoserver.log       
    find ${buildout:eggs-directory} -type d -name LC_MESSAGES -exec chown -R ${client1:effective-user} {} \;
    find ${zope2:location} -type d -name LC_MESSAGES -exec chown -R ${client1:effective-user} {} \;
    chown -R ${zeoserver:effective-user} ${buildout:directory}/var/filestorage
    chmod 700 ${buildout:directory}/var/filestorage 
    chown -R ${zeoserver:effective-user} ${buildout:directory}/var/zeoserver
    chmod 700 ${buildout:directory}/var/zeoserver                
    chown -R ${client1:effective-user} ${buildout:directory}/var/client?
    chmod 700 ${buildout:directory}/var/client?
update-command = ${chown:command}


# This recipe installs the plonectl script and a few other convenience  
# items.
# For options see http://pypi.python.org/pypi/plone.recipe.unifiedinstaller
[unifiedinstaller]
recipe = plone.recipe.unifiedinstaller              
user = ${client1:user}
recipe = plone.recipe.unifiedinstaller              
user = ${client1:user}
primary-port = ${client1:http-address}
sudo-command =sudo


# This recipe builds the backup, restore and snapshotbackup commands.
# For options see http://pypi.python.org/pypi/collective.recipe.backup
[backup]                           
recipe = collective.recipe.backup
location = ${buildout:backups-dir}/backups
snapshotlocation = ${buildout:backups-dir}/snapshotbackups


[versions]
Cheetah = 2.0.1               
Paste = 1.7.2
PasteScript = 1.7.3   
ZopeSkel = 2.11.1
collective.recipe.backup = 1.1
plone.recipe.command = 1.0
plone.recipe.distros = 1.5
plone.recipe.osxcontroller = 0.3
plone.recipe.precompiler = 0.3
plone.recipe.unifiedinstaller = 0.9
collective.recipe.zope2cluster = 1.0
PasteDeploy = 1.3.3
zc.recipe.egg = 1.2.2