On Thu, 2009-03-26 at 21:58 +, Chris Lamb wrote:
> Malcolm Tredinnick wrote:
>
> > The development server is intended for single user, simple development
> > stuff. It runs as a foreground process and ^C stops it very nicely.
> [..]
> > The goal is, intentionally, to keep the development serv
Malcolm Tredinnick wrote:
> The development server is intended for single user, simple development
> stuff. It runs as a foreground process and ^C stops it very nicely.
[..]
> The goal is, intentionally, to keep the development server simple since
> there are numerous options for more functional s
On Mar 24, 5:04 pm, Graham Dumpleton
wrote:
> Use Apache/mod_wsgi and the documented method of running a WSGI
> application in a specific daemon process in a autoreloading
> development mode. You could even have both the production and
> development instances under same Apache under different hos
On Mar 25, 9:27 am, Dave Benjamin wrote:
> No, I'm trying to run it as a dev server. I use mod_python in
> production. However, I use the dev server in a shared environment so
> that a few other programmers and testers in the office can view the
> site.
>
> In any case, sending a TERM signal to
On Mar 24, 4:13 pm, Malcolm Tredinnick
wrote:
> On Tue, 2009-03-24 at 15:27 -0700, Dave Benjamin wrote:
> > In any case, sending a TERM signal to the parent process should cause
> > the child to die. There is no reasonable justification for the current
> > behavior, IMHO.
>
> There's a lot of jus
On Tue, 2009-03-24 at 15:27 -0700, Dave Benjamin wrote:
> No, I'm trying to run it as a dev server. I use mod_python in
> production. However, I use the dev server in a shared environment so
> that a few other programmers and testers in the office can view the
> site.
>
> In any case, sending a T
No, I'm trying to run it as a dev server. I use mod_python in
production. However, I use the dev server in a shared environment so
that a few other programmers and testers in the office can view the
site.
In any case, sending a TERM signal to the parent process should cause
the child to die. Ther
It looks like you're trying to run the dev server as a real web
server, which is a very bad idea (it's only serves one request at a
time, for starters). As it says here:
http://docs.djangoproject.com/en/dev/ref/django-admin/#runserver-optional-port-number-or-ipaddr-port
"DO NOT USE THIS SERVER
Hello,
I run the Django development server (manage.py runserver) under
Daemontools on Linux. Daemontools is a server management framework
that runs a foreground process as a daemon and automates the tasks of
starting, restarting, signal handling, and logging. I use a run script
that looks like th
