django-stack
The backend glue of DjangoStack.
Projects created with npx @django-stack/cli init depend on it.
django_stack.settings.configure()sets Django's settings from environment variables: database, cache, task queue, mail, storage, security, and safe defaults for Django Headless and Django Content Studio.PublishableModel: draft and published content, with preview access.- API defaults: a closed API with a full-access and a read-only key, and rate-limited public forms.
- Preview tokens and signed revalidation requests to the frontend.
/healthzand/readyz, system checks, and the management commandscreate_admin,seed_content,export_content,import_contentandwait_for_db.
# config/settings.py
from pathlib import Path
from django_stack.settings import configure
configure(globals(), base_dir=Path(__file__).resolve().parent.parent)
License
MIT; see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for django-stack 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 | Provenance | Actions |
|---|---|---|---|---|
| django_stack-0.1.0.tar.gz | 99.2 kB | With provenance | Details for django_stack-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_stack-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for django_stack-0.1.0-py3-none-any.whl |
Total release size: 132.9 kB
Release files / django_stack-0.1.0.tar.gz
| Download URL | django_stack-0.1.0.tar.gz |
|---|---|
| Size | 99.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7b5bb1dbf052b9ff8c2af31e71781ff902ef77f2f0e62dd5009007fb26261e37
|
|
BLAKE2b-256 checksum How to use checksums |
64a5acb5b795cda61ab39f466c6e9f3dcb32872b7029efbdba5097d508edcd02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 5, 2026.
Transparency logRelease files / django_stack-0.1.0-py3-none-any.whl
| Download URL | django_stack-0.1.0-py3-none-any.whl |
|---|---|
| Size | 33.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5cee88e5b77e72ad6c8052e83b680cb4d3d33af72cb8c10803174861ed619fd3
|
|
BLAKE2b-256 checksum How to use checksums |
d0999b8782566050e3ac77635d29b87240579b2f42aa96f69b4892558054e7e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 5, 2026.
Transparency logSecurity for django-stack 0.1.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for django_stack-0.1.0.tar.gz
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 Nov 5, 2026.
Transparency logA 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.
