Set up PostgreSQL on this VM by following the exe.dev recipe at https://exe.dev/deploy/postgres.md from top to bottom.

The recipe's example VM name is my-postgres. This VM's name is the output of `hostname`: use it wherever the recipe writes my-postgres. Skip the step that creates the VM; you are on it.

You are done when all of these are true. Check each one yourself:
- PostgreSQL 18 with pgvector, started at boot and sized for the VM's memory.
- An `app` database and role, with its DATABASE_URL in `~/postgres/app.env`.
- Adminer at the VM's private URL, open only to the owner's exe.dev email.
- Nightly backups of every database and role, one restored and checked.

Read the whole recipe, including the closed details. For initial setup,
follow "Install by hand" from top to bottom: PostgreSQL and pgvector,
tuning, the app database, Adminer on port 8000, the backup timer, and
the scratch-cluster restore test. The walkthrough sections are for the
owner afterwards: don't import data, set up Tailscale or Docker access,
or run the Restore or Update instructions during initial setup.
Never overwrite an existing ~/postgres/*.env file. Drop only the
scratch cluster the restore test creates.
Allow only the owner's email in Adminer, read from the reflection
integration; if that fails, ask the owner for it. Check Adminer on
localhost with no email, a wrong email, and the owner's email.
Leave the VM private and do not reboot. Don't paste passwords into the
chat; say they are in ~/postgres/app.env.

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-postgres.exe.xyz cat postgres/app.env
  ssh -N -L 5433:localhost:5432 my-postgres.exe.xyz