<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>lithostech.com &#187; web server</title>
	<atom:link href="http://lithostech.com/tag/web-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://lithostech.com</link>
	<description>making it work</description>
	<lastBuildDate>Tue, 17 Jan 2012 06:58:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>stevecrozz&#8217; custom nginx binary for ubuntu 0.7.59</title>
		<link>http://lithostech.com/2009/06/stevecrozz-custom-nginx-binary-for-ubuntu-0-7-59/</link>
		<comments>http://lithostech.com/2009/06/stevecrozz-custom-nginx-binary-for-ubuntu-0-7-59/#comments</comments>
		<pubDate>Tue, 09 Jun 2009 03:45:36 +0000</pubDate>
		<dc:creator>stevecrozz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[web server]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[The nginx build in the official ubuntu package repository is somewhat out-of-date, so I built my own package from source using <a href="http://www.nginx.eu/download/sources/nginx-0.7.59.tar.gz">0.7.59</a>. I'm going to provide it here in case anyone else would like it. One of the new features I like is the <a href="http://wiki.nginx.org/NginxHttpCoreModule#try_files">try_files</a> directive. Here's an example of what I'm doing using 0.6.35, the full post is here <a href="http://lithostech.com/lighten-apaches-load-nginx">http://lithostech.com/lighten-apaches-load-nginx</a>:

]]></description>
		<wfw:commentRss>http://lithostech.com/2009/06/stevecrozz-custom-nginx-binary-for-ubuntu-0-7-59/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>lighten apache&#8217;s load with nginx</title>
		<link>http://lithostech.com/2009/05/lighten-apaches-load-with-nginx/</link>
		<comments>http://lithostech.com/2009/05/lighten-apaches-load-with-nginx/#comments</comments>
		<pubDate>Thu, 28 May 2009 06:59:58 +0000</pubDate>
		<dc:creator>stevecrozz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[web server]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Since we've been on <a href="http://slicehost.com">slicehost</a>, I've been forced to play the role of system administrator since we don't have a real one. One problem I've run into is the long string of legacy applications that I have to support. Some of them I wrote, and some of them I inherited. For many reasons, they're often organized and run in sub-optimal ways.

Separating your static and dynamic content is a good habit to get into when you're building scalable web applications. Static content is highly portable because it can live without context. You can serve it from anywhere and nobody knows the difference. When your site starts to get huge traffic, you can easily offload your static content to a <a href="http://en.wikipedia.org/wiki/Content_Delivery_Network">CDN</a> if you host it in an easy-to-separate way using an URL like static.domain.com or domain.com/static.
]]></description>
		<wfw:commentRss>http://lithostech.com/2009/05/lighten-apaches-load-with-nginx/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

