- commit
- 8c0e0fcf472c9fbe113aeaac5bd62cb1ce4e70e6
- parent
- c7b1950eba39c0a9a48314585a669d43ebe11dc4
- author
- dami <gazey55@gmail.com>
| M | deploy.md | 10 | +++++++++- |
@@ -14,7 +14,15 @@ One app on Fly.io, one machine, and a nightly job on slate:
1414 `deno task push-day --tomorrow --host https://mosaic-daily.fly.dev1515 --rings all --jobs $(nproc) --band 24` with the `mosaic_push_token`1616 secret; caches live under `/var/lib/mosaic-nightly` on the agent (repo17- is trusted for volumes). Woodpecker repo id 4, cron id 9. `/status`17+ is trusted for volumes). Woodpecker repo id 4, cron id 9. Measured:18+ pipeline #5 (2026-08-27, `--jobs 16` on slate's 16 cores) built the19+ engine in 17 s and generated the whole G=1000 field (197 tiles + 1220+ rings, 22 MB) in 1098 s; the Fly performance-4x fallback took 3019 s21+ for the same field. Jobs are now `cores/3` (5 on slate: a chunk uses22+ 1.5-2.6 cores, more parallel chunks only oversubscribe); #6 with jobs23+ 5 hit the agent's generator cache (0 s), so the first real comparison24+ is the next cron run (2026-08-28 05:00 UTC, generating 2026-08-29) —25+ read its `generated in` line in the push step's log. `/status`1826 on the app reports whether tomorrow's field has arrived.1927 - **If slate is down**, push from any machine with the engine built:2028 `MOSAIC_PUSH_TOKEN=... deno task push-day <date> --host