Re: apache2 + mod_python vhosts conflict

2007-10-20 Thread simonbun
Yes, apache needs that line for virtualhosting to work at all. If it is not provided, apache just picks the first virtualhost it finds and sends requests its way, regardless of Host header. regards, Simon On Oct 20, 11:36 am, Wiley <[EMAIL PROTECTED]> wrote: > Graham, > > I am not to my

Re: apache2 + mod_python vhosts conflict

2007-10-20 Thread Wiley
Graham, I am not to my knowledge using mod_cache...I certainly never set it up, but as far as I can tell, the definitive factor was that single NameVirtualHost * line Please let me know if there's any further testing I can do to help you Wiley On Oct 20, 5:33 pm, Graham Dumpleton <[EMAIL

Re: apache2 + mod_python vhosts conflict

2007-10-20 Thread Graham Dumpleton
Huh. I'll have to do some experimentation now, but I don't quite understand why at the level of mod_python at least, that would make a difference. Are you using any Apache caching system, mod_cache etc? Graham On Oct 20, 7:22 pm, Wiley <[EMAIL PROTECTED]> wrote: > Sorry - further

Re: apache2 + mod_python vhosts conflict

2007-10-20 Thread Wiley
Sorry - further experimentation revealed the following: it was not the python eggs line that made the difference, it was the fact that i had not put the NameVirtualHost * line in my apache2.conf file this is covered in the documentation, thanks again for everyones help On Oct 20, 4:00 pm,

Re: apache2 + mod_python vhosts conflict

2007-10-20 Thread Wiley
Update on this issue, things seemed to work themselves out when I commented out the python eggs line in each of the virtual hosts settings and re-enabled the virtual hosts using the a2ensite in apache... I hope that this might be a help to any other web dev newbies out there :) Thanks to

Re: apache2 + mod_python vhosts conflict

2007-10-17 Thread Graham Dumpleton
On Oct 17, 5:38 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > On 17-Oct-07, at 7:31 AM, Wiley wrote: > > > Kenneth and Bob, the PythonInterpreter thing was the first thing I > > checked (because it was in the official docs) if you notice I have > > different PythonInterpreters already set in

Re: apache2 + mod_python vhosts conflict

2007-10-17 Thread Kenneth Gonsalves
On 17-Oct-07, at 7:31 AM, Wiley wrote: > Kenneth and Bob, the PythonInterpreter thing was the first thing I > checked (because it was in the official docs) if you notice I have > different PythonInterpreters already set in the two virtual hosts in > my original post...am I missing something

Re: apache2 + mod_python vhosts conflict

2007-10-16 Thread Wiley
Graham, You're right, removing the PythonPath line doesn't make any difference, but the two virtual hosts still have the same problem...so I guess the next thing that I will try is seeing if I can display the environment variables via template debugging as you suggest. Thanks again. Wiley >

Re: apache2 + mod_python vhosts conflict

2007-10-16 Thread Graham Dumpleton
On Oct 17, 12:18 pm, Wiley <[EMAIL PROTECTED]> wrote: > > 1. Why are you using: > > > PythonPath "['/usr/lib/python2.5/site-packages/django'] + sys.path" > > > It seems awfully odd that you would be adding django package directory > > to sys.path explicitly. > > A friend of mine set it up this

Re: apache2 + mod_python vhosts conflict

2007-10-16 Thread Wiley
> 1. Why are you using: > > PythonPath "['/usr/lib/python2.5/site-packages/django'] + sys.path" > > It seems awfully odd that you would be adding django package directory > to sys.path explicitly. A friend of mine set it up this way for me, at the time I was only using a single virtual host and

Re: apache2 + mod_python vhosts conflict

2007-10-16 Thread Wiley
Thanks for all who repsonded...Graham, I'll go through your steps very carefully. Kenneth and Bob, the PythonInterpreter thing was the first thing I checked (because it was in the official docs) if you notice I have different PythonInterpreters already set in the two virtual hosts in my original

Re: apache2 + mod_python vhosts conflict

2007-10-16 Thread Kenneth Gonsalves
On 17-Oct-07, at 12:19 AM, Wiley wrote: > apache with only one of these hosts enabled, each works fine, its just > when I run then both at the same time, if i go to mandarinland.com, it > loads a css-free version of chinabites.comdoes anyone know what's > going on here? I attach the apache

Re: apache2 + mod_python vhosts conflict

2007-10-16 Thread Graham Dumpleton
Hmmm, I have been trying to track down what is behind this one for a while. I only do this as someone who knows about mod_python and not as a Django user, so dependent on people trying things and giving feedback. Although someone else suggested PythonInterpreter directive, you are already doing

Re: apache2 + mod_python vhosts conflict

2007-10-16 Thread Bob T.
> from the "Django with mod python" documentation. Should have included the link: http://www.djangoproject.com/documentation/modpython/#multiple-django-installations-on-the-same-apache Bob --~--~-~--~~~---~--~~ You received this message because you are

Re: apache2 + mod_python vhosts conflict

2007-10-16 Thread Bob T.
Wiley, I ran into the same problem. Even though I wasn't running two Django installations in the same VirtualHost caching seemed to be crossing my installations together. Adding the PythonInterpreter directive to the virtual hosts did the trick for me - you won't need the Location directive, just

apache2 + mod_python vhosts conflict

2007-10-16 Thread Wiley
Hi guys, noob question here about setting up apache to serve up 2 different domains, each with a distinct django project. When I run apache with only one of these hosts enabled, each works fine, its just when I run then both at the same time, if i go to mandarinland.com, it loads a css-free