in reply to Re: mod_perl 2 and CGI::Carp fatalstobrowser
in thread mod_perl 2 and CGI::Carp fatalstobrowser

yup, the writing the errors to the apache errorlog is a good alternative except when the developer isn't allowed read access to the errorlog (apache is administered by another group).

Jason L. Froebe

Team Sybase member

No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1

  • Comment on Re^2: mod_perl 2 and CGI::Carp fatalstobrowser

Replies are listed 'Best First'.
Re^3: mod_perl 2 and CGI::Carp fatalstobrowser
by BerntB (Deacon) on Sep 04, 2006 at 08:42 UTC
    Uh, you do web development work without a local install on your own desktop/laptop of the database, Apache and the rest of the neccesary environment?

    Sounds... painful. Isn't it hard to e.g. write tests if you can't separate out everything cleanly? (Or is the DB helvetes(*) large and just too much to keep locally?)

    (*) I saw people discussing in the CB that we shouldn't offend people with four letter words. If any over-sensitive people know Swedish, please let me know and I'll Google for the relevant expressions in some other language. :-)