Go back and get a WSGI hello world program working rather than trying to get Django working first up. Using a hello world program will validate your configuration. See:
http://code.google.com/p/modwsgi/wiki/ConfigurationGuidelines for a simple hello world program to use. Stick it in a file 'hello.wsgi' in your '/var/www/wsgi-scripts' directory and see if you can access it as: http://192.168.201.247/wsgi/hello.wsgi Next time properly describe what you mean by no response to browser. Ie., what exactly do you see in browser, an error page, a blank page and if a blank page then view source for page from browser and see what is actually in it but which may not be getting displayed. Graham On 1 April 2011 02:17, Fred <[email protected]> wrote: > I temporarily disabled selinux; I'll let our sysadmin do the more > robust change once I get everything to work. > > I'm no longer getting an error and the wsgi script runs but I'm not > launching the django view. Nothing in the error log. No response to > the browser. > I suspect I just don't know how to properly edit urls.py for the wsgi > config. Can you please help me with this or provide a URL that > explains it better than the sites I've hit so far? > > This url works with the dev server: > http://192.168.201.247:7777/hw/getlist/homeworks/census > I tried this url with wsgi: > http://192.168.201.247/wsgi/test3.wsgi/hw/getlist/homeworks/census > > my urls.py file (in the same directory as settings.py) looks like > this: > urlpatterns = patterns('', > (r'^hw/getlist/homeworks/([a-z]*)', > 'census.views.get_homeworks_list'), #also tried r'wsgi/ > test3.wsgi/... > (r'^', 'census.views.index'), > ) > > and test3/wsgi looks like this > import sys, os > > #os.chdir('/home/djangodeploy') > sys.path.insert(0, '/home/djangodeploy/HWdj') > import settings > import django.core.management > django.core.management.setup_environ(settings) > utility = django.core.management.ManagementUtility() > command = utility.fetch_command('runserver') > command.validate() > import django.conf > import django.utils > django.utils.translation.activate(django.conf.settings.LANGUAGE_CODE) > import django.core.handlers.wsgi > application = django.core.handlers.wsgi.WSGIHandler() > > > I guess I just don't "see the magic" where the wsgi application > transfers control to django. > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
