Set up SeaweedFS on this VM by following the exe.dev recipe at https://exe.dev/deploy/seaweedfs.md?via=terminal from top to bottom. The recipe's example VM name is my-seaweedfs. This VM's name is the output of `hostname`: use it wherever the recipe writes my-seaweedfs. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - SeaweedFS 4.54 running `weed mini` under systemd, with its data in /var/lib/seaweedfs, back after a reboot. - An S3 API that refuses requests without a valid key, and an admin key in /etc/seaweedfs/seaweedfs.env. - An `app` bucket and a key that can use only that bucket, in `~/seaweedfs/app.env`, checked with put, get, a multipart upload and a presigned URL. - The admin UI at the VM's private URL, behind exe.dev login and its own password. - The VM still private, with the choices for reaching S3 from elsewhere explained. Read the whole recipe, including the closed details. For initial setup, follow "Install by hand" from top to bottom: the weed binary, the keys file, the systemd service, the app bucket and key, and the s3-check.py run. The walkthrough sections are for the owner afterwards: don't make the VM or the S3 port public, create VM tokens, set up Tailscale, backups, mounts, or more VMs, and don't run the Update or Restore instructions during initial setup. Never overwrite an existing /etc/seaweedfs/seaweedfs.env or ~/seaweedfs/app.env. Leave the VM private and do not reboot. Don't paste keys or passwords into the chat; say where they are. 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-seaweedfs.exe.xyz cat seaweedfs/app.env ssh my-seaweedfs.exe.xyz sudo cat /etc/seaweedfs/seaweedfs.env