Re: Django + Cherokee Web Server

one thing I can add is that, is that possibly-- your development and production environment may not be identical (going with what Jarek said) and an error is happening on your production environment that gets bypassed in the development machine this has happened to me a few times GD On Nov

Re: Django + Cherokee Web Server

Wiadomość napisana w dniu 2009-11-27, o godz. 17:42, przez hcarvalhoalves: >>> I'm able to configure Cherokee to run my Django project correctly, >>> using the included wizard. The problem is, if an exception is >>> thrown, >>> Cherokee just shows a "Unhandled Exception" page. I figured out

Re: Django + Cherokee Web Server

On Nov 27, 5:56 am, Jarek Zgoda wrote: > Wiadomo¶æ napisana w dniu 2009-11-27, o godz. 00:31, przez   > hcarvalhoalves: > > > I'm able to configure Cherokee to run my Django project correctly, > > using the included wizard. The problem is, if an exception is thrown, > >

Re: Django + Cherokee Web Server

Wiadomość napisana w dniu 2009-11-27, o godz. 00:31, przez hcarvalhoalves: > I'm able to configure Cherokee to run my Django project correctly, > using the included wizard. The problem is, if an exception is thrown, > Cherokee just shows a "Unhandled Exception" page. I figured out that > if I

Django + Cherokee Web Server

I'm able to configure Cherokee to run my Django project correctly, using the included wizard. The problem is, if an exception is thrown, Cherokee just shows a "Unhandled Exception" page. I figured out that if I run fcgi with debug=true, then I get a stacktrace from Flup, but I wanted the default