Set up Appsmith on this VM by following the exe.dev recipe at https://exe.dev/deploy/appsmith.md?via=terminal from top to bottom. The recipe's example VM name is my-appsmith. This VM's name is the output of `hostname`: use it wherever the recipe writes my-appsmith. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Appsmith Community 2.7.2 behind exe.dev login, back after a reboot. - A PostgreSQL database for your tools, with a sample orders table to build on. - Email from Appsmith and from your apps through exe.dev, with no mail service. - Appsmith's AI Assistant and your apps' AI queries on exe.dev's LLM gateway, with no API key. - Nightly backups of your apps, the tools database, and Appsmith's keys. Read the whole recipe, including closed details, and follow "Install by hand" first. The opening walkthrough is for the owner afterwards. Do not create the Appsmith admin account: whoever finishes setup first becomes the admin, so leave it to the owner and don't share the VM before they have. Don't connect datasources, invite people, or send email. Do not run the later Restore or Update instructions, or the ToolJet and Budibase installs. Work as exedev in ~/appsmith. Verify docker.service is enabled, all four containers are up with appsmith and tools-db healthy, curl -fs localhost:8000/api/v1/health says "All systems are up", and the llm check prints a list of models. Check that the backup timer is enabled and the first archive lists appsmith-backup.tar.gz and tools.dump. Finish with https://.exe.xyz/, invite the owner to create their admin account and follow "Build an admin page", and tell them how to read the tools-db password (the grep command in that section). Finish with the URLs I should open.