Set up Dify on this VM by following the exe.dev recipe at https://exe.dev/deploy/dify.md from top to bottom. The recipe's example VM name is my-dify. This VM's name is the output of `hostname`: use it wherever the recipe writes my-dify. Skip the step that creates the VM; you are on it. This recipe needs a 40GB disk, and a new VM's may be smaller. Before you install anything, run `df -h /`. If its size is under 36G, stop and ask me to grow the disk, either with this link: https://exe.dev/suggest?command=resize%20my-dify%20--disk%3D40GB or, on my computer, with `ssh exe.dev resize my-dify --disk=40GB`. When I say it's done, run `sudo resize2fs "$(findmnt -no SOURCE /)"`, check `df -h /` again, and carry on. You are done when all of these are true. Check each one yourself: - Dify 1.19 in Docker Compose with its own generated secrets in `~/dify/docker/.env` (mode 600), coming back after a reboot. - The console at `https://.exe.xyz:8080/`, with you as admin, signed in with your exe.dev email. - OpenAI and Anthropic models from exe.dev's LLM gateway, with no API keys. - A published sample chatbot answering through port 8000, which serves apps and the API but not the console. - Workflows that can call your exe.dev integrations, with no credentials stored in Dify. - Nightly backups of the databases, files, and vectors into `~/dify-backups`, with one checked. Read the whole recipe, including the closed details. For initial setup, follow "Install by hand" first, skipping VM creation and SSH but not the disk check, through "Test a backup". The walkthrough at the top is for the owner afterwards. Do not run Restore unless the user asks. Never print ~/dify/docker/.env or ~/dify-admin-password into the chat; tell the owner where the password is. Don't share the VM or make it public: the owner decides. Leave the Helpdesk bot app in place so the owner can see it. The API takes a few minutes to start on a 2-CPU VM; 502 errors from nginx in that time are normal. Finish with the URLs I should open.