/ 
Developer-Dashboard-3.58
/ serve

NAME

serve - private built-in command wrapper for Developer Dashboard

SYNOPSIS

dashboard serve ...

DESCRIPTION

This private helper is staged under ~/.developer-dashboard/cli/dd/ so the public dashboard entrypoint can stay a thin switchboard.

PURPOSE

This staged helper exposes dashboard serve, the command that starts the dashboard web server in background or foreground mode and can also print or follow logs and worker information, including the persisted browser-only --no-editor/--no-endit and --no-indicators/--no-indicator modes.

WHY IT EXISTS

It exists because serving the dashboard is a built-in runtime operation, but the CLI wrapper should remain staged and thin while the runtime and web server modules own process and transport behavior.

WHEN TO USE

Use this file when changing serve CLI flags, foreground/background behavior, or the handoff into the runtime manager and web server stack.

HOW TO USE

Users run dashboard serve or one of its log/worker submodes. The staged helper forwards the request into the private runtime, which launches or inspects the managed web process and persists serve settings such as the read-only --no-editor/--no-endit browser mode and the top-right-chrome --no-indicators/--no-indicator browser mode.

WHAT USES IT

It is used by local dashboard startup, by integration smoke runs, and by runtime manager tests that verify background serving and log inspection.

EXAMPLES

Example 1:

dashboard serve --foreground

Run the public built-in command path that stages or re-enters this helper.

Example 2:

dashboard serve --no-editor

Start the dashboard in read-only browser mode so bookmark edit and source routes stay blocked.

Example 3:

dashboard serve --no-indicators

Start the dashboard with the top-right browser context and indicator strip removed while leaving the left-side page chrome and terminal prompt behavior unchanged.

Example 4:

~/.developer-dashboard/cli/dd/serve --help

Inspect the staged helper directly after dashboard init or helper extraction has populated the home runtime.

Example 5:

prove -lv t/05-cli-smoke.t t/30-dashboard-loader.t

Rerun the focused staged-helper and thin-loader tests after changing helper dispatch behavior.

Example 6:

prove -lr t

Verify that the helper still behaves correctly inside the complete repository suite.