Re: virtualhosts, mod_python, and Django's cache

2007-06-22 Thread Graham Dumpleton
On Jun 22, 10:45 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I will try it out. If you say it is stable, it most likely is. Do > you have a tutorial for getting it configured? If not, I can make one > as I go along. Thanks for all your help. Instructions linked off

Re: virtualhosts, mod_python, and Django's cache

2007-06-22 Thread [EMAIL PROTECTED]
I will try it out. If you say it is stable, it most likely is. Do you have a tutorial for getting it configured? If not, I can make one as I go along. Thanks for all your help. On Jun 22, 5:43 am, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > On Jun 22, 2:40 pm, "Jeremy Dunck" <[EMAIL

Re: virtualhosts, mod_python, and Django's cache

2007-06-22 Thread Graham Dumpleton
On Jun 22, 2:40 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote: > On 6/21/07, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > > > To be honest I haven't ever done anything with Django past the hello > > world examples, > > Graham, thank you for frequently answering questions that fall in the > gap

Re: virtualhosts, mod_python, and Django's cache

2007-06-21 Thread Jeremy Dunck
On 6/21/07, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > To be honest I haven't ever done anything with Django past the hello > world examples, Graham, thank you for frequently answering questions that fall in the gap between Django and mod_python, especially given your more recent work on

Re: virtualhosts, mod_python, and Django's cache

2007-06-21 Thread Graham Dumpleton
On Jun 22, 1:29 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I have restarted apache, and I do not have those directives in my > config files. I'm running out of ideas. What it comes down to is that, according to your traceback, for some reason under atlantaice the:

Re: virtualhosts, mod_python, and Django's cache

2007-06-21 Thread [EMAIL PROTECTED]
I feel so stupid. Somehow the urls file from the other site got copied over the urls file for the site having the problems. On Jun 21, 11:29 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I have restarted apache, and I do not have those directives in my > config files. > > On Jun 21, 9:34

Re: virtualhosts, mod_python, and Django's cache

2007-06-21 Thread [EMAIL PROTECTED]
I have restarted apache, and I do not have those directives in my config files. On Jun 21, 9:34 pm, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > On Jun 22, 10:14 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > Interestingly, I am getting some strange errors when trying to output > >

Re: virtualhosts, mod_python, and Django's cache

2007-06-21 Thread Graham Dumpleton
On Jun 22, 10:14 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Interestingly, I am getting some strange errors when trying to output > the interpreter ID to my error log. Attempting to do so generates an > error in my logs: > > [Thu Jun 21 20:00:23 2007] [error] [client 209.155.235.13] >

Re: virtualhosts, mod_python, and Django's cache

2007-06-21 Thread [EMAIL PROTECTED]
Interestingly, I am getting some strange errors when trying to output the interpreter ID to my error log. Attempting to do so generates an error in my logs: [Thu Jun 21 20:00:23 2007] [error] [client 209.155.235.13] PythonHandler django.core.handlers.modpython: File "/djangosites/

Re: virtualhosts, mod_python, and Django's cache

2007-06-21 Thread Graham Dumpleton
What is in: atlantaice.urls If the details in the error page are to be believed, it would look like one of the URL mapping rules is referencing the other site. I really wish the Django error page would show the interpreter name when using mod_python. I guess another suggestion I should

Re: virtualhosts, mod_python, and Django's cache

2007-06-21 Thread [EMAIL PROTECTED]
prefork On Jun 21, 3:42 pm, Joe <[EMAIL PROTECTED]> wrote: > Are you using Apache Prefork or MPM? > > On Jun 21, 9:39 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > Error can be seen herehttp://beta.atlantaicecompany.com/ > > > AGDWeb is an app in a totally separate project under the

Re: virtualhosts, mod_python, and Django's cache

2007-06-21 Thread Joe
Are you using Apache Prefork or MPM? On Jun 21, 9:39 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Error can be seen herehttp://beta.atlantaicecompany.com/ > > AGDWeb is an app in a totally separate project under the same > PythonPath. It has a separate settings file. > > I am not using

Re: virtualhosts, mod_python, and Django's cache

2007-06-21 Thread [EMAIL PROTECTED]
Error can be seen here http://beta.atlantaicecompany.com/ AGDWeb is an app in a totally separate project under the same PythonPath. It has a separate settings file. I am not using any Django cache, I am referring to some sort of internal caching that mod_python is doing. The settings file

Re: virtualhosts, mod_python, and Django's cache

2007-06-21 Thread Deryck Hodge
On 6/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I have two sites configured just like the configuration below (except > with different ServerName directives and different > DJANGO_SETTINGS_MODULE variables. The trouble is that Django's cache > is confusing the two sites and is saying

Re: virtualhosts, mod_python, and Django's cache

2007-06-21 Thread Graham Dumpleton
On Jun 21, 5:46 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote > On 21-Jun-07, at 12:50 PM, [EMAIL PROTECTED] wrote: > > > cache gets confused. But if I do that, the settings don't work > > correctly and the site won't load. What am I doing wrong? > > you need a pythonInterpretor line in each

Re: virtualhosts, mod_python, and Django's cache

2007-06-21 Thread Kenneth Gonsalves
On 21-Jun-07, at 12:50 PM, [EMAIL PROTECTED] wrote: > cache gets confused. But if I do that, the settings don't work > correctly and the site won't load. What am I doing wrong? you need a pythonInterpretor line in each Location with a different name. It is in the documentation --

virtualhosts, mod_python, and Django's cache

2007-06-21 Thread [EMAIL PROTECTED]
I am having a terrible time getting multiple vhosts running Django up and running. I have two sites configured just like the configuration below (except with different ServerName directives and different DJANGO_SETTINGS_MODULE variables. The trouble is that Django's cache is confusing the two