dsh-remote-access

You are running dsh --profile web locally and want to open it from another device, only to find that stock dsh hard-locks the server to 127.0.0.1 - --host 0.0.0.0 is flat-out refused by web-startup. dsh-remote-access is a deliberately tiny bundle built for exactly this gap: no forking, no rewrites, no custom token gate. It simply overrides the webserver row host via a single env-var, letting it bind to 0.0.0.0 while authentication stays fully in dsh's built-in BrowserAuth ?token= flow.

Because the entire patch is just one declarative config layer in the profile directory that the loader re-reads on every boot, it is inherently immune to dsh upgrades - nothing to re-run, re-apply, or even remember. The startup log prints both the LAN address and the token URL; the browser cookie stays valid across restarts for up to cookieMaxAgeDays (default 30 days), so an already-open tab will not suddenly return a 401.

Who it is for: anyone who needs LAN access to a local dsh Web GUI from a phone, tablet, or second laptop; anyone who wants a persistent launchd KeepAlive remote entry point without pulling in a third-party proxy or inventing their own auth; and anyone who prefers the change-one-parameter-let-the-rest-be-official minimalism.