Ok this is where I'm at. Here is my config file for sites-available.
<VirtualHost *:80>
ServerName www.dev.xxx.us
ServerAlias dev.xxx.us
DocumentRoot /home/dev/djprojects/xxx
<Directory /home/dev/djprojects/xxx>
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Order allow,deny
allow from all
AddHandler mod_python .py
PythonHandler mod_python.publisher
PythonDebug On
</Directory>
<Location "/">
SetHandler python-program
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE mysite.settings
PythonDebug On
PythonPath "['/home/dev/djprojects/xxx'] + sys.path"
</Location>
</VirtualHost>
And I'm getting this error.
Could not import settings 'mysite.settings' (Is it on sys.path? Does
it have syntax errors?): No module named mysite.settings
I understand that mysite.settings is supposed to be the location of my
settings.py, but is it just supposed to be the path of that file?
On Nov 10, 3:32 pm, prem1er <[EMAIL PROTECTED]> wrote:
> Thanks for your replies everyone. I'm looking into it more now and
> will let you know if I have any other questions.
>
> On Nov 10, 8:44 am, Brandon Martin <[EMAIL PROTECTED]> wrote:
>
> > I would just like to note here that when I first installed django with
> > apache and mod_python most of the problem I had was on the apache side
> > with vhosts not django. Each operating system handles apache configs a
> > little different. The guide on django's web site is great for the base
> > information. You just might need to adjust slightly for you OS.
>
> > Steve Holden wrote:
> > > If you read your httpd.conf file you will find at some point there is a
> > > line that includes the configuration data from the sites-enabled
> > > directory. This idea is to be able to switch sites on and off by adding
> > > and removing symbolic links from sites-enabled.
>
> > > Make sure you *always* edit the files in sites-available! If you edit in
> > > site-enabled, some editors will replace the original symbolic link in
> > > sites-enabled with an updated copy of the file itself, and then you will
> > > lose you configuration data if you decide to switch the site off
> > > temporarily ...
>
> > > The configuration commands are exactly the same for a configuration
> > > sub-file: it's exactly as though they had appeared in the main
> > > configuration file at the point of inclusion, so once you understand the
> > > relationship between the sites-available and sites-enabled directories
> > > and your main configuration file you should be good to go.
>
> > > You *could* put the configuration commands in http.conf itself, but this
> > > goes against the Debian/Ubuntu organization scheme, and so probably
> > > wouldn't be helpful long-term.
>
> > > The Django setup instructions aren't bad, but there are so many
> > > different ways that Apache is organized that the authors couldn't hope
> > > to cover them all.
>
> > > regards
> > > Steve
>
> > >> On Nov 9, 10:33 pm, "DULMANDAKH Sukhbaatar" <[EMAIL PROTECTED]>
> > >> wrote:
>
> > >>> Please follow instructions
> > >>> onhttp://docs.djangoproject.com/en/dev/howto/deployment/modpython/to
> > >>> setup django and mod_python.
>
> > >>> And it's interesting that how do you know that mod_python is working?
>
> > >>> --
> > >>> Regards
> > >>> Dulmandakh
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
