<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nginx on System Overlord</title><link>https://systemoverlord.com/tags/nginx.html</link><description>Recent content in Nginx on System Overlord</description><generator>Hugo</generator><language>en-us</language><managingEditor>david@systemoverlord.com (David Tomaschik)</managingEditor><webMaster>david@systemoverlord.com (David Tomaschik)</webMaster><lastBuildDate>Wed, 31 Aug 2011 22:53:21 +0000</lastBuildDate><atom:link href="https://systemoverlord.com/tags/nginx/index.xml" rel="self" type="application/rss+xml"/><item><title>Git On Your Web Server: A Security Reminder</title><link>https://systemoverlord.com/2011/08/31/git-on-your-web-server-a-security-reminder/</link><pubDate>Wed, 31 Aug 2011 22:53:21 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2011/08/31/git-on-your-web-server-a-security-reminder/</guid><description>&lt;p&gt;
	Earlier this month, I wrote about &lt;a href="https://systemoverlord.com/2011/08/04/managing-drupal-with-git"&gt;managing a Drupal site with git&lt;/a&gt;.  What I neglected to remember, of course, is this places a full copy of your git repository within your web server's document root.  This has the potential to expose any data in your git repository -- a malicious attacker could (depending on your configuration) clone the entire repository, thus exposing source code, configuration files, database dumps, and other sensitive data.&lt;/p&gt;</description></item><item><title>Welcome to Nginx!</title><link>https://systemoverlord.com/2011/01/23/welcome-to-nginx/</link><pubDate>Sun, 23 Jan 2011 17:49:21 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2011/01/23/welcome-to-nginx/</guid><description>&lt;p&gt;If you're reading this, it's thanks to Nginx.  As of about midnight last night, all content on SystemOverlord.com is being served up by Nginx.  I did this for two reasons: Nginx has a much smaller memory profile than Apache, which is important when running on a 512MB VPS, and Nginx's preferred PHP path is through a FastCGI interface, which allows me to run separate PHP FastCGIs under different users for each application on my server.  Privilege separation for different webapps has always been a big thing security-wise, and I'm glad I was able to get it going with a minimum of fuss.  &lt;a href="http://wordpress.org"&gt;Wordpress&lt;/a&gt;, &lt;a href="http://nginx.org"&gt;Nginx&lt;/a&gt;, &lt;a href="http://mysql.com"&gt;MySQL&lt;/a&gt;, and &lt;a href="http://ubuntu.com"&gt;Ubuntu Server&lt;/a&gt; powered, all on a &lt;a href="http://www.linode.com/?r=680a893e24df3597d32f58cd41930e969027dc06"&gt;Linode VPS&lt;/a&gt;!&lt;/p&gt;</description></item></channel></rss>