dsh-univer-office

Configuration

The defaults are designed for local use: the service starts at port 9080. If that port is occupied, it tries 9081, then continues upward one port at a time. Set these plugin options when you need different values:

Field	Default	Purpose
gatewayPort	9080	Initial loopback service port; occupied ports advance by one
autoStartGateway	true	Start the service on first use
gatewayStartupTimeoutMs	10000	Service startup timeout
gatewayRequestTimeoutMs	3000	State-read timeout
gatewayMutationTimeoutMs	60000	Write-operation timeout
unitContentOperationTimeoutMs	120000	Import, export, inspection, and execution timeout
screenshotOperationTimeoutMs	120000	Overall timeout for one browser screenshot operation
printPdfOperationTimeoutMs	120000	Overall timeout for one browser PDF print operation
screenshotMaxPages	30	Maximum Doc or Slide pages rendered by one screenshot call
screenshotMaxPixels	16777216	Maximum pixel count for each screenshot image
browserExecutablePath	auto-detected	Browser executable for screenshots, PDF printing, and Slide checks; takes precedence over UNIVER_RENDER_BROWSER
resourceCacheRoot	$DSH_HOME/cache/dsh-univer-office/resources	Persistent downloaded-SVG cache; falls back to ~/.dsh when DSH_HOME is unset
resourceDownloadTimeoutMs	15000	Timeout for one SVG resource download
resourceOperationTimeoutMs	120000	Overall timeout for one resource-library tool operation
tools	true	Enable agent editing capabilities
skills	true	Enable bundled task guidance
telemetry	true	Send anonymous product telemetry

The Viewer, its HTTP API, and its WebSocket collaboration traffic are served by the plugin on the DSH WebServer origin itself (/univer-viewer/... and /uf/...), so remote deployments work through whatever entry already fronts DSH — no extra reverse-proxy configuration. Every browser request passes DSH browser authentication via the connection service. Viewer document opens and /univer-api requests also validate the named session workspace; subsequent /uf API and WebSocket requests do not require a plugin session cookie or repeat that workspace check. Authenticated browsers can address any .univer file accessible to the Host process, including in remote deployments. In DSH Desktop, the Viewer obtains the current Host loopback address through an authenticated runtime endpoint for WebSocket connections; HTTP requests continue through the desktop shell. The Gateway itself stays on loopback and is never exposed. (The former viewerBaseUrl option was removed by this change and is ignored.)