The editor

The PDM's editor is Buerligons, built into the web app. ClassCAD can run for it in one of two places, chosen by EDITOR_RUNTIME when you build.

In the browser: wasm

ClassCAD runs as WebAssembly in the user's browser tab. Nothing runs on the server for editing, and it scales with your users' machines. It needs a WebAssembly key (CLASSCAD_WASM_KEY), and the key is bound to the address your PDM is served from. ClassCAD's WebAssembly loads from ClassCAD's CDN unless you host it yourself (CLASSCAD_WASM_URL).

This runs parts. Assemblies always use the server.

On the server: drogon

The editor connects to ClassCAD by WebSocket, at EDITOR_CC_URL. Point that at the scheduler through your proxy, for example wss://pdm.example.com/classcad/, and every editing session gets an engine of its own from the pool. See Reverse proxy for the forwarding.

That WebSocket has no sign-in yet. Until the PDM has one, keep this setup on a trusted network.

Both settings are read at build time. Change them, build the web app again.