Set up Medusa on this VM by following the exe.dev recipe at https://exe.dev/deploy/medusa.md?via=terminal from top to bottom. The recipe's example VM name is my-medusa. This VM's name is the output of `hostname`: use it wherever the recipe writes my-medusa. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Medusa 2.23 with its admin and worker on port 9000, and the Next.js starter storefront behind nginx on port 8000, restarting after a reboot. - PostgreSQL and Redis on the VM, and uploads in ~/medusa-data, backed up every night and before every deploy. - A storefront you can make public in one command, while the admin and admin API stay on a private port behind exe.dev login. - An email to you through exe.dev for every order, with no mail provider, and a note in the admin's notification bell. - ~/store as the one place to change the server and the storefront, and ~/bin/medusa-deploy to build, back up, migrate, and switch, with rollback. Read the whole recipe, including the closed details. For initial setup, follow "Set up by hand" from "Install the tools" to the end of it, as exedev; the walkthrough sections are for the owner afterwards. Use the exact versions given. Never overwrite an existing ~/medusa.env or ~/storefront.env. Don't make the VM public and don't run Restore or Update. Do not reboot. If a build fails, read its output and fix what you can; never commit secrets. At the end, create an admin invite for the owner's exe.dev email (the reflection email) as in "Sign in to the admin", and give the owner the invite link and https://.exe.xyz/. Don't paste anything from ~/medusa.env into the chat. 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): ssh exe.dev share set-public my-medusa