JakeBreath/J621
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Let push_desktop.sh copy the feed to a remote deploy checkout

Browse Source 
--host user@server:/path syncs deploy/data/desktop to the same path on the
server with rsync, falling back to tar over ssh when the server has no
rsync. A failed transfer now exits non-zero instead of claiming the feed is
live.
This commit is contained in:
JakeBreath
2026-09-20 20:22:59 -05:00
parent 1c6735cde8
commit f4b534aa09
2 changed files with 57 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy/README.md
+7 -3
View File
@@ -152,12 +152,16 @@ Push the desktop builds and their update metadata to the frontend's feed:
```bash
./push_desktop.sh # Linux packages (deb + pacman)
./push_desktop.sh --win # also cross-build the NSIS installer (wine)
./push_desktop.sh --win --host jakerasp:/home/jake/servers/J621
```
Artifacts land in `deploy/data/desktop/`, which the frontend nginx mounts
read-only and serves at `/desktop/`. The desktop app's "Check for updates…"
menu item reads `latest-linux.yml` / `latest.yml` from there (see
`desktop/README.md`). Backend-only composes have no frontend, so no feed.
read-only and serves at `/desktop/`. `--host` also copies that directory to
a remote deploy checkout — rsync when both ends have it, tar over ssh when
the server does not — so the build can run here and prod only receives the
files. The desktop app's "Check for updates…" menu item reads
`latest-linux.yml` / `latest.yml` from there (see `desktop/README.md`).
Backend-only composes have no frontend, so no feed.
## Scheduled jobs