Louvre, version 1.1
How Section 411 went serverless (mostly)
A little over two years ago, I launched Section 411. In a post that made the launch official, I formally introduced the site, writing about the new name and some of the technology that powered it. I wrote that unlike its predecessor, Section 411 was built using a static site generator (Hugo) instead of relying on something to render the pages in real time. I also wrote about Louvre, an image manager and processor I built that could dynamically serve images to a CDN, solving what’s typically a pain point for static site generators.
Of commits and containers
Using a Dockerfile to embed revision information in your Go application
Guillaume Bolduc, Unsplash When I’m debugging an issue with an application, one of the first questions I ask is what version of the application I’m looking at. If different versions of my app are deployed in multiple environments, it’s always worth checking to make sure the environment I’m looking at is running the code I think it is. There are a few ways of accomplishing this. Sometimes you can SSH into your server and run git log -1, but if your application is running in a container that’s not always available.
The Manhattan Project
As the summer of 2016 began, I started work on a project I ambitiously codenamed The Manhattan Project. A tongue-in-cheek nod to the real Manhattan Project of World War II, I felt like my project was similarly ambitious, despite the stakes for mine being far lower. After a few months, my Manhattan Project got its real name: Section 411. It’s pronounced “section four eleven” – as opposed to “section four one one”, for a reason I’ll explain below – and it’s where I’ll be doing my writing for the foreseeable future.
This post was originally written as a guest post for RyboMedia on October 15, 2009. Thanks to Rybo for letting me post this! Hope you all found it enjoyable and informative. We ran into a problem at work last week that was, at the same time, a nightmare and exactly the kind of problem you want to have. The culprit was our latest Big Prize Giveaways promotion, and the problem was that our app had metaphorically gone from 0-60 in about two seconds, and it experienced the same thing your neck feels when it accelerates that fast: whiplash.