On Mon, May 10, 2010 at 9:39 AM, Ivan Uemlianin <i...@llaisdy.com> wrote:
> Dear Kenneth
>
> Thanks for your suggestion.
>
> I tried
>
> $ chmod -R a+x mysite
>
> (where mysite is the django site directory)
>
> and stopped and started apache, but no effect.
>
> I'm finding nginx a lot easier to work with than apache, especially
> CentOS' apache. My plan now is to get rid of apache altogether and
> have nginx talk to django directly via fastcgi (e.g., [1]) (will also
> give me an excuse to try out git instead of svn). If you don't hear
> back from me in a day or two, it worked.
>
> With thanks and best wishes
>
> Ivan
>
> [1] http://code.djangoproject.com/wiki/ServerArrangements#nginx
>
>
Good luck with setting up your pure nginx configuration. Your apache
configuration did not work because you had not granted apache access
to the required on disk folders.
You didn't mention this in your configuration, but you must allow
access to your DocumentRoot in your vhost:
<VirtualHost *:80>
ServerName foo
DocumentRoot /path/to/foo/htdocs
<Directory /path/to/foo/htdocs>
Order allow,deny
Allow from all
</Directory>
WSGIScriptAlias /app/ /path/to/foo/run/app.wsgi
</VirtualHost>
Cheers
Tom
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@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.
