majordomus web validate
Check the topology's invariants; exit 10 on any error finding
majordomus web validate
Usage
majordomus web validate [OPTIONS]Arguments
| argument | value | default | description |
|---|---|---|---|
| --artifacts | flag | — | Also require every static surface's directory and index to exist |
| --repo | <PATH> | — | Start the search for the repository root here (default: the current directory) (accepted by every subcommand) |
| --discovery | vcs | filesystem | vcs | How declarative files are enumerated (accepted by every subcommand)
|
| --strict | flag | — | Refuse to proceed when any file of the layer carries an error diagnostic (accepted by every subcommand) |
| --share | <DIR> | — | The tool distribution's share directory (kinds.yaml, schemas/); default: $MAJORDOMUS_SHARE, then the repository's own share/, then the one beside the executable (accepted by every subcommand) |
| --format | text | json | text | Output shape (accepted by every subcommand)
|
| --only | <ONLY> | — | Only these surfaces, by discovered id (repeat or separate with commas) (accepted by every subcommand) |
| --exclude | <EXCLUDE> | — | Every surface except these, by discovered id (accepted by every subcommand) |
Examples
-
Check the topology before anything serves or publishes it
Two surfaces claiming one path, a surface nested inside another's subtree, a directory outside the generated root or one that walks out of the repository: each is a named finding with the surface, the value, its source and the fix. Exit 10 on any error finding. `--artifacts` also requires every static surface's directory and index to exist, which is what serving and publishing need.
$ majordomus web validateVerified by the example tests: exits 0; prints no conflict.
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 web validate --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.