What would Murray Walker do?
Seems like the buzz around Go over the last couple of years since its 1.0 launch hasn't just been hot air. There were a couple of high profile projects such as Cloudflare's Railgun back in 2012/23, which many (inc. myself) suspected may have been at least partially sponsored / encouraged by Google themselves to get #golang into the . . .
No, obviously not - but the title got you here.
Back in 2010 I wrote a blog post called HTTP self-service, which advocated the use of embedded HTTP servers inside software running in on the server, to make it easier to manage and maintain. The basic premise then was that HTTP was everywhere, and that everyone seemed to have their own lightweight embeddable HTTP server software library. In . . .
What we did in the aftermath of Heartbleed
Last Tuesday (8th April) we had a period of unexpected downtime on the site (from 8pm BST). This turned out to have been caused by Heroku (our hosting platform) resetting their SSL certificates in response to the now infamous Heartbleed bug. (One of the advantages of using a platform like Heroku is that you have the people on top of these . . .
Runtime DNS resolution of Docker container IP addresses.
Three months ago I wrote an article entitled "Is Fig Docker's missing link?" It wasn't, quite, and I abandoned my attempt to move off of a single Vagrant VM and onto a super-clean Docker-powered development environment. My discovery of Skydock has reeled me back in.
First, some background - my experience of getting a . . .
Where to put side-effects in the event of a cascade delete.
Django's ORM supports the concept of a 'cascade delete' - whereby the deletion of an object via the ORM results in the deletion of its related child object (related via a Foreign Key relationship).
We had an open question re. where to put side-effects that we wanted to run every time an object was deleted, irrespective of whether . . .
Linking Trello to Git has closed the loop on tracking progress.
We've written before about our workflow, and the tools that we use, but one thing that I've also missed from my Fogbugz days is the link between issues and commits. We've tried various methods, including adding branch names to Trello cards to try and link things together, but it never really caught on as it required more attention . . .
Orchard have gazumped me with their latest posting, but that's probably for the best.
I've had a draft post on Docker sitting in my in-tray for a couple of weeks now. The essence of the post is encapsulated in the related Trello card notes:
Having spent time working with Docker**, I've now got a much better (albeit still naive) understanding of what it is and how it works, and have switched focus. . . .