Databases
StackOverflow2013
Postsdbo
POError when running "python manage.py syncdb" locally, but no error when running the same command via Heroku
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POError when running "python manage.py syncdb" locally, but no error when running the same command via Heroku
    text
    copied!<p>I am new to Heroku and Django/Python. I was hoping to find an answer for an issue I'm experiencing. I have been following the Getting Started tutorial in Heroku's Dev Center: <a href="https://devcenter.heroku.com/articles/django" rel="nofollow">https://devcenter.heroku.com/articles/django</a></p> <p>Everything is working properly when running commands and pushing app code to Heroku. For example, when I run the CLI command "heroku run python manage.py syncdb" everything works as expected with no errors. However, when I try to run the same command locally, "python manage.py syncdb", I am getting the following output and error:</p> <pre><code> Scotts-MacBook-Pro:bonavina scottklieberman$ python manage.py syncdb Traceback (most recent call last): File "manage.py", line 10, in &lt;module&gt; ... File "/Library/Python/2.7/site- packages/django/db/backends/postgresql_psycopg2/base.py", line 162, in _cursor raise ImproperlyConfigured("You need to specify NAME in your Django settings file.") django.core.exceptions.ImproperlyConfigured: You need to specify NAME in your Django settings file. </code></pre> <p>I then went back and checked my settings.py file. I am not specifying NAME in the settings file because I am using dj_database_url, as per the Heroku tutorial. I am curious as to why this is failing locally (why it is requiring NAME), whereas it is compiling successfully on Heroku. Any help would be greatly appreciated. Let me know if there is any additional information you need to diagnose the issue.</p> <p>Best, Scott</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload