Suppose you want to generate a cue sheet from a wave file without having to do any tedious data entry. The obvious way to accomplish this is to use a visual wave editor like Sound Forge (or Audacity if you’d like something free and open source) to set cue points generate the cue sheet file on the spot. The problem is that there isn’t widespread support for cue sheet generation. Just about anything and everything can read cue sheets but generating them is a different story—you’re probably going to have to resort to some hack, script, or kludge.
These days I have been doing a fair amount of work with Sass, a CSS preprocessor. I have some experience with Compass but haven’t used it for my last few projects. It just feels like overkill—particularly when I am only using a handful of its functions.
Bourbon recently jumped out as a lightweight alternative to Compass. But then it hit me: both of these frameworks concentrate on solving a problem I no longer have: vendor prefixing.
Despite the web’s origin in academia it isn’t immediately obvious what HTML5 markup should be used for scholarly references and bibliographies. By “scholarly references” I mean the usual sort of references one finds at the end of an academic paper. I went Googling this one night and this post by Ian Devlin is just about the only relevant post I found on the subject. What follows is an investigation of the various options open to anyone interested in including a bibliography or reference list in their online work.
Now and then I want to link posts together in a series on my personal WordPress blog. For instance, while publishing photographs from a trip to South Korea, I wanted some way to connect those galleries to make it easy for visitors to move from one to the next. Similarly, much of my travel writing is episodic, and it makes sense to link posts in a standardized way rather than injecting links willy-nilly.
And so I did what most people would do in this situation: search the obvious on Google. Predictably, there are many plugins to accomplish my stated aim. Apple popularized “there’s an app for that”. WordPress may as well have popularized “there’s a plugin for that”. So, which plugin should I install?
Since switching to Nginx I have had some trouble accessing phpMyAdmin on my Dreamhost dedicated server. I spent some time trying to debug the issues but had no luck. Rather than continue to bash my head against a wall I installed a copy of phpMyAdmin on my laptop to manage my databases through port forwarding (as suggested in the Dreamhost wiki). It was easy enough but there were a few twists and turns so I thought I might document what steps I took to get up and running.
Nginx is a high performance, scalable, event-driven HTTP server with a small memory footprint. It excels at serving static content, particularly in conjunction with X-Accel, Nginx’s implementation of X-Sendfile. X-Accel facilitates controlled downloads while using minimal resources. From the Nginx wiki:
X-accel allows for internal redirection to a location determined by a header returned from a backend. This allows you to handle authentication, logging or whatever else you please in your backend and then have Nginx handle serving the contents from redirected location to the end user, thus freeing up the backend to handle other requests.