mainplane-server

Overview ¶

mainplane-server is the server binary: the harness, and the credentials that reach it. A new key prints its token once; the table holds only hashes. A machine joins with the network name and the device code.

mainplane-server up   <config.json>
mainplane-server install [config.json]    and again at every boot, as a service, behind a quick tunnel; asks for sudo or admin itself;
                                          with none, keeps an installed config; prints the join lines, with the network name and
                                          device code made at the first install, and a new api key "default", the ones before it kept
mainplane-server tunnel <url> <cloudflared token> | quick   the installed harness moves to the user's own tunnel, or back
mainplane-server key  new <name> | revoke <name> | list    on the installed harness, as root
mainplane-server join [cycle]             the join lines, with a new device code after cycle
mainplane-server rename <name>            the network name
mainplane-server update [version]         the installed harness becomes release version, the latest stable by default
mainplane-server uninstall                the service, binary and admin worker go; sessions and the auth table stay
mainplane-server version