django-conjure
Conjure your Django admin — read your models, summon a CRUD API + schema.
The Python package behind Conjure. It introspects your
models and serves a generic admin REST API (/conjure/) plus a schema endpoint that a
frontend — or codegen — can read. A matching React dashboard lives in the repo and is in
active development; for the 0.1.x line, point any client at the API below.
Install
pip install django-conjure # session auth (default)
pip install "django-conjure[jwt]" # add JWT auth mode
# settings.py
INSTALLED_APPS += ["conjure"]
CONJURE = {
"AUTH": "session", # or "jwt"
"BRAND": {"name": "My Admin", "accent": "#4f46e5"},
# "USER_PAYLOAD": "myapp.hooks.payload", # custom user model? return any dict
}
# urls.py
urlpatterns += [path("conjure/", include("conjure.urls"))]
python manage.py migrate conjure # AdminAuditLog table (audit log, optional but recommended)
Register a model
Drop an admin_config.py into any app — it's discovered automatically, like admin.py:
from conjure import register, AdminConfig
from myapp.models import Product
@register(Product)
class ProductConfig(AdminConfig):
list_display = ["name", "price", "is_active"]
search_fields = ["name"]
list_filter = ["is_active"]
inlines = [(ProductImage, "product")] # inline child editing
is_readonly = False # True => log/history models, blocks writes
Anything you leave unset is inferred from the model's fields.
What you get
GET /conjure/schema/+…/schema/{app.Model}/— model introspection (codegen + runtime source)GET/POST /conjure/r/{app.Model}/and…/{pk}/— generic CRUD…/autocomplete/,…/bulk/(atomic inline ops),…/{pk}/related/(delete impact)- Django-permission gating (
view/add/change/delete, shared with Django admin),is_staffrequired - Audit log with before/after diff, staff auth (session or JWT), dashboard widget registry
Extend without forking
from conjure import register_widget
@register_widget("signup-trend")
def signup_trend(request):
... # return any JSON; served at /conjure/widgets/signup-trend/
Full docs, the settings reference, the REST contract, and the extension SDK live at docs.conjure.terracelab.co.kr.
Develop
pip install -e ".[dev]"
pytest
ruff check . && ruff format --check .
MIT © Terrace Lab
Metadata
Release files for django-conjure 0.6.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 | |
|---|---|---|---|
| django_conjure-0.6.1.tar.gz | 27.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_conjure-0.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 57.3 kB
Release files / django_conjure-0.6.1.tar.gz
| Download URL | django_conjure-0.6.1.tar.gz |
|---|---|
| Size | 27.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c983af38a22567500b5ca8cdaa2c035027d9cfb5df7ea572dfc957f2d6c0bd72
|
|
BLAKE2b-256 checksum How to use checksums |
7a46dbe8782c6f64a41f3ab2ec48836501053120f610e8deee6279900ec3d177
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 19, 2026.
Transparency logRelease files / django_conjure-0.6.1-py3-none-any.whl
| Download URL | django_conjure-0.6.1-py3-none-any.whl |
|---|---|
| Size | 29.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cd56c50499b9f78b9001ae1b2985a8e7f89bd1457da8340fca994117f4553aa4
|
|
BLAKE2b-256 checksum How to use checksums |
e58aae8f54a24bfab521d95f638cc0183ef0328b33c47302d994809d5f9a2881
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 19, 2026.
Transparency log