Set up Backup to exe.dev on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/backup-to-exe.md?via=terminal from top to bottom. The recipe's example VM name is my-backups. This VM's name is the output of `hostname`: use it wherever the recipe writes my-backups. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - rest-server 0.14 in append-only mode on port 8000, storing repositories in ~/restic, started at boot. - The VM private, so only clients with an exe.dev VM token or VM-to-VM integration, or you over SSH, reach the repositories. - A daily check that emails you when any repository has gone two days without a new snapshot, or the disk is 80% full. - A test repository created, backed up to, refused a delete, restored, and removed again. Read the whole recipe, including the closed details. For initial setup, follow "Install by hand" first, skipping VM creation and SSH. The walkthrough at the top is for the owner afterwards. Work as exedev. Install exactly the pinned versions and check their checksums. Leave the VM private. Never put a repository password on this VM except the throwaway one in "Test it", and delete that test repository afterwards as the steps say. You can't make VM tokens from the VM; leave tokens and client setup to the owner. Don't run Update or Restore. Verify rest-server.service and backup-watch.timer are enabled and active, port 8000 answers, the append-only test refused the delete, and backup-watch.sh --dry-run prints ok. Do not reboot. 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 ssh-key generate-api-key --vm=my-backups --label=backup-laptop --exp=1y --json | jq -r .token