Process runner inspired by foreman
You should use it during development.
Usage
Create a Henfile (it is YAML):
name: Shopium[dev]
proc:
web: "python -u ./manage.py runserver -b 0.0.0.0"
cdn: "python -u ./dev_cdn_server.py"
solr: "./run_solr"
workers: "python -u ./manage.py runworkers"
smtp_worker: "sh -c \"PYTHONPATH=libs:core python workers/smtp_gateway.py shopium.ini\""
env:
PYTHONUNBUFFERED: "1"
Run hen:
hen
Running with some processes disabled:
hen --nocdn --nosolr
Installation
pip install hen
Compatibility
Tested with Python 2.7 and Python 3.2/3.3
How to contribute
It is easy. Fork repo on GitHub, fix stuff and send me nice looking pull-request.
Metadata
Release files for hen 1.4.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 |
|---|---|---|---|---|
| hen-1.4.1.tar.gz | 3.2 kB | Without provenance | Details for hen-1.4.1.tar.gz |
Release files / hen-1.4.1.tar.gz
| Download URL | hen-1.4.1.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d07bf04f477d17db3e8de19ed89f28e356788a5995153b04f4c5389942336184
|
|
BLAKE2b-256 checksum How to use checksums |
bd983c1a8b3de405621f0f827ffc7360866ad4fb072b432fca58f163ea54edff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for hen 1.4.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.