NAME

d2 - first-class short entrypoint for the Developer Dashboard CLI

SYNOPSIS

d2 version
d2 doctor
d2 upgrade [--dry-run]
d2 collector status housekeeper
d2 ask "How do I list collectors?"

DESCRIPTION

d2 is a real, installed command that runs the same dashboard CLI as the longer dashboard command. It re-execs its sibling dashboard entrypoint in the same bin directory with the same arguments, so anything you can do with dashboard you can do with d2.

PURPOSE

This entrypoint gives operators a short, real command name for the dashboard CLI that behaves exactly like dashboard, so d2 version or d2 collector status work the same as their dashboard equivalents without typing the full command name.

WHY IT EXISTS

It exists so d2 is a genuine installed command rather than only a shell function defined by the shell bootstrap. As a real entrypoint in the same bin directory as dashboard, d2 is available in non-interactive scripts, cron jobs, and fresh shells that never sourced the dashboard shell integration, which a shell-only alias could not guarantee.

WHEN TO USE

Use this file when changing how the short d2 command locates and re-enters the main dashboard entrypoint, or when adjusting how d2 is packaged as an installed executable.

HOW TO USE

Run d2 followed by any dashboard subcommand and arguments, exactly as you would run dashboard. The script resolves its sibling dashboard file from its own install directory and re-execs it under the same Perl interpreter, so the full command surface, hooks, and shell bootstrap output are identical.

WHAT USES IT

It is used by operators who prefer the short command name, by shell bootstrap tab-completion that also completes d2, and by CLI smoke tests that exercise the short entrypoint.

EXAMPLES

Example 1:

d2 version

Print the dashboard version through the short real command.

Example 2:

d2 ask --codex "Explain this stack trace"

Run any dashboard subcommand through d2 exactly as through dashboard.

Example 3:

prove -lv t/05-cli-smoke.t t/40-install-bootstrap.t

Rerun the focused CLI-smoke and install-bootstrap tests after changing the short entrypoint.

Example 4:

prove -lr t

Verify the short entrypoint inside the complete repository suite.