Add local file conflict metadata
This commit is contained in:
parent
e1f36ffafb
commit
20c88af800
13 changed files with 673 additions and 15 deletions
|
|
@ -94,9 +94,12 @@ 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. Iroh-blobs,
|
||||
providers, encrypted blobs, richer cache policies, cross-node file roots, and
|
||||
sync conflict handling are future work.
|
||||
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. Iroh-blobs, providers, encrypted
|
||||
blobs, richer cache policies, cross-node file roots, and automatic conflict
|
||||
detection are future work.
|
||||
|
||||
`geth-db` currently registers local SQLite paths as DB resources and reports
|
||||
local-only sync status plus a read-only SQLite schema summary/hash. It also
|
||||
|
|
|
|||
Loading…
Reference in a new issue