ansaurus

Question

Answer 1

A:

This seems to be what I have for my application except that I didn't see the NameVirtualHost directive in the http.conf which is required if you want to setup virtual servers. You can try adding NameVirtualHost *:80 before the virtual host definition.

abhaga 2010-01-16 22:14:57

if I do that I've got one more error in the error.log : '[error] VirtualHost *:80 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results'

Martin Trigaux 2010-01-17 06:35:32

Sorry, it should have been `NameVirtualHost *:80`. Updated the answer.

abhaga 2010-01-17 08:16:10

Answer 2

+1 A:

Your django.wsgi file,

WSGIScriptAlias / /srv/http/wsgi-scripts/django.wsgi

is outside of the <Directory> defined by:

<Directory /home/mart/programmation/python/django/martfiles/>

Try adding this to httpd.conf:

<Directory /srv/http/wsgi-scripts/>
    Order allow,deny
    Allow from all
</Directory>

Or, put your django.wsgi file somewhere inside /home/mart/programmation/python/django/martfiles/. That should work.

EDIT: alright, here's an example httpd.conf that is working on a production machine:

<VirtualHost *:80>
    # Admin email, Server Name (domain name) and any aliases
    ServerAdmin [email protected]
    ServerName  www.example.de

    DocumentRoot /home/example/testing/parts/public

    Alias /media /home/example/testing/parts/public/media

    # WSGI Settings
    WSGIDaemonProcess example user=example group=example threads=25
    WSGIProcessGroup example
    WSGIScriptAlias / /home/example/testing/parts/public/django.wsgi

    <Directory "/home/example/testing/parts/public">
        # Allow Apache to follow links
        Options FollowSymLinks
        # Turn on the ability to use .htaccess files
        AllowOverride All
        # Controls who can get stuff from this directory
        Order allow,deny
        Allow from all
    </Directory>
</VirtualHost>

So, if your dhango.wsgi is defined in a place set as accessible by a <Directory> directive, you could also sudo su httpd if that's the user that runs apache on your system, and simply try to read the css files, to see if apache can really access them...

Attila Oláh 2010-01-16 22:54:46

if I put the django.wsgi in martfiles, I've an error 403 access denied ([error] [client 127.0.0.1] (13)Permission denied: access to / denied). if I add the <Directory /srv... it doesn't change anything ([error] [client 127.0.0.1] (13)Permission denied: access to /media/css/style.css denied, referer: http://localhost/).

Martin Trigaux 2010-01-17 06:30:07

Try simply adding `DocumentRoot /home/mart/programmation/python/django/martfiles` inside the `<VirtualHost>` section.

Attila Oláh 2010-01-17 10:48:18

Answer 3

+4 A:

It is not sufficient for just the directory '/home/mart/programmation/python/django/martfiles/media' containing static files to be readable and searchable. The user that Apache runs as must have read and potentially search access, to all parent directories of it back up to root directory. Since home directories on many systems are 'rwx------' this would deny Apache access irrespective of the Deny/Allow directives in Apache configuration.

Suggest you place the Django project and static files outside of your home account somewhere and relax the file system permissions as necessary.

Graham Dumpleton 2010-01-17 04:55:18

that's why I gave the 775 permission with the group devusers containing my apache user (http). Where and which permission ? I'll try it

Martin Trigaux 2010-01-17 06:32:29

I put my medias in /usr/share/django with just root privileges and it works ! Thanks a lot

Martin Trigaux 2010-01-17 10:53:54

+1 for fixing my error. What are the security implications of setting home permissions to 755?

Noah 2010-03-27 20:21:06

ansaurus

tags:

views:

answers:

static file with mod_wsgi in django

related questions