Fix typos

[catagits/Catalyst-Manual.git] / lib / Catalyst / Manual / Deployment / FastCGI.pod

diff --git a/lib/Catalyst/Manual/Deployment/FastCGI.pod b/lib/Catalyst/Manual/Deployment/FastCGI.pod
index 71e3a24..90a6f24 100644 (file)
--- a/lib/Catalyst/Manual/Deployment/FastCGI.pod
+++ b/lib/Catalyst/Manual/Deployment/FastCGI.pod
@@ -4,8 +4,9 @@ Catalyst::Manual::Deployment::FastCGI - Deploying Catalyst with FastCGI
 
 =head1 FastCGI Deployment
 
-FastCGI is a high-performance extension to CGI. It is suitable
-for production environments.
+FastCGI is a high-performance extension to CGI. It is suitable for production
+environments, and is the standard method for deploying Catalyst in shared
+hosting environments.
 
 =head2 Pros
 
@@ -26,9 +27,9 @@ restarting.
 
 =head3 Load-balancing
 
-You can launch your application on multiple backend servers and allow the
-frontend web server to load-balance between all of them.  And of course, if
-one goes down, your app continues to run fine.
+You can launch your application on multiple backend servers and allow
+the frontend web server to perform load-balancing among all of them. And
+of course, if one goes down, your app continues to run.
 
 =head3 Multiple versions of the same app
 
@@ -40,6 +41,10 @@ versions of the same app on a single server.
 Since your app is not running inside of Apache, the faster mpm_worker module
 can be used without worrying about the thread safety of your application.
 
+=head3 Widely supported.
+
+FastCGI is compatible with many server implementations, not just Apache.
+
 =head2 Cons
 
 You may have to disable mod_deflate.  If you experience page hangs with
@@ -50,11 +55,51 @@ mod_fastcgi then remove deflate.load and deflate.conf from mods-enabled/
 With FastCGI, there are more things to monitor and more processes running
 than when using mod_perl.
 
-XXX - FIXME, note not just apache!
+=head2 Standalone FastCGI Server
+
+In server mode the application runs as a standalone server and accepts
+connections from a web server.  The application can be on the same machine as
+the web server, on a remote machine, or even on multiple remote machines.
+Advantages of this method include running the Catalyst application as a
+different user than the web server, and the ability to set up a scalable
+server farm.
+
+To start your application in server mode, install the FCGI::ProcManager
+module and then use the included fastcgi.pl script.
+
+    $ script/myapp_fastcgi.pl -l /tmp/myapp.socket -n 5
+
+Command line options for fastcgi.pl include:
+
+    -d -daemon     Daemonize the server.
+    -p -pidfile    Write a pidfile with the pid of the process manager.
+    -l -listen     Listen on a socket path, hostname:port, or :port.
+    -n -nproc      The number of processes started to handle requests.
+
+See below for the specific web server configurations for using the external
+server.
+
+=head1 WEB SERVERS
+
+Any web server which supports FastCGI should work with Catalyst. Configuration
+recipes for well-known web servers are linked below, and we would welcome
+contributions from people deploying Catalyst on other web servers.
+
+=head2 Apache
+
+L<Catalyst::Manual::Deployment::Apache::FastCGI>
+
+=head2 nginx
+
+L<Catalyst::Manual::Deployment::nginx::FastCGI>
+
+=head2 lighttpd
+
+L<Catalyst::Manual::Deployment::lighttpd::FastCGI>
 
-=head3 More Info
+=head2 Microsoft IIS
 
-L<Catalyst::Engine::FastCGI> - XXX FIXME.
+L<Catalyst::Manual::Deployment::IIS::FastCGI>
 
 =head1 AUTHORS