@froststarinquire/dsh-remote-access-web

Configuration

The row honors the deployment env (all optional; provider defaults to none):

Env	Meaning
DSH_REMOTE_ACCESS_PROVIDER	Tunnel backend; frp mounts a tunnel through an frpc-compatible client, absent keeps the schema default none (inert). The field is deployment-configurable so other backends can be added
DSH_REMOTE_ACCESS_FRPC_PATH	absolute path to frpc (or compatible); required when provider is frp
DSH_REMOTE_ACCESS_FRP_ARGS	frp fast-start value for -f, i.e. :
DSH_REMOTE_ACCESS_CWD	working directory for the tunnel child; defaults to the process cwd
DSH_REMOTE_ACCESS_PUBLIC_URL	public URL surfaced once the tunnel is up; the plugin's trustedAuthority() canonicalizes it for the trust fence

When provider is frp but frpcPath/frpArgs are absent, the owning plugin refuses to activate loud rather than silently running without a tunnel.

The tunnel's connection address is yours to supply — the plugin never ships a default endpoint. Set the env above to your own provider's public host (DSH_REMOTE_ACCESS_PUBLIC_URL) and launch credential (DSH_REMOTE_ACCESS_FRP_ARGS); without them, an install stays inert.