メインコンテンツへスキップ

AFS

Get started with AFS

Inspect the installed AFS command surface before choosing a provider, mount, or path.

Start by checking the runtime you are actually using. Commands and provider availability can vary between ARC releases.

bash
arc --version
arc afs --help

Verified on arc 2.0.0-beta.28:

text
2.0.0-beta.28
text
arc afs

AFS file system operations (ls, read, write, stat, exec, search, mount…)

Commands:
  arc afs ls [path]               List directory contents        [aliases: list]
  arc afs read <path>             Read file content               [aliases: cat]
  arc afs write <path> [content]  Write content to file
  arc afs delete <path>           Delete file or directory         [aliases: rm]
  arc afs stat <path>             Get file or directory info
  arc afs exec <executable_path>  Execute an action
  arc afs explain [topic]         Explain AFS concepts or paths
  arc afs search <path> <query>   Search for content within an AFS path
                                                           [aliases: grep, find]
  arc afs mount                   Mount management

These commands only report the installed version and available AFS command surface. They do not invent mounts or storage for you.

What to do next

  1. Prefer read-only inspection first: ls, stat, read, explain, and search on paths that already exist on your instance.
  2. Do not begin with write, delete, or exec against an unknown path. A path is meaningful only after the target instance has a provider and mount configuration.
  3. Continue with local inspection for a verified walk of a running instance.
  4. Read the core contract before relying on an operation in application code.

Related CLI man page

The full arc afs flag reference lives in the arc-cli board. This AFS board explains the path, capability, and provider contract; it does not restate every CLI flag.

Environment notes

  • arc afs talks to the local AFS surface available to your CLI session (typically a running daemon). Paths and mounts on your machine are not universal defaults.
  • mount list can print provider URIs that include credentials. Treat that output as secret material; redact before sharing or pasting into issues.
  • Adding a mount with arc afs mount add may report success while subsequent ls/read still fail on that path. Confirm with stat/ls before documenting a new mount as usable. See Runtime boundaries.