Set up ClickHouse on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/clickhouse.md?via=terminal from top to bottom. The recipe's example VM name is my-clickhouse. This VM's name is the output of `hostname`: use it wherever the recipe writes my-clickhouse. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - ClickHouse 26.8 LTS from ClickHouse's apt repository, held at 26.8, started at boot, listening on localhost only. - A password on the `default` user, and an `app` database and user whose settings are in `~/clickhouse/app.env`. - Memory limits and system log retention sized for a small VM. - An `app.events` table ready for events and logs. - The Play UI at `https://.exe.xyz:8123/play`, private behind exe.dev login. - Nightly backups with ClickHouse's BACKUP, one restored and checked. Read the whole recipe, including the closed details. For initial setup, follow "Install by hand" from top to bottom, skipping VM creation: the repository and packages, passwords, the config files, starting ClickHouse, the app user and events table, the backup timer, and the restore test. The walkthrough sections are for the owner afterwards: don't load the taxi demo, set up Tailscale, S3, Grafana or Docker access, or run the Restore or Update instructions during initial setup. Never overwrite an existing ~/clickhouse/*.env file. Drop only the app_restored database the restore test creates. Leave the VM private and do not reboot. Don't paste passwords into the chat; say they are in ~/clickhouse/admin.env and ~/clickhouse/app.env. Finish with https://.exe.xyz:8123/play and the steps in "Open the Play UI". 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 my-clickhouse.exe.xyz cat clickhouse/admin.env ssh exe.dev ssh-key generate-api-key --vm=my-clickhouse --label=clickhouse