← Components

Demo tree

Code and build · tree manifest. On a deployment this row is a control; the demo shows the row with the reading its source supports.

Evidence

Running

manifest 6996879ff411 (205 files)

Built

manifest 6996879ff411; www-demo/app/components_data.php excluded

Latest known

the same tree, hashed at build

Source

git ls-files www-demo | git hash-object --stdin-paths

Checked

2 hours ago

Cadence

none — record only

Mode

record only

State

current

Backup unit

n/a: the demo records its own tree and nothing else.

Recovery

n/a: a demo host is redeployed from its payload, not recovered by this screen.

The five steps

Plan, back up, apply, verify, recover — in record only mode. On a deployment each step runs, is verified and lands on the audit trail; every component on the demo is current, so every step reads done.

1. ✓ done Plan The deploy script hashes every file git tracks under www-demo and writes the manifest into the payload; there is nothing to confirm.
2. ✓ done Back up Nothing is backed up here; the previous payload under deploy/ is the way back, by hand.
3. ✓ done Apply Nothing is applied; the demo ships by hand and the manifest travels with it.
4. ✓ done Verify The screen compares the manifest it carries with the tree it is served from and shows the result.
5. ✓ done Recover Nothing is recovered here; a tree that does not match its manifest is redeployed.

Every row behind this reading (205)

History

Applies and recoveries of this row, from the update journal. On a deployment every apply and every recovery lands here as it completes.

No apply or recovery recorded for this row. The demo's journal holds one completed update, of Running image.

Acknowledge: keep as is until <date> because <reason> — on a deployment this line is a form, audited as system.component_acknowledged; the demo shows the words.

← Back to Components