REPO= Set up Astro on this VM by following the exe.dev recipe at https://exe.dev/deploy/astro.md?via=terminal from top to bottom. The values at the top of this message are mine: - REPO: the GitHub repository of the Astro site to deploy, as owner/name or a URL, or `new` to start a fresh Astro blog with a server-rendered guestbook Ask me for any that still say before you need them. The recipe's example VM name is my-astro. This VM's name is the output of `hostname`: use it wherever the recipe writes my-astro. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Node.js 26 and Caddy installed; the site answering on port 8000, from Caddy for a static build or from app.service for a build with @astrojs/node, enabled to come back after a reboot. - A ~/app.git repository whose pre-receive hook builds each push to main into a new release and rejects the push if the deploy fails. - Settings and secrets in ~/app.env (mode 600), read by the build and by the server. - Data in ~/data, backed up nightly by app-backup.timer, with the newest backup opened and checked in a scratch directory. - With REPO=new, the Astro 7 blog starter plus a /guestbook page whose Astro Action saves messages to SQLite, signed with the visitor's exe.dev name. Read the whole recipe, including the closed details. Follow "Set up by hand" from "Install Node.js and Caddy" to the end of it, as exedev; the walkthrough above it is for the owner afterwards. Do not run Restore or Update, do not reboot, and do not set up "Deploy from GitHub" unless the owner asks. Leave public sharing off. REPO picks one path in "Get the code": `new` starts a fresh site; anything else is a GitHub repository (turn URLs into owner/name). Never commit to a repository you cloned: its settings go in ~/app.env. 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 site, read its astro.config and README: fill ~/app.env from .env.example if there is one, ask the owner for keys to outside services, and never invent values. If a build fails, read its output, fix what you can without editing the code, and redeploy with ~/app.git/hooks/pre-receive HEAD. If the site uses an adapter other than @astrojs/node (Netlify, Vercel, Cloudflare), tell the owner what "Coming from Netlify, Vercel, or Cloudflare" says instead of changing it. Finish with the site's URL (and /guestbook for a new site), whether it deployed as static or server, and the git commands the owner runs on their own computer, from "Deploy with git push". Finish with the URLs I should open.