Another way would be to set up a receiver for a signal, emit a message via
the logging module, configure LOGGING to log those messages to stderr.
Question for others: Is there a good document on what signals django sends?
Since I have it available, here's how you would adjust the LOGGING setting
On Wed, Dec 5, 2012 at 6:44 AM, Gontran Magnat wrote:
> So you mean there is no way to get this kind of log with fastcgi mode:
>
There is always a way, it just doesn't do it by default. If you
require this output even in fastcgi mode than you can create a trivial
middleware to print this output t
So you mean there is no way to get this kind of log with fastcgi mode:
Validating models...
0 errors found
Django version 1.4.2, using settings 'finderauto_dj.settings'
Development server is running at http://127.0.0.1:8080/
Quit the server with CONTROL-C.
[04/Dec/2012 23:10:47] "GET /admin/ HTTP
I believe you only get the per-request logs when you're running the
development server (runserver). When you're running in fastcgi mode (and
its been a while since I have), you'll only get entries in outlog and
errlog if you actually send stuff to stdout and stderr yourself. And THAT
will requi
Hello,
I'm running a django app on lighttpd with fastcgi.
For debugging matters I would need the output logs that usually are
displayed on the console.
Because I run my application in a daemonize mode I tried to use the outlog
and errlog options but it did not work.
Here is the command I run:
5 matches
Mail list logo
