django-celery-results-redis
A Celery result backend for Django that stores task, group and chord results in Redis, with the behaviour, models, manager API and admin of django-celery-results.
- Drop-in backend semantics:
result_extended,result_expires, groups, chords,task_track_started, retries. - Django admin identical to django-celery-results: list filters, facets, search, sorting, date hierarchy, change form, delete and bulk actions, history.
- Three storage drivers:
raw,indexed(own secondary indexes) andredis_om(RediSearch), plus an optional RediSearch index for the admin search. - Redis Sentinel supported through a
sentinel://URL. - Workers never touch the SQL database.
Requirements
Python 3.10+, Django 5.2+, Celery 5.5+, Redis 7.0+ (Redis 8 or Redis Stack for
the redis_om driver).
Installation
$ pip install django-celery-results-redis
$ pip install "django-celery-results-redis[redis-om]" # for the redis_om driver
INSTALLED_APPS = [
...,
"django_celery_results_redis",
]
DJANGO_CELERY_RESULTS_REDIS = {
"DRIVER": "indexed",
"URL": "redis://localhost:6379/0",
}
CELERY_RESULT_BACKEND = "django-redis-db"
CELERY_RESULT_EXTENDED = True
$ python manage.py migrate django_celery_results_redis
The migration creates no table; it registers the models so that content types and admin permissions exist.
Optional JSON status views:
urlpatterns = [
path("celery/", include("django_celery_results_redis.urls")),
]
Migrating from django-celery-results
Both packages can be installed side by side. Point CELERY_RESULT_BACKEND at
django-redis-db, copy the rows you want to keep with
manage.py celery_results_redis_import, and restart the workers; see the
migration guide.
Documentation
Full documentation: https://ctolon.github.io/django-celery-results-redis/
- Installation
- Migrating from django-celery-results
- Examples
- Settings and system checks
- Storage drivers
- Performance
- Parity with django-celery-results
Contributing
$ uv sync
$ docker compose up -d --wait
$ uv run pytest -n auto
See the contributing guide.
License
BSD 3-Clause, the same license as Django, Celery and django-celery-results. Parts of the backend, models, managers and views are derived from django-celery-results; the derived files and their copyright holders are listed in LICENSE.
Metadata
Release files for django-celery-results-redis 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_celery_results_redis-0.1.0.tar.gz | 120.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_celery_results_redis-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 190.4 kB
Release files / django_celery_results_redis-0.1.0.tar.gz
| Download URL | django_celery_results_redis-0.1.0.tar.gz |
|---|---|
| Size | 120.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a8597971e81eb9dd41d3bf6fac9174e13fdc3fe38d19d86de1bfae1c6cd3d4c0
|
|
BLAKE2b-256 checksum How to use checksums |
961399f826076cfccb62cf44cbf369128ba4b3ecd6253b0e9acae1788f84c17f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 23, 2026.
Transparency logRelease files / django_celery_results_redis-0.1.0-py3-none-any.whl
| Download URL | django_celery_results_redis-0.1.0-py3-none-any.whl |
|---|---|
| Size | 69.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8198ede944d7755f6edc5023aae799ab853516bcff1006ee9d6636b6d22ed3c8
|
|
BLAKE2b-256 checksum How to use checksums |
0d523be8092f1d8ff9acc2a238d810580e1d9f83277cc3a0a269cce244ca592e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 23, 2026.
Transparency log