[Jifty-commit] jifty branch, master, updated. 1dd765f482c16da93abfe529b82c8797b46d44da
Jifty commits
jifty-commit at lists.jifty.org
Fri Jul 9 12:27:07 EDT 2010
The branch, master has been updated
via 1dd765f482c16da93abfe529b82c8797b46d44da (commit)
from aa381496f5d89490c9f9f828e349a9c3c7af3490 (commit)
Summary of changes:
lib/Jifty/Script/FastCGI.pm | 63 ++++++++++++++++++++++++++++---------------
1 files changed, 41 insertions(+), 22 deletions(-)
- Log -----------------------------------------------------------------
commit 1dd765f482c16da93abfe529b82c8797b46d44da
Author: Thomas Sibley <trs at bestpractical.com>
Date: Fri Jul 9 12:28:12 2010 -0400
Fix lighty config and add more doc for its quirks
diff --git a/lib/Jifty/Script/FastCGI.pm b/lib/Jifty/Script/FastCGI.pm
index 1250a89..874ace9 100755
--- a/lib/Jifty/Script/FastCGI.pm
+++ b/lib/Jifty/Script/FastCGI.pm
@@ -65,6 +65,14 @@ When you're ready to move up to something that can handle the increasing load yo
new world-changing application is generating, you'll need something a bit heavier-duty
than the pure-perl Jifty standalone server. C<FastCGI> is what you're looking for.
+If you have MaxRequests options under FastCGI in your config.yml, or
+commandline option C<--maxrequests=N> assigned, the fastcgi process
+will exit after serving N requests.
+
+=head1 SERVER CONFIGURATIONS
+
+=head2 Apache + mod_fastcgi
+
# These two lines are FastCGI-specific; skip them to run in vanilla CGI mode
AddHandler fastcgi-script fcgi
FastCgiServer /path/to/your/jifty/app/bin/jifty -initial-env JIFTY_COMMAND=fastcgi
@@ -72,28 +80,7 @@ than the pure-perl Jifty standalone server. C<FastCGI> is what you're looking f
DocumentRoot /path/to/your/jifty/app/share/web/templates
ScriptAlias / /path/to/your/jifty/app/bin/jifty/
-For B<lighttpd> (L<http://www.lighttpd.net/>), use this setting:
-
- server.modules = ( "mod_fastcgi" )
- server.document-root = "/path/to/your/jifty/app/share/web/templates"
- fastcgi.server = (
- "" => (
- "your_jifty_app" => (
- "socket" => "/tmp/your_jifty_app.socket",
- "check-local" => "disable",
- "bin-path" => "/path/to/your/jifty/app/bin/jifty",
- "bin-environment" => ( "JIFTY_COMMAND" => "fastcgi" ),
- "min-procs" => 1,
- "max-procs" => 5,
- "max-load-per-proc" => 1,
- "idle-timeout" => 20,
- )
- )
- )
-
-If you have MaxRequests options under FastCGI in your config.yml, or
-commandline option C<--maxrequests=N> assigned, the fastcgi process
-will exit after serving N requests.
+=head2 Apache + mod_fcgid + mod_rewrite
An alternative to Apache mod_fastcgi is to use mod_fcgid with mod_rewrite.
If you use mod_fcgid and mod_rewrite, you can use this in your Apache
@@ -114,6 +101,38 @@ configuration instead:
It may be possible to do this without using mod_rewrite.
+=head2 Lighttpd (L<http://www.lighttpd.net/>)
+
+Version 1.4.23 or newer is recommended, and you may adapt this config:
+
+ server.modules = ( "mod_fastcgi" )
+ server.document-root = "/path/to/your/jifty/app/share/web/templates"
+ fastcgi.server = (
+ "/" => (
+ "your_jifty_app" => (
+ "socket" => "/tmp/your_jifty_app.socket",
+ "check-local" => "disable",
+ "fix-root-scriptname" => "enable",
+ "bin-path" => "/path/to/your/jifty/app/bin/jifty",
+ "bin-environment" => ( "JIFTY_COMMAND" => "fastcgi" ),
+ "min-procs" => 1,
+ "max-procs" => 5,
+ "max-load-per-proc" => 1,
+ "idle-timeout" => 20,
+ )
+ )
+ )
+
+Versions before 1.4.23 will work, but you should read L<Plack::Handler::FCGI's lighttpd
+documentation|http://search.cpan.org/dist/Plack/lib/Plack/Handler/FCGI.pm#lighttpd>
+for how to configure your server.
+
+=head2 More information
+
+Since this uses L<Plack::Handler::FCGI>, you might also want to read
+L<its documentation on webserver
+configurations|http://search.cpan.org/dist/Plack/lib/Plack/Handler/FCGI.pm#WEB_SERVER_CONFIGURATIONS>.
+
=head1 METHODS
=head2 run
-----------------------------------------------------------------------
More information about the Jifty-commit
mailing list