security - stage 1 - cleaning sensitive data out of git history
After a security review flagged AWS identifiers committed to a public repo, we used git-filter-repo to scrub them from all 46 commits — including file content and commit messages.
blog
site: stage 6: site monitoring with aws cloudwatch
Setting up availability monitoring for tacedata.ca using CloudWatch Synthetics — what it is, what it costs, and how we set it up.
new digs
Introducing the new tacedata.ca — why I moved from WordPress to a static site on AWS, and what I plan to do with it.
site: stage 5: cutting over a website
Moving tacedata.ca from Websavers DNS to AWS Route 53 — what the cutover actually involves, and how to do it without taking the site down.
site: stage 4: building the site itself
Getting the site into a state worth sharing — PaperMod setup, profile home page, content structure, and a few problems solved along the way.
site: stage 3: deploying a static site on aws
How we set up S3, CloudFront, and a GitHub Actions deploy pipeline for tacedata.ca — no long-lived credentials, no manual deploys.
site: stage 2: migrating email before touching dns
Why email migration had to happen before any DNS work — moving tacedata.ca email to Fastmail without losing anything.
site: stage 1: choosing a static site generator
Evaluated Hugo and three themes before committing to a stack — and what we were actually looking for.