buildout_script
- Author:
Nathan R. Yergler <nathan@yergler.net>
- Copyright:
2006-2015, Nathan R. Yergler, Creative Commons; licensed to the public under the MIT license.
Overview
buildout_script is a zc.buildout recipe for generating scripts from a template. Unlike scripts specified by the console_scripts entry point, those generated by buildout_script are not restricted to Python code.
Scripts are generated from templates and can include settings from the buildout substituted at runtime.
One example usage is the generation of a wrapper script for Paste Script to check the status of a daemonized server process (see paster-check below).
Usage
To use the buildout_script recipe, specify it as the recipe for a zc.buildout part along with the template part. For example:
[sample_part] recipe = buildout_script template = paster-check.sh.in
The script will be created in the bin-directory. You may also specify the following parameters:
- target
The filename for the generated script; if omitted, the script will have the template filename without the extension.
- template_dir
An optional directory to look for templates in. Default: templates Templates included with the recipe may also be used without specifying a template_dir.
Templates
Template variables should be formatted using the buildout convention of ${part-name:variable-name}.
NB. Until version 0.2a1 of buildout_script the python string formatting syntax was used where the dictionary for the formatting operation was a flattened dictionary of the buildout settings and part settings.
For example, a trivial script template to list the files in the buildout installation directory would look like this:
#!/bin/bash
# Sample buildout_script script template
ls ${buildout:directory}
buildout_script ships with one script template, paster-check.sh.in, described below. Additional template contributions are welcome.
paster-check.sh.in
At Creative Commons we used Paste Script as the server for simple web applications. We run them using the --daemon flag, but occassionally something goes awry and the process dies. This template generates a script which can be called periodically from cron to ensure the process is still running. Note that this script can also be used to start the server if it is not already running.
Configuration Parameters
Configuration parameters used by this script, which should be specified as settings in the zc.buildout part:
- server_cfg
The Paste Deploy configuration file to serve.
- pid_file
The PID file to use when starting the server (and to subsequently check).
- log_file
The log file to use.
Change History
0.3.1 (2017-03-06)
Fix packaging issues
CHANGES.rst was referenced by setup.py, but not included in the package.
0.3 (2015-10-12)
PyPI release of changes contributed by jjmurre
0.2a3 (2015-10-08)
Templating syntax now cf. buildout, e.g. ${buildout:directory} NB. backwards incompatible!
0.2a2 (2015-10-07)
Fixes to make recipe work with modern pythons (>=2.7)
0.2a1 (2007-03-14)
Implemented template recipe for creating a non-executable file.
0.1 (2006-12-12)
Initial public release
Download
Metadata
Release files for buildout_script 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 |
|---|---|---|---|---|
| buildout_script-0.3.1.tar.gz | 1.1 MB | Without provenance | Details for buildout_script-0.3.1.tar.gz |
Release files / buildout_script-0.3.1.tar.gz
| Download URL | buildout_script-0.3.1.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1db74f813ed0c3499fd5ec4e282f9a9e14d199349ad847ddcc801e7b35b840ee
|
|
BLAKE2b-256 checksum How to use checksums |
966e1344f9b5e769e801a344420466962f732dfbfd44052fa576735679d43b9b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for buildout_script 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.