Library and CLI for working with multiple cron jobs within a single cron table
Example
# The following examples assume you have the following example
# crontab file jobs.tab. Note that due to the way the examples
# are laid out, they will not run in the order shown below.
#
# jobs.tab contents:
# # [Frequent Job]
# MAILTO=user
# MAILFROM=root
# PATH=/home/user
# SHELL=/bin/sh
# CRON_TZ=/Etc/UTC
# * * * * * echo "This runs frequently"
#
# # [Specific Job]
# MAILTO=""
# MAILFROM="user"
# PATH=/some/specific/dir
# SHELL=/bin/bash
# CRON_TZ=/Etc/Universal
# 1 2 3 4 5 echo "This runs... oddly specifically
# Add a job to the crontab
cronberry add jobs.tab
# Add a specific job to the crontab
cronberry add jobs.tab --title "Specific Job"
# Add a job manually to the crontab
cronberry enter "Manually Added" '5 4 3 2 1 echo "Custom cronjob"'
# You can also pass environment variables
cronberry enter "With Env Vars" '1 1 2 3 5 echo "This uses bash!"' --shell /bin/bash
# Remove a job from the crontab
cronberry remove "Specific Job"
# Clear the current crontab
cronberry clear
# Save the current crontab to a file
cronberry save "saved.tab"
# Get the specific job with the given title, from a diff
cronberry view "Frequent Job"
# Returns:
# * * * * * echo "This runs frequently"
# See the environment variables of a given job as well
cronberry view "Frequect Job" -v
# Returns:
# [Frequent Job]
# MAILTO=user
# MAILFROM=root
# PATH=/home/user
# SHELL=/bin/sh
# CRON_TZ=/Etc/UTC
# * * * * * echo "This runs frequently"
# See all the jobs in crontab (you can also use the -v flag)
cronberry list
# Returns:
# jobs.tab contents:
# * * * * * echo "This runs frequently"
#
# # [Specific Job]
# 1 2 3 4 5 echo "This runs... oddly specifically
# Get all the job titles from the crontab
cronberry jobs
# Returns:
# Frequent Job
# Specific Job
Metadata
Release files for cronberry 5.0.0.post0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cronberry-5.0.0.post0.tar.gz | 41.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cronberry-5.0.0.post0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.4 kB
Release files / cronberry-5.0.0.post0.tar.gz
| Download URL | cronberry-5.0.0.post0.tar.gz |
|---|---|
| Size | 41.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf15d1fc0e529b539e373b8b44a3374c5fb006c3f491b000e0517728623df1e8
|
|
BLAKE2b-256 checksum How to use checksums |
ebec355b06bab18489df3d7fa475ea7c475cef687c9393e9a29bbb4156bcf931
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 23, 2025.
Transparency logRelease files / cronberry-5.0.0.post0-py3-none-any.whl
| Download URL | cronberry-5.0.0.post0-py3-none-any.whl |
|---|---|
| Size | 21.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86dbbef83a4a5a8e09a1286288caa43e873f6d720f25ff6b3432dd7dc1f39a65
|
|
BLAKE2b-256 checksum How to use checksums |
d53a988a5653b270cca3f3620a2551647e07f53542fc833bbfc4d120dbfd754b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 23, 2025.
Transparency log