guys, fixed it. apparently the issue was having it in /home/chris/ i moved it to var/www/ and now it's working :) i knew it'd be something as simple as that.
On Sep 9, 1:12 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Tue, Sep 9, 2008 at 11:53 AM, <[EMAIL PROTECTED]> wrote: > > > i'm really at a loss. > > > mod_python and django are both installed under python2.4. SELinux is > > disabled. the standard permissions for the django_projects folder is > > 775. everything validates. i can run python at the command line and > > import the settings, etc. > > What about the permissions on the directory containing django_projects? And > (though you asked this in a different note I can't find at the moment) > moving the code to someplace you are sure Apache has read access to may fix > the problem. If it does, then you know that the problem is Apache's ability > to read the files, for whatever mysterious reason. > > (Personally I put my 'production' code level someplace outside my home > directory. That way I don't break the 'real' server by anything I do in my > home directory, and updates to what Apache is running have to be done by me > with full consciousness that I'm updating the production site. So moving > what Apache runs out of your home directory may not be a bad idea in > general, but that's just how I operate.) > > Karen --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
