REPO= Set up Spring Boot on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/spring-boot.md from top to bottom. The values at the top of this message are mine: - REPO: the GitHub repository to deploy, as owner/name or a URL, or `new` to start a fresh Spring Boot app Ask me for any that still say before you need them. The recipe's example VM name is my-spring-boot. This VM's name is the output of `hostname`: use it wherever the recipe writes my-spring-boot. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Your app from GitHub (REPO), or a new Spring Boot 4 guestbook, running on Java 25 as app.service on port 8000, enabled to come back after a reboot. - PostgreSQL 18 on the VM with a database and a generated password for the app, passed in through ~/app.env (mode 600), with the JVM's memory flags. - A ~/app.git repository whose pre-receive hook builds each push to main with the project's Maven or Gradle wrapper, backs up the database, and rejects the push if the new version doesn't report ready. - Actuator's health and readiness on 127.0.0.1:8081, off the app's port, and the proxy's X-Forwarded headers trusted, so redirects and cookies use HTTPS. - For a new app, a guestbook that signs people in through exe.dev's X-ExeDev-Email header with Spring Security, and an /admin page for the emails in APP_ADMINS. - A nightly backup timer, and a first backup whose database dump is restored into a scratch database and counted. Read the whole recipe, including the closed details. Follow "Set up by hand" from "Install Java" 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). 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 app, follow "Bring your app": fill ~/app.env from its application.properties or application.yml and README, generate secrets with openssl, 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. Keep the deploy hook and backup script as written, since the page documents how they behave; if one looks wrong, say so at the end. Finish with the app's URL; only the one git command from `after` that fits; and what you set in ~/app.env for their app. 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): git clone -o exe my-spring-boot.exe.xyz:app.git # if you started fresh git remote add exe my-spring-boot.exe.xyz:app.git # if you brought your app: in your checkout