Comments on: Minimal lighttpd configuration http://therning.org/magnus/archives/198?&owa_from=feed&owa_sid= Incoherent mumblings Sat, 30 Aug 2008 04:37:37 +0000 http://wordpress.org/?v=2.6.1 By: Bob http://therning.org/magnus/archives/198#comment-119869 Bob Wed, 07 May 2008 17:53:06 +0000 http://therning.org/magnus/archives/198#comment-119869 <p>Nice! I needed a thin webserver for posting a "We're sorry, but our service seems to be on fire..." placeholder page to placate users during extended outages. While we're currently using Apache, I want to reduce the footprint of the "sorry" announcement and the example lighttpd config was just too much to wade through. I added entries for server.username and server.groupname so the "sorry" docroot could lie within the (broken) application directory and there'd be no issue with users and permissions.</p> <p>All this gets stuffed into our configuration management system (Puppet) so as we deploy servers, lighttpd is automatically installed and configured on the boxes that need it.</p> Nice! I needed a thin webserver for posting a “We’re sorry, but our service seems to be on fire…” placeholder page to placate users during extended outages. While we’re currently using Apache, I want to reduce the footprint of the “sorry” announcement and the example lighttpd config was just too much to wade through. I added entries for server.username and server.groupname so the “sorry” docroot could lie within the (broken) application directory and there’d be no issue with users and permissions.

All this gets stuffed into our configuration management system (Puppet) so as we deploy servers, lighttpd is automatically installed and configured on the boxes that need it.

]]>