Usage:
Create a part in your rpm buildout:
[zookeeper-deploy] recipe = zc.recipe.egg eggs = zc.zookeeper_deploy_buildout arguments = 'APP', 'RECIPE'
where
- APP
the name of your application and the name of the directory in /etc where deployments will be recorded
- RECIPE
the name of the meta-recipe to use
In development mode, you can include initlization logic to run the recipe in development mode:
[zookeeper-deploy] recipe = zc.recipe.egg eggs = zc.zookeeper_deploy_buildout arguments = ‘APP’, ‘RECIPE’ initialization = zc.zookeeper_deploy_buildout.development_mode = True
Changes
0.2.0 (2012-09-25)
Allow the application name (APP) to be blank or None, in which case it’s determined from the script name.
Added a -r option to specify a recipe entry point to the recipe supplied to main.
0.1.0 (2012-05-31)
Initial release
1 maintainer
Release files for zc.zookeeper_deploy_buildout 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| zc.zookeeper_deploy_buildout-0.2.0.tar.gz | 3.8 kB | Details |
Release files / zc.zookeeper_deploy_buildout-0.2.0.tar.gz
| Download URL | zc.zookeeper_deploy_buildout-0.2.0.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33f72c2c79165a27910e6bcbacd533b9b8bdf603d53c5d74efc9257f4bae199f
|
|
BLAKE2b-256 checksum How to use checksums |
a7f10216b606ff9a6df0525cbc32f48625a84338cd4c0bf8e9ea3c4bd5a221f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
