fghj wire
fghj wire <entry> [--workspace <path>]Wires a workspace into the currently running fghjd, so it shows up in
the web UI and can have runs started against it.
Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
entry | Git URL of the entry repo. Cloned into the workspace if it isn’t already checked out there. |
--workspace <path> | Workspace root directory holding sibling repo checkouts. Defaults to the current directory. |
Requirements
Section titled “Requirements”fghjd must already be running (sudo fghjd) — wire fails immediately
with a clear error if it can’t find the daemon’s control API.
What it does
Section titled “What it does”- Captures your identity — uid, gid,
$HOME, and your SSH agent socket — if$HOMEis set. This is what lets the root-ownedfghjdclone private repos over SSH on your behalf later, without ever holding your credentials itself; see Persistence & workspace store for the full mechanism. - Sends the entry repo and workspace path to
fghjd’s control API, which registers the workspace (and clones the entry repo if needed). - Prints a link to open the workspace in the UI:
https://fghj.internal/?workspace=<id>.
Run fghj wire again for the same workspace any time your SSH agent has
restarted — the captured identity is refreshed on every call, since the
agent socket it points at is only valid for the login session that was
live when it was captured.
wire only registers the workspace — it doesn’t resolve its graph or
start any containers. Graph resolution happens separately, either via
fghj graph or when the UI loads the workspace. Use the UI’s “Pull all”
and “Start default environment” (or fghj graph to inspect what would be
resolved) as the next steps; see
Quickstart.