The service detail pane shows the image and state, what the service depends on, which sites use it, its env vars, and the action row. The dashboard shows all of that plus four more facets, the published ports, the client tools it exposes as host shims and which are on, the tuning values in effect, and the entities it holds, buckets, indexes or collections depending on the service. Someone debugging a connection in the terminal cannot see which port the service is actually published on without leaving for the CLI.
All four read as rows. Ports, tuning and entities are pure information. The client tools are information plus one reversible toggle, turning a shim on or off writes or removes a file in the bin dir and flipping it back undoes it exactly, so it sits alongside start, stop and restart rather than beyond them.
Entities want a light touch, listing what is there is informative, creating or dropping one is not, so the pane lists and the CLI keeps the rest.
The service detail pane shows the image and state, what the service depends on, which sites use it, its env vars, and the action row. The dashboard shows all of that plus four more facets, the published ports, the client tools it exposes as host shims and which are on, the tuning values in effect, and the entities it holds, buckets, indexes or collections depending on the service. Someone debugging a connection in the terminal cannot see which port the service is actually published on without leaving for the CLI.
All four read as rows. Ports, tuning and entities are pure information. The client tools are information plus one reversible toggle, turning a shim on or off writes or removes a file in the bin dir and flipping it back undoes it exactly, so it sits alongside start, stop and restart rather than beyond them.
Entities want a light touch, listing what is there is informative, creating or dropping one is not, so the pane lists and the CLI keeps the rest.