REPO= Set up Apps from Replit on this VM by following the exe.dev recipe at https://exe.dev/deploy/migrate-replit.md from top to bottom. The values at the top of this message are mine: - REPO: the GitHub repository your Replit app syncs to, as owner/name (in Replit: Tools → Git). Without one, say so and upload the app's zip as "Get your code out" says Ask me for any that still say before you need them. The recipe's example VM name is my-replit. This VM's name is the output of `hostname`: use it wherever the recipe writes my-replit. 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 24, pnpm 10, uv, and Caddy installed; PostgreSQL 18 with an empty `app` database and nightly backups, as in the PostgreSQL recipe; `replitdb.service` answering Replit Database's API on 127.0.0.1:8099. - `~/app.git` with the app's code, and `~/bin/replit-plan`'s reading of its `.replit` in place: each published server as a unit in `app.target`, Caddy on port 8000 routing paths and serving static builds, and the build in `~/bin/app-build`. - `~/app.env` (mode 600) pointing the app at the VM's PostgreSQL and Replit Database, and Replit AI Integrations' variables at exe.dev's LLM gateway. - `~/bin/app-deploy` building a commit into `~/releases`, updating the schema, switching over, and keeping the previous release if a page doesn't answer; run by `app-deploy.timer` for a GitHub repository, or by a push to `~/app.git`. - The app answering at https://my-replit.exe.xyz/, still private, and `~/bin/app-import` ready to copy the production database and Replit Database from Replit. - A report of what in the app still needs Replit (`replit-plan`'s `Uses` lines), each with the section of this page that deals with it. Read the whole recipe, including the closed details. Follow "Set up by hand" from "Install Node.js, pnpm, and Caddy" to the end of it, as exedev; the walkthrough above it is for the owner afterwards. Do not run "Update", do not reboot, and leave public sharing off. The scripts and units were tested as written: use them unchanged, and leave no test files behind. REPO is a GitHub repository; turn a URL into owner/name. Clone it through the GitHub integration. If that fails with "not found" or a 403, and https://github.com/OWNER/NAME is public, clone that instead; otherwise give the owner the integration command from "Get the code", with this VM's name, and wait for them. Install everything else meanwhile. If the owner has no repository, ask for the zip and the scp command from "Get your code out", and use the zip steps. Never commit or push to a GitHub repository in this setup. If replit-plan prints a Nix line, install the apt packages that provide those tools before the first deploy. If the first deploy fails, read the error above FAILED and fix what's on the VM's side (a missing apt package, a setting in ~/app.env); if the code itself needs Replit, say what and leave the rest set up. Don't run app-import: the owner runs it with Replit's connection strings, which should never be pasted into this conversation. Keep keys and passwords out of your replies; say which file holds them. In your report, say in plain words what the Uses lines found, with the section of this recipe that deals with each. Then give the owner the next steps: copy the secrets over and bring the data across, as "Settings and secrets" and "Bring your data over" say, with this VM's name. Finish with the URLs I should open.