Set up Ghost on this VM by following the exe.dev recipe at https://exe.dev/deploy/ghost.md?via=terminal from top to bottom. The recipe's example VM name is my-ghost. This VM's name is the output of `hostname`: use it wherever the recipe writes my-ghost. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Ghost 6 with MySQL 8.4 under Docker Compose, restarting after a reboot. - Ghost's setup screen waiting at your private URL, for you to name the publication and create the owner account. - Ghost Admin open only to exe.dev accounts you list, and signed in by your exe.dev login, even after the site goes public. - Search, member sign-up, comments, and the social web working for visitors once the site is public. - Nightly backups of the database, images, themes, and settings, keeping a week. Read the whole recipe, including the closed details. For initial setup, follow "Install by hand" from top to bottom: Docker, ~/ghost with .env, ghost.env and compose.yaml, the Caddyfile, the owner's email in ~/ghost/caddy/staff-emails (from the reflection integration; if that fails, ask the owner), the exe.dev sign-in adapter, starting Ghost, and the backup timer. Never overwrite an existing .env, ghost.env or staff-emails. Don't fill in Ghost's setup screen yourself, and don't make the site public, add a domain, set up email, Mailgun or Stripe, import anything, or run the Restore or Update instructions during initial setup; the walkthrough sections are for the owner afterwards. Check the login gate on localhost as "Start Ghost" shows. Ghost logs "Failed to send email" until email is set up; that's expected. Do not reboot. Finish with https://.exe.xyz/ghost/ and ask the owner to open it and fill in Ghost's setup screen with the same email they use for exe.dev. Don't paste the database passwords into the chat; say they are in ~/ghost/.env. Finish with the URLs I should open.