This release is a pre-release and may not be stable for production use.
Django JET
| what | where |
|---|---|
| master tests | |
| dev tests | |
| live demo | http://demo.jet.geex-arts.com/admin/ |
| documentation | http://jet.readthedocs.org/ |
| PyPi | https://pypi.org/project/djet2 |
Why Django JET?
- New fresh look
- Responsive mobile interface
- Useful admin home page
- Minimal template overriding
- Easy integration
- Themes support
- Autocompletion
- Handy controls
Screenshots
Installation
- Download and install latest version of Django JET:
pip install djet2
- Add 'jet' application to the INSTALLED_APPS setting of your Django project settings.py file (note it should be before 'django.contrib.admin'):
INSTALLED_APPS = (
...,
'jet',
'django.contrib.admin',
)
- Make sure
django.template.context_processors.requestcontext processor is enabled in settings.py (Django 1.8+ way):
TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [],
'APP_DIRS': True,
'OPTIONS': {
'context_processors': [
...,
'django.template.context_processors.request',
...,
],
},
},
]
- Add URL-pattern to the urlpatterns of your Django project urls.py file (they are needed for related–lookups and autocompletes):
urlpatterns = patterns(
'',
path('jet/', include('jet.urls', 'jet')), # Django JET URLS
path('admin/', include(admin.site.urls)),
...
)
- Create database tables:
python manage.py migrate jet
- Collect static if you are in production environment:
python manage.py collectstatic
- Clear your browser cache:
- firefox/chrome: Cmd+Shift+R (Ctrl+Shift+R) for hard reload
Dashboard installation
Dashboard is located into a separate application. So after a typical JET installation it won't be active. To enable dashboard application follow these steps:
- Add 'jet.dashboard' application to the INSTALLED_APPS setting of your Django project settings.py file (note it should be before 'jet'):
INSTALLED_APPS = (
...,
'jet.dashboard',
'jet',
'django.contrib.admin',
...,
)
- Add URL-pattern to the urlpatterns of your Django project urls.py file (they are needed for related–lookups and autocompletes):
urlpatterns = patterns(
'',
path('jet/', include('jet.urls', 'jet')), # Django JET URLS
path('jet/dashboard/', include('jet.dashboard.urls', 'jet-dashboard')), # Django JET dashboard URLS
path('admin/', include(admin.site.urls)),
...,
)
- For Google Analytics widgets only install python package:
pip install djet2[google_analytics]
# or
pip install google-api-python-client==1.4.1
- Create database tables:
python manage.py migrate dashboard
- Collect static if you are in production environment:
python manage.py collectstatic
Metadata
Release files for djet2 1.0.9a9
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 |
|---|---|---|---|---|
| djet2-1.0.9a9.tar.gz | 1.8 MB | Without provenance | Details for djet2-1.0.9a9.tar.gz |
Release files / djet2-1.0.9a9.tar.gz
| Download URL | djet2-1.0.9a9.tar.gz |
|---|---|
| Size | 1.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d8c7dd385a7c58c9948790d11b5df22c6e126817d5dd89a97f54f01944e6ac7a
|
|
BLAKE2b-256 checksum How to use checksums |
3a277dd0fdf8ce867a088280872abe4c722a9400b0a05e66adca8ad1e8bd003b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.0 CPython/3.8.0 Darwin/19.4.0
|
Security for djet2 1.0.9a9
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.