@meshwhisper/cli
v0.2.1
Published
MeshWhisper CLI — developer tooling for MeshWhisper projects
Readme
@meshwhisper/cli
Developer tooling for MeshWhisper — the self-hostable, end-to-end encrypted messaging SDK and relay.
npx @meshwhisper/cli initCommands
init
Scaffolds a MeshWhisper project in the current directory. Asks for your namespace, where your app should connect (Foundation relay for development, self-hosted for production), and what kind of app you're building. Writes:
meshwhisper-node/(self-hosted only) — a complete server deployment:docker-compose.yml, standalone Dockerfiles that install the published@meshwhisper/nodeand@meshwhisper/push-servicepackages, a.env(mode 600) with generated Web Push VAPID keys, and afederation-peers.jsonbootstrapped against the Foundation relay so your node can join the open relay meshsrc/meshwhisper.ts(browser/PWA) ormeshwhisper-chat.mts(Node.js) — a working SDK skeleton with your namespace and node URL threaded in.gitignoreentries for the.envand local identity stores
Idempotent: existing files are never overwritten.
doctor [url]
Health-checks a MeshWhisper node (defaults to the Foundation relay):
npx @meshwhisper/cli doctor wss://relay.myapp.comPrints the /health snapshot — connected clients, stored blobs, prekey entries, federation status.
vapid
Generates a Web Push VAPID key pair (RFC 8292) with no dependencies — byte-identical output format to web-push generate-vapid-keys:
npx @meshwhisper/cli vapidDocumentation
MIT
