Django Promoter
Give me the damn rights.
Current Features
Promote an existing user
Demote an existing user
Installation
Install using pip install django-promoter
Add 'django_promoter' to your 'INSTALLED_APPS' settings
You can now access the promote and demote commands from your ./manage.py
Usage
Promote a user
$ ./manage.py promote username
Demote a user
$ ./manage.py demote username
Why would I use this ?
The main purpose of this project is to be able to manage rights when you have to use a read-only backend. The ./manage.py createsuperuser isn’t available because you can’t create new users. Using Django Promoter, once the user is inserted in the Django database, you can promote him to a superuser without having to modify the auth database.
License
The MIT License (MIT)
Copyright © 2017 Numberly
Metadata
Release files for django-promoter 1.0.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 | Provenance | |
|---|---|---|---|---|
| django-promoter-1.0.1.tar.gz | 4.2 kB | Without provenance | Details |
Release files / django-promoter-1.0.1.tar.gz
| Download URL | django-promoter-1.0.1.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b6de86b36f0728260706c6a126c651d0550e81eff55d9665bcf46ddf6b485076
|
|
BLAKE2b-256 checksum How to use checksums |
7bc86421390facb2fab019b0d1dfb48f216a9ce058868353e14b32b004d50717
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-promoter 1.0.1
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.