Sync docs, add verae-bootstrap, and run the full stack on NS1.
Some checks are pending
offline / test (push) Waiting to run
Some checks are pending
offline / test (push) Waiting to run
Docs match current modules: public portal is access-web /portal/, IAM and keep are listed, edge is loopback. Bootstrap clones every Forgejo repo and installs deps per server type. Fleet starts IAM and staff-session. NS1 all-in-one uses edge :13000 because :3000 is taken; archive workers stay with keep.
This commit is contained in:
parent
baaf1c2275
commit
03f557203a
42 changed files with 481 additions and 13 deletions
|
|
@ -51,6 +51,9 @@ Zapier cloud **never** connects to NATS. Internal services do: middleware worker
|
|||
| zapier-user-docs | `zapier-user-docs` | Static | — | catalog `/user-docs/` |
|
||||
| verae-chain-client | `verae-chain-client` | Library | — | HTTPS `api.veraetime.net` or MOCK |
|
||||
| fleet | `verae-fleet` | Local HTTP :3850 | operator | keepFloor + SSH hosts |
|
||||
| staff-iam | `verae-staff-iam` | :3028 | staff login | none (HTTP) |
|
||||
| keep | `verae-keep` | :3860 / :3861 | host supervisor | none |
|
||||
| bootstrap | `verae-bootstrap` | clone/install | — | — |
|
||||
| overview | `overview` | Static | — | high-level map |
|
||||
| nats-process | `verae-nats-process` | Template worker | `verae.example.process.in` | `.out` / `.reply.*` |
|
||||
| docs-master | `zapier-docs-master` | Static | — | published on zapier.georgelambert.org |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue