Oregami
Repositories/oxedyne/fe2o3

fe2o3_jdat/tests/datmap_strict.rs

4 operations, oldest first

created by r1870400018:76228, which is this file's identity for as long as the history lasts, whatever it is later renamed to

read the file · who wrote it · compare two states

An operation carries no clock of its own. Each row is therefore dated by the first mark written after it by the same replica, which is one copy of the repository, and that mark is where the command that wrote the operation ended.

+ signed and verified, ? signed by a key this forge does not carry, - unsigned

OperationAuthorWhatWhen
+r1870400018:76228replica 1870400018created fe2o3_jdat/tests/datmap_strict.rs21 days ago under "fe2o3_steel, fe2o3_shield: state_root and secret_root beside app_root, read as a cfg::Roots (prefix STEEL or SHIELD). Steel writes its vhost databases, certificates and ACME cache, mail spool, admin-audit.log, server log (new server key log_dir_rel, ./www/logs when absent) and shell log under the state root, and reads its wallet, health token, alert credentials, DKIM keys, mail users file and every {file:} reference under the secret root; the www trees stay under the app root. Shield puts its database and logs under the state root and its wallet under the secret root. With neither key a config resolves exactly as before, the wallet still beside the config. ServerContext::with_roots carries the two roots to the cert loader and the mail listeners. tests/app_roots: three tests, red (no field state_root, no method roots) before, green after. D-20261030-22 SRV-LAYOUT U3"
+r1870400018:76229replica 1870400018inserted 2.1 KiB21 days ago under "fe2o3_steel, fe2o3_shield: state_root and secret_root beside app_root, read as a cfg::Roots (prefix STEEL or SHIELD). Steel writes its vhost databases, certificates and ACME cache, mail spool, admin-audit.log, server log (new server key log_dir_rel, ./www/logs when absent) and shell log under the state root, and reads its wallet, health token, alert credentials, DKIM keys, mail users file and every {file:} reference under the secret root; the www trees stay under the app root. Shield puts its database and logs under the state root and its wallet under the secret root. With neither key a config resolves exactly as before, the wallet still beside the config. ServerContext::with_roots carries the two roots to the cert loader and the mail listeners. tests/app_roots: three tests, red (no field state_root, no method roots) before, green after. D-20261030-22 SRV-LAYOUT U3"
+r1870400018:77091replica 1870400018inserted 78 bytes8 days ago under a mark the tool wrote
+r1870400018:77092replica 1870400018inserted 639 bytes8 days ago under a mark the tool wrote