GARAGE_VM= Set up Garage Web UI on this VM by following the exe.dev recipe at https://exe.dev/deploy/garage-webui.md?via=terminal from top to bottom. The values at the top of this message are mine: - GARAGE_VM: the name of the VM that runs Garage, such as my-garage Ask me for any that still say before you need them. The recipe's example VM name is my-garage-ui. This VM's name is the output of `hostname`: use it wherever the recipe writes my-garage-ui. 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 Web UI at `https://my-garage-ui.exe.xyz/`, open only to the exe.dev emails in `~/garage-webui/allowed-emails`. - Buckets, keys, permissions, and files of your Garage VM, browsed and changed from the browser. - An admin token that expires in a year and can't create other tokens or change the cluster layout. - No secrets on this VM. The admin token and exe.dev's key live in two exe.dev integrations, which add them at the edge. Read the whole recipe, including the closed details. Follow "Install by hand" on this VM. The step "Connect it to Garage" runs on the owner's computer, not here: give the owner those commands with GARAGE_VM and this VM's name filled in, and wait until they say they ran them. Check with `curl -s https://reflection.int.exe.xyz/integrations` that garage-admin and garage-s3 are attached (if the owner picked other names, use those). Then continue with "Point it at Garage" and the checks. Allow only the owner's email, read from the reflection integration; if that fails, ask the owner for it. Leave this VM and the Garage VM private, and don't change anything on the Garage VM. 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 add my-garage-ui teammate@example.com # then add them to allowed-emails ssh exe.dev integrations remove garage-admin # cut the UI off from Garage