master-zapier-plan-draft/packages/verae-fleet/services/middleware-http.json
George Lambert a1a5b957fd
Some checks are pending
offline / test (push) Waiting to run
Wire zappier-edge into the live stack and add billing department APIs
Fleet now spawns the real zappier and middleware processes. Metered
timestamp/receipt/hash calls proxy to middleware when ZAPPIER_UPSTREAM
is set. CS credits, sales per-customer pricing, and QuickBooks export
are separate repos plugged into zappier-edge admin.
2026-09-11 15:15:55 -04:00

27 lines
770 B
JSON

{
"id": "middleware-http",
"title": "Verae Zapier HTTP middleware",
"kind": "http",
"package": "verae-zapier-middleware",
"role": "middleware-http",
"managed": true,
"runtime": "HTTPS :3100 /zapier/v1",
"health": { "type": "http", "path": "/health", "timeoutMs": 4000 },
"ports": { "healthBase": 3100 },
"spawn": {
"cwd": "../verae-zapier-middleware",
"command": "node",
"args": ["src/index.js"]
},
"env": {
"PORT": "3100",
"NATS_URL": "nats://127.0.0.1:4222",
"NATS_ENABLED": "true",
"MOCK_VERAE": "true"
},
"nats": {
"in": ["verae.zapier.jobs.events"],
"out": ["verae.zapier.jobs.watch", "verae.zapier.webhooks.deliver"]
},
"notes": "Wait path subscribes jobs.events. Never expose NATS to Zapier."
}