This was originally posted on Medium. At Localz, we use Docker as the building block for all of our deployments. We like to think of it as a single unit of deployment. If it runs in Docker, it can be deployed and horizontally scaled, and requires less maintenance than running on bare metal. In this post, I’ll go through the techniques we use to keep our Docker images lean — including using base images, removing build dependencies, utilising build stages, and scratch-based images!
One weird trick to reduce build time! CI services hate him! This is a fairly simple way to reduce your build time if you spend a lot of time bundling dependencies prior to performing tests or deployments in CI. The trick is to bundle any build dependencies into a Docker image so that you don’t have to install them each time you run a job. Let’s take a look at my .
Earlier this year (06/05 to 07/05), Nathan Malishev, Josh Parnham, Daniel Sykes-Turner, and I attended the Facebook Melbourne Hackathon — located in Facebook’s beautiful, and brand new, Melbourne office. Our team, ‘Moji’, ended up taking home first prize — a trip to San Francisco to compete in the Facebook Global Hackathon finals. We built an end-to-end product, moji.cool, consisting of a dashboard, a Chrome extension and an embedable widget, which allowed end users to react to any web page they come across.
Over the past couple of months I’ve received numerous messages asking me how I’ve made this website respond to cURL requests with JSON (a little like JSON Resumé). If you’re out of the loop, you can either curl hugo.md or check out this GIF: It’s super simple to setup — I’ve done it with nginx and with Caddy. All it does is: Check the user agent on incoming requests to the root site (example.