REPO= Set up ASP.NET Core on this VM by following the exe.dev recipe at https://exe.dev/deploy/aspnet-core.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 ASP.NET Core app Ask me for any that still say before you need them. The recipe's example VM name is my-aspnet. This VM's name is the output of `hostname`: use it wherever the recipe writes my-aspnet. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - The .NET 10 SDK installed from Ubuntu's packages, and the app published and running as app.service on 127.0.0.1:8000, enabled to come back after a reboot. - A ~/app.git repository whose pre-receive hook publishes 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 service; ASP.NET Core sees them as configuration. - Data in ~/data, backed up nightly by app-backup.timer, with the newest backup opened and checked in a scratch directory. - With REPO=new, a Razor Pages guestbook on EF Core and SQLite that signs visitors in from exe.dev's X-ExeDev-Email header, makes the owner an admin, and trusts the proxy's forwarded headers. Read the whole recipe, including the closed details. Follow "Set up by hand" from "Install .NET" 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. Skip the optional sections (SQL Server, Blazor, the LLM example) unless the owner asks. 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, read its README, appsettings*.json and .csproj files: set PROJECT if it has more than one web project; check its TargetFramework (net10.0 builds as is; net8.0 and net9.0 are out of support, so tell the owner, and for net11.0 follow "Use .NET 11"); put connection strings and secrets in ~/app.env as Section__Key lines, generating secrets with openssl and asking the owner for keys to outside services, never inventing values. Tell the owner about forwarded headers and sign-in from "Behind the proxy" if their Program.cs lacks them, but don't change their code. If a build fails, read its output, fix what you can without editing the code, and redeploy with ~/app.git/hooks/pre-receive HEAD. Finish with the app's URL and the git commands the owner runs on their own computer, from "Deploy with git push": `git clone -o exe` for a new app, `git remote add exe` for a GitHub repository, then `git push exe main` (or their default branch). Finish with the URLs I should open.