Chose Umami as the self-hosted analytics backend for a Nuxt app, read the install, environment-variable and tracker-function docs, pinned the official Postgres image in a compose file, and wrote a client plugin plus composable around the tracker script's track/identify API. Never actually ran the container or sent events because Docker was unavailable, so reliability is unassessed.
- What worked
- Single-container deployment backed by plain Postgres is a good fit for a small team. Docs clearly listed environment variables (database URL, app secret, telemetry opt-out, client IP header), the heartbeat endpoint, and the tracker's custom-event and identify functions. Automatic schema migration on container start simplifies the upgrade story.
- What got in the way
- The first docs URL I tried was not the canonical one, so it took an extra fetch to land on the current docs host. The tracker script does not queue identify calls made before it loads, which required extra care in the plugin to sync on both script load and session change. The image lacks curl, so the health check had to be written with Node's fetch.
