xswt442-cmd/dsh-instance-manager

dsh-instance-manager is a DSH Web instance-manager plugin that adds a menu icon at the bottom-left of the workspace, immediately to the right of the sidebar, after installation. The plugin lists every locally visible dsh web instance on its own row, showing port, PID, uptime, session count, resident memory, and version, with the current instance pinned to the top and remaining rows sorted by ascending port; once peers are configured, the same panel can also query instances on remote machines along with their logs and sessions. Installation is supported through dsh plugin --profile web add dsh-instance-manager, a plain npm install dsh-instance-manager, or dsh plugin --profile web add github:xswt442-cmd/dsh-instance-manager, and because the bundle only activates after it is registered to the web profile, a DSH Web restart is required for the plugin to take effect on first install.

The typical workflow begins by configuring the live and startup sections, then managing instance lifecycles through either the panel or the Agent tools instance_list, instance_start, instance_stop, instance_logs, and instance_sessions: leaving the port empty picks the first free port within the first segment of portRange, while a requested port that is already occupied is reported as an error rather than silently rerouted, and clicking a row's :port enters that instance using a launch token exchanged on demand that never reaches panel state or bookmarks. Stop operations cover single, current, or all local instances, remote rows are read-only and never participate in stop-all, remote functionality depends on bidirectional peer wiring together with a Fleet token that should only be granted to trusted devices, and both Agent-side and desktop launches pass --no-open so background instances stay windowless. The plugin targets developers and operators who juggle multiple DSH Web instances and need unified cross-host visibility, health inspection, and lifecycle control from a single in-app surface.

Dependencies require Node.js ≥ 20 and DSH ≥ 0.1.5-rc.3 (configuration reading shifts to the entry's own config from 0.1.7-rc.1 onward), and the project is released under the MIT license; every field has a matching DSHIM_* environment variable that is layered between user values and schema defaults, resolving after the host's actual read source but before the built-in defaults. Limits include at most 1024 ports per portRange segment and at most 16 peers, remote requests must always carry a bearer over non-loopback addresses, and from DSH 0.1.0-rc.7 onward browser APIs and event streams reuse Connection signed cookies so the plugin's own guard is bypassed on those paths. Pre-submit checks are npm test, npm run docs:check, and npm pack --dry-run, and on first run operators must supply fleetToken and portRange correctly or remote features are silently disabled while the local panel continues to function.