[Checkins] SVN: gocept.zeoraid/trunk/doc/DEPLOYMENT.txt Added a note about using zc.recipe.deployment or
Christian Theune
ct at gocept.com
Sat Nov 14 03:06:59 EST 2009
Log message for revision 105638:
Added a note about using zc.recipe.deployment or
gocept.recipe.deploymentsandbox to avoid killing your volatile data.
Changed:
U gocept.zeoraid/trunk/doc/DEPLOYMENT.txt
-=-
Modified: gocept.zeoraid/trunk/doc/DEPLOYMENT.txt
===================================================================
--- gocept.zeoraid/trunk/doc/DEPLOYMENT.txt 2009-11-13 22:38:58 UTC (rev 105637)
+++ gocept.zeoraid/trunk/doc/DEPLOYMENT.txt 2009-11-14 08:06:57 UTC (rev 105638)
@@ -15,7 +15,7 @@
the actual FileStorages.
- On the ZEORAID server, install the `gocept.zeoraid` package using
- `distutils` or `setuptool` so that the ZEO server can access it.
+ `distutils` or `setuptools` so that the ZEO server can access it.
- Configure your `zeo.conf` file for ZEORAID by defining a storage like this::
@@ -54,5 +54,10 @@
- When running `buildout`, each configured `raidstorage` will get a
RAID management generated to control the specific raid storage.
+- For production environments *ALWAYS* use a deployment recipe
+ (zc.recipe.deployment, gocept.recipe.deploymentsandbox) that stores your
+ dynamic data (like PID and log files) in a safe place so buildouts don't
+ disrupt operation.
+
Any maintenance (log rotration, packing, ...) can be done as you do for any
other ZEO server using `zc.zodbrecipes:server`.
More information about the checkins
mailing list