The process traditionally is: create a new blog article, edit it some, save. run hugo on the command line to generate the static site. copy/sync the public directory onto your webserver. Needing a webserver, build environment and text editor is a bit of hassle. It’s all a bit manual too. I’ve previously …

Read More

The problem Booting instances on EC2 is easy. But once it comes to connecting to them, you end up having to copy around transient and unwieldy ec2-....compute.amazonaws.com host names. So you manually set up a CNAME in your DNS to give the instance a friendly name, but as soon as you stop and restart the instance, the …

Read More

Due to the recent outage on GoDaddy a lot of people are reconsidering their DNS options. Amazon Route53 is a great option - cheap, flexible and well proven. To migrate you first need to export a zone file for the domain from GoDaddy. It’s been highlighted the zone files are slightly broken in CNAME records, so …

Read More

Amazon have launched a neat new Route 53 feature: latency-based routing. The idea behind this is when someone hits www.yoursite.com this resolves to the closest server to them, cutting latency. This DNS cleverness has been used by the big boys for some time, but not been available to us mortals without shelling out big …

Read More

If you’ve used Amazon webservices much at all you’ll probably have come across their DNS service route53. This offers very competitively priced DNS hosting on the Amazon cloud. To install: $ pip install cli53 The first step everyone migrating commonly goes through is getting their existing zones into the …

Read More

This is the first in a series of posts introducing some of the tools I’ve developed. The first is s3grep - parallelized grep for Amazon S3. The need for this one arose as one recent project processes and stores on S3 large (text) log files. Often to diagnose problems it’s really handy to check direct in the …

Read More