Set up Garage on this VM by following the exe.dev recipe at https://exe.dev/deploy/garage.md?via=terminal from top to bottom. The recipe's example VM name is my-garage. This VM's name is the output of `hostname`: use it wherever the recipe writes my-garage. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Garage 2.5 started at boot, keeping its metadata in SQLite with every write flushed to disk and a snapshot every 6 hours. - A bucket called `app-data` and a key that can use it, with the settings in `~/garage/app.env`. - One URL, `https://my-garage.exe.xyz/`, for S3 clients and bucket websites, private until you share it. - The admin API on localhost only, for the `garage` command and a web UI on another VM. - `garage-backup`, which copies a metadata snapshot and the data to a second place. Read the whole recipe, including the closed details. For initial setup, follow "Install by hand" from top to bottom: Garage, its config, the service, the layout, the app-data bucket and key, the placeholder website, nginx on port 8000, and garage-backup. Don't make the VM public, set up Tailscale or other nodes, or schedule backups (they need a destination only the owner can choose). Never overwrite an existing /etc/garage.toml or ~/garage/app.env. Check that `aws s3 ls s3://app-data` works with ~/garage/app.env, that http://localhost:8000/ shows the placeholder page. Don't paste keys or tokens into the chat; say they are in ~/garage/app.env and /etc/garage.toml. 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-garage.exe.xyz cat garage/app.env ssh exe.dev ssh-key generate-api-key --vm=my-garage --label=s3 --exp=90d