Skip to content

ChatShare

ChatShare places Dufs inside ChatArch-owned paths and operational boundaries. The CLI owns trusted installation, configuration, service lifecycle, and streaming upload/directory queries from a new machine securely connected to an existing share; Dufs owns HTTP/WebDAV file serving.

  • Get started

    Connect a new machine to an existing share, or deploy Dufs on the server, then publish the first file.

    Open Quick Start

  • Inspect the CLI

    Browse commands by install, configuration, service, and sharing responsibilities.

    Open the CLI Tree

  • Understand the runtime

    Review version pinning, storage layout, the systemd user service, and rollback.

    Open Dufs Runtime

  • Confirm the security boundary

    Review authentication, loopback defaults, permissions, and explicit exclusions.

    Open Security and Boundaries

Current capabilities

Responsibility ChatShare Dufs
Binary selection and integrity Selects the release asset and verifies its GitHub sha256 digest Publishes official release assets
Configuration and state Owns state under ~/.chatarch/chatshare/ Reads generated YAML configuration
Service lifecycle Linux systemd --user Foreground file-server process
File publication and queries Copies locally with atomic replacement, or streams to a configured remote, lists directories, and builds URLs Serves files and accepts HTTP/WebDAV uploads
Authentication Collects and stores the shared credential safely HTTP Digest Auth path permissions

Out of scope

ChatShare does not currently provide accounts, per-file capability links, expiry, download counts, per-file revocation, object storage, or multi-host orchestration. Dufs's direct-path model does not imply those semantics.