Celery-BeatX is a modern fail-safe schedule for Celery.
Celery-BeatX allows you to store schedule in different storages and provides functionality to start celery-beat simultaneously at many nodes.
- Features:
stores schedule in different storages (currently support: redis, memcached)
allows to correctly run several instances of celerybeat simultaneously
See the documentation for more details.
Install
The package can be installed using:
pip install celery-beatx
After package installed you should set celery scheduler:
celery_app.config_from_object({
# ...
'beat_scheduler': 'beatx.schedulers.Scheduler',
'beatx_store': 'redis://127.0.0.1:6379/',
# ...
})
Contributing
If you have any valuable contribution, suggestion or idea, please let us know as well because we will look into it.
Pull requests are welcome too.
2 maintainers
Metadata
2 maintainers
Release files for celery-beatx 0.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 |
|---|---|---|---|---|
| celery-beatx-0.4.1.tar.gz | 5.2 kB | Without provenance | Details for celery-beatx-0.4.1.tar.gz |
Release files / celery-beatx-0.4.1.tar.gz
| Download URL | celery-beatx-0.4.1.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dfcff5a4e232a5e8accada62a88c48b8f970ef745923b70894972be39245213d
|
|
BLAKE2b-256 checksum How to use checksums |
1577d9d3d043a225ad550298254a01290dcfe01a39802cca0dac39130a1cdc9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for celery-beatx 0.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.
