## pyre admin hubs bootstrap

Build the very first hub (no primary exists yet)

### Synopsis

Three steps. Without flags: prints the block to paste on the future hub
as the management user (passwordless sudo, this control plane's
provisioning key for that one machine, ssh keys-only: root and password
login off) -- the key is
minted for the address you name, so check the spelling first. Then
--start: the control plane logs in with that key, installs the hub and
revokes the key. "bootstrap-status" follows the build; when it reports
ok the machine has registered itself as the primary, under --name (the
address's first label without it). Nothing to "add". Bare machine only:
the build removes any previous Pyre installation on it. --rebuild mints
a fresh key for a machine already built here.

```
pyre admin hubs bootstrap [flags]
```

### Examples

```
  pyre admin hubs bootstrap --address hub-a.example.com                       # 1. print what to paste on the machine
  pyre admin hubs bootstrap --address hub-a.example.com --start --name hub-a  # 2. build it from here
  pyre admin hubs bootstrap-status --address hub-a.example.com                # 3. follow; ok = registered as the primary
```

### Options

```
      --address string   the future hub's hostname or IP (required)
  -h, --help             help for bootstrap
      --name string      with --start: the name the hub is registered under when the build finishes (default: the address's first label)
      --rebuild          a machine already built here: mint a fresh provisioning key, and with --start reinstall it from scratch
      --start            start the build (after the block was pasted on the machine)
```

### Options inherited from parent commands

```
      --api string       API base URL (default from the profile, or https://api.pyredata.io)
      --ca-cert string   PEM file with an extra CA to trust (self-hosted managers)
      --insecure         skip TLS certificate verification (lab use only)
  -o, --output string    output format: table, json or plain (default "table")
      --profile string   config profile to use (see: pyre config)
  -q, --quiet            print results only, no notices
      --token string     API token (default from the profile; prefer PYRE_TOKEN in scripts)
  -y, --yes              answer yes to every confirmation (for scripts)
```

### SEE ALSO

* [pyre admin hubs](pyre_admin_hubs.md)	 - Add, build, promote, demote and remove hubs