Fix FIXMEs

diff --git a/lib/Catalyst/Manual/Deployment.pod b/lib/Catalyst/Manual/Deployment.pod
index 745bdcf..fd1aed7 100644 (file)
--- a/lib/Catalyst/Manual/Deployment.pod
+++ b/lib/Catalyst/Manual/Deployment.pod
@@ -60,14 +60,14 @@ and a list of possible deployment servers are shown below:
 
 =head3 Starman
 
-L<Starman> is a high performance pure perl server implementation, which is designed to be used
-directly.
+L<Starman> is a high performance perl server implementation, which is designed to be used
+directly (rather than behind a reverse proxy). It includes HTTP/1.1 support,
+chunked requests and responses, keep-alive xxand pipeline requests.
 
 =head3 Starlet.
 
-XXX - FIXME
-
-+ other options?
+Starlet is a standalone HTTP/1.0 server with keep‐alive support which is suitable for running
+HTTP application servers behind a reverse proxy.
 
 =head3 Twiggy
 

diff --git a/lib/Catalyst/Manual/Deployment/DevelopmentServer.pod b/lib/Catalyst/Manual/Deployment/DevelopmentServer.pod
index 86d22ab..bb537f2 100644 (file)
--- a/lib/Catalyst/Manual/Deployment/DevelopmentServer.pod
+++ b/lib/Catalyst/Manual/Deployment/DevelopmentServer.pod
@@ -1,37 +1,22 @@
-=head2 Development server deployment
+=head1 NAME
 
-The development server is a mini web server written in perl.  If you
-expect a low number of hits or you don't need mod_perl/FastCGI speed,
-you could use the development server as the application server with a
-lightweight proxy web server at the front.
+Catalyst::Manual::DevelopmentServer - Development server deployment
 
-XXX - FIXME Starman!
+The development server is a mini web server written in perl.  However if
+you supply the C<-f> option to the development server, it will load
+the higher performance L<Starman> server, which can be used as an
+application server with a lightweight proxy web server at the front.
 
-=head3 Pros
+=head1 Setup
 
-=head4 Simple
+=head2 Start up the development server
 
-The development server is what you create your code on, so if it works
-here, it should work in production!
-
-=head3 Cons
-
-=head4 Speed
-
-Not as fast as mod_perl or FastCGI. Needs to fork for each request
-that comes in - make sure static files are served by the web server to
-save forking.
-
-=head3 Setup
-
-=head4 Start up the development server
-
-   script/myapp_server.pl -p 8080 -k -f -pidfile=/tmp/myapp.pid
+   script/myapp_server.pl -p 8080 -k -f --pidfile=/tmp/myapp.pid
 
 You will probably want to write an init script to handle stop/starting
 the app using the pid file.
 
-=head4 Configuring Apache
+=head2 Configuring Apache
 
 Make sure mod_proxy is enabled and add:
 
@@ -59,6 +44,11 @@ Make sure mod_proxy is enabled and add:
 You can wrap the above within a VirtualHost container if you want
 different apps served on the same host.
 
+=head2 Other web servers
+
+The proxy configuration above can also be replicated with a different front end server
+or proxy such as varnish, nginx or lighttpd.
+
 =head1 AUTHORS
 
 Catalyst Contributors, see Catalyst.pm

diff --git a/lib/Catalyst/Manual/Deployment/FastCGI.pod b/lib/Catalyst/Manual/Deployment/FastCGI.pod
index 13bbabb..e568198 100644 (file)
--- a/lib/Catalyst/Manual/Deployment/FastCGI.pod
+++ b/lib/Catalyst/Manual/Deployment/FastCGI.pod
@@ -41,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 a lot more server implementations than Apache.
+
 =head2 Cons
 
 You may have to disable mod_deflate.  If you experience page hangs with
@@ -51,8 +55,6 @@ 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