Ccorrection: The names and paths in WSGIScriptAlias and Directory were
inconsistent. The sample config file should read as follows:
========================
httpd/conf.d/python.conf
========================
LoadModule wsgi_module modules/mod_wsgi.so
WSGIDaemonProcess myapp
WSGIProcessGroup %{GLOBAL}
WSGIReloadMechanism Process
Alias /media/ /usr/local/www/media/
<Directory /usr/local/www/media>
Order allow,deny
Allow from all
</Directory>
Alias /site_media/ /usr/local/www/site_media/
<Directory /usr/local/www/site_media>
Order allow,deny
Allow from all
</Directory>
WSGIScriptAlias /myapp /usr/local/django-apps/myapp/apache/django.wsgi
<Directory /usr/local/django-apps/myapp/apache>
Order allow,deny
Allow from all
</Directory>
========================
On May 14, 11:11 am, Vincent <jellygr...@gmail.com> wrote:
> Hi Dan,
>
> Thanks for the tips. I think I've figured out what went wrong.
>
> First up: no, I am not using a virtualenv. I was able to serve the
> site using "./manage.py runserver" albeit a bit slow (due to load
> issues I believe). So the problem ultimately was my mod_wsgi setup.
>
> The fix:
>
> For starters, my httpd.conf file was poorly configured. I had defined
> the wrong user and group under the "WSGIDaemonProcess" directive.
> Ultimately, what I should've done was used the defaults instead of
> defining things. The documentation on the mod_wsgi wiki lead me to
> think otherwise.
>
> So my current config is as follows:
>
> ========================
> httpd/conf.d/python.conf
> ========================
>
> LoadModule wsgi_module modules/mod_wsgi.so
>
> WSGIDaemonProcess myapp
> WSGIProcessGroup %{GLOBAL}
> WSGIReloadMechanism Process
>
> Alias /media/ /usr/local/www/media/
>
> <Directory /usr/local/www/media>
> Order allow,deny
> Allow from all
> </Directory>
>
> Alias /site_media/ /usr/local/www/site_media/
>
> <Directory /usr/local/www/site_media>
> Order allow,deny
> Allow from all
> </Directory>
>
> WSGIScriptAlias /snufkin /usr/local/django-apps/snufkin/apache/
> django.wsgi
>
> <Directory /usr/local/django-apps/myapp/apache>
> Order allow,deny
> Allow from all
> </Directory>
>
> ========================
>
> My second issue was related to the first, I had the wrong user & group
> for my django application. Chown-ing things to apache:apache did the
> trick. I realize that all of these things are most likely trivial
> issues and silly mistakes but my hope is that this post here may act
> as an example should someone else make the same mistakes as I did.
>
> ~Vincent
--~--~---------~--~----~------------~-------~--~----~
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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
