Apache::PAR::PerlRun - Apache::PerlRun (or ModPerl::PerlRun) subclass which serves PerlRun scripts to clients from within .par files.
A sample configuration (within a web.conf) is below:
Alias /myapp/cgi-run/ ##PARFILE##/ <Location /myapp/cgi-run> Options +ExecCGI SetHandler perl-script PerlHandler Apache::PAR::PerlRun PerlSetVar PARPerlRunPath perlrun/ </Location>
Subclass of Apache::PerlRun (or ModPerl::PerlRun) to serve PerlRun scripts to clients from within .par files. PerlRun scripts should continue to operate as they did before when inside a .par archive.
To use, add Apache::PAR::PerlRun into the Apache configuration, either through an Apache configuration file, or through a web.conf file (discussed in more detail in the Apache::PAR manpage.)
Options +ExecCGI must be turned on in the configuration in order to serve PerlRun scripts.
.par files must be executable by the web server user in order to serve PerlRun scripts.
File modification testing is performed on the script itself. Otherwise modifying the surrounding package should not cause mod_perl to reload the module.
Modules can be loaded from within the .par archive as if they were physically on the filesystem. However, because of the way PAR.pm works, your scripts can also load modules within other .par packages, as well as modules from your @INC.
By default, scripts are served under the script/ directory within a .par archive. This value can be changed using the PARPerlRunPath variable, for instance:
PerlSetVar PARPerlRunPath perlrun/
NOTE: The default location has changed with Apache::PAR 0.20. Previously, the default location for PerlRun scripts was the scripts/ directory. To continue to use the old path in an archive, set the following in a web.conf:
PerlSetVar PARPerlRunPath scripts/
None by default.
Nathan Byrd, <email@example.com>
Copyright 2002 by Nathan Byrd <firstname.lastname@example.org>.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.