Django: Local development vs. Webfaction deployment

Question

Hello,

I've got my Django app all set up like this, as described in the answer.

I develop locally, and then use Fab to deploy this to the server. Locally, I use manage.py runserver, so going into the myapp directory and running that means that things like:

ROOT_URLCONF = 'myapp.urls'

Run just fine. However, when pushing that to production and running it, I get the following

ImportError at /
No module named myapp.urls

Here's the relevant line from my WSGI file:

os.environ['DJANGO_SETTINGS_MODULE'] = 'project.myapp.settings'

Is there a step I've missed? I've got an app with templatetags in it called twitter, and using {% load twitter %} in a template also produces a similar error.

Answer 1

Normally, settings reside in the root of the Django project(rather than inside apps), so references like 'myproject.settings' work just fine (assuming that settings are found inside ~/webapps/<your_app>/myproject/settings.py). If you are using your own directory structure, however, and the settings file is one level deeper, you can add the new location that Python needs to see (i.e. your "myapp" folder) to the import path.

One way of adding folders to the import Path seen by your web application is listed at http://docs.webfaction.com/software/python.html#adding-to-sys-path-from-myproject-wsgi

Django: Local development vs. Webfaction deployment

Follow this question

Related questions