On Aug 24, 6:33 pm, "Timothy Kanters" <[EMAIL PROTECTED]> wrote:
> > Some may suggest that you set maximum number of requests per Apache
> > child to 1. This however is a rather brute force approach and if doing
> > that you may as well use CGI.
>
> Aye, but for my development server that is quite
> Some may suggest that you set maximum number of requests per Apache
> child to 1. This however is a rather brute force approach and if doing
> that you may as well use CGI.
Aye, but for my development server that is quite ok, easier to do than
restarting apache after every change :)
Thanks for
That clarifies much. Thank you.
On 23 Sie, 13:52, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
> On Aug 23, 9:17 pm, eXt <[EMAIL PROTECTED]> wrote:
>
> > Yes very familiar. I also experienced this kind of strange behaviour
> > from my app behind apache. Two things to do:
> > 1. restart apache afte
On Aug 23, 9:17 pm, eXt <[EMAIL PROTECTED]> wrote:
> Yes very familiar. I also experienced this kind of strange behaviour
> from my app behind apache. Two things to do:
> 1. restart apache after changes to your files (there is a directive to
> autoreload described somewhere in the docs - useful fo
Yes very familiar. I also experienced this kind of strange behaviour
from my app behind apache. Two things to do:
1. restart apache after changes to your files (there is a directive to
autoreload described somewhere in the docs - useful for development)
2. if it doesn't help you then manually remo
Hey,
I've got django installed on a webserver with apache / mod_python /
mysql (on debian). I've got the latest svn version of django
installed.
I'm runinng through the tutorials but I'm getting some strange results.
Tutorial 1 went fine, so I've got the Poll / Choice models and I can
work with
6 matches
Mail list logo
