TANGLED_HANDLE=<fill-this-in>
KNOT_CONTACT_EMAIL=<fill-this-in>

Set up Tangled knot on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/tangled.md from top to bottom.

The values at the top of this message are mine:
- TANGLED_HANDLE: the handle you sign in to tangled.org with: `alice.tngl.sh` if you signed up there with an email, or your Bluesky handle; it becomes the knot's owner
- KNOT_CONTACT_EMAIL: an email address the knot publishes for abuse reports and questions
Ask me for any that still say <fill-this-in> before you need them.

The recipe's example VM name is my-knot. This VM's name is the output of `hostname`: use it wherever the recipe writes my-knot. Skip the step that creates the VM; you are on it.

You are done when all of these are true. Check each one yourself:
- Tangled's knot 1.20 at `https://my-knot.exe.xyz/`, owned by your atproto DID, restarted on failure and after a reboot.
- `/xrpc/_health` and `/.well-known/did.json` answering on the knot's address, ready to add on tangled.org.
- `knot-member add <handle>` on the VM, to let other people create repositories on the knot.
- The knot's SSH server on port 2222, for pushes through exe.dev's SSH.
- Repositories, keys and settings in `/var/lib/knot` and `/etc/knot`, backed up nightly to `/var/backups/knot`, with a restore checked.

Read the whole recipe, closed details included, and follow "Set up by
hand" in order, skipping VM creation; the walkthrough above it is for
the owner. Resolve TANGLED_HANDLE to a DID as written and stop if it
doesn't resolve. The build takes 15-25 minutes: run it in the
background. On an existing VM, ask before replacing anything on port
8000. Don't make the VM public yourself: the owner runs `ssh exe.dev
share set-public` on their computer. Show the owner the master key's
line from /etc/knot/knot.env once, and tell them to store it off the
VM. Finish with the `set-public` command, then "Add the knot on
tangled.org" and "Push over SSH" for the owner to follow.

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-knot
  ssh my-knot.exe.xyz sudo systemctl restart knot.service