Custom Desktop Commander Development

Turn repeated checks into named actions

We start with the questions operators ask every day: which service is down, where disk space went, which certificate needs attention and whether a scheduled job ran. Each panel has a defined command or API, expected output and failure state.

A health panel can collect information without granting permission to restart a service. Controls for changes appear separately with their target, required permission and confirmation.

Keep file work beside the active server

A commander workspace can combine directory browsing, search, text editing, transfers and checksums. The selected host and path remain visible. File saves can preserve a previous copy, detect changed content and return a clear write result.

Database, container and service modules are selected for the operating environment. We agree what each one may read or change. The available system permissions remain part of the design.

The DSDillon implementation

DSDillon Terminal includes its own Commander workspace with panels for identity, health, services, processes, logs, storage and other infrastructure checks. It shares the selected server with the terminal and file tools. The case study follows that implementation.

A graphical remote desktop with screen sharing and pointer control is a separate integration. Specify it where the work requires a visual application. The third party product named Desktop Commander is an independent product; the DSDillon workspace is our own implementation.

Demonstrate the operator decisions

We test missing permissions, unavailable commands, empty results, a disconnected host and a failed maintenance action. A panel should report the outcome of its operation and keep the operator on the correct target.