[Catalyst] MOD_PERL environment variable

[Alan Humphrey]

It's all magic.  I upgraded to the latest version of mod_perl2 and it all
started to work.  Maybe just recompiling everything was enough.

Thanks for the advice on letting Catalyst auto-detect the Engine.  One less
thing to worry about.

- Alan

-----Original Message-----
From: catalyst-bounces at lists.rawmode.org
[mailto:catalyst-bounces at lists.rawmode.org] On Behalf Of Andy Grundman
Sent: Friday, January 27, 2006 12:00 PM
To: The elegant MVC web framework
Subject: Re: [Catalyst] MOD_PERL environment variable

Alan Humphrey wrote:
> - I'm setting MOD_PERL to mod_perl/2.000001 which is the version of 
> mod_perl on my system.

This should come from mod_perl itself, you shouldn't be setting this
manually.

> - My application uses -Engine=Apache2::MP20 in the use Catalyst line.

You do not ever want to specify the engine manually like this.  Let Catalyst

auto-detect.

I'm not sure what you're trying to do but if you are looking to test an app 
running in mod_perl, the solution is to run your app under Apache and then
set 
the environment variable CATALYST_SERVER="http://server/myapp"

Then any test scripts will run against that remote server using LWP.  Even 
though the test scripts specify URLs of http://localhost, it will be
rewritten 
internally to use the remote server.

-Andy

_______________________________________________
Catalyst mailing list
Catalyst at lists.rawmode.org
http://lists.rawmode.org/mailman/listinfo/catalyst