From 0d04aefa0c5e7956cb2dbc80596910cbe53136bf Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 25 Sep 2026 07:36:19 +0000 Subject: publish-apk: allow publishing from another machine over ssh The host gate stopped the Fedora laptop publishing at all, which left a build made there with nowhere to go. It now takes PUBLISH_SSH and sends the file to the real host instead. The gate itself is unchanged in spirit: without PUBLISH_SSH a build from elsewhere is still refused, because the failure it guards against is writing to a local path that merely looks like the deploy host's. Two tests cover that -- the error names the way out, and a failed remote publish never falls back to writing locally. Transfers land on a temporary name and move into place only once complete, and the remote copy is hash-compared against the source before the served bytes are checked. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B --- README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'README.md') diff --git a/README.md b/README.md index 6e8fc59..160c5ae 100644 --- a/README.md +++ b/README.md @@ -144,3 +144,15 @@ a full copy of a large APK in a public directory, and four publishes in one even ``` publish-apk app/build/outputs/apk/debug/app-debug.apk listen-debug.apk ``` + +From another machine — the laptop — send it to the real host rather than +writing locally: + +``` +PUBLISH_SSH=user@tungsten publish-apk app/build/outputs/apk/debug/app-debug.apk listen-debug.apk +``` + +The host check still applies: without `PUBLISH_SSH` a build from elsewhere is +refused outright, and with it the file is copied to a temporary name and moved +into place only once the transfer completes. The remote copy is hash-compared +against the source and the served bytes are checked, same as a local publish. -- cgit v1.2.3