ownduck/dsh-custom-env
Manages $DSH_HOME/.env from Settings → Environment, hot-applies values to the running Host and syncs them to the OS user environment.
Provider keys and tool tokens for DSH usually live in $DSH_HOME/.env, which means editing a dotfile by hand and restarting to see whether the value took. This adds a Settings → Environment page that does CRUD on that file (creating it if missing), hot-applies the values to the running Host process, and pushes them into the OS user environment so other tools inherit them. Rejecting bootstrap names is the careful part: it stops you from saving a PATH or DSH_* value that would be silently ignored at boot. It also shows which dsh is on your user PATH versus the launcher that started this Host, with an Install button when they differ.
Install
dsh plugin --profile web add github:ownduck/dsh-custom-envThe repository ships a ready-to-run lib/, so nothing needs publishing to install from GitHub — the README calls the GitHub form the recommended path while it is unpublished on npm. It suggests verifying with dsh --profile web --dump-config, which should contain a # == dsh-custom-env layer and a custom-env plugin row. The examples use the PowerShell-configured console it documents for UTF-8 output on Windows; the desktop profile is managed by the Electron app, so use its in-app plugin manager or edit that profile's package.json instead.
Compatibility
On save, values are applied to the Host's process.env immediately and synced to the Windows and macOS user environment, with the README noting that new terminals pick up OS changes only after they start. Linux user-env sync is stated as unsupported. Bootstrap names (PATH, DSH_*, XDG_* and friends) are rejected because app boot will not load them from .env anyway.
Details
- Repo: ownduck/dsh-custom-env
- Category: Infrastructure & Deployment
- Stars: 0
- Version: installed from the repository (not published to npm per the README)
Alternatives
ddtcorex/dsh-maestro-review · leoswing/dsh-tool-grafana · ddtcorex/dsh-maestro-core