Quantcast
Channel: [Catalyst] Debug with FCGI
Browsing all 8 articles
Browse latest View live

[Catalyst] Debug with FCGI

Hi all. I run my cat app as standalone FCGI server+apache2: script/myapp_fastcgi.pl -l /tmp/myapp.socket -n 5 How can i run it in debug mode same as catalyst development server? -- Angel Kolev

View Article



[Catalyst] Debug with FCGI

Try CATALYST_DEBUG=1 script/myapp_fastcgi.pl -l /tmp/myapp.socket -n 5 -- Moritz Onken

View Article

[Catalyst] Debug with FCGI

Prefixing "env CATALYST_DEBUG=1" will work in more shells than just "CATALYST_DEBUG=1". Chris -- Chris Dolan

View Article

[Catalyst] Debug with FCGI

Doesn`t work too. All debug output goes to apache log. I tryed with -e option - same result. -- Angel Kolev

View Article

[Catalyst] Debug with FCGI

Look at Catalyst::Log::Log4perl if you want to send debugging output somewhere different than stderr. I have this in MyApp.pm just before my setup() call: unless ( $ENV{LOG4PERL} &&...

View Article


[Catalyst] Debug with FCGI

2008/8/1 Peter Karman : Isn't debug configurable? __PACKAGE__->setup(qw/ -Debug ........... ); -- Dermot

View Article

[Catalyst] Debug with FCGI

Use the "keep error" option, -e. Regards, Jonathan Rockway -- print just => another => perl => hacker => if $,=$" -- Jonathan Rockway

View Article

[Catalyst] Debug with FCGI

Hmm, I should read the whole post before I reply. Anyway, it should work. -- print just => another => perl => hacker => if $,=$" -- Jonathan Rockway

View Article

Browsing all 8 articles
Browse latest View live




Latest Images