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 zope2instance part, you can use ${zope2:location} for this parameter.
- 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.
- zeo-log
The filename of the ZEO log file. Defaults to var/log/${partname}.log
- file-storage
The filename where the ZODB data file will be stored. Defaults to var/filestorage/Data.fs.
- socket-name
The filename where ZEO will write its socket file. Defaults to var/zeo.zdsock.
- zope-conf-additional
Give additional lines to zope.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.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]
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for plone.recipe.zope2zeoserver-0.8.tar.gz
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 2fe4a40fd8c506902dbff7e903e1d9af7d89ba74ea879afe13547deda0ba9149 |
|
| MD5 | e9f4fd1a95fbfb6f5c17b8b0dc4a9a69 |
|
| BLAKE2b-256 | 923e4f509fe3cfdb666f65b277da4e84e493f456e97ba61022f6572f8bae7b5b |
Hashes for plone.recipe.zope2zeoserver-0.8-py2.4.egg
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 17dda007edf195b70a97f3bc17e18ff34af6cd673b719e4baca7dab62bc545d1 |
|
| MD5 | 9746d4653bd79e69c0493b20803d0374 |
|
| BLAKE2b-256 | e2c9e246f90b123b78c86ab67aef8293dadd168e28384267329b73a03dc71dfe |
