plack::handler::cgi(3pm) [debian man page]

Plack::Handler::CGI(3pm)				User Contributed Perl Documentation				  Plack::Handler::CGI(3pm)

NAME

       Plack::Handler::CGI - CGI handler for Plack

SYNOPSIS

       Want to run PSGI application as a CGI script? Rename .psgi to .cgi and change the shebang line like:

	 #!/usr/bin/env plackup
	 # rest of the file can be the same as other .psgi file

       You can alternatively create a .cgi file that contains something like:

	 #!/usr/bin/perl
	 use Plack::Loader;
	 my $app = Plack::Util::load_psgi("/path/to/app.psgi");
	 Plack::Loader->auto->run($app);

       This will auto-recognize the CGI environment variable to load this class.

       If you really want to explicitly load the CGI handler, you can. For instance you might do this when you want to embed a PSGI application
       server built into CGI-compatible perl-based web server:

	 use Plack::Handler::CGI;
	 Plack::Handler::CGI->new->run($app);

DESCRIPTION

       This is a handler module to run any PSGI application as a CGI script.

UTILITY METHODS

   setup_env()
	 my $env = Plack::Handler::CGI->setup_env();
	 my $env = Plack::Handler::CGI->setup_env(\%override_env);

       Sets up the PSGI environment hash for a CGI request from %ENV> and returns it.  You can can provide a hashref of key/value pairs to
       override the defaults if you would like.

SEE ALSO

       Plack

perl v5.14.2							    2011-06-22						  Plack::Handler::CGI(3pm)

Plack::Runner(3pm)					User Contributed Perl Documentation					Plack::Runner(3pm)

NAME

       Plack::Runner - plackup core

SYNOPSIS

	 # Your bootstrap script
	 use Plack::Runner;
	 my $app = sub { ... };

	 my $runner = Plack::Runner->new;
	 $runner->parse_options(@ARGV);
	 $runner->run($app);

DESCRIPTION

       Plack::Runner is the core of plackup runner script. You can create your own frontend to run your application or framework, munge command
       line options and pass that to "run" method of this class.

       "run" method does exactly the same thing as the plackup script does, but one notable addition is that you can pass a PSGI application code
       reference directly to the method, rather than via ".psgi" file path or with "-e" switch. This would be useful if you want to make an
       installable PSGI application.

       Also, when "-h" or "--help" switch is passed, the usage text is automatically extracted from your own script using Pod::Usage.

NOTES

       Do not directly call this module from your ".psgi", since that makes your PSGI application unnecessarily depend on plackup and won't run
       other backends like Plack::Handler::Apache2 or mod_psgi.

       If you really want to make your ".psgi" runnable as a standalone script, you can do this:

	 my $app = sub { ... };

	 unless (caller) {
	     require Plack::Runner;
	     my $runner = Plack::Runner->new;
	     $runner->parse_options(@ARGV);
	     return $runner->run($app);
	 }

	 return $app;

       WARNING: this section used to recommend "if (__FILE__ eq $0)" but it's known to be broken since Plack 0.9971, since $0 is now always set to
       the .psgi file path even when you run it from plackup.

SEE ALSO

       plackup

perl v5.14.2							    2012-03-21							Plack::Runner(3pm)