|
Some checks are pending
offline / test (push) Waiting to run
High-level system map with diagrams, TOC, and a docs index. Template worker shows how to add a new verae.* address for search, storage, or unplanned functions without teaching Zapier NATS. |
||
|---|---|---|
| .. | ||
| src | ||
| test | ||
| fleet.service.json | ||
| NATS.md | ||
| package.json | ||
| README.md | ||
| ROUTING.md | ||
| SUMMARY.md | ||
verae-nats-process
Template for a new addressed messaging process on the central Verae NATS.IO cluster.
Repo: https://git.georgelambert.org/marchon/verae-nats-process
Clone: ssh://git@git.georgelambert.org:2223/marchon/verae-nats-process.git
Overview: https://git.georgelambert.org/marchon/overview
npm test
npm start # /health on 127.0.0.1:13900
- Duplicate this repository (new Forgejo name).
- Edit
src/subjects.js—verae.<area>.<resource>.*. - Replace
handle()insrc/handle.js. - Update
ROUTING.md; add a fleet service withmin/max. - If Zapier needs the result, add HTTPS on verae-middleware only.
Zapier cloud must not subscribe. See overview 06-address-routing.