Add dev-overview: designed vs running NATS routes and Zapier-Verae path.
Some checks failed
offline / test (push) Has been cancelled
Some checks failed
offline / test (push) Has been cancelled
Independent Forgejo repo maps every verae.* address, endpoint I/O, job monitor loop, and remaining billing/archive wiring.
This commit is contained in:
parent
c83f1c6717
commit
86b421db05
1 changed files with 436 additions and 1 deletions
9
packages/dev-overview/NATS.md
Normal file
9
packages/dev-overview/NATS.md
Normal file
|
|
@ -0,0 +1,9 @@
|
|||
# NATS — dev-overview
|
||||
|
||||
This repo does not subscribe. It documents every `verae.*` address.
|
||||
|
||||
Cluster (running): `nats://10.10.10.21:4222,nats://10.10.10.22:4222,nats://10.10.10.23:4222` on `vmbr1`.
|
||||
|
||||
Public client edge (token): `nats://70.88.205.138:4222` and `wss://nats.zapier.georgelambert.org`. Zapier cloud still uses **HTTPS only**.
|
||||
|
||||
See [01-nats-routes.md](01-nats-routes.md).
|
||||
Loading…
Reference in a new issue