ansaurus

Question

Django Deploy trouble

Answer 1

A:

My guess is that your path is actually /opt/workshop/workshop/

So in your wsgi file you should have sys.path.append('/opt/workshop/workshop') And if that's not the case, than workshop.settings should be settings instead.

[edit] The way I see it you have 3 options.

Add opt to sys.path so workshop.urls and such work (bad idea imho since opt could include anything`
Remove workshop from all paths
Move the Python code to a workshop (or something else) directory (make sure it contains an __init__.py)

Personally I would take option 3 since otherwise you'll be mixing your python apps with the rest (media, templates, etc...)

WoLpH 2010-04-21 20:56:08

It can't be /opt/workshop/workshop/ or apache would not be outputting logs into the directory he did an `ls` on.

Jack M. 2010-04-21 21:04:27

I think it's the latter. If his /opt/workshop is on the system path, then the /opt/workshop/workshop directory structure would actually work - at least the settings module would be at workshop.settings anyway.

Chris Lawlor 2010-04-21 21:04:34

That is true Jack M. In that case it's probably the settings that's killing it now :)

WoLpH 2010-04-21 21:07:56

Would the fact that `vehicles.__init__.py` is empty have any bearing on it?

Jack M. 2010-04-21 21:08:57

You'll have to probably also change your vehicles module from 'workshop.vehicles' to just 'vehicles' in your INSTALLED_APPS setting as well.

Chris Lawlor 2010-04-21 21:09:17

__init__.py can be empty - the presence of an __init__.py file just tells python that the directory is a python module. It can optionally contain module-level functions and docstrings just like any python file, but it doesn't have to.

Chris Lawlor 2010-04-21 21:10:49

all my app is in /opt/workshop, example: /opt/workshop/settings.py, so the path /opt/workshop/workshop doesn't exists... i tried put 'settings' only and didnt work either, still getting 500 error

i-Malignus 2010-04-21 21:12:08

still cant get it running, it seems it cant import the installed app vehicles...

i-Malignus 2010-04-22 14:23:31

My error changed to: ImportError: No module named vehicles

i-Malignus 2010-04-22 14:27:30

That might be an improvement - if this changed after changing DJANGO_SETTINGS_MODULE to simply `'settings'`, now change the vehicles module in INSTALLED_APPS from `'workshop.vehicles'` to `'vehicles'`

Chris Lawlor 2010-04-22 20:52:32

Don't forget to restart apache if you make any changes to your .wsgi or settings files.

Chris Lawlor 2010-04-22 20:57:01

Answer 2

+2 A:

Try adding both the directory containing the settings.py file and its parent directory to sys.path. Better still, read 'http://blog.dscpl.com.au/2010/03/improved-wsgi-script-for-use-with.html' and use the WSGI script file contents described right at the end (after you have read the post as to why it is an issue). :-)

UPDATE 1

In another comment you post your permissions as 'drw-r--r-- 2 root root vehicles'.

The 'x' bit isn't set on the directory for anyone. This will cause anything to fail which needs to be able to generate a directory listing to see what is in the directory.

In other words, look at all your directory permissions and fix things up to be 'drwxr-xr-x'.

Also, because you have made directories owned by root, if your application needs to write to any directories it will not be able to.

In summary, directory/file permissions issues.

Graham Dumpleton 2010-04-21 23:27:11

i-Malignus 2010-04-23 15:43:39

man, this saved my day. totally different problem though.THANKS!

Ulf 2010-07-29 13:53:22

ansaurus

tags:

views:

answers:

Django Deploy trouble

related questions