Opened 17 years ago
Closed 16 years ago
#5614 closed (fixed)
Add createsuperuser management command to auth
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Contrib apps | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Since we can now add custom commands through apps, auth could provide a createsuperuser command
Attachments (8)
Change History (17)
by , 17 years ago
Attachment: | 5614.patch added |
---|
comment:1 by , 17 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
by , 17 years ago
Attachment: | 5614.2.patch added |
---|
comment:3 by , 17 years ago
Triage Stage: | Design decision needed → Ready for checkin |
---|
comment:4 by , 17 years ago
Needs documentation: | set |
---|---|
Triage Stage: | Ready for checkin → Accepted |
This is a nice addition, but it needs docs before we can check it in. Who wants to tackle them?
by , 17 years ago
Attachment: | 5614.3.patch added |
---|
by , 17 years ago
Attachment: | create_superuser.diff added |
---|
Refactored and fixed signals being registered twice in management/init.py
by , 17 years ago
Attachment: | create_superuser.3.diff added |
---|
After seeing the discussion on django-developers made create_superuser.py backwards compatible
comment:5 by , 16 years ago
Needs documentation: | unset |
---|
Hello. I've written up the docs that reflect the changes.
I was able to merge create_superuser.3.diff with the current svn trunk without problems.
comment:6 by , 16 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
programmerq: couple of typos (usermane, filesestem) so check those when you're documenting. Thanks for the update that the merge is still fine. I think we're ready to promote (but feel free to put a fixed doc patch up and perhaps combine with the actual code patch - it's easy then for the committer).
comment:7 by , 16 years ago
I am in fact a terrible speller, but not that bad. I must have been sleepy when I wrote those up. :)
I've fixed the errors, and looked over my changes again. It should be good to go!
comment:8 by , 16 years ago
Be careful generating your patches, programerq: this one was generated in "reverse". Luckily it applies fine with a patch -R
, but it confused the heck out of me first!
comment:9 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I'm not that keen on letting users put the unhashed superuser password on their bash history. My suggestion is that the password is removed as an option, therefore requiring it to be prompted for.