NAME

dashboard - command-line entrypoint for Developer Dashboard

SYNOPSIS

dashboard help
dashboard init
dashboard update
dashboard ps1 [--jobs N] [--cwd PATH] [--mode compact|extended] [--color]
dashboard paths
dashboard path list
dashboard path resolve <name>
dashboard path add <name> <path>
dashboard path del <name>
dashboard path locate <term...>
dashboard path project-root
dashboard of [--print] [--line N] [--editor CMD] <file|scope> [pattern...]
dashboard open-file [--print] [--line N] [--editor CMD] <file|scope> [pattern...]
dashboard pjq [path] [file]
dashboard pyq [path] [file]
dashboard ptomq [path] [file]
dashboard pjp [path] [file]
dashboard encode < input.txt
dashboard decode < token.txt
dashboard indicator set <name> <label> <icon> <status>
dashboard indicator list
dashboard indicator refresh-core [cwd]
dashboard collector write-result <name> <exit_code>
dashboard collector status <name>
dashboard collector list
dashboard collector job <name>
dashboard collector output <name>
dashboard collector inspect <name>
dashboard collector log
dashboard collector run <name>
dashboard collector start <name>
dashboard collector stop <name>
dashboard collector restart <name>
dashboard config init
dashboard config show
dashboard auth add-user <username> <password>
dashboard auth list-users
dashboard auth remove-user <username>
dashboard page new [id] [title]
dashboard page save <id>
dashboard page list
dashboard page show <id>
dashboard page encode [id]
dashboard page decode [token]
dashboard page urls <id>
dashboard page render [id|file]
dashboard page source <id|token>
dashboard action run <page_id> <action_id>
dashboard docker compose [--addon NAME] [--mode NAME] [--service NAME] [--project DIR] [--dry-run] <compose-args...>
dashboard serve [logs [-f] [-n N]|workers <N>] [--host HOST] [--port PORT] [--workers N] [--foreground]
dashboard stop
dashboard restart [--host HOST] [--port PORT] [--workers N]
dashboard shell [bash]
dashboard <custom-subcommand> [args...]

DESCRIPTION

Developer Dashboard provides a project-neutral local developer cockpit with:

• saved and transient dashboard pages

• file-backed collectors and indicators

• prompt rendering for PS1

• background web-service lifecycle management

• trusted and safer page actions

• config-backed providers and aliases

• project-aware Docker Compose resolution

• user CLI extensions loaded from ~/.developer-dashboard/cli

• built-in dashboard of / dashboard open-file resolution for direct files, file:line references, Perl module names, Java class names, and recursive pattern matching

• built-in dashboard pjq / dashboard pyq / dashboard ptomq / dashboard pjp parsing for JSON, YAML, TOML, and Java properties input

Unknown top-level subcommands can be provided by executable files under ~/.developer-dashboard/cli. For example, dashboard foobar a b will exec ~/.developer-dashboard/cli/foobar with a b as argv, while preserving stdin, stdout, and stderr.

Per-command hook files can also be placed in either ~/.developer-dashboard/cli/<command> or ~/.developer-dashboard/cli/<command>.d. Executable files in that directory are run in sorted filename order before the real command runs, their stdout and stderr stream live to the terminal while still being accumulated into $ENV{RESULT} as JSON, and non-executable files are skipped. Built-in commands such as dashboard pjq use the same hook location. A directory-backed custom command may provide its real executable as ~/.developer-dashboard/cli/<command>/run; that runner receives the final $ENV{RESULT} value after the hook files finish. If a subcommand does not have a built-in implementation, the real command can be supplied as ~/.developer-dashboard/cli/<command> or ~/.developer-dashboard/cli/<command>/run.

Run dashboard with no arguments for the quick synopsis, or dashboard help for the full POD-backed manual.