chore: drop the umami beacon (the lab retires umami; visits are counted server-side) #2
Loading…
Reference in a new issue
No description provided.
Delete branch "ctrl-agent/zddc-website:chore/drop-umami-beacon"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The lab is retiring its umami analytics service (
stats.someonetoldme.xyz, operator decision 2026-10-22). This removes the beacon<script>from the four pages that load it (index.html,reference.html,spec/index.html,workflow.html). No other change.Visit counting continues server-side: the origin Caddy's opt-in access log for
zddc.varasys.io(client IP masked to /24, User-Agent/Referer/cookies dropped before anything is written; runbook 09 §9 in the lab repo), already used for metronome, renew and chidot. That needs a matchingaccess_log: trueon the lab side.Order: merge this first. The pushed image redeploys the site without the script. Only after that does the lab remove
stats.someonetoldme.xyz. Otherwise every page would request a script that no longer exists. That would be harmless (the tag isdefer) but noisy.umami recorded 72 zddc events in the last 30 days (last one 2026-10-19).
🤖 Generated with Claude Code