Skip to content

ph setup ​

One-time setup: Tara, login, harness, GitHub/GitLab connection, checks: ph setup

This page is generated from ph setup --help by npm run gen in site/, so do not edit it by hand.

text
Usage: ph setup [--tara <url>] [--harness <name>] [--yes]

One-time setup, safe to run again (finished steps are skipped) ​

1. Tara: address and public key (prints the fingerprint, asks whether to trust it) ​

text
1. Tara: address and public key (prints the fingerprint, asks whether to trust it)

2. Log in to Tara in the browser ​

text
2. Log in to Tara in the browser

3. Project (run inside a git repo with an origin): pick a harness and run ph init; if phillip.lock pins versions this Tara no longer has, ​

text
3. Project (run inside a git repo with an origin): pick a harness and run ph init; if phillip.lock pins versions this Tara no longer has,
   offers to run ph tara upgrade (--yes accepts; without a terminal it prints the command and stops)

4. Connect GitHub/GitLab (ph connect) ​

text
4. Connect GitHub/GitLab (ph connect)

5. Check: ph forge doctor (✗ is required; ⚠ is optional, such as Ryoma, Collector, Guardrails: it suggests a fix and does not fail setup) ​

text
5. Check: ph forge doctor (✗ is required; ⚠ is optional, such as Ryoma, Collector, Guardrails: it suggests a fix and does not fail setup)

--tara <url> ​

text
--tara <url>       Tara address (skipped if the install script already wrote it)

--harness <name> ​

text
--harness <name>   Harness to apply to the project (skips the prompt)

--yes ​

text
--yes              No prompts: trust the Tara key, accept community resources on init, use the existing gh/glab/git token (ph connect --reuse)