Commands: Carrying it

These commands take the record somewhere else: an export with a manifest, a bundle another repository clones, and a check of this machine against the runs.

Generated from the --help of rabbit-brain 0.8.0.

rb export

write the project’s page with a hashed manifest, readable without rb; with --with-record, the record too, as a portable bundle

usage: rb export [-h] [--json] [--out OUT] [--zip] [--with-record] [--url URL]
                 [--no-repo] [--replace]

options:
  -h, --help     show this help message and exit
  --json         print one JSON object (the envelope) instead of text
  --out OUT      where to write it (default rb-export/ beside .rb/)
  --zip          write one zip file instead of a directory (default rb-
                 export.zip)
  --with-record  carry the record too, for rb clone: its files and log keep
                 who made each write, agent sessions and the user's words
  --url URL      with --with-record, the public address this will be served
                 from: the page then opens with the exact rb clone command,
                 and a directory export also contains bundle.zip
  --no-repo      leave the code repository's address out of the manifest and
                 page
  --replace      with --zip, write over a file at --out that rb did not write
                 (default: refused, the file left as it is)

rb clone

start your own line of work from an exported bundle: the structure arrives inherited, and nothing counts until reproduced here

usage: rb clone [-h] [--json] [--code ADDRESS] source [dest]

positional arguments:
  source          a bundle rb export --with-record wrote: a directory, a .zip,
                  or its address
  dest            where to create it (default ./<project id>)

options:
  -h, --help      show this help message and exit
  --json          print one JSON object (the envelope) instead of text
  --code ADDRESS  where to get the code the runs need, in place of the
                  repository the bundle names (a copy you can reach, or one
                  the bundle does not name): the record lands in a checkout of
                  it at the bundle's commit

rb env

the environment: check this machine against the record’s runs and any env.* settings

usage: rb env [-h] [--json] <command> ...

positional arguments:
  <command>
    check     compare; differences are said, never fatal (exit 0)

options:
  -h, --help  show this help message and exit
  --json      print one JSON object (the envelope) instead of text

rb env check

usage: rb env check [-h] [--json]

options:
  -h, --help  show this help message and exit
  --json      print one JSON object (the envelope) instead of text