Deploy recipe restarts mac app

This commit is contained in:
Ian Gulliver
2026-10-17 08:41:26 -07:00
parent aea1a81b2c
commit ceb441a132
+1
View File
@@ -15,6 +15,7 @@ When asked to deploy, do exactly this, from the worktree root:
1. `go generate ./web`, if anything under `web/src/` or `api/openapi.yaml` changed. 1. `go generate ./web`, if anything under `web/src/` or `api/openapi.yaml` changed.
2. `go install ./cmd/byre && launchctl kickstart -k gui/$(id -u)/run.fc.byre`, always as that one command, never `go install` on its own, and always the last action of the turn. 2. `go install ./cmd/byre && launchctl kickstart -k gui/$(id -u)/run.fc.byre`, always as that one command, never `go install` on its own, and always the last action of the turn.
3. When you resume, confirm it came up: read the tail of `~/Library/Logs/byre.log`, and `GET /api/admin/status` through the `tailscale serve` URL (`tailscale serve status` shows it). Report what you deployed and what you checked. 3. When you resume, confirm it came up: read the tail of `~/Library/Logs/byre.log`, and `GET /api/admin/status` through the `tailscale serve` URL (`tailscale serve status` shows it). Report what you deployed and what you checked.
4. Once the service is confirmed healthy, rebuild and relaunch the macOS app: run `mac/bundle.sh`, then `pkill -x Byre` to quit every running byre app, whichever worktree it was built from (it exits 1 when none is running, which is fine), then `open mac/.build/byre.app`. The app reads its server address from the shared `run.fc.byre.mac` defaults, so the new build reconnects to prod with no setup. Report that the app was rebuilt and relaunched.
What to expect: What to expect: