verae-fleet/server

Package: verae-fleet
Source: packages/verae-fleet/src/server.js
Lines: 146

What this module is

Implementation module in verae-fleet. The tables below are extracted from the source (signatures + JSDoc).

Exports

startControlServer

Types / interfaces / classes

None extracted.

Functions

Name

Parameters

Param types (JSDoc)

Returns

Calls (same file / helpers)

json

res, code, obj

—

unknown

see Call graph

startControlServer

sup, mon

sup: import('./supervisor.js').Supervisor, mon: import('./monitor.js').Monitor

unknown

see Call graph

What it imports / requires

  • node:http

  • node:fs

  • node:path

  • node:url

  • ./load.js

  • ../../verae-zapier-simulator/src/pipeline.js

Call graph (identifiers invoked)

join, dirname, fileURLToPath, json, writeHead, end, stringify, import, startControlServer, createServer, async, snapshot, reset, push, parse, concat, toString, run, listServices, status, addMachine, match, checkMachine, setMachineEnabled, reconcile, startService, stopService, pauseService, resumeService, fn, pauseInstance, resumeInstance, restartInstance, stopInstance, markUnhealthy, createReadStream, pipe, startsWith, normalize, existsSync, statSync, isFile, extname, toLowerCase, listen, write

Each identifier is a call site in this file. Follow the import list to see the defining module; open that module’s MD for parameter and return types.

Return values (how to read this)

  • HTTP route handlers return Express res.json(...) bodies (see route docs).

  • Zapier perform functions return a single object (creates) or an array (triggers/searches).

  • Pricing functions return integer cents on Quote.totalCents.