master-zapier-plan-draft/docs/sphinx/repos/verae-nats-process.md
George Lambert e401635fd6
Some checks are pending
offline / test (push) Waiting to run
Document every repo in Sphinx, catalog PDFs, and verae-ops
Add missing package READMEs, expand Sphinx to all runtime modules,
publish a LaTeX/PDF README book, and add verae-ops for Docker,
Proxmox, VMs, dedicated hardware, and service linking. Catalog
defaults to public PDF links for each module README and samples.
2026-09-11 14:36:17 -04:00

21 lines
889 B
Markdown

# 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://zapier.georgelambert.org/overview/README.pdf
**Routing:** https://zapier.georgelambert.org/packages/verae-nats-process/ROUTING.pdf
```bash
npm test
npm start # /health on 127.0.0.1:13900
```
1. Duplicate this repository (new Forgejo name).
2. Edit `src/subjects.js``verae.<area>.<resource>.*`.
3. Replace `handle()` in `src/handle.js`.
4. Update `ROUTING.md`; add a fleet service with `min`/`max`.
5. If Zapier needs the result, add HTTPS on **verae-middleware** only.
Zapier cloud must not subscribe. See [address routing](https://zapier.georgelambert.org/overview/06-address-routing.pdf).