> Ok, so i've written my Django app on computer A with the dev server,
> and have pushed it to server B, running apache (implemented with
> mod_wsgi). The server also has Django installed, but cannot find the
> settings for some reason.
It's probably either a pythonpath or permissions problem.
> what i've gathered is that because i've
> never run the 'makeproject' command that the Django instance on the
> server simply doesn't know the project exists.
And you're plain wrong.
There's nothing like a "Django instance" to starts with, all you have
is a django package somewhere in your pythonpath, and a "django
project" (ie : your app) package somewhere else that imports stuff
from the django package. The "startproject" command only creates a
"stub" project package, period.
> the project on the
> server has a slightly different path than it did on the original
> computer, however i have changed settings.py to reflect that.
> Now, my assumption is that the fix will be to go into the django files
> and edit whatever file notes what projects exist,
Once again : django is nothing else than a Python package so it don't
"do" anything by itself, and is *totally* ignorant of your project.
NB : if you don't know what's a Python package is, please read
Python's official tutorial, with special attention to the part about
modules, packages and the pythonpath).
> however i dont even
> know where to start looking. any help?
Read your apache's error log, you should get more information about
why your settings file is not found.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment