majordomus mesh build-cache
The mesh build cache: what each dependency install and build directory is cached under
majordomus mesh build-cache
Usage
majordomus mesh build-cache <COMMAND>This command groups the commands below and is not run on its own, so it carries no example.
Commands
- majordomus mesh build-cache key Every lockfile the repository tracks, with the key its install or build directory is cached under: schema version, platform, toolchain and input digest
- majordomus mesh build-cache ensure Restore a dependency install or a cold cargo build directory from the local level or this node's store, verified by its digest; on a miss run the command and save what it left. MAJORDOMUS_BUILD_CACHE=off bypasses every level
- 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 provision Plan what this host still owes as a cache provider, or with --apply bring it there as root; idempotent, no secret reported
Arguments
Arguments: none.
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 --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.