Skip to content
Permalink
Browse files

From Plone Installer

dumped-versions.cfg are things we haven't pinned yet.
base.cfg has changes, the others are default.
  • Loading branch information
jean committed Sep 28, 2015
1 parent 3453586 commit ea6ec97e31b26bb35b9454ec9783f486ecad1574
Showing with 734 additions and 0 deletions.
  1. +169 −0 base.cfg
  2. +144 −0 develop.cfg
  3. +144 −0 dumped-versions.cfg
  4. +38 −0 lxml_static.cfg
  5. +50 −0 zope-versions.cfg
  6. +74 −0 zopeapp-versions.cfg
  7. +115 −0 ztk-versions.cfg
169 base.cfg
@@ -0,0 +1,169 @@
######################################################
# Base Configuration; used by both standalone and zeo,
# which extend it.
# ---------------------------------------------------

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

[buildout]
eggs-directory=../buildout-cache/eggs
download-cache=../buildout-cache/downloads

# Don't download new things unless needed to satisfy dependencies.
# Override this on the command line with the "-n" flag.
newest = false

# pick final releases over newer development releases
prefer-final = true

versions = versions

# 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

# Load the DumpPickedVersions extension, which will notify
# you of versions picked by buildout that were not specifically
# pinned.
extensions = buildout.dumppickedversions




[zopepy]
# installs a zopepy python interpreter that runs with your
# full Zope environment
recipe = zc.recipe.egg
eggs = ${buildout:eggs}
interpreter = zopepy
scripts = zopepy




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


[repozo]
# This recipe builds the repozo script for non-zeo installations.
recipe = zc.recipe.egg
eggs = ZODB3
scripts = repozo


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


[zeoserver]
# Use this section to install and configure a Zope
# Enterprise Objects server.
# For options see http://pypi.python.org/pypi/plone.recipe.zeoserver
recipe = plone.recipe.zeoserver
zeo-address = ${site:zeo-address}
# if we try to start as root, Zope will switch to the user below
effective-user = ${site:zeo-user}
# 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
blob-storage = ${buildout:directory}/var/blobstorage


# More complicated one in build.cfg
# [chown-zeo]
# # This recipe is used to set permissions for root mode installs
# # For options see http://pypi.python.org/pypi/plone.recipe.command
# recipe = plone.recipe.command
# command =echo Dummy references to force this to execute after referenced parts
# echo ${backup:location} ${unifiedinstaller:sudo-command}
# chmod 600 .installed.cfg
# touch ${buildout:directory}/var/zeoserver/zeoserver.log
# find ${buildout:directory}/var -type d -exec chmod 700 {} \;
# chmod 744 ${buildout:directory}/bin/*
# update-command = ${chown-zeo:command}


[zopeskel]
# installs paster and Zopeskel
recipe = zc.recipe.egg
eggs =
ZopeSkel
Paste
PasteDeploy
PasteScript
${buildout:eggs}


[client1]
# Use this section to install and configure a Zope
# client instance.
# For options see http://pypi.python.org/pypi/plone.recipe.zope2instance
# Additional clients are a
recipe = plone.recipe.zope2instance
zeo-client = true
zeo-address = ${zeoserver:zeo-address}
# The line below sets only the initial password. It will not change an
# existing password.
user = ${buildout:user}
# if we try to start as root, Zope will switch to the user below
effective-user = ${buildout:effective-user}
http-address = ${buildout:http-address}
blob-storage = ${zeoserver:blob-storage}
shared-blob = on
# 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

# You may also control the environment variables for the instance.
environment-vars = ${buildout:environment-vars}



[client2]
# a copy of client1, except adjusted address and var location
<= client1
http-address = ${buildout:client2-address}
event-log = ${buildout:directory}/var/client2/event.log
z2-log = ${buildout:directory}/var/client2/Z2.log
pid-file = ${buildout:directory}/var/client2/client2.pid
lock-file = ${buildout:directory}/var/client2/client2.lock
@@ -0,0 +1,144 @@
#################################################################
#
# Development Configuration
# =========================
#
# This is a buildout configuration that sets up a development
# environment for Plone. It extends buildout.cfg.
#
# To use this configuration, run buildout via:
#
# bin/buildout -c develop.cfg
#
# This specifies develop.cfg as buildout's configuration file. This configuration
# file extends buildout.cfg, so that all the options from that file are
# automatically included.
#
# Included in the development configuration
#
# Common development tools:
#
# * paster and Zopeskel, an add-on skeleton construction kit.
#
# * mr.developer, a tool that automatically checks out source for
# add ons from a versioning system, then adds them to your
# development package list.
#
# * testrunner, which provides a command-line option to run
# test suites.
#
# * omelette, which automatically musters python package sources
# into parts/omelette for easy find / grep access.
#
# * DocFinderTab, which adds a "doc" tab to the ZMI to explore documentation
# for the current Zope object.
#
# * plone.reload, which allows you to use a URL like http://localhost:8080/@@reload
# to reload Python and ZCML code without restarting Zope.
#
# Common Customizations
# =====================
#
# Add packages to the sources managed by mr.developer by adding them to the
# [sources] section below.
#
# Add packages to the test suite by adding them to the "test-packages" option
# in the [buildout] section below.


############################################
# Sources
# -------
# Specify packages under development here.
#
# See http://pypi.python.org/pypi/mr.developer for mr.developer source specifications.
# <name> = <kind> [key=value] <url> [path] [key=value]
# kind = The kind of repository. Currently supported are one of svn (>= 1.5), hg, git, cvs or fs.
#
[sources]
# Examples: to check out plonetheme.sunburst from Plone's svn, use:
# plonetheme.sunburst = svn https://svn.plone.org/svn/plone/plonetheme.sunburst/trunk
#
# To use a python package that is being developed in your src subdirectory, use:
# myproduct.betterplone = fs myproduct.betterplone


[buildout]

############################################
# Test Packages
# ----------
# Specify a list of packages that you wish to explicity include in your test suite.
# Base eggs are automatically included
#
test-packages =
# plonetheme.sunburst


############################################
# Debug Mode
# ----------
# Most development work is done with Zope/Plone started
# in foreground mode (bin/plonectl fg), which automatically
# turns on debug mode and causes Zope/Plone to stop on
# package loading errors.
#
# Note that debug mode makes Plone run *very* slowly due to
# extra filesystem checks and granular transmission of browser resources.
#
# If you have a need to run in debug mode outside foreground
# operation, turn on debug mode below.
debug-mode = off
#
# If you're developing Plone add-ons, you should want to see
# deprecation warnings that let you know if you're using outmoded
# methods or modules.
deprecation-warnings = on
#
# Turning on verbose security may help diagnose security bugs.
# You'll also need to disable the intercepting of "unauthorized"
# errors in the error_log via the ZMI.
verbose-security = off


############################################
# Less Commonly Changed Options
# -----------------------------
# The remainder of the buildout mainly sets up the development
# environment based on the settings above.

# we're extending buildout.cfg
extends =
buildout.cfg

extensions +=
mr.developer

eggs +=
Products.DocFinderTab
plone.reload

parts +=
test
omelette

# mr.developer settings:
always-checkout = force
sources = sources
auto-checkout = *


[omelette]
recipe = collective.recipe.omelette
eggs = ${buildout:eggs}


[test]
recipe = zc.recipe.testrunner
defaults = ['--auto-color', '--auto-progress']

eggs =
${buildout:eggs}
${buildout:test-packages}


0 comments on commit ea6ec97

Please sign in to comment.
You can’t perform that action at this time.