diff --git a/README.md b/README.md
index 71f1856..6f9820d 100644
--- a/README.md
+++ b/README.md
@@ -20,12 +20,15 @@ sudo ./hamlab-linux-amd64 install          # that's the whole install
 or, from wherever `make release` output is served:
 
 ```sh
-curl -fsSL "$HAMLAB_URL/install.sh" | sh
-curl -fsSL "$HAMLAB_URL/install.sh" | sh -s -- --listen 0.0.0.0:8100 --tls auto
+curl -fsSL https://hamlab-demo.bigham.dev/install.sh | sh        # asks: user, address, HTTPS, firewall, password
+curl -fsSL https://hamlab-demo.bigham.dev/install.sh | sh -s -- --yes                              # asks nothing, all defaults
+curl -fsSL https://hamlab-demo.bigham.dev/install.sh | sh -s -- --listen 0.0.0.0:8100 --tls auto   # flags go to `hamlab install`
 ```
 
-`install.sh` only picks the build for `uname -m`, checks it against `SHA256SUMS` and runs
-`hamlab install`; run it beside the `hamlab-linux-*` files and it installs offline.
+`install.sh` is a wizard when there is a terminal (it reads answers from `/dev/tty`, so it
+works piped from curl) and silent otherwise. Either way it picks the build for `uname -m`,
+checks it against `SHA256SUMS` and runs `hamlab install`; re-running it upgrades in place.
+`make publish` puts a release where that URL serves it (`HAMLAB_URL` points it elsewhere); run it beside the `hamlab-linux-*` files and it installs offline.
 `hamlab install`:
 
 - copies the binary to `/usr/local/bin` (`--prefix`), atomically;