/ 
Developer-Dashboard-3.26
/ docker

NAME

docker - private built-in command wrapper for Developer Dashboard

SYNOPSIS

dashboard docker ...

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 docker compose, dashboard docker list, and the isolated service toggle commands dashboard docker enable and dashboard docker disable. It is the command surface for dashboard-specific Compose discovery, addon/mode handling, dry-run output, service-state reporting, and local disabled.yml marker management.

WHY IT EXISTS

It exists because the docker helper is a built-in dashboard feature, but the command wrapper should stay staged and thin while the compose resolver owns the hard rules.

WHEN TO USE

Use this file when changing docker helper CLI arguments or the handoff into the compose resolver.

HOW TO USE

Users run dashboard docker compose ..., dashboard docker list, dashboard docker enable <service>, or dashboard docker disable <service>. The staged helper forwards the request into the private runtime, which either resolves and execs the final Docker command, reports the effective enabled or disabled state of isolated services, or creates or removes the deepest-layer disabled.yml marker for one isolated service.

WHAT USES IT

It is used by developers who keep compose stacks under dashboard config roots, by docker command tests, and by docs around isolated service folders.

EXAMPLES

Example 1:

dashboard docker compose ps

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

Example 2:

dashboard docker list --disabled

Show only isolated service folders that are currently disabled by the effective layered marker state.

Example 3:

dashboard docker disable green
dashboard docker enable green

Toggle one isolated service without manually creating or deleting the disabled.yml marker file.

Example 4:

~/.developer-dashboard/cli/dd/docker --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.