Server side logging to Chrome console from PHP and Python

Another excellent option, if you'd rather not have to use Chrome dev tools:<p><a href="https://github.com/mgood/flask-debugtoolbar" rel="nofollow">https://github.com/mgood/flask-debugtoolbar</a><p>It will include a fixed positioned panel on your page including a bunch of server-side inspection, including request vars, environ variables, and logs. It works with Flask, and there's a version for Django as well.

<a href="http://getglimpse.com/" rel="nofollow">http://getglimpse.com/</a><p><pre><code> &#62; Glimpse gathers and presents detailed diagnostic information about the &#62; behavior and execution of your web application. &#62; It is used in a similar manner to client side diagnostics and debugging &#62; tools (such as FireBug or Chrome Developer Tools), but instead focuses on &#62; concepts such as server configuration, model binding, url routing, and &#62; execution profiling. </code></pre> Currently implemented for .NET; it has a pretty shiny cross-browser UI which might be useful as a target instead of the Chrome console.

This is fantastic. There have been a few times where I've thought to myself it would be handy to have a view of server-side events in the inspector. Very eager to spend some time later today to get this set up.

Happy to see this here, been using ChromePHP for quite some time now. The <i>only</i> complain I have is how it lacks support for styled logs[1], since it could come handy to apply different colors to different segments of the logs when they start to build up, but otherwise I'm a fan.<p>[1] <a href="https://plus.google.com/+AddyOsmani/posts/TanDFKEN9Kn" rel="nofollow">https://plus.google.com/+AddyOsmani/posts/TanDFKEN9Kn</a>

You may want to mention that the Python library is not thread-safe, since it essentially uses a global variable to store the logged statements until the middleware writes them to the response. Shouldn't be a problem when used with a development server, though.

I've been using this with ChromePhp and it works fantastically well. It sends all of the data as part of the page's header, so you don't have to worry about something hacky like injected console.log calls.

Isn't this a bit like FirePHP (except FirePHP has more browser support) ?

Very useful if you don't want to or can't use xdebug for PHP.

Have been using this for a while debugging PHP. Amazingly useful.

Is there anything like this for Ruby?

I wonder how hard it would be to use the reflect package to make this work in Go?