CLI reference

What helm prints about itself, verbatim. Build it from a clone with go build -o bin/helm ./cmd/helm; the first release will ship it.

helm

usage: helm <command> [arguments]

commands:
  validate <manifest.yaml>...   validate one or more studio manifests
  validate -theme <dir>         lint a studio's stylesheets against helm-css (-strict to fail)
  dev [-f helmstudio.yaml]      run a studio against the embedded provider, no daemon

helm validate

usage: helm validate [--json] [-criteria] [-theme <dir> [-strict]] [<manifest.yaml|registry-entry.yaml>...]

helm dev

usage: helm dev [-f helmstudio.yaml] [-addr 127.0.0.1:0] [-link weight=dir]... [-venv dir]
  -addr string
    	loopback address for the studio API (port 0 picks a free one) (default "127.0.0.1:0")
  -f string
    	the studio's manifest (default "helmstudio.yaml")
  -link value
    	use an existing weights directory: -link <weight>=<directory> (repeatable)
  -venv string
    	the Python environment a studio that declares python: runs in (default: the active one, $VIRTUAL_ENV)

Not built

The design names four more commands, and none of them exists yet: helm studio init (scaffold a studio), helm test (the smoke harness certification runs), helm doctor (which provider a studio would get, and why) and helm adopt. They belong to no milestone yet. helm dev's design also names --fixtures and --fail, which are not built either.