REPO= Set up Bun on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/bun.md?via=terminal from top to bottom. The values at the top of this message are mine: - REPO: the GitHub repository to run, as owner/name or a URL, or `new` to start a fresh Bun app Ask me for any that still say before you need them. The recipe's example VM name is my-bun. This VM's name is the output of `hostname`: use it wherever the recipe writes my-bun. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Bun 1.4.5, pinned, where your shell, scripts, and systemd all find it. - The app's code in ~/app, served by bun --hot as app-dev.service at port 3000, with hot reloading through exe.dev's proxy. - The same code compiled to one binary and running as app.service on port 8000, shipped with ~/bin/app-release, which puts the old binary back if the new one doesn't answer. - Settings and secrets in ~/app.env (mode 600) and data in ~/data, backed up nightly and before each release, with the newest backup opened and checked. - With REPO=new, a guestbook on Bun.serve, bun:sqlite, and WebSockets, with tests. Read the whole recipe, including the closed details. Follow "Set up by hand" from "Install Bun" to the end of it, as exedev; the walkthrough above it is for the owner afterwards. Do not run Restore or Update, and do not reboot. Leave public sharing off. REPO picks one path in "Get the code": `new` starts a fresh app; anything else is a GitHub repository (turn URLs into owner/name). If a clone fails, follow the private-repository steps, and if that fails too, give the owner the integration command and wait for them. For a cloned app, fill ~/app.env from its .env.example (or README): generate secrets with openssl, ask the owner for keys to outside services, and never invent values. Don't commit to a cloned repository; if the app can't run here without a code change (a hard-coded port, say), make the smallest one, leave it uncommitted, and tell the owner. If its dev server is Vite, follow "Hono, Elysia, and Vite". If app-release fails, read its output, fix what you can, and run it again. Finish with both URLs, port 8000 and port 3000, and how the owner works from here: edit in ~/app (or ask Shelley), watch port 3000, then run ~/bin/app-release. Finish with the URLs I should open.