dsh-terminal-panel

Configuration

Field	Type	Default	Description
trustedHosts	string[]	[]	Extra hostnames (besides loopback) allowed to call the terminal RPC. Required when the web UI is served through a reverse proxy / Tailscale Serve with a real hostname.
sshTarget	string	''	SSH target for command execution, e.g. user@127.0.0.1 or user@my-server. Empty = run commands locally.
sshIdentity	string	~/.ssh/dsh-terminal	SSH identity file used for sshTarget.
sshUser	string	''	SSH username when sshTarget holds a bare host.
sshPassword	string	''	SSH password (delivered via SSH_ASKPASS, never through a pty prompt). Empty = key auth.

Runtime configuration (no restart needed)

Open the 设置 button in either tab (or the first-run setup panel when no target is configured) and set host / username / password / key path — the Terminal and SFTP tabs share this one login. Settings persist in ~/.local/share/dsh-terminal-panel/config.json and take effect on the next command — no cordis.patch.yml edits or service restarts. The panel lists the host's detected addresses (Tailscale IP first) for convenience, and a one-click key initialisation for localhost targets.

SFTP tab

The SFTP tab opens at the target user's home directory and offers:

• directory navigation (click, breadcrumbs, up button) with type/size columns
• a two-column grid, 20 items per page with 上一页/下一页 pager buttons — the panel stays the same height as the terminal (no scrolling)
• download files to the browser (saved via the browser download)
• upload files from the local machine (native file picker)
• new directory and delete (files, and empty directories only)

Transfers run through the system sftp client in batch mode, reusing the terminal's SSH credentials — password auth works without extra prompts (SSH_ASKPASS), key auth is used automatically when configured. The transfer cap is 64 MB per file (the payload crosses the HTTP layer as base64); for larger files use scp/rsync from the terminal tab. In local mode (sshTarget empty) the SFTP tab shows a hint pointing to the settings panel.

SSH mode (why you want it)

When dsh runs sandboxed (bwrap/user namespace — the default on Linux), the process cannot setuid, so sudo is unusable in local mode. In SSH mode the panel keeps one persistent ssh -t session (pseudo-tty) per terminal, exactly like an SSH client:

• commands run in the host namespace of the sshd server → setuid/sudo work
• sudo asks for the password only once per 15 minutes (credential cache is bound to the session's tty, just like a normal SSH terminal)
• cd and environment persist natively inside the session
• interactive programs (top, htop, …) work
• the same mechanism turns the panel into a remote terminal for any SSH host:

- insert:
    - id: dsh-terminal-panel
      name: 'dsh-terminal-panel'
      config:
        trustedHosts:
          - myhost.tailXXXX.ts.net
        sshTarget: user@127.0.0.1      # localhost: sudo works
        # sshTarget: user@remote-host   # or any SSH host
        sshIdentity: /home//.ssh/dsh-terminal

Set up the identity once (one command, no password prompts afterwards):

ssh-keygen -t ed25519 -N "" -f ~/.ssh/dsh-terminal

### Runtime configuration (no restart needed)

Open the **设置** button in either tab (or the first-run setup panel when no
target is configured) and set host / username / password / key path — the
**Terminal and SFTP tabs share this one login**. Settings persist in
`~/.local/share/dsh-terminal-panel/config.json` and take effect on the next
command — no `cordis.patch.yml` edits or service restarts. The panel lists
the host's detected addresses (Tailscale IP first) for convenience, and a
**one-click key initialisation** for localhost targets.