Documentation
¶
Overview ¶
mainplane is the device binary: the worker, and the plainest connector.
mainplane the TUI; mainplane <session id> opens on that session; on the harness's machine
with no provider yet, the quickstart
mainplane quickstart the TUI on the quickstart, which the server install opens
mainplane worker [<network> <device code>] make this machine a worker, named by its hostname
mainplane install <network> <device code> and again at every boot, as a service; asks for sudo or UAC, code still runs as you
mainplane login <api key> find the harness, remember it and the key in ~/.mainplane/login.json, and become its release
mainplane uninstall remove the worker service and the CLI; ~/.mainplane stays
mainplane status the harness logged in to, and this worker on the mesh from its local socket
mainplane version the release this binary was built from
mainplane <verb> ... one verb per harness route, see cli.go
Click to show internal directories.
Click to hide internal directories.