REPO= Set up Streamlit on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/streamlit.md from top to bottom. The values at the top of this message are mine: - REPO: the app to deploy: a GitHub repository (owner/name or a URL), a Hugging Face Space URL, or `new` to start from a small Streamlit dashboard Ask me for any that still say before you need them. The recipe's example VM name is my-streamlit. This VM's name is the output of `hostname`: use it wherever the recipe writes my-streamlit. 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, or a new Streamlit starter dashboard, running as `app.service` on 127.0.0.1:8000 and enabled to start after a reboot. - `git push exe main` deploys: the hook builds a new release in `~/releases` with uv, runs a Streamlit app once headless with Streamlit's AppTest, switches `~/app` to it, restarts, and checks it answers. A failed deploy rejects the push and leaves the running version up. - The app private behind exe.dev login, reading the viewer's email from the `X-ExeDev-Email` header (`st.context.headers` in Streamlit, `gr.Request` in Gradio). - Settings and secrets outside the repository, mode 600, in `~/app.env` and `~/.streamlit/secrets.toml` (`st.secrets`). - Data in `~/data`, refreshed every hour by `app-refresh.timer` in the starter, and backed up every night to `~/backups`, with a backup restored and checked in a scratch directory. Read the whole recipe, including the closed details, and follow "Set up by hand" in order, skipping VM creation. The walkthrough above it is for the owner afterwards. Ask for REPO first if it says . For REPO=new, build the starter exactly as written. For a GitHub repository or a Hugging Face Space, follow "Bring your app": set APP_FILE and the other settings in ~/app.env, and for a Gradio app change ExecStart as it says. Never commit to the owner's repository or push to ~/app.git (run the hook by hand instead), so the owner's first push fast-forwards. Remove whatever you make only for testing. If a private GitHub repository can't be cloned, give the owner the `integrations add github` command with this VM's name and wait for them. If the app needs API keys you don't have, say which, and where they go. Don't reboot, don't make the VM public, and don't run the Restore steps on live data: test the backup in a scratch directory as written. The VM can't open its own https://.exe.xyz; "Check it" tests through localhost instead. Skip the optional sections (Gradio next to Streamlit, integrations, public access) unless the owner asks. Finish with https://.exe.xyz/ and only the one git command from "Deploy with git push" that fits: `git clone -o exe` for REPO=new, `git remote add exe` for a repository, plus the branch to push if it isn't main, and anything you adapted or that the owner should change. 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-streamlit.exe.xyz:app.git # if you started fresh git remote add exe my-streamlit.exe.xyz:app.git # or, in your own app's checkout