Set up Strapi on this VM by following the exe.dev recipe at https://exe.dev/deploy/strapi.md?via=terminal from top to bottom. The recipe's example VM name is my-strapi. This VM's name is the output of `hostname`: use it wherever the recipe writes my-strapi. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Strapi 5 on Node.js 26 and PostgreSQL 17, under systemd, back after a reboot. - An admin panel on port 8337 that only people signed in to exe.dev can reach. - A content API on port 8000 that is safe to make public, with drafts kept private. - An example Article type with a cover image, ready to edit or delete. - Strapi's email (password resets, invitations) sent through exe.dev, no SMTP server. - Nightly backups of the database, uploads, and secrets, and a tested restore. Read the whole recipe, including closed details, and follow "Install by hand" first. The opening walkthrough is for the owner afterwards. Work as exedev in ~/cms. Do not make the VM public, set up S3, add the LLM summaries, or run the later Restore, Update, or Troubleshooting steps. Never print the contents of ~/cms/.env into the chat. Leave the admin registration to the owner: don't create an admin user. Verify each step as the recipe says: strapi.service is enabled and /_health answers 204 on port 8337, port 8000 answers 404 for /admin and 403 for /api/articles, and the backup test restores the database. Finish with the admin URL on port 8337 and the content API URL. Finish with the URLs I should open.