I have a basic nginx (pronounced Engine EX) configuration on github. This is a basic version of perusio's nginx configuration in more of a stand-alone set up - and it uses unix sockets in the PHP connection configuration to do the processing instead of an upstream configuration (where the processing could optionally be coming from another server that has PHP), that can include Apache web servers. perusio's config is an advanced configuration with multiple failover backup servers that just wasn't necessary in my case so I decided to make another example config on github. Instead of having PHP connect to itself using TCP/IP, this setup eliminates the need for communication with itself using the TCP network layer. Data does not have to be "converted" into a standardized network layer format as it's processed from the file system through PHP. A performance enhancement side effect for stand alone nginx web servers.
I've re-factored the Drupal 6 module creator that I used to have on my website. It's been down since I changed hosting accounts and finally got a chance to finish it. Even though I'm using more Drupal 7 now than Drupal 6, it's still going to be useful to have around anytime I (or you!) need to make a module.