X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FDeployment%2FDevelopmentServer.pod;h=ca4f32a4199b3e87315acc44fc7bb3402b73986f;hp=44472068ec4b23cafd2f545c9f04db4e32ebddd8;hb=7ce05098c9b1df9078e709e5a724e821a3b3b00d;hpb=c34dd09beab3dd7007945887a88258a49a0d0eaf

diff --git a/lib/Catalyst/Manual/Deployment/DevelopmentServer.pod b/lib/Catalyst/Manual/Deployment/DevelopmentServer.pod
index 4447206..ca4f32a 100644
--- a/lib/Catalyst/Manual/Deployment/DevelopmentServer.pod
+++ b/lib/Catalyst/Manual/Deployment/DevelopmentServer.pod
@@ -1,42 +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.  However, consider using
-L<Catalyst::Engine::HTTP::Prefork> for this kind of deployment instead, since
-it can better handle multiple concurrent requests without forking, or can
-prefork a set number of servers for improved performance.
+Catalyst::Manual::DevelopmentServer - Development server deployment
 
-=head3 Pros
+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.
 
-As this is an application server setup, the pros are the same as
-FastCGI (with the exception of speed).
-It is also:
+=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:
 
@@ -64,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
+frontend server or proxy, such as varnish, nginx, or lighttpd.
+
 =head1 AUTHORS
 
 Catalyst Contributors, see Catalyst.pm
@@ -73,4 +58,4 @@ Catalyst Contributors, see Catalyst.pm
 This library is free software. You can redistribute it and/or modify it under
 the same terms as Perl itself.
 
-=cut
\ No newline at end of file
+=cut