mitchell/hamlab
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 14 Wiki Activity

README: the public install one-liner

Browse Source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Mitchell-Johnson
2026-09-19 10:57:31 -07:00
co-authored by Claude Fable 5.1
parent e75fa0d759
commit 3c0c504e35
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+7 -4
View File
@@ -20,12 +20,15 @@ sudo ./hamlab-linux-amd64 install # that's the whole install
or, from wherever `make release` output is served: or, from wherever `make release` output is served:
```sh ```sh
curl -fsSL "$HAMLAB_URL/install.sh" | sh curl -fsSL https://hamlab-demo.bigham.dev/install.sh | sh # asks: user, address, HTTPS, firewall, password
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 -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 `install.sh` is a wizard when there is a terminal (it reads answers from `/dev/tty`, so it
`hamlab install`; run it beside the `hamlab-linux-*` files and it installs offline. 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`: `hamlab install`:
- copies the binary to `/usr/local/bin` (`--prefix`), atomically; - copies the binary to `/usr/local/bin` (`--prefix`), atomically;