django-privatesite
==================
Django custom admins.
Don`t reinvent the bicycle and use django.contrib.admin everywhere.
[](https://crate.io/packages/django-privatesite)
BENEFITS of django.contrib.admin
--------------------------------
* Used access control from django.contrib.admin
* Used inlines (generic inlines)
* Used fieldsets
* Used filters
* Used Actions
* Delete Confirmation
* Object history
* Pagination
* Widgets for dates, raw id field
INSTALLATION
------------
Install from pypi, with pip::
pip install django-privatesite
Add ``privatesite`` to ``INSTALLED_APPS``::
INSTALLED_APPS = ("privatesite", ) + ('django.contrib.admin', ...)
Please note, that ``privatesite`` app must be upper
then ``django.contrib.admin app`` in ``INSTALLED_APPS`` list
to overload ``admin/base_site.html`` template
USAGE
------------
from privatesite.admin import CustomAdminSite
site1 = CustomAdminSite(name="site1", app_name="admin")
class MyPrivateZone(CustomAdminSite):
admin_base_template = 'my_zone/base.html'
site2 = MyPrivateZone(name="zone", app_name="admin")
personal = CustomAdminSite(name="personal", app_name="admin")
register models now
from myapp.models import Car, Animal, Human
site1.register(Car)
site2.register(Car)
site2.register(Animal)
site2.register(Human)
personal.register(Human)
in urls.py
urlpatterns += patterns("",
(r'^manage/admin/', include(site1.urls)),
(r'^private/admin/', include(site2.urls)),
(r'^personal/', include(personal.urls)),
)
And go to see, whats happen.
In template you may use
{% url 'site1:myapp_car_changeview' %}
{% url 'site2:myapp_car_change' car_id %}
{% url 'personal:myapp_human_history' human_id %}
If you want to add custom views, use this helper
https://github.com/ionelmc/django-admin-utils
TODO
------
* don`t work with django-admin-tools now (fix in near future)
* write tests
==================
Django custom admins.
Don`t reinvent the bicycle and use django.contrib.admin everywhere.
[](https://crate.io/packages/django-privatesite)
BENEFITS of django.contrib.admin
--------------------------------
* Used access control from django.contrib.admin
* Used inlines (generic inlines)
* Used fieldsets
* Used filters
* Used Actions
* Delete Confirmation
* Object history
* Pagination
* Widgets for dates, raw id field
INSTALLATION
------------
Install from pypi, with pip::
pip install django-privatesite
Add ``privatesite`` to ``INSTALLED_APPS``::
INSTALLED_APPS = ("privatesite", ) + ('django.contrib.admin', ...)
Please note, that ``privatesite`` app must be upper
then ``django.contrib.admin app`` in ``INSTALLED_APPS`` list
to overload ``admin/base_site.html`` template
USAGE
------------
from privatesite.admin import CustomAdminSite
site1 = CustomAdminSite(name="site1", app_name="admin")
class MyPrivateZone(CustomAdminSite):
admin_base_template = 'my_zone/base.html'
site2 = MyPrivateZone(name="zone", app_name="admin")
personal = CustomAdminSite(name="personal", app_name="admin")
register models now
from myapp.models import Car, Animal, Human
site1.register(Car)
site2.register(Car)
site2.register(Animal)
site2.register(Human)
personal.register(Human)
in urls.py
urlpatterns += patterns("",
(r'^manage/admin/', include(site1.urls)),
(r'^private/admin/', include(site2.urls)),
(r'^personal/', include(personal.urls)),
)
And go to see, whats happen.
In template you may use
{% url 'site1:myapp_car_changeview' %}
{% url 'site2:myapp_car_change' car_id %}
{% url 'personal:myapp_human_history' human_id %}
If you want to add custom views, use this helper
https://github.com/ionelmc/django-admin-utils
TODO
------
* don`t work with django-admin-tools now (fix in near future)
* write tests
Metadata
Release files for django-privatesite 0.0.2
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 | |
|---|---|---|---|---|
| django-privatesite-0.0.2.zip | 7.5 kB | Without provenance | Details |
Release files / django-privatesite-0.0.2.zip
| Download URL | django-privatesite-0.0.2.zip |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f50a1a5adc493d34cce799907e60dea44917411218e406ce1fed639137ac2d35
|
|
BLAKE2b-256 checksum How to use checksums |
a11b5fa40f747791499c8026ccb2d88a2e2e61b124f18396e11cee90215fa54e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-privatesite 0.0.2
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.