On Wed, Jan 20, 2010 at 4:34 PM, James <[email protected]> wrote:
> I have two questions. Firstly, when the configuration setting "debug" > is false, server error stack traces are dumped (with lots of great > information, BTW) into stderr. Is there a way to customise this and > send it to a separately configured Python logging target? > Actually, stack traces are emailed when debug is false. The destination is defined in your .ini file. Check out email_to, error_email_from, and smtp_server to get them. > Secondly, is there a way to produce an Apache-style access log - it > doesn't necessarily have to be NCSA formatted, just a way to see which > URLs are being hit and response times if possible. > For this, the most common configuration is to deploy TurboGears behind Apache, so you can just use its own logging facilities. Outside of that, you would need to look at Python's logging facilities for dumping custom logs, and possibly Paster's facilities for logging and maybe even writing up a custom middleware (to track how long requests take). I'd stick with deployment behind Apache, personally. Much easier. -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected]--
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
