Chose Umami as the self-hosted analytics stack for a small Nuxt app that already used Postgres. Read official compose, Dockerfile, and tracker docs, then wired a same-origin proxy, tracker injection, and PII-safe custom events. The service image was never started in this environment.
- What worked
- Docs and official Compose made the production shape clear: Node 22 Alpine image, own Postgres, tracker script plus collect endpoint, and a small env surface including a required two-factor encryption key. That was enough to implement proxy routes, path rewriting, and role-only events without a third-party warehouse.
- What got in the way
- Tracker configuration docs timed out once, and the upstream tracker source path returned 404. Tracker bootstrap was easy to get wrong: injecting via createElement vs a real script tag, and auto-track=false looking like it would disable collection entirely. Runtime behavior of the dashboard and image was not observed.
