Plone Runscript Recipe
Abstract
This is a buildout recipe for zope/plone which runs a script using zopectl in a zope instance.
Recipe options
- instance-home
The INSTANCE_HOME. This can commonly be found in the ${instance:location} buildout variables.
- zeo-home
If you are using a zeo server then you must define this option so zopectl can connect to your database. This can commonly be found in the ${zeoserver:location} buildout variable.
- script
The path to the script that will be run. If not specified the script name is taken form the part name with a .py suffix added and assumed to be location in ${buildout:bin-directory}.
- args
The arguments for the script.
The script is run using the instance startup script, which is assumed to be named like the basename part of the instance-home directory.
Changes
0.3.1 2009-03-08
Removed SVN tags – dont need no more SPAM [seletz]
0.3 2009-03-08
Long overdue release [seletz]
added support for zeo by adding a ‘zeo-home’ option which works in the same manner as the ‘instance-home’ option. the zeo is started and then stopped once the script has been run. [claytron]
Document the .py suffix default [wichert]
Allow specifying a custom script as well [wichert]
Expand the documentation a little bit [wichert]
1 maintainer
Metadata
1 maintainer
Release files for plone.recipe.runscript 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| plone.recipe.runscript-0.3.1.tar.gz | 3.6 kB | Without provenance | Details for plone.recipe.runscript-0.3.1.tar.gz |
Release files / plone.recipe.runscript-0.3.1.tar.gz
| Download URL | plone.recipe.runscript-0.3.1.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17862b00c464d546a69d438845d743b07c0fc444438efa0b81b19f17abbcfd39
|
|
BLAKE2b-256 checksum How to use checksums |
0d1f32912bcb9c628518c192b299209fec75ad31b82cd6074e47e13ea2926e75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for plone.recipe.runscript 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
