Documentation
dumont
One filesystem over local disk, object stores, Google Drive, archives, and HTTP — driven from the command line. The same verbs everywhere; data flows between unlike stores with a single command.
“All that is visible must grow beyond itself, and extend into the realm of the invisible.” — Dumont, keeper of the I/O Tower
Data flows between worlds
Start here
Build the binary, copy your first file, and take the zero-config end-to-end tour.
One filesystem over local disk, S3-compatible stores, Bunny, archives, and HTTP — each honest about what it can do.
Name remotes in config, reference secrets by env/file/keychain, and preflight with `remote test`.
Browse
Commands
Every verb — cp, mv, sync, ls, cat, stat, rm — its flags, and what it does.
Recipes
Cross-store copies, incremental mirrors, peeking inside archives.
Architecture
The conformance spine, honest capabilities, and composable decorators.
Addressing
How a URI scheme maps to a backend, and the built-in schemes.
Backends
The capability matrix and a page per store.
FAQ
What dumont is not, and why.
One gateway. Every store.
Copy, move, and mirror between local disk, object stores, archives, and HTTP — with honest capabilities and no silent corruption.