@rayspec/cli
v1.8.0
Published
The RaySpec CLI — a READ-ONLY diagnostic floor (`rayspec doctor` static parseSpec, `rayspec plan` read-only deploy front-half, `rayspec gen-handler`; never mutates a real/target DB, never prints secrets) PLUS a clearly-separated LOCAL-DEV, MUTATING `dev`
Readme
@rayspec/cli
The RaySpec CLI: a read-only diagnostic floor (rayspec doctor for static spec
diagnosis, rayspec plan for a deploy preview), a production-mutating tenant
command group (rayspec tenant ensure — idempotently create or resolve the
organization a deployment binds to), and a clearly separated, local-dev dev
command group (scaffolding, secret minting). Every subcommand emits
machine-parseable JSON to stdout — --help is the one exception and prints plain
text there — and none of them prints a secret except rayspec dev bootstrap-tenant,
whose org token is its documented output.
Usually invoked through the unscoped launcher
rayspec (npx rayspec …).
Part of RaySpec — file-deployable AI infrastructure: describe a product's backend in one declarative YAML file, and RaySpec stands up accounts and authentication, in-process agents, an HTTP API, a Postgres-backed data layer, durable background jobs, and the supporting tooling — deployed GitOps-style from that single file.
Links
- Website & docs: https://rayspec.dev
- Source (monorepo): https://github.com/rayspec-labs/rayspec
- Changelog: https://github.com/rayspec-labs/rayspec/blob/main/CHANGELOG.md
License
Source-available under the Functional Source License (FSL-1.1-ALv2) — each release converts to Apache-2.0 two years after publication. See LICENSE.
