comp bootstrap¶

NAME¶

phyware comp bootstrap — initialise and inspect PhyComp platform state.

SYNOPSIS¶

phyware comp bootstrap init   [OPTIONS]
phyware comp bootstrap status [OPTIONS]

DESCRIPTION¶

init¶

Creates the admin PhyComp tenant, default rule set, and seed credentials. Idempotent.

status¶

Reports whether the PhyComp platform has been bootstrapped.

OPTIONS¶

Flag	Type	Required	Default	Env
`--url`	string	No	`http://localhost:8001`	`PHYCOMP_URL`
`--api-key`	string	No	—	`PHYCOMP_API_KEY`
`--output`	enum	No	`table`	—

| --admin-email | string | No | — | — | | --force | bool | No | false | — |

ARGUMENTS¶

None.

INPUT¶

None.

OUTPUT¶

Field	Type	Description
`status`	string	`bootstrapped` / `not_bootstrapped`
`healthy`	bool	All PhyComp services healthy

EXIT CODES¶

Code	Meaning
`0`	Success
`1`	Generic / connection error
`2`	Authentication / authorisation error
`3`	Resource not found
`4`	Validation error
`5`	Server-side error

EXAMPLES¶

# Check PhyComp bootstrap status
phyware comp bootstrap status

# Bootstrap PhyComp
phyware comp bootstrap init

# Bootstrap with explicit admin email
phyware comp bootstrap init --admin-email admin@example.com

# Force re-bootstrap
phyware comp bootstrap init --force

# Get status as JSON
phyware comp bootstrap status --output json

AGENT NOTES¶

Always run status before init in automated pipelines. Run init after cloud bootstrap init since PhyComp depends on a running PhyCloud instance. Requires direct service access on first bootstrap.

ERRORS¶

Code	Message	Remediation
`ALREADY_DONE`	Already bootstrapped	Use `--force` to re-run
`SERVER_ERROR`	PhyComp unavailable	Check PhyComp service health