stephenmcd/drum

Unknown command: 'createdb'

naarkhoo opened this issue · 7 comments

naarkhoo commented

I am following the installation manual from github,
After running ./manage.py createdb --noinput I face the following error,

Unknown command: 'createdb' Type 'manage.py help' for usage.

when I run directly, python manage.py syncdb
I get, raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.

any hint? thanks,

stephenmcd commented

What do you think the problem is?

naarkhoo commented

I guess it is a django version issue ! I am not sure
here a similar question is asked ,http://stackoverflow.com/questions/16322479/django-error-the-secret-key-setting-must-not-be-empty-after-upgrading-from-1-4

what do you think ?
Thank you

j7nn7k commented

Try adding a SECRET_KEY = "CHANGE_THIS" to your settings.py file

naarkhoo commented

I changed SECRET_KEY to "CHANGE_THIS" in my setting_local.py file.

stephenmcd commented

The intended suggestion wasn't to literally use the text "CHANGE_THIS", but to do as the text implies, and change it to something else. As the name of the SECRET_KEY setting suggests, this should be secret! So change it to something else, and don't reply here with what you change it to - otherwise it won't be secret anymore. Here are some examples, but please don't use these literally:

SECRET_KEY = "vwR%GE%6eb56bedrtbdrtbdr6yedhd7hj"
SECRET_KEY = "FWE%VS%TSE%GYHFT&NYUFGFUJffw4t554"
SECRET_KEY = "WVDXFbdr5EB^&NM*GFJSWG4vvsffvaw4f"
SECRET_KEY = "W$FV$drrxdfxbftbd6d6R^H^HDHGCGHff"
SECRET_KEY = "F$zsdfgdsfgse5sgt5^%E74567456hdth"
naarkhoo commented

haha ... sure ,I just meant that instead of modifying setting.py I should
have modified setting_local.py
thank you again

On Tue, Aug 6, 2013 at 6:35 PM, Stephen McDonald
notifications@github.comwrote:

The intended suggestion wasn't to literally use the text "CHANGE_THIS",
but to do as the text implies, and change it to something else. As the name
of the SECRET_KEY setting suggests, this should be secret! So change it
to something else, and don't reply here with what you change it to -
otherwise it won't be secret anymore. Here are some example, but please don't
use these literally:

SECRET_KEY = "vwR%GE%6eb56bedrtbdrtbdr6yedhd7hj"
SECRET_KEY = "FWE%VS%TSE%GYHFT&NYUFGFUJ"
SECRET_KEY = "WVDXFbdr5EB^&NM*GFJSWG4vvsffv"
SECRET_KEY = "W$FV$drrxdfxbftbd6d6R^H^HDHGCGH"
SECRET_KEY = "F$zsdfgdsfgse5sgt5^%E74567456hdtfh"

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-22217157
.

stephenmcd commented

Sorry, took your word for it :-)