docs(okf): add server memory budget and analytics proposal

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Noel SabiaandClaude Opus 5.5 committed 2026-10-11 14:39:54 +02:00
1 parent 64fef83314
commit 261cf17e52
13 files changed
+178 -12

No files matched your search

+38
View File
@@ -0,0 +1,38 @@
---
type: Decision
title: GoatCounter over Umami for analytics
description: Proposed; GoatCounter gives cookie-free open source analytics in about 30 MB, where Umami needs Postgres and about 300-400 MB.
tags: [decision, analytics, resources]
status: draft
generated: { by: claude-code/claude-opus-5-5, at: 2026-10-11T12:15:30Z }
---
# Proposal
Self-host GoatCounter in namespace `cv` instead of Umami. Needs Noel's
approval as new tooling.
# Why
| | Umami | GoatCounter |
|---|---|---|
| Runtime | Node app | Single Go binary |
| Database | Postgres | SQLite file |
| Memory | ~300-400 MB with Postgres | ~30 MB |
| Cookie-free, no consent banner | Yes | Yes |
| Custom events | Yes | Yes |
| License | Open source | Open source |
On a [4 GB shared server](/architecture/server-budget.md), Umami alone would
match the whole CV budget.
# Track
- Page views.
- PDF CV downloads.
- Falls per chapter.
# Details
One Deployment, 64Mi limit, SQLite on a small `local-path` volume. No backup:
losing analytics hurts nobody.