Set up Chroma on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/chroma.md?via=terminal from top to bottom. The recipe's example VM name is my-chroma. This VM's name is the output of `hostname`: use it wherever the recipe writes my-chroma. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Chroma 1.5.9 in Docker, started at boot, listening on localhost only, its data in `~/chroma/data`. - The API and its Swagger docs at `https://.exe.xyz/`, private behind exe.dev login. - An `exe-docs` collection of exe.dev's documentation, embedded with no API key, and a script that answers questions from it. - A script that copies collections from Chroma Cloud or another Chroma server and checks the copy. - Nightly backups, one restored and checked. Read the whole recipe, including the closed details. For initial setup, follow "Install by hand" from top to bottom, skipping VM creation: Docker, the config and Compose files, starting Chroma, the scripts and the exe-docs collection, the backup timer, and the restore test. The walkthrough sections are for the owner afterwards: don't run chroma-migrate.py, ask for a Chroma Cloud key, set up Tailscale, integrations or Qdrant, or run the Restore or Update instructions during initial setup. Remove only the chroma-restore-test container and /tmp/chroma-restore that the restore test creates. Leave the VM private and do not reboot. Finish with https://.exe.xyz/docs/ and the answer ask.py gives to "How do I make my VM public?". 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 my-chroma.exe.xyz 'cd chroma && uv run ask.py "How do I make my VM public?"' ssh exe.dev ssh-key generate-api-key --vm=my-chroma --label=chroma --exp=90d