dsh-db-connections

Overview

Named database connections for DeepSeek Harness: configure MySQL in a settings page, then refer to them by name in chat (for example "query 128"). Read-only by default, with writes opt-in per connection.

README / EN

Package documentation

Registry summary

Named database connections for DeepSeek Harness: configure MySQL in a settings page, then refer to them by name in chat (for example "query 128"). Read-only by default, with writes opt-in per connection.

dsh.pub verifies the pinned bundle contract, runtime facts, and distribution semantics. The complete README remains in the source repository.

Read the full README on GitHub

LIMITATIONS

Known limitations

- MySQL / MariaDB only. Adding PostgreSQL means a second pool and read-only path in `src/registry.js`, plus a `SUPPORTED_DRIVERS` entry in `src/config.js`. - The read-only guarantee relies on the server supporting `START TRANSACTION READ ONLY` (MySQL 5.6+, MariaDB 10.0+). On older servers, use a read-only account instead. - Schema answers are read live from `information_schema` on every `db_schema` call — no cache, so what you see is current. - The client-plugin roster is scanned at **app startup**, so a first install (or any new client half) needs one desktop restart before the page appears. Later configuration and code changes hot-reload without a restart. - The page's **Test** button probes the *saved* connection, because pools are built from saved names. Change the settings, save, then test. - The profile references this directory by link, so **do not delete, rename, or move it**; to relocate, `dsh plugin remove` and `add` again.

dsh-db-connections