Set up Vaultwarden on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/vaultwarden.md?via=terminal from top to bottom. The recipe's example VM name is my-vaultwarden. This VM's name is the output of `hostname`: use it wherever the recipe writes my-vaultwarden. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Vaultwarden running with signups closed, ready for you to invite yourself. - The admin panel on a private port behind exe.dev login, with an Argon2-hashed admin password. - A public front door for Bitwarden apps that refuses /admin and keeps live sync working. - Nightly backups of the database, attachments and keys, with one checked in a scratch copy. - Everything starts again after a reboot. Read the whole recipe, including the closed details. For initial setup, follow "Install by hand" first, skipping VM creation and SSH: Docker and argon2, the admin password and settings, the Compose stack, nginx, the backup timer, and the backup test. The walkthrough at the top is for the owner afterwards. Work as exedev in ~/vaultwarden. Never overwrite an existing vaultwarden.env or admin-password. Don't create Vaultwarden accounts, invite anyone, set up SMTP or Tailscale, or change DOMAIN. Don't run Restore or Update. You can't make the VM public from the VM; leave that to the owner, and don't ask them to until you're done. Verify docker.service is enabled, the container uses unless-stopped, /alive answers on localhost:8000 and localhost:8080, /admin returns 404 on localhost:8000 and 200 on localhost:8080, the backup timer is enabled and the backup test passes. Do not reboot. Never paste the admin password into the chat; say it's in ~/vaultwarden/admin-password. Finish by pointing the owner to "Choose who can reach it" and "Make your account". Finish with the URLs I should open.