Set up Umami on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/umami.md?via=terminal from top to bottom. The recipe's example VM name is my-umami. This VM's name is the output of `hostname`: use it wherever the recipe writes my-umami. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Umami 3 on PostgreSQL, restarted after a reboot. - A private dashboard on port 3000 and a tracker-only public URL. - Nightly database backups, with the secrets file beside them. Read the whole recipe, including closed details, and follow "Install by hand" first. The opening walkthrough is for the owner afterwards. Do not run the later Restore or Update instructions. Work as exedev in ~/umami. Never overwrite an existing ~/umami/.env. Do not log in to Umami, change its password, or add websites: the owner does that in the browser. Leave public sharing off; only the owner can turn it on. Verify docker.service is enabled, all three containers are restart unless-stopped and healthy or up, localhost:3000/api/heartbeat answers {"ok":true}, localhost:8000/script.js returns 200, and localhost:8000/login and localhost:8000/api/websites return 404. Check the backup timer is enabled and the first dump exists in ~/umami/backups. Finish with the dashboard URL on port 3000, the default login (admin / umami, which Umami makes them replace at once), and the command the owner runs on their own computer to make the tracker public: ssh exe.dev share set-public my-umami Finish with the URLs I should open and these commands, which only I can run, from my own computer (with this VM's name in them): ssh exe.dev share set-public my-umami # lets visitors' browsers reach the tracker