Simply use django's build-in server, it restarts automatically (./
manage.py runserver)
On Sep 28, 12:02 pm, ygneo <[EMAIL PROTECTED]> wrote:
> Ok, doesn't mind. There's nothing to do, you have to restart apache if
> settings.py is changed. Is better
> apache2 stop && apache2 start than apache2 r
/Rails who is doing the thing, the server *has* to run
> it. So it's nonsense speaking about mephisto doing that. The deal would
> be in apache taking care of it.
>
> El s?b, 22-09-2007 a las 17:26 +, julian.bash escribi?:
>
> > Thanks a lot for your answers!
>
>
Thanks a lot for your answers!
The even greater thing with funky caching is that the webserver only
has to serve html (if there is a cached version) and doesn't have to
run django. So, django's normal caching is good, but when the server
only has to serve already-generated html-files, the whole t
Hi!
Does anyone have an idea how to implement funky caching with django?
For those who don't know what that is (it's similar to how movabletype
does caching but doesn't prepache everything):
"you redirect 404 errors to a script, which looks at the requested
URL, decides whether it should actuall
4 matches
Mail list logo