[Django] #25443: tutorial 1: database setup fails
Django
-------------------------------+------------------------
Reporter: xtrick | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.8
Severity: Normal | Keywords: SECRET_KEY
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------
All went well until the command
$ python manage.py makemigrations polls
This fails with the following message
django.core.exceptions.improperlyconfigured: The SECRET_KEY setting must
not be empty.
I'm sorry if this is trivia(probably is) but i'm new to al this and
stumped.
Others may get the same problem and i will await your response
d_he...@zoho.com
--
Ticket URL: <https://code.djangoproject.com/ticket/25443>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: xtrick | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.8
Severity: Normal | Resolution: worksforme
Keywords: SECRET_KEY | Triage Stage: Unreviewed
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by timgraham):
* status: new => closed
* needs_docs: => 0
* resolution: => worksforme
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
Hi, I doubt this is a bug in the tutorial. Could you please try the ways
listed at TicketClosingReasons/UseSupportChannels to get help first?
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/25443#comment:1>
Django
Reporter: xtrick | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.8
Severity: Normal | Resolution: worksforme
Keywords: SECRET_KEY | Triage Stage: Unreviewed
Easy pickings: 0 | UI/UX: 0
Comment (by xtrick):
no further comment
--
Ticket URL: <https://code.djangoproject.com/ticket/25443#comment:2>
Django
Reporter: xtrick | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.8
Keywords: SECRET_KEY | Triage Stage: Unreviewed
Easy pickings: 0 | UI/UX: 0
Changes (by xtrick):
* status: closed => new
* resolution: worksforme =>
--
Ticket URL: <https://code.djangoproject.com/ticket/25443#comment:3>
Django
Reporter: xtrick | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.8
Keywords: SECRET_KEY | Triage Stage: Unreviewed
Easy pickings: 0 | UI/UX: 0
Comment (by xtrick):
i have checked thoroughly and get the same result. Please Help!
i find mention of a 'secret key' strange in itself given your database is
not a complex one and maybe a clue in itself.
Suggestion: Perhaps the tutorial used to work however some change has
invalidated it.....i'm also surprised to be confronted with this problem.
i'll abandon database use until i get explanation and press on.
--
Ticket URL: <https://code.djangoproject.com/ticket/25443#comment:4>
Django
Reporter: xtrick | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.8
Keywords: SECRET_KEY | Triage Stage: Unreviewed
Easy pickings: 0 | UI/UX: 0
Comment (by collinanderson):
Hi, there should be a SECRECT_KEY listed in your settings.py that was
generated when you ran startproject. Please ask on django-users for ideas
to help diagnose. https://groups.google.com/forum/#!forum/django-users
--
Ticket URL: <https://code.djangoproject.com/ticket/25443#comment:5>
Django
Reporter: xtrick | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.8
Severity: Normal | Resolution: worksforme
Keywords: SECRET_KEY | Triage Stage: Unreviewed
Easy pickings: 0 | UI/UX: 0
Changes (by timgraham):
* status: new => closed
* resolution: => worksforme
--
Ticket URL: <https://code.djangoproject.com/ticket/25443#comment:6>