runapp(3pm) [debian man page]

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

NAME

       RunApp - A generic module to run web-applications

SYNOPSIS

	use RunApp '-chdir';

	use RunApp;
	use RunApp::Apache;

	my $cmd = shift || 'development';
	my $config = { var => 'value', app_apache => { var_for_apache => 'value'} };
	RunApp->new (app_apache => RunApp::Apache->new
			   (root => catfile (cwd, $_),
			    httpd => '/path/to/httpd'),
		     my_daemon => RunApp::Control::AppControl->new
			   (binary => '/path/to/daemon',
			    args => ['--daemon'],
			    pidfile => '/path/to/daemon.pid',
			   )
			)->$cmd ($config);

DESCRIPTION

       "RunApp" streamlines the process for configuring applications that requires one or more web servers and/or other daemons, during develop-
       ment or deployment.

       It builds the config files required by the services from the $config hash, such as apache's httpd.conf.

OPTIONS

	use RunApp '-chdir';
	use RunApp qw(-chdir ..);

       This will cause the your script to "chdir" to the base directory.  If it's a symbolic link it will be resolved and you will be in the
       directory of where the original script is.  The "lib" directory will be added into @INC, and you can use the modules in that path.

       It also takes an optional relative path if want the script to chdir to somewhere else.

       This makes it possible for symlinking the your runapp script into system's rc.d startup directory.

CONSTRUCTOR

       new (@services)

       @services is actually an hash, with keys being the name of the service, and values being "RunApp::Control" objects.  Use an array instead
       of a hash here to retain the order of dispatching.

       The names are used to pick config from the hash, which will be flatten into top level of the config hash, when running "build" for the each
       service.

METHODS

       $self->development ($conf)

       Runs "build" and "start", and then waits for SIGINT to <stop> the servers.

AUTOLOAD

       All other methods are dispatched to the "RunApp::Control" objects in the order called in CONSTRUCTOR.  Note that this is done with
       RunApp::Control dispatching to the "dispatch" method.

SEE ALSO

       RunApp::Apache, RunApp::Control::AppControl, App::Control

AUTHORS

       Chia-liang Kao <clkao@clkao.org>

       Refactored from works by Leon Brocard <acme@astray.com> and Tom Insam <tinsam@fotango.com>.

COPYRIGHT

       Copyright (C) 2002-5, Fotango Ltd.

       This module is free software; you can redistribute it or modify it under the same terms as Perl itself.

perl v5.8.8							    2008-01-09							       RunApp(3pm)

Apache::XMLRPC::Lite(3pm)				User Contributed Perl Documentation				 Apache::XMLRPC::Lite(3pm)

NAME

       Apache::XMLRPC::Lite - mod_perl-based XML-RPC server with minimum configuration

SYNOPSIS

       httpd.conf (Location), directory-based access
	     <Location /mod_xmlrpc>
	       SetHandler perl-script
	       PerlHandler Apache::XMLRPC::Lite
	       PerlSetVar dispatch_to "/Your/Path/To/Deployed/Modules, Module::Name, Module::method"
	       PerlSetVar options "compress_threshold => 10000"
	     </Location>

       httpd.conf (Files), file-based access
	     <FilesMatch ".xmlrpc$">
	       SetHandler perl-script
	       PerlHandler Apache::XMLRPC::Lite
	       PerlSetVar dispatch_to "/Your/Path/To/Deployed/Modules, Module::Name, Module::method"
	       PerlSetVar options "compress_threshold => 10000"
	     </FilesMatch>

       .htaccess, directory-based access
	     SetHandler perl-script
	     PerlHandler Apache::XMLRPC::Lite
	     PerlSetVar dispatch_to "/Your/Path/To/Deployed/Modules, Module::Name, Module::method"
	     PerlSetVar options "compress_threshold => 10000"

DESCRIPTION

       This Apache Perl module provides the ability to add support for XML-RPC protocol with easy configuration (either in .conf or in .htaccess
       file).  This functionality should give you lightweight option for hosting SOAP services and greatly simplify configuration aspects. This
       module inherites functionality from XMLRPC::Transport::HTTP::Apache component of XMLRPC::Lite module.

CONFIGURATION

       The module can be placed in <Location>, <Directory>, <Files>, <FilesMatch> directives in main server configuration areas or directly in
       .htaccess file.

       All parameters should be quoted and can be separated with commas or spaces for lists ("a, b, c") and with 'wide arrows' and commas for hash
       parameters ("key1 => value1, key2 => value2").

       All options that you can find in XMLRPC::Transport::HTTP::Apache component are available for configuration. Here is the description of most
       important ones.

       dispatch_to (LIST)
	   Specifies path to directory that contains Perl modules you'd like to give access to, or just list of modules (for preloaded modules).

	     PerlSetVar dispatch_to "/Your/Path/To/Deployed/Modules, Module::Name, Module::method"

       options (HASH)
	   Specifies list of options for your module, for example threshold for compression. Future versions will support more options. See
	   XMLRPC::Transport::HTTP documentation for other options.

	     PerlSetVar options "compress_threshold => 10000"

METHODS
/SUBROUTINES
   server
	my $server = Apache::XMLRPC::Lite->server();

       Returns the server object.

       Useful if you need to manipulate the server object from your code.

   handle
       Request handler. Called by apache.

DEPENDENCIES

	XMLRPC::Lite
	mod_perl

SEE ALSO

	XMLRPC::Transport::HTTP::Apache for implementation details,
	XMLRPC::Lite for general information, and
	F<examples/server/mod_xmlrpc.htaccess> for .htaccess example

COPYRIGHT

       Copyright (C) 2000-2001 Paul Kulchenko. All rights reserved.

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

AUTHOR

       Paul Kulchenko (paulclinger@yahoo.com)

perl v5.12.4							    2011-08-18						 Apache::XMLRPC::Lite(3pm)