Expand description
borg setup: from a fresh install to a working borg in one guided command.
usage: borg setup [–yes] [–no-vectors] [–harness LIST] [–private DIR…] [–team NAME –paths DIR… [–relay URL|disabled] | –join TICKET [–paths DIR…]] [–home DIR]
Steps, each saying what it will do: what is here (harness CLIs, the model CLI, git identity, an
existing config), the collectives (setup/collectives.rs: personal, team or company, off paths), the
wiring (install::plan: hooks or adapter, and the borg skill). Then one plan: the config diff, the
mesh command, the vector model, the wiring diff, and nothing is written before the engineer confirms
it. After that (setup/steps.rs): the config, with a backup (setup/config.rs: an existing one is only
ever extended); borg mesh init or join; the vector model and indexes, on by default (a failure is a
WARN, never the end of setup); the wiring; an optional import; borg doctor.
Questions read stdin (setup/prompt.rs); without a terminal setup refuses unless --yes takes every
default. Flags answer their question. A second run changes nothing. --home DIR isolates as borg install --home does (super::home_overrides), so a test never reaches a real config or store.
Structs§
- Opts
- The flags; each answers its question.
Constants§
- FLAGS
- The flags (completions.rs lists these).
Functions§
- main
borg setup; the exit code.