To make this change on dynamic hyperbola would have meant 5-10 Ansible deploys to a Vagrant VM. Iteration speed would have been terrible. #devops #a11y #lighthouse #hypstatic

permalink

whoa throwback `chattr +i` to prevent puppet from overwriting files on a prod box that you were manually changing #devops

permalink

hyperbola: now with multi-homed DNS. AWS Route 53 and CloudFlare, made possible by terraform. (In the process upgraded hyperbo.la mail to a 2048-bit DKIM key) #win #redundancy #devops

permalink

Packer + Ansible + AWS + Terraform is really quite lovely #devops #win

permalink

All done. Downgraded from 8GB of RAM to a more reasonable 2GB of RAM. Went from 4 cores down to one though 😱 #devops #maintenance

permalink

Woo! First 2 hyperbola releases with #git tags today #win. Also local development. dev + ops = #devops

permalink

Next #devops steps for hyperbola: Rebuild machine from scratch on 64-bit kernel; use #docker and dockerize all services: nginx, staging django, prod django, MySQL; real deploy step; #git tag releases

permalink

The last bits of the #hyperbola deployment are gone from my home directory ... finally productionized a cron to do a #database and media backup #devops

permalink

And with about 30 minutes of downtime I've now got 2x the ram #devops

permalink

Part of pushing #metadata to production meant we got to puppet our service across dev/staging/perfpod/production. #puppet is pretty cool #box #devops

permalink