brintos-fs

What it does

brintos mounts a brintOS repository's filesystem as a local drive over FUSE, backed by the machine's filesystem API. Once mounted, the repository looks like an ordinary folder: list it, edit files, run builds, and copy trees in and out with any tool you already use.

Writes use an asynchronous write-back model — the same shape as the Linux page cache — so bulk copies and fsync-heavy workloads stay fast while changes drain to the server in the background. The mount is read-write when you have write access to the repository, and read-only otherwise (anonymous/public mounts are always read-only).

Mounting a drive

brintos login                          # or omit for public repos
mkdir -p /tmp/demo
brintos mount <owner>/<repo> /tmp/demo   # read-only unless you have write access; Ctrl-C to unmount

Mount flags

--server URL — API server origin (default https://brintos.io).

--snapshot NAME — for an image repo, mount a specific top-level snapshot instead of the active one (normally live).

--squash — present all files as the mounting user instead of the stored uid/gid.

--allow-other — let other users access the mount (needs user_allow_other in /etc/fuse.conf).

--no-seed — skip the initial full tree sync and populate lazily on access.

--prefetch — after seeding, warm the content cache with every small file (faster cold boot/run, more bandwidth up front).

--read-only — force a read-only mount even when you have write access.

See the source repository for the full reference.