cronster
Installation
To install cronster, type:
$ pip install cronster
Getting Started
Install Redis
To get started with cronster, install Redis on your computer (macOS & Homebrew in this example):
$ brew install redis
$ brew services start redis
Digital Ocean has a great tutorial on how install Redis on Ubuntu.
Run the crawler
Assuming Redis is running on your machine in default configuration and you want to crawl from ~/projects, run the following command:
$ cronster_crawler -r ~/projects
The full help output explains the other options of the CLI application. It is possible to change certain parameters should Redis on a different host/port or should you want to adjust the interval between crawls:
Usage: cronster_crawler [OPTIONS]
Options:
-r, --root TEXT Crawling root, default: the current working directory
-h, --cache-host TEXT Cache host, default: localhost
-p, --cache-port INTEGER Cache port, default: 6379 (Redis default)
-i, --interval INTEGER Crawling interval, default: 2 seconds
--help Show this message and exit.
Run the scheduler
Assuming Redis is running on your machine in default configuration, run the following command:
$ cronster_scheduler
The full help output explains the other options of the CLI application. It is possible to change Redis-related parameters should Redis on a different host or port:
Usage: cronster_scheduler [OPTIONS]
Options:
-h, --cache-host TEXT Cache host, default: localhost
-p, --cache-port INTEGER Cache port, default: 6379 (Redis default)
--help Show this message and exit.
Write a crontab file
Write the following YAML file to ~/projects/crontab (or any other location anywhere in the hierarchy under your root location):
test_job:
cmd: echo "Hello, World!"
schedule: "*/5 * * * *"
You should see the job being picked up by the crawler on the next crawl and should see the scheduler run the job every five minutes.
Metadata
Release files for cronster 0.1.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 |
|---|---|---|---|---|
| cronster-0.1.1.tar.gz | 17.1 kB | Without provenance | Details for cronster-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cronster-0.1.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for cronster-0.1.1-py2.py3-none-any.whl |
Total release size: 27.3 kB
Release files / cronster-0.1.1.tar.gz
| Download URL | cronster-0.1.1.tar.gz |
|---|---|
| Size | 17.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c0785def704e04a9110097dd7812d07db576fc2bf4c9269b14225d657fb3591f
|
|
BLAKE2b-256 checksum How to use checksums |
aa6ecb30f5c63b2680a13b1cad6c08750939fbe02ae5f9812c8404c6f1f713ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / cronster-0.1.1-py2.py3-none-any.whl
| Download URL | cronster-0.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 10.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
a1aceb7d14ce4d031c8f909512972b0f0dd7b5463da3b5b469980ab13d83cb6d
|
|
BLAKE2b-256 checksum How to use checksums |
e214fbd2bbafa1bfee2d5105f3a332eb20fb7d2854eb1534e04dd81aa8162dd8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cronster 0.1.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.