catalyst::engine::apache::mp13(3pm) [debian man page]

Catalyst::Engine::Apache::MP13(3pm)			User Contributed Perl Documentation		       Catalyst::Engine::Apache::MP13(3pm)

NAME

       Catalyst::Engine::Apache::MP13 - Catalyst Apache mod_perl 1.3x Engine

SYNOPSIS

	   # Set up your Catalyst app as a mod_perl 1.3x application in httpd.conf
	   <Perl>
	       use lib qw( /var/www/MyApp/lib );
	   </Perl>

	   # Preload your entire application
	   PerlModule MyApp

	   <VirtualHost *>
	       ServerName   myapp.hostname.com
	       DocumentRoot /var/www/MyApp/root

	       <Location />
		   SetHandler	    perl-script
		   PerlHandler	    MyApp
	       </Location>

	       # you can also run your app in any non-root location
	       <Location /some/other/path>
		   SetHandler	   perl-script
		   PerlHandler	   MyApp
	       </Location>

	       # Make sure to let Apache handle your static files
	       # (And remember to remove the Static::Simple plugin in production)
	       <Location /static>
		   SetHandler	   default-handler
	       </Location>
	   </VirtualHost>

DESCRIPTION

       This is the Catalyst engine specialized for Apache mod_perl version 1.3x.

Apache::Registry
       While this method is not recommended, you can also run your Catalyst application via an Apache::Registry script.

       httpd.conf:

	   PerlModule Apache::Registry
	   Alias / /var/www/MyApp/script/myapp_registry.pl/

	   <Directory /var/www/MyApp/script>
	       Options +ExecCGI
	   </Directory>

	   <Location />
	       SetHandler  perl-script
	       PerlHandler Apache::Registry
	   </Location>

       script/myapp_registry.pl (you will need to create this):

	   #!/usr/bin/perl

	   use strict;
	   use warnings;
	   use MyApp;

	   MyApp->handle_request( Apache->request );

METHODS

   ok_constant
OVERLOADED METHODS

       This class overloads some methods from "Catalyst::Engine::Apache".

   $c->engine->finalize_headers
SEE ALSO

       Catalyst, Catalyst::Engine, Catalyst::Engine::Apache.

AUTHORS

       o   Sebastian Riedel <sri@cpan.org>

       o   Christian Hansen <ch@ngmedia.com>

       o   Andy Grundman <andy@hybridized.org>

       o   Tomas Doran <bobtfish@bobtfish.net>

COPYRIGHT AND LICENSE

       This software is copyright (c) 2010 by The "AUTHORS".

       This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

perl v5.10.1							    2010-11-26				       Catalyst::Engine::Apache::MP13(3pm)

DB(3pm) 						User Contributed Perl Documentation						   DB(3pm)

NAME

       Apache::DB - Run the interactive Perl debugger under mod_perl

SYNOPSIS

	<Location /perl>
	 PerlFixupHandler +Apache::DB

	 SetHandler perl-script
	 PerlHandler +Apache::Registry
	 Options +ExecCGI
	</Location>

DESCRIPTION

       Perl ships with a very useful interactive debugger, however, it does not run "out-of-the-box" in the Apache/mod_perl environment.
       Apache::DB makes a few adjustments so the two will cooperate.

FUNCTIONS

       init
	   This function initializes the Perl debugger hooks without actually starting the interactive debugger.  In order to debug a certain
	   piece of code, this function must be called before the code you wish debug is compiled.  For example, if you want to insert debugging
	   symbols into code that is compiled at server startup, but do not care to debug until request time, call this function from a
	   PerlRequire'd file:

	    #where db.pl is simply:
	    # use Apache::DB ();
	    # Apache::DB->init;
	    PerlRequire conf/db.pl

	    #where modules are loaded
	    PerlRequire conf/init.pl

	   If you are using mod_perl 2.0 you will need to use the following as your db.pl:

	     use APR::Pool ();
	     use Apache::DB ();
	     Apache::DB->init();

       handler
	   This function will start the interactive debugger.  It will invoke Apache::DB::init if needed.  Example configuration:

	    <Location /my-handler>
	     PerlFixupHandler Apache::DB
	     SetHandler perl-script
	     PerlHandler My::handler
	    </Location>

SELinux
       Security-enhanced Linux (SELinux) is a mandatory access control system many linux distrobutions are implementing.  This new security scheme
       can assist you with protecting a server, but it doesn't come without its own set of issues.  Debugging applications running on a box with
       SELinux on it takes a couple of extra steps and unfortunately the instructions that follow have only been tested on RedHat/Fedora.

       1) You need to edit/create the file "local.te" and add the following:

       if (httpd_tty_comm) {
	   allow { httpd_t } admin_tty_type:chr_file { ioctl getattr }; }

       2) Reload your security policy.

       3) Run the command "setsebool httpd_tty_comm true".

       You should be aware as you debug applications on a system with SELinux your code may very well be correct, but the system policy is denying
       your actions.

CAVEATS

       -X  The server must be started with the "-X" to use Apache::DB.

       filename/line info
	   The filename of Apache::Registry scripts is not displayed.

SEE ALSO

       perldebug(1)

AUTHOR

       Originally written by Doug MacEachern

       Currently maintained by Frank Wiles <frank@wiles.org>

LICENSE

       This module is distributed under the same terms as Perl itself.

perl v5.14.2							    2008-04-27								   DB(3pm)