Set up Activepieces on this VM by following the exe.dev recipe at https://exe.dev/deploy/activepieces.md?via=terminal from top to bottom. The recipe's example VM name is my-activepieces. This VM's name is the output of `hostname`: use it wherever the recipe writes my-activepieces. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Always-on Activepieces with PostgreSQL and Redis, back after a reboot. - A builder only you can open, and webhooks you can make public with one command. - An example flow file that summarizes a webhook with AI and emails you. - Nightly database backups, with a restore checked before you start. Read the whole recipe, including the closed details. For initial setup, follow "Install by hand" first: containers, nginx gate, backup cron, and scratch restore check. The opening walkthrough is for the owner afterwards. Do not run the later Restore or Update instructions during initial setup. Work as exedev in ~/activepieces. Never overwrite an existing ~/activepieces/.env: it holds the encryption key for saved connections. Do not create the Activepieces account; the owner does that in the browser, and the first account becomes the admin. Leave public sharing off. Verify the three gate checks at localhost:8000 (302, 403, 200). Verify docker.service is enabled and every container uses unless-stopped; do not reboot. Finish with the builder URL, a link to the example flow file, and the OPTIONAL command the owner can run on their own computer to let webhooks and MCP clients in: ssh exe.dev share set-public my-activepieces Finish with the URLs I should open.