marchon/master-zapier-plan-draft
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
master-zapier-plan-draft/packages/verae-ops/README.md
George Lambert cb07f5b321
Some checks are pending
offline / test (push) Waiting to run
Details
Restyle staff and console UIs; add UI-Docs walkthrough and review PDF. 
Match CS/sales/accounting/access-staff to the portal indigo system with
dollar amounts, skip links, and empty states. Fleet replica actions move
into overflow menus, roles become chips, Docs become cards, and the
header copy reflects the 0.0.0.0 bind. Simulator uses the same shell
(orange only for faults). Portal API keys are masked; admin customers
edit in a drawer. Catalog uses system-ui. New UI-Docs repo holds
screenshots, usage notes, and UI-REVIEW.pdf.
2026-09-11 18:01:33 -04:00

2.2 KiB
Raw Blame History

verae-ops — install, run, maintain

How to stand up Verae Time × Zapier on Docker, Proxmox, generic VMs, or dedicated hardware, and how to link dependent services.

Forgejo: https://git.georgelambert.org/marchon/verae-ops
Clone: ssh://git@git.georgelambert.org:2223/marchon/verae-ops.git
Catalog: https://zapier.georgelambert.org/packages/verae-ops/README.pdf
System map: https://zapier.georgelambert.org/overview/README.pdf

This is the operations repo. Application code lives in the other independent git repositories.

Reading order

  1. GETTING-STARTED.md — install, first-up, monitor (read this first)
  2. 01-dependencies.md — what must exist, who talks to whom
  3. 02-docker.md — Compose (NATS 3-node cluster + HTTPS edges)
  4. 03-proxmox.md — LXC / QEMU VMs
  5. 04-virtual-servers.md — cloud or hypervisor VMs
  6. 05-dedicated-hardware.md — bare metal (NS1-style)
  7. 06-linking-services.md — env vars, URLs, replica floors
  8. 07-maintenance.md — upgrade, backup, fleet, NATS

Public PDFs of the same files: https://zapier.georgelambert.org/packages/verae-ops/<name>.pdf.

Non-negotiables

Rule Why
Zapier cloud → HTTPS only (zappier-edge) Never NATS, never api.veraetime.net
NATS binds loopback or a private docker/VM net Not on the public NIC
Tree-node min 3, pause does not count Bulk Merkle lookups
Private keys stay on disk; git stores paths machines.json identityFile
Operator console HTTP binds 0.0.0.0:3850 Not a public NATS bus; NATS stays private

Quick lab (one machine)

git clone ssh://git@git.georgelambert.org:2223/marchon/verae-ops.git
cd verae-ops
docker compose up --build

Then: zappier http://127.0.0.1:3000/ middleware http://127.0.0.1:3100/health NATS monitoring http://127.0.0.1:8222/

Production layout is three NATS nodes + fleet-spread workers; see 02-docker.md and 05-dedicated-hardware.md.