ergosteur/instaarchive-viewer
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: profiles timer now weekly on the host; Persistent catch-up on restart

Browse Source
This commit is contained in:
ergosteur
2026-10-14 21:25:57 -04:00
parent 832bbdb391
commit 5c3307685a
1 changed files with 15 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TOOLING.md
+15 -7
View File
@@ -131,10 +131,12 @@ scraped profiles, plus 8 single-post live metadata fetches, paced):
*outside* the Resilio-synced, viewer-scanned `archives/` tree; and the *outside* the Resilio-synced, viewer-scanned `archives/` tree; and the
request budget (suggested: ≤40 posts/day, behind the preflight). request budget (suggested: ≤40 posts/day, behind the preflight).
**Open: profiles cadence.** `scripts/systemd/gdl-sync@profiles.timer` says **Host brought in line with the repo (same day).** Every tracked script and unit
weekly with a randomised day (commit 09-14) but the host is still on the on `mattellite` is now byte-identical to `scripts/`, including the weekly
monthly (3rd, 04:00) unit installed 08-22. The repo version was never profiles timer (it had been left monthly since 08-22). Installing it fired an
installed; decide which one is wanted. unplanned catch-up profiles run (see "Scheduling"); that run honoured the
20 h floor (20 of 24 sources skipped) and fetched the four `reels` sources,
~15 min each at the usual pacing.
## 2026-09-14 — a tracked account renamed on Instagram: 0ct0ber19 → heejin ## 2026-09-14 — a tracked account renamed on Instagram: 0ct0ber19 → heejin
@@ -446,7 +448,7 @@ systemctl --user list-timers 'gdl-sync@*'
| unit | schedule | next fire (as installed) | | unit | schedule | next fire (as installed) |
|---|---|---| |---|---|---|
| `gdl-sync@stories.timer` | daily 09:00 | 09:36:45 — the delay is the randomisation working | | `gdl-sync@stories.timer` | daily 09:00 | 09:36:45 — the delay is the randomisation working |
| `gdl-sync@profiles.timer` | 3rd of each month, 04:00 | 04:37:44 | | `gdl-sync@profiles.timer` | weekly (`OnCalendar=weekly`) + `RandomizedDelaySec=6d` — a random day each week, not pinned | 2026-10-24 06:44 (first weekly fire after the 10-14 install) |
| `gdl-sync@full-sweep.timer` | 7th of Jan/Apr/Jul/Oct, 04:00 | 04:42:39 | | `gdl-sync@full-sweep.timer` | 7th of Jan/Apr/Jul/Oct, 04:00 | 04:42:39 |
Unit files are version-controlled in `scripts/systemd/` and installed to Unit files are version-controlled in `scripts/systemd/` and installed to
@@ -454,8 +456,14 @@ Unit files are version-controlled in `scripts/systemd/` and installed to
the mode as its instance name and runs `run-%i.sh` (the fixed-mode wrappers the mode as its instance name and runs `run-%i.sh` (the fixed-mode wrappers
around `gdl-cron.sh` — they carry the Healthchecks URL; see "Healthchecks.io"). around `gdl-cron.sh` — they carry the Healthchecks URL; see "Healthchecks.io").
Before 2026-10-14 it ran `gdl-cron.sh %i` directly, which skipped every ping. Before 2026-10-14 it ran `gdl-cron.sh %i` directly, which skipped every ping.
The profiles timer in the table is as originally installed; the repo's copy is The profiles timer was monthly (3rd, 04:00) until 2026-10-14, when the repo's
weekly (see "2026-10-14" → "Open: profiles cadence"). weekly/random-day unit (committed 09-14 but never installed) was put on the host.
Timer installs: copy the unit to `~/.config/systemd/user/`, `systemctl --user
daemon-reload`, `restart` the timer. **`Persistent=true` makes that restart fire
a catch-up run immediately if a scheduled elapse was missed** (it did, 2026-10-14:
a real profiles run started the moment the timer was restarted). Touch
`~/.local/share/systemd/timers/stamp-gdl-sync@<mode>.timer` first if a run has
just happened by hand and you do not want one.
Three settings are load-bearing: Three settings are load-bearing: