base-django-project
This is a base project for django work. It contains a handful of django apps that I find useful installed by default. Specifically:
- dj_database_url for extracting a database configuration from a valid DB URI
- django-extensions for running a more powerful shell
- django-fsm for easily creating state machines to track complex processes through the application
- django-simple-history for easily creating history tables for our models in order to improve application auditability
- djangorestframework for easily creating REST APIs
Usage
In your project's settings.py, remove all default configuration generated by django.
Then at the top, simply put:
from base_django_project.webapp.settings import *
# place any custom modifications here
Motivation
When standing up many django projects over a short amount of time, I often find myself duplicating configurations. This project allows any user to quickly drop in their favorite default configuration for settings.py.
Metadata
Release files for django-base-project 0.0.6
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-base-project-0.0.6.tar.gz | 3.9 kB | Without provenance | Details for django-base-project-0.0.6.tar.gz |
Release files / django-base-project-0.0.6.tar.gz
| Download URL | django-base-project-0.0.6.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
119aca787cc8d737846df48ce51405bc9a11131fb1f261656b38f4722b96a864
|
|
BLAKE2b-256 checksum How to use checksums |
dc5033af3dfbeebcd14b12a7953078cbae2bdd4d8b326b777f9c62a90650c1c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.20.1 setuptools/40.9.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.7
|
Security for django-base-project 0.0.6
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.