Set up Supabase on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/supabase.md?via=terminal from top to bottom. The recipe's example VM name is my-supabase. This VM's name is the output of `hostname`: use it wherever the recipe writes my-supabase. Skip the step that creates the VM; you are on it. This recipe needs a 40GB disk, and a new VM's may be smaller. Before you install anything, run `df -h /`. If its size is under 36G, stop and ask me to grow the disk, either with this link: https://exe.dev/suggest?command=resize%20my-supabase%20--disk%3D40GB or, on my computer, with `ssh exe.dev resize my-supabase --disk=40GB`. When I say it's done, run `sudo resize2fs "$(findmnt -no SOURCE /)"`, check `df -h /` again, and carry on. You are done when all of these are true. Check each one yourself: - Supabase v0.8.4 running in Docker Compose, with its own generated secrets and keys in `~/supabase/.env` (mode 600), and coming back after a reboot. - Studio at `https://.exe.xyz:8001/`, behind exe.dev login and the dashboard password, showing a `notes` table with one row. - The API on port 8000 answering `GET /rest/v1/notes` with the publishable key, and refusing Studio and `/pg/` paths. - Studio's AI Assistant answering through exe.dev's LLM gateway. - The Supabase CLI and rclone installed, and `supabase-backup.timer` saving the database and files to `~/backups` nightly, with a first backup made. Read the whole recipe, including the closed details. For initial setup, follow "Install by hand" first, skipping VM creation and SSH, through the first backup. The walkthrough at the top is for the owner afterwards. Do not run the email hook, SMTP, S3, Cloud move, Restore, or Update sections unless the user asks. Never print ~/supabase/.env or setup.sh's secret output into the chat; tell the owner where the dashboard password is (`grep DASHBOARD ~/supabase/.env`). Don't make the VM public or share it: the owner decides. Leave the `notes` table in place so the owner can see it in Studio. 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-supabase