A simple command to install a cron table, and make it evolve over time.
Use it in a deployement task to deploy a file containing your crontab.
Usage
Call the command using the module name.
Indicate a marker, unique on the host, with -m option, that will help identify the start / end of your specific tasks in crontab.
Indicate a file containing your crontab. The file may reference environment variables, that will be replaced at installation time using the python builtin template module.
For example, if we have a file crontab.tpl containing:
MAILTO="$ADMIN_MAIL" # recompute the model 0 0 * * * python -m project.rebuild_model >>/dev/null # check stuff in $STUFF_DIRNAME */10 * * * /usr/local/bin/check_stuff $STUFF_DIRNAME >>/dev/null
Launching:
$ ADMIN_MAIL="admin@acme.info" STUFF_DIRNAME="/srv/stuff" python3 -m cron_install -m MY_PROJECT crontab.tpl
Will install the following table:
$ crontab -l # START MY_PROJECT MAILTO="admin@acme.info" # recompute the model 0 0 * * * python -m project.rebuild_model >>/dev/null # check stuff in /srv/stuff */10 * * * /usr/local/bin/check_stuff /srv/stuff >>/dev/null # END MY_PROJECT
On a new run, all the part between # START MY_PROJECT and # END MY_PROJECT, will be replaced by the new crontab.
2 maintainers
Metadata
2 maintainers
Release files for cron-install 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 | Provenance | Actions |
|---|---|---|---|---|
| cron-install-0.2.0.tar.gz | 3.3 kB | Without provenance | Details for cron-install-0.2.0.tar.gz |
Release files / cron-install-0.2.0.tar.gz
| Download URL | cron-install-0.2.0.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f4d88dab25440b582aba6e5ec6e729efa3f7cfc6e1a9b4684d5c1dc074f8375
|
|
BLAKE2b-256 checksum How to use checksums |
8087733bddfc19f77fe6ce70a0d8f06d0a3053408d13af9fccf7f00288fb9303
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.0.0 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.7.5
|
Security for cron-install 0.2.0
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.
