majordomus mesh build-cache env
The sccache client configuration for the store this node selected, as a script `eval` reads: local disk first, the store second only when it is healthy now, the credential by file path only
majordomus mesh build-cache env
Usage
majordomus mesh build-cache env [OPTIONS]Arguments
| argument | value | default | description |
|---|---|---|---|
| --sccache | <SCCACHE> | — | The sccache executable to ask (a name on PATH or a path); `sccache` when unset |
| --node-file | <NODE_FILE> | — | The node file that names the store this node offers or knows; `~/.config/majordomus/build-cache.json` when unset |
| --credentials | <CREDENTIALS> | — | The AWS-format credential file, mode 0600, profile `mesh-build-cache`; `~/.config/mesh-build-cache/credentials` when unset |
| --format | text | json | text | `text` is the script an `eval` reads; `json` is the full answer, with its reason
|
Examples
-
The sccache client of this node, derived
The environment the process that starts the sccache server should have: local disk first and the selected store second, only when sccache has the chain, a credential file of mode 0600 exists and the store answers now; otherwise nothing, and the comment line says which condition did not hold. The credential is a file path, never a key. `--format json` gives the whole answer.
$ majordomus mesh build-cache env --sccache no-such-sccacheWhat it asserts: exits 0; prints build cache: local-only.
Tested by apps/majordomus-cli/tests/cli_examples.rs, which runs the command against the built executable and asserts what the page states.
Where this comes from
Declared once in apps/majordomus-cli/src/cli.rs: clap for the structure, typed Rust metadata beside it for the examples. This page, majordomus mesh build-cache env --help, docs/generated/cli.md and docs/generated/cli.json are projections of that one declaration.
The whole command line on one page: the registry's command-line page. The task lifecycle (init, start, finish, doctor, ...) belongs to the shell tool, a different program: Commands and its specification.