## pyre admin hubs build

Build (or rebuild) a hub from the primary

### Synopsis

The primary preflights the machine (can it log in with its onboarding
key, sudo, DNS, UDP 51820, disk) and refuses to start on a FAIL, naming
it: a machine that has not run the block from "onboard-key" is the usual
one. Then it installs the hub, detached; "build-status" follows it.

```
pyre admin hubs build <hub> [flags]
```

### Examples

```
  pyre admin hubs build hub-e
  pyre admin hubs build hub-e --rebuild   # the machine ran Pyre before
  pyre admin hubs build hub-e --force     # skip the preflight
```

### Options

```
      --force     skip the primary's preflight
  -h, --help      help for build
      --rebuild   rebuild a hub that was built before
```

### 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