I'm not clear about the python path to myproject.settings. I've created myproject and have the lines in django.wsgi:

os.environ['DJANGO_SETTINGS_MODULE'] = 'myproject.settings'
sys.path.insert(0, '/home/me/webapps/(appname)/')

But the error_log shows that myproject.settings can't be found. The path is wrong? I'm following from this and the installing wsgi posts. Apache and wsgi have been installed successfully. Any idea what I'm missing on the PYTHONPATH? Django is installed under /home/me/webapps/(appname)/



Thanks,

tlopez

I've got three django applications, all of which I'm trying to move over to using mod_wsgi. The first django application I installed came with an 'apache' directory, the next two got 'apache2' directories, with much less in them. I installed mod_wsgi in the first application and switched it over, apparently without problems. I went to install mod_wsgi in the other two applications, and saw there's no apxs to build against; if I leave that line out of the mod_wsgi configure, it finds the apxs in my first django application's apache installation (but seems to make just fine).

My question is, are my second two apache installations subordinate to the first? Can I safely point them at the mod_wsgi module in the first django/apache installation? Do I need to install mod_wsgi once for each django application I've got running?

Thanks,
Eric

Okay, one more question. None of the django apps I've got going under mod_wsgi are able to reach the admin media. My other media is served from a different domain, so that works fine, but the admin media comes like this:

Alias /admedia "/home/username/webapps/djangomedia/admin"

Where that is a symlink to the actual media files in my django installation. Visiting anything under /admedia results in a server error, though I can't find that error in any error logs. According to this page:

http://code.djangoproject.com/wiki/djan … d_mod_wsgi

I should be able to get admin media served with a configuration like this:

Alias /media/ "<PATH TO YOUR DJANGO SRC>/trunk/django/contrib/admin/media/"
<Directory "<PATH TO YOUR DJANGO SRC>/trunk/django/contrib/admin/media">
Order allow,deny
Options Indexes
Allow from all
IndexOptions FancyIndexing
</Directory>

I don't know if that would solve my problem, because when I try to put something like that in, it tells me that Order is an unrecognized command. That's weird, because mod_access should be part of the base Apache configuration, and anyway I don't seem to have mod_access anywhere to load it.

Is my problem not what I think it is? What's going on here?

Thanks,
Eric

Django/mod_wsgi has been added to the control panel.

That's what I'm doing (three medium-sized sites under one Apache/mod_wsgi/worker MPM installation) and it's working just fine for me. It might be me, but there seems to be a noticeable lag now in establishing the initial connection, though the response then comes through as quickly as ever.

eric wrote:

That's what I'm doing (three medium-sized sites under one Apache/mod_wsgi/worker MPM installation) and it's working just fine for me. It might be me, but there seems to be a noticeable lag now in establishing the initial connection, though the response then comes through as quickly as ever.

i noticed the same thing on my setup  It feels like a half to full-second lag on the initial request. It makes me wonder if I should explore another implementation.  mod_python is by far the easiest to set up and use, but I was constantly blowing past my memory allotment.

so, following along, I get this error when I try and start apache:

syntax error on line 16 of. ..httpd.conf:
Invalid command 'Order', perhaps misspelled or defined by a module not included in the server configuration


This is what I have:


<Directory /home/msainson/webapps/results/>
    Order allow,deny
    Allow from all
</Directory>


Line 16 is the line that starts with (the correctly spelled) Order.

Here is my configuration for running multiple proyects with the same django/mod_wsgi instance:

# optimization
StartServers 1
MinSpareServers 1
MaxSpareServers 5
MaxClients 5
MaxRequestsPerChild 300
ServerLimit 4
Keepalive off
HostnameLookups Off

NameVirtualHost 127.0.0.1:7268
ServerAdmin mail@mail.com

<VirtualHost 127.0.0.1:7268>
    WSGIScriptAlias / /path/to/site1.wsgi
    ServerName site1.com
    ServerAlias www.site1com
    ErrorLog "logs/site1_errors_log"
</VirtualHost>

<VirtualHost 127.0.0.1:7268>
    WSGIScriptAlias / /path/to/site2.wsgi
    ServerName site2.com
    ServerAlias *.site2.com
    ErrorLog "logs/site2_errors_log"
</VirtualHost>

-------
webfaction username: movaxes

Last edited by pablo (2008-08-01 04:29:58)

I found that:

      svn export http://svn.djangoproject.com/svn/django/trunk/django/

did not work but that

     svn export http://code.djangoproject.com/svn/django/trunk/django/

did. I assume there has been a chnage at djangoproject.com

Peter

Hi Mike -

If you've installed a Django/mod_wsgi app via our control panel, then you do not need to install a separate mod_wsgi application.

Yes, you can delete myproject* from you Django app and use your own project. You might want to keep myproject.wsgi around for reference, since you'll need to have a wsgi script for your new Django project.

Hope that helps!

Regards,

Sean F, WebFaction Support
--
WebFaction - Agile hosting for everyone
http://webfaction.com - http://twitter.com/webfaction

airjaw wrote:

Is there an updated installation guide for django/mod_wsgi/apache2 ?

I get this error : syntax error on line 16 of. ..httpd.conf:
Invalid command 'Order', perhaps misspelled or defined by a module not included in the server configuration

I've also followed this: In Apache 2.0 Order is a mod_access directive, do you have a "LoadModule mod_access modules/mod_access.so" line in your httpd.conf? If not, add one and restart Apache.

and now get this: /home/airjaw/webapps/django/apache2/modules/mod_access.so: cannot open shared object file: No such file or directory 

a look into my /modules directory and there is no mod_access.so

Any help would be appreciated. Thanks.

Edit:: just found this from another post::

"Ah - N00b mistake, Doh - mod_access is now "LoadModule authz_host_module modules/mod_authz_host.so" in Apache 2.2.  Hope that helps someone else.  Still getting 500 Internal Server error though."

Ok, so you found the mod_authz_host stuff

The traceback for your current 500 error is in ~/webapps/django/apache2/logs/error_log - basically, you need to fix your sys.path in your WSGI script so that Python can find all of your libraries (or install the libraries if they don't exist).