economic dashboard series: stage 6 — threshold alerting
sixth post in the series: adding threshold detection and SNS email alerts so meaningful indicator crossings surface without having to check the dashboard.
Aws
economic dashboard series: stage 5 — historical storage
fifth post in the series: adding a DynamoDB snapshot store so the dashboard can display 3-month and 6-month sparklines alongside the existing 30-day view.
site: scheduled rebuild — publishing future-dated posts automatically
Adding a daily GitHub Actions cron workflow so future-dated Hugo posts go live on their scheduled date without a manual push.
economic dashboard series: stage 4 — data source upgrades
fourth post in the series: replacing ETF proxies with direct data sources, investigating free alternatives, and fixing a BoC query bug hiding three months of bond yield data.
economic dashboard series: stage 3 — server-side data fetching
third post in the series: moving all data fetching out of the browser and into AWS Lambda.
economic dashboard series: stage 2 — hugo integration
second post in the series: giving the dashboard a proper home on tacedata.ca and the decisions that went into it.
security - stage 2 - internet cache and the wayback machine
Cleaning git history removes data from your repo — but not from search engines, the Wayback Machine, or GitHub’s cache. Here is what to check.
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.
economic indicators dashboard
A Canadian mortgage rate decision aid — eight economic indicators translated into plain-English signals.
security remediation — what we got wrong
A post-launch security review of tacedata.ca uncovered sensitive AWS identifiers committed to a public repository. This is a full account of what was exposed, how it was found, and what it took to fix it.