dsh-restart-control

DSH deployments span a wide range of environments: Windows launched manually, macOS started from Terminal, Linux managed by systemd or PM2. Restarting means switching back to a CLI each time, and a careless move can leave duplicate DSH processes running. dsh-restart-control brings the task into the DSH Web settings page: an administrator confirms twice in the browser, and the plugin restarts DSH following the safety rules of the current environment—no terminal, no root, sudo, or shell-execution privileges required.

The core design revolves around the word "controlled." Three strategies are selected via the DSH_RESTART_CONTROL_MODE environment variable. In auto mode the plugin detects the runtime and picks the right path. In portable mode a built-in helper waits for the old process to exit, then relaunches DSH using the original executable, arguments, working directory, and environment. In external mode the plugin simply exits with code 75 and lets systemd, PM2, Docker, or Windows Service handle the restart according to their own policies. Browser payloads are restricted to a fixed set of state fields; shell commands, file paths, and arbitrary parameters are rejected. The host validates request freshness, enforces a cooldown window, and verifies a fresh bootId before marking the restart as successful.

This plugin suits any team that wants to restart DSH safely from the web: developers running DSH manually on Windows or macOS, sysadmins managing Linux instances under systemd or PM2, and DevOps engineers orchestrating containers with Docker all benefit from a single, auditable, cross-platform restart experience.