fix: skip local canvas server start when EXPRESS_SERVER_URL is set
Docker Build (ARM64) / Build & Push (push) Has been cancelled
Docker Build (ARM64) / Build & Push (push) Has been cancelled
This commit is contained in:
+11
-6
@@ -2912,12 +2912,17 @@ async function runServer(): Promise<void> {
|
||||
|
||||
applyTenant(workspacePath);
|
||||
|
||||
try {
|
||||
await startCanvasServer();
|
||||
logger.info('Canvas server started — lifecycle managed by MCP process');
|
||||
} catch (canvasError) {
|
||||
logger.warn('Canvas server failed to start:', (canvasError as Error).message);
|
||||
logger.warn('MCP tools will work without real-time canvas sync');
|
||||
// Skip local canvas server when targeting a remote EXPRESS_SERVER_URL
|
||||
if (!process.env.EXPRESS_SERVER_URL) {
|
||||
try {
|
||||
await startCanvasServer();
|
||||
logger.info('Canvas server started — lifecycle managed by MCP process');
|
||||
} catch (canvasError) {
|
||||
logger.warn('Canvas server failed to start:', (canvasError as Error).message);
|
||||
logger.warn('MCP tools will work without real-time canvas sync');
|
||||
}
|
||||
} else {
|
||||
logger.info('Remote canvas server configured, skipping local canvas start');
|
||||
}
|
||||
|
||||
// HTTP mode: one shared process serves many clients over Streamable HTTP.
|
||||
|
||||
Reference in New Issue
Block a user