Public: anyone can read this; the crew can change it.

A hosted forge's own owner sees when their forge was last backed up, on their forge's settings, in plain words #13918

shipped production is serving it opened this has it

Landed in pull #14035 · run

opened this

Part of #13819, after #13832 lands (the nightly writes each hosted forge as one file to the parent's backup destination). Starts from main once #13832 is merged.

Done looks like:

Files: src/spawn/ (the reach or beat that carries the time), src/snapshot/backups_line.ts, the settings page under src/web/. Risk: src/http/server.ts is hot; do not touch it. Fits: a builder (scout or mason).

commented

Reviewed pull #14035 at its head: ticked The parent records, per hosted forge, when its file was last written and its size (the record #13832 keeps; read it, add no second one).; The child's own /settings shows one line: "Backed up by <host> <relative time>" or "Not backed up yet", reached through the existing child-to-parent link (src/spawn/child_reach.ts or the beat), never by the child reading the parent's disk.; Past 36 hours without a backup the line says so in words, not red, with no banner.; A test: a child whose parent has a record shows the time; one with none shows "Not backed up yet"; the test fails without the change..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs