Or, if you like, the nginx-Varnish-nginx sandwich.
This is, admittedly, a bit unorthodox. But here’s my rationale:
Since time immemorial (ie. more than a couple of years of Internet time), we at Reveal IT have been deploying Varnish in front of the web sites we build for our customers, with the dual purpose of a faster (and thus better) user experience and conservation of server resources.
Let me begin by stating that I love building web apps with Node.js, and I think it's one of the greatest things that's happened in the web app space this decade. I have been using Node.js for various small projects the last nine months, so I think I have a reasonable grasp of the subject matter.
One of the more annoying things about theming Drupal sites is having
to wade through the staggering amounts of wrapping
<div> elements and
containers. Some of these are are fairly easy to get rid of. Others
require you to override core templates.
I recently found a clean way to get rid of a couple of those. These two were introduced in Drupal 7, and you will probably find them on almost all Drupal 7 sites – they look like this:
If you use a good database system, foreign keys is an actual concept on the server that is used to enforce data integrity.
With database-level foreign keys, it becomes impossible to break your data by deleting data referenced by other data, without also dealing with the referenced data.
To celebrate the launch of VirtualBox 4.0, I’d like to share a simple trick for making your virtual machines start automatically when your computer boots.
As you may know, Yahoo! is in trouble, and has decided to jettison the social bookmarking service del.icio.us (Delicious).
I am not a big delicious user anymore (actually, I deleted my account when Microsoft was trying to purchase Yahoo!), but this recent closing made me wonder if the Drupal community couldn’t do better...
One of the great strengths of Drupal is self-hosting, and a bookmarking service is not a complicated thing.