This release is a pre-release and may not be stable for production use.
Plone Runscript Recipe
- Author:
Stefan Eletzhofer <stefan.eletzhofer@inquant.de>
- Date:
$Date: 2007-06-03 22:24:17 +0200 (Sun, 03 Jun 2007) $
- Revision:
$Revision: 43085 $
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
- args
The arguments for the script
The name of the script is created from the section name and is assumed to be in the ${buildout:bin-directory}.
The script is the run using the instance startup script, which is assumed to be named like the basename part of the instance-home directory.
1 maintainer
Metadata
1 maintainer
Release files for plone.recipe.runscript 0.1dev-r43085
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.1dev-r43085.tar.gz | 2.8 kB | Without provenance | Details for plone.recipe.runscript-0.1dev-r43085.tar.gz |
Release files / plone.recipe.runscript-0.1dev-r43085.tar.gz
| Download URL | plone.recipe.runscript-0.1dev-r43085.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13967b4395365815401e653211bc116a74626f2cb4b82d54b510cfe71df8acd2
|
|
BLAKE2b-256 checksum How to use checksums |
9a0f93b50fa23570a13ca291d254738c5514f9766284e2b7aa95385311e8711a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for plone.recipe.runscript 0.1dev-r43085
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.
