@blotout/qinto-cli 0.1.14 → 0.1.15

package/README.md

@@ -268,6 +268,7 @@ are namespaced by its slug, so two apps declaring a `d1` called `ledger` get a d
 | `--reset` | Discard this directory's local installs, variables, secrets and stored data first. |
 | `--tunnel` | Expose the site worker on a fresh `trycloudflare.com` hostname, so a vendor webhook can reach its endpoints. |
 | `--tunnel-name <name>` | Expose it through this named Cloudflare Tunnel instead, for a hostname that survives a restart. |
+| `--tunnel-hours <hours>` | Close the tunnel after this many hours, instead of leaving it open until `app dev` stops. |
 | `--no-input` | Disable all interactive prompts, mounting every app found. |
 
 All four listeners bind `127.0.0.1` only.
@@ -300,9 +301,16 @@ register with the vendor and keeps the loopback one beside it for `curl`.
 
 `cloudflared` is downloaded and cached on first use, unless you already have one on `PATH` or at `CLOUDFLARED_PATH`.
 
-**The tunnel closes after an hour.** It is a public door onto your machine, and an `app dev` left running overnight would hold it
-open until you noticed. `dev` says how long is left every ten minutes; press `a` then Enter to add an hour, up to three hours from
-now. When it closes, the public URL stops being advertised and the loopback one carries on.
+**The tunnel closes when `app dev` does.** It is a public door onto your machine, so quitting `dev` is what shuts it: there is no
+separate clock, and a session left running overnight holds the door open until you stop it. Cloudflare places no limit of its own,
+so a named tunnel will happily run for days.
+
+**`--tunnel-hours <hours>` closes it earlier.** Give it a deadline and `dev` says how long is left every ten minutes; press `a`
+then Enter to add an hour, as often as you like. When it closes, the public URL stops being advertised and the loopback one
+carries on. Fractions work, so `--tunnel-hours 0.5` is half an hour. Nothing caps the number.
+
+For a run measured in days, use `--tunnel-name`. Cloudflare gives `trycloudflare.com` no uptime guarantee and caps it at 200
+in-flight requests, so a quick tunnel is a debug aid rather than something to leave up over a weekend.
 
 **A hostname that survives a restart — `--tunnel-name <name>`.** A quick tunnel is free and needs no account, but its hostname is
 new on every run, so a vendor has to be told the new one each time. A named tunnel keeps one hostname. `dev` reads it from **your