Although I've loved using Wordpress for the duration of this blog, recently I've been working on a custom replacement blog platform that I can host and maintain myself. This probably sounds odd, especially since there are already so many excellent blogging platforms available, but I've pushed ahead with it for a couple of reasons I think most developers will understand:
Once you’ve got the tunnel running (ideally you’d set it up to run automatically), all that’s left is to mount the NFS share(s) to appropriate locations in your filesystem. This process varies by operating system (even across UNIXes), so for now I’ll leave that up to you.
As a sort of proof of concept for the ideas I discussed in my previous post, I've put together the first draft of what could become a very helpful reusable module. With this post, I'd like to introduce my new Zend Framework "content" module, which provides several abstract components for a reusable model layer, along with a concrete framework for building a variety of content types sharing a common database-based persistence layer.
A few weeks back, Matthew Weier-O'Phinney wrote a very helpful discussion of model layer infrastructure using various components of the Zend Framework. I especially appreciated his advice on using Zend_Form as an input filter inside the model class itself; it provides a very clean way to keep validation and filtering logic properly encapsulated.
Earlier this week I posted about my PHP spades project for automated testing of bidding and playing strategies. In that post I highlighted my use of the strategy design pattern to make it easy to test a variety of approaches to the game; however, I didn't provide much structural detail. Lucky you, as it turns out, because the structure I was using at the time was far from ideal.
My overall idea for running the tests was to be able to use a very thin controller script, something along these lines:
Ran a search or two this morning, and discovered to my dismay that my computer was in danger from the entire internet; every result I saw in every search I tried contained this ominous warning about how the site "may damage [my] computer":