Django Celery Beat Endpoint
A library that provides basic status and tasks endpoint for Django Celery Beat.
Inspired by vintasoftware/django-celerybeat-status
Requirements
Install
pip install django-celery-beat-endpoint
✨🍰✨
Or you can use pip install git+https://github.com/ZhaoQi99/django-celery-beat-endpoint.git install latest version.
Usage
Quick start
Just edit proj/celery.py, and replace Celery with AwareCelery
from django_celery_beat_endpoint.celery import AwareCelery
app = AwareCelery("proj")
# Or
from django_celery_beat_endpoint.celery import AwareCelery as Celery
app = Celery("proj")
Settings
You can easily configure lower case setting by referring Configuration and defaults.
Or you can use a CELERY_ prefix uppercase setting and loading configuration from the Django settings module.
- beat_port / CELERY_BEAT_PORT - port for http server
Default: 8005
- http_server / CELERY_BEAT_HTTP_SERVER - HTTP server class
Default: "django_celery_beat_endpoint.backends:HTTPServer"
API
- /status
{
"status": "OK"
}
- /tasks
[
{
"name": "proj.tasks.add",
"task": "",
"args": "()",
"last_run_at": "2024-06-18 20:00:00",
"schedule": "<freq: 1.00 minute>",
"kwargs": "{}",
"is_due": true,
"next_execution": "2024-06-18 20:00:10"
}
]
Roadmap
- Support more server backends, such as Tornado, Flask and FastAPI.
License
GNU General Public License v3.0
Author
- Qi Zhao(zhaoqi99@outlook.com)
Metadata
Release files for django-celery-beat-endpoint 0.1.3
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_celery_beat_endpoint-0.1.3.tar.gz | 17.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_celery_beat_endpoint-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.2 kB
Release files / django_celery_beat_endpoint-0.1.3.tar.gz
| Download URL | django_celery_beat_endpoint-0.1.3.tar.gz |
|---|---|
| Size | 17.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1bc4322cca1b41e66561692d8834d8bc93bc991b38a5776c8c6ca9e9c8c7ddd2
|
|
BLAKE2b-256 checksum How to use checksums |
a0b81421e08a81e8c7c683c49199db6ce317ff81fa0137ba4928012a15958d84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.21 {"installer":{"name":"uv","version":"0.9.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / django_celery_beat_endpoint-0.1.3-py3-none-any.whl
| Download URL | django_celery_beat_endpoint-0.1.3-py3-none-any.whl |
|---|---|
| Size | 18.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7cba8602171a99dd3f0a0d05614bf64cbb641c257a8fa2c523926f4973cc9659
|
|
BLAKE2b-256 checksum How to use checksums |
72a1be5947d7a8b8b3dba1d66b132bc4673191b523e249f50882494b6b9fb9c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.21 {"installer":{"name":"uv","version":"0.9.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for django-celery-beat-endpoint 0.1.3
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.