Chronograph
Control django-admin commands via the web.
Creating cron jobs for Django apps can be a pain, annoying and repetitive. With django-chronograph you simply create a single cron job to run every minute, point it at your site’s directory and run manage.py cron. Then from the admin you can add jobs.
Installation and Usage
Read docs/overview.txt for more information, build the documentation with Sphinx or view them online here.
You can also grab the latest release from PyPI:
pip install django-chronograph
Release files for django-chronograph 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 | |
|---|---|---|---|---|
| django-chronograph-0.3.1.tar.gz | 13.2 kB | Without provenance | Details |
Release files / django-chronograph-0.3.1.tar.gz
| Download URL | django-chronograph-0.3.1.tar.gz |
|---|---|
| Size | 13.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18bb6fe7d5dcb8308197891023d4cb01542ae7d95e4a7a7d9cfdc7dfcb43c8dd
|
|
BLAKE2b-256 checksum How to use checksums |
b7ab5719f0b78f179386da838fb3785309cd5d200290e57e8cd81f35f2b39a5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-chronograph 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.
