| Filename | Latest commit message | Latest commit date |
|---|---|---|
* ci: read release secrets from aws secrets manager * ci: read the linux signing key from hex/release/RELEASE_SIGNING_KEY * ci: hex's own aur and homebrew keys; the signing cert has no password * ci: the signing certificate has no password * ci: use the shared aur and homebrew keys * docs: the shared homebrew deploy key is anomaly-release * docs: the shared homebrew deploy key is anomaly-release * site: own /hex/files, drop the r2 write credential (#1611) * site: own /hex/files for installers, appcast, and dev notes The site build now copies install-linux.sh, install-windows.ps1, and packaging/macos/legacy-appcast.xml into its Worker assets, so the same Worker serves them at /hex/files with the Content-Type and Cache-Control the bucket objects had. The Installers and Legacy appcast workflows, r2-put.sh, and their R2 write credential are gone. The dev notes move to the one-commit dev-notes branch, published by Release's dev-notes job with GITHUB_TOKEN only; the Worker proxies that file at /hex/files/dev-notes.json (falling back to the bucket copy until the first dev release creates the branch) and renders /hex/dev from it. Both site Workers now bind hex-production-files, read-only in code, for the frozen 2.3.1 feeds and artifacts, which lets hex-dev-files go. The Site build runs the installer test and appcast check the removed workflows ran, and the verify job compares the served bytes. * docs: the site owns /hex/files and needs no R2 write credential Hosting, secrets, old clients, and Linux packages describe the built installers and appcast, the dev-notes branch, and the read-only bucket. |
||
| .. | ||
| README.md | ||
| worker.js | ||
| wrangler.jsonc | ||
Legacy redirects (Kit's account)
One Worker, hex-legacy-downloads, takes over Kit's four old Hex hosts:
downloads.hex.kitlangton.dev/*, .com/* 302 → https://anoma.ly/hex/files<path><query> (Hex ≤ 2.3.1 feeds, appcast, files)
hex.kitlangton.dev/*, .com/* 301 → https://anoma.ly/hex/
/download → https://anoma.ly/hex/download/macos-arm64-dmg
/install-linux.sh, /install-windows.ps1 → https://anoma.ly/hex/files/<same name>
The downloads hosts get Worker routes, which run in front of the
hex-releases bucket's custom domains, so the bucket keeps its domains. The
website hosts become Custom Domains of this Worker, taken over from the
hex-voice-site Worker (a hostname has one Worker). Deploy from the
repository root with Kit's Wrangler login:
bunx wrangler@latest deploy --config packaging/legacy-downloads/wrangler.jsonc
Wrangler asks before moving a hostname from hex-voice-site; answer yes. If
it refuses instead (for example because hex-voice-site serves the hosts by
routes, not custom domains), remove hex-voice-site's domains and routes in
the dashboard (Workers & Pages → hex-voice-site → Settings → Domains &
Routes) and deploy again. Nothing is deleted: the bucket and
hex-voice-site stay as they are.
Roll back with bunx wrangler@latest delete --config packaging/legacy-downloads/wrangler.jsonc, then reattach hex.kitlangton.com and .dev to
hex-voice-site in the dashboard (the downloads hosts fall back to the
bucket by themselves) (the bytes there never
changed, so old installs see exactly what they did before).