Add authorized file-root sync
This commit is contained in:
parent
0e3ca7e80a
commit
1caaedda90
7 changed files with 489 additions and 11 deletions
|
|
@ -127,10 +127,14 @@ blobs. The CAS crate can build deterministic tree objects that describe
|
|||
directories, files, executable bits, and file blob hashes; those tree objects
|
||||
are stored as CAS blobs. The daemon can register local file roots and scan them
|
||||
into CAS tree objects while reporting create/update/delete/rename changes. These
|
||||
scans are local metadata only and never overwrite the working tree. The daemon
|
||||
also has durable local file-conflict records with explicit resolution choices;
|
||||
future cross-node file sync will create those records automatically instead of
|
||||
silently applying ambiguous remote changes.
|
||||
scans are local metadata only and never overwrite the working tree. A peer can
|
||||
pull authorized remote file-root tree metadata with `geth cas root sync <node>
|
||||
<name>` when it has `cas.fetch` on `resource:cas-tree:<name>`; sync imports the
|
||||
remote CAS tree bytes and records a peer-qualified remote root whose path is
|
||||
`remote:<node>:<name>` without applying files. The daemon also has durable local
|
||||
file-conflict records with
|
||||
explicit resolution choices; future cross-node file sync will create those
|
||||
records automatically instead of silently applying ambiguous remote changes.
|
||||
|
||||
As a bootstrap network path, `geth cas fetch <node-id> <hash>` dials an
|
||||
imported signed peer card over the daemon-owned Iroh control ALPN. The serving
|
||||
|
|
|
|||
Loading…
Reference in a new issue