From: Kieren Diment <diment@gmail.com>
Date: Tue, 8 May 2007 23:58:43 +0000 (+0000)
Subject: added lighttpd static deployment recipe
X-Git-Tag: v5.8005~343
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=commitdiff_plain;h=3cca83594d8071ecc4bc3bd7307f5144a8de9aca;hp=8f45565456f999c57d82a3588d70677f8cc83e5d

added lighttpd static deployment recipe
---

diff --git a/lib/Catalyst/Manual/Cookbook.pod b/lib/Catalyst/Manual/Cookbook.pod
index 89cc05d..f4b756b 100644
--- a/lib/Catalyst/Manual/Cookbook.pod
+++ b/lib/Catalyst/Manual/Cookbook.pod
@@ -1534,6 +1534,25 @@ This will let all files within root/static be handled directly by Apache.  In
 a two-tiered setup, the frontend server should handle static files.
 The configuration to do this on the frontend will vary.
 
+The same is accomplished in lighttpd with the following snippet:
+
+   $HTTP["url"] !~ "^/(?:img/|static/|css/|favicon.ico$)" {
+         fastcgi.server = (
+             "" => (
+                 "MyApp" => (
+                     "socket"       => "/tmp/myapp.socket",
+                     "check-local"  => "disable",
+                 )
+             )
+         )
+    }
+
+Which serves everything in the img, static, css directories
+statically, as well as the favicon file.
+
+Note the pathof the applqication needs to be stated explicitly for
+boththese recipes.
+
 =head2 Catalyst on shared hosting
 
 So, you want to put your Catalyst app out there for the whole world to