Skip to main content

ZC Buildout recipe for installing a Zope 2 ZEO server

Project description

plone.recipe.zope2zeoserver

This recipe creates and configures a Zope 2 ZEO server in parts. It also installs a control script, which is like zeoctl, in the bin/ directory. The name of the control script is the the name of the part in buildout.

You can use it with a part like this:

[zeoserver]
recipe = plone.recipe.zope2zeoserver
zope2-location = /path/to/zope2/install
zeo-address = 8100

Options

zope2-location

The path where Zope 2 is installed. If you are also using the plone.recipe.zope2install recipe, and you have that configured as a part called ‘zope2’ prior to the zope2zeoserver part, you can use ${zope2:location} for this parameter. You must ensure the zope2zeoserver part is run after the zope2install one.

zeopack

The path to the zeopack.py backup script. A wrapper for this will be generated in bin/zeopack, which sets up the appropriate environment to run this. Defaults to “${zope2-location}/utilities/ZODBTools/zeopack.py”. Set this option to an empty value if you do not want this script to be generated.

zeo-conf

A relative or absolute path to a zeo.conf file. If this is not given, a zeo.conf will be generated based on the the options below.

The following options all affect the generated zope.conf.

zeo-address

Give a port for the ZEO server. Defaults to 8100.

effective-user

The name of the effective user for the ZEO process. Defaults to not setting an effective user.

invalidation-queue-size

The invalidation-queue-size used for the ZEO server. Defaults to 100.

zeo-log

The filename of the ZEO log file. Defaults to var/log/${partname}.log

zeo-log-custom

A custom section for the eventlog, to be able to use another event logger than logfile. zeo-log is still used to set the logfile value in the runner section.

storage-number

The number used to identify a storage.

file-storage

The filename where the ZODB data file will be stored. Defaults to var/filestorage/Data.fs.

blob-storage

The folder where the ZODB blob data files will be stored.

socket-name

The filename where ZEO will write its socket file. Defaults to var/zeo.zdsock.

zeo-conf-additional

Give additional lines to zeo.conf. Make sure you indent any lines after the one with the parameter.

Reporting bugs or asking questions

We have a shared bugtracker and help desk on Launchpad: https://bugs.launchpad.net/collective.buildout/

Change History

0.12 (2008-03-02)

  • Fixed zeopack generation so it includes zope-location. [tarek]

0.11 (2008-02-19)

  • Made Python 2.3 compatible [fschulze]

  • Added win32 specific scripts. [tarek]

  • Added a zeo-log-custom option. [tarek]

  • Added a test environement and a basic doctest to validate the recipe. [tarek]

0.10 (2008-01-09)

0.9 (2007-12-30)

0.8

  • Small documentation update. Added link to the bugtracker. [hannosch]

  • Have PID file’s location default to ${buildout:directory}/var/${name}.pid. Keeping the PID file in $INSTANCE_HOME gives trouble when buildout rebuilds the part. [nouri, mbenali]

0.7

  • Change default location of zeo socket to var. [smcmahon]

  • Add option to set socket-name. [smcmahon]

0.6

  • Move the documentation to a separate README.txt and read that from setup.py. [wichert]

  • Add a wrapper around zeopack which inserts default options for our ZEO server. [wichert]

0.5

  • Added an option to set the effective-user. [optilude]

0.3

  • Updated setup.py. [optilude]

0.2

  • Similarly, there are some hardcoded dependencies on $INSTANCE_HOME/etc/. [optilude]

  • Documented options, cleaned up code, and added the ability to use a manual zeo.conf. [optilude]

  • Make this work, at least on OS X and probably unix-like system. It wouldn’t surprise me if this needs adjustment for Windows in the same way that we do in plone.recipe.zope2instance. :-( [optilude]

0.1

  • Initial implementation. [regebro, hannosch]

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

plone.recipe.zope2zeoserver-0.12.tar.gz (15.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

plone.recipe.zope2zeoserver-0.12-py2.4.egg (27.0 kB view details)

Uploaded Egg

File details

Details for the file plone.recipe.zope2zeoserver-0.12.tar.gz.

File metadata

File hashes

Hashes for plone.recipe.zope2zeoserver-0.12.tar.gz
Algorithm Hash digest
SHA256 1c584f048e5bc82f5c4588d196be5599edc7b563c6c4c2da52b9cfeb2f3fab05
MD5 878a5021ed9c9e89ff7fd47d1b062778
BLAKE2b-256 0002ca1d0bce5ac41b4a893fd1ebf7bf92ed10d5d84fc47a824e3609ba107176

See more details on using hashes here.

File details

Details for the file plone.recipe.zope2zeoserver-0.12-py2.4.egg.

File metadata

File hashes

Hashes for plone.recipe.zope2zeoserver-0.12-py2.4.egg
Algorithm Hash digest
SHA256 59fc37d44a99398bc06519b7bf6645cb36f62b644a286cae327d8d0c63569a5d
MD5 cfafb23b441edc8d0a24c3dae8886fbb
BLAKE2b-256 3ce6ee7ecfe068897ea3a564c7d54be267e42cca3f3dc6a56d74a684142ee5fd

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page