Am 01.08.2008 um 12:45 schrieb Angel Kolev:
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?
___
List:
On Aug 1, 2008, at 6:28 AM, Moritz Onken wrote:
Try CATALYST_DEBUG=1 script/myapp_fastcgi.pl -l /tmp/myapp.socket -n 5
Prefixing env CATALYST_DEBUG=1 will work in more shells than just
CATALYST_DEBUG=1.
Chris
___
List:
Chris Dolan wrote:
On Aug 1, 2008, at 6:28 AM, Moritz Onken wrote:
Try CATALYST_DEBUG=1 script/myapp_fastcgi.pl -l /tmp/myapp.socket -n 5
Prefixing env CATALYST_DEBUG=1 will work in more shells than just
CATALYST_DEBUG=1.
Chris
___
List:
On 08/01/2008 07:55 AM, Angel Kolev wrote:
Doesn`t work too. All debug output goes to apache log. I tryed with -e
option - same result.
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:
2008/8/1 Peter Karman [EMAIL PROTECTED]:
On 08/01/2008 07:55 AM, Angel Kolev wrote:
Doesn`t work too. All debug output goes to apache log. I tryed with -e
option - same result.
Isn't debug configurable?
__PACKAGE__-setup(qw/
-Debug
* On Fri, Aug 01 2008, Angel Kolev wrote:
Doesn`t work too. All debug output goes to apache log. I tryed with -e
option - same result.
Use the keep error option, -e.
Regards,
Jonathan Rockway
--
print just = another = perl = hacker = if $,=$
___
* On Fri, Aug 01 2008, Jonathan Rockway wrote:
* On Fri, Aug 01 2008, Angel Kolev wrote:
Doesn`t work too. All debug output goes to apache log. I tryed with -e
option - same result.
Use the keep error option, -e.
Hmm, I should read the whole post before I reply. Anyway, it should work.
--
