https://deevnet.github.io/deevnet-filesync/docs/development/Recent content in Development on Deevnet FileSyncHugoen-ushttps://deevnet.github.io/deevnet-filesync/docs/development/tooling/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-filesync/docs/development/tooling/<h1 id="build-tooling"> Build Tooling <a class="anchor" href="#build-tooling">#</a> </h1> <p><strong>Status:</strong> Tracking list. Development so far happens on the Deevnet build server. This page records every tool added there <strong>beyond what the Ansible-built builder provides</strong>, so that it can later become a <code>filesync</code> builder role, or be handled in another way.</p> <table> <thead> <tr> <th>Tool</th> <th>Version installed</th> <th>Installed how</th> <th>Needed for</th> <th>Since</th> </tr> </thead> <tbody> <tr> <td><code>rust</code>, <code>cargo</code></td> <td>1.99.0 (Fedora 43 packages)</td> <td><code>dnf install rust cargo</code></td> <td>Building the Rust workspace</td> <td>Prototype</td> </tr> <tr> <td><code>clippy</code>, <code>rustfmt</code></td> <td>1.99.0 (Fedora 43 packages)</td> <td><code>dnf install clippy rustfmt</code></td> <td>Linting and formatting</td> <td>Prototype</td> </tr> <tr> <td>MinIO container image</td> <td><code>quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Z</code></td> <td>Already present in local podman storage; public pulls of MinIO images now fail</td> <td>A disposable local S3 endpoint for end-to-end tests</td> <td>Prototype</td> </tr> <tr> <td><code>hugo</code> (extended)</td> <td>0.140.1</td> <td>Already present on the build server</td> <td>Building the docs site</td> <td>Docs</td> </tr> </tbody> </table> <p>Rust crates are fetched by Cargo from crates.io at build time and pinned in <code>Cargo.lock</code>. They are project dependencies, not host tooling, so they are not listed here.</p>https://deevnet.github.io/deevnet-filesync/docs/development/prototype/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-filesync/docs/development/prototype/<h1 id="prototype"> Prototype <a class="anchor" href="#prototype">#</a> </h1> <p><strong>Status:</strong> Working (2026-10-15). This is the <a href="https://deevnet.github.io/deevnet-filesync/deevnet-filesync/docs/roadmap/#phase-p-prototype">Phase P</a> prototype: the <code>filesync</code> CLI and the <code>filesync-core</code> library, in <code>crates/</code>.</p> <h2 id="what-it-does"> What it does <a class="anchor" href="#what-it-does">#</a> </h2> <ul> <li>Encrypted hub on any S3-compatible store (tested against MinIO), or on a local directory.</li> <li>Roots, mounted at any path, with a different path on each device.</li> <li><code>status</code>, <code>sync</code> (push now), and <code>pull</code> (pull now), plus <code>run --interval N</code> for unattended polling.</li> <li>Three-way sync: changes flow both ways, conflicting edits keep both versions as a conflict copy, and an edit beats a delete.</li> <li>Receive-only mounts (<code>mount --receive-only</code>).</li> <li>Portable-name checks (Windows-invalid names and case/normalization collisions are skipped, with a warning), symlinks skipped, a per-file size limit (100 MiB by default).</li> <li>Version history (<code>history</code>) and restore of a whole root or one path from any snapshot (<code>restore</code>).</li> <li>Refuses to sync a root whose folder is missing, or to propagate &ldquo;everything deleted&rdquo; without <code>--allow-mass-delete</code>.</li> </ul> <h2 id="what-it-deliberately-does-not-do-yet"> What it deliberately does not do (yet) <a class="anchor" href="#what-it-deliberately-does-not-do-yet">#</a> </h2> <table> <thead> <tr> <th>Shortcut</th> <th>Final design</th> </tr> </thead> <tbody> <tr> <td>One shared hub key, copied to each device by hand</td> <td>PKI device identity, enrollment, revocation (SEC-7, SEC-9..12)</td> </tr> <tr> <td>Whole-file blobs, no chunking</td> <td>Content-defined chunking (PERF-3)</td> </tr> <tr> <td>Blob sizes visible to the hub</td> <td>Padding or chunking to hide sizes (SEC-2)</td> </tr> <tr> <td>Every snapshot lists every path</td> <td>Incremental snapshots or a compacted index</td> </tr> <tr> <td>No garbage collection or retention</td> <td>VER-2, VER-6, HUB-7</td> </tr> <tr> <td>Polling only (<code>run --interval</code>)</td> <td>Filesystem watching plus rescans (LNX-7)</td> </tr> <tr> <td>One static S3 credential, with delete rights</td> <td>Per-device, least-privilege credentials (HUB-6, HUB-7)</td> </tr> </tbody> </table> <h2 id="build-and-test"> Build and test <a class="anchor" href="#build-and-test">#</a> </h2> <div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>cargo build --release <span style="color:#75715e"># target/release/filesync</span> </span></span><span style="display:flex;"><span>cargo test <span style="color:#75715e"># unit tests, plus two-device tests on a directory hub</span> </span></span></code></pre></div><h2 id="try-it-with-two-devices-on-one-machine"> Try it with two &ldquo;devices&rdquo; on one machine <a class="anchor" href="#try-it-with-two-devices-on-one-machine">#</a> </h2> <p>Each device is a config directory plus a state directory. A directory hub needs no credentials:</p>