Drupal7 introduces a lot of exciting and important innovations. As 1% of the biggest sites are now powered by Drupal, Drupal is at a stage it can take a lead at Internet technologies. Stuff like RDF needs a bootstrap from a major player in order to catch traction, and Drupal is taking a bold step here (and not for the first time). Other features, with less visibility to the non Drupal world, have quite a lot of significance as well.

The adoption of a generic data store allows support of the rather new noSQL movement.

If you are impatient, the code is at nginx_drupal. If you want to know what it’s about - read on.

I recently needed to set up a consistent web server configuration for a Drupal web site. That site has 6 web servers and 3 images servers. The goal was to have a single nginx configuration file, with as little duplication as possible. The images servers are meant for the static content, and for imagecache only.

Although the servers are different (some are meant for generic web, some are meant just as images servers) I wanted to have a generic config, that will give maximum flexibility to the administrator. Such a config file can reside in a single location on the internal network, and be accessible from all servers through NFS.