dsh-wei-sitecontrol

Websites and HTTP services produced by DSH Agents tend to end up scattered across work directories with no shared registry, no version history, and no reliable way to know which one is holding a port. dsh-wei-sitecontrol collects them into a single dependency-aware registry and layers real operations tooling on top: start/stop/restart with logging, built-in isomorphic-git commit and push (no system git required), ssh2-based scheduled deployment with a rollback-capable release mode, and a live monitor showing CPU, memory, disk, per-site process usage, and running task names.

On the deployment side, the description-driven provisioning flow stands out. Hand the plugin a natural-language environment note plus a PEM directory and it parses the IP, SSH port, and service type, connects to the server to read the actual Tomcat or nginx configuration, back-fills uploadDir, configFile, appHome, and every other publishing field, then stores a timestamped verified snapshot. From there, manual publishes, scheduled runs, and release rollbacks all share the same code path, each step recorded, pending schedules re-bound after a DSH restart. The key vault exposes only fingerprints; private key material never crosses an API boundary or log line.

The plugin fits developers who use DSH Agents to produce batches of lightweight sites or internal HTTP services and want multi-site version control plus one-click rollback without maintaining a fleet of systemd units or hand-rolled deploy scripts. Once installed, a sidebar panel appears and the Agent gains a set of site_* tools; the rest is schedule-driven.