recala cms connect
Connect Sanity or WordPress. Credentials come from env, --token-stdin or a hidden human prompt.
recala cms connect [OPTIONS] Replace [OPTIONS] with the flags you need, or omit it.
Scroll horizontally to see all columns →
| Flag | Required | Description |
|---|---|---|
--json | No | Print one JSON document (errors as JSON on stderr). |
--org | No | Organization name, slug or id (else RECALA_ORG, else recala org use). |
--provider | No | No description supplied by the CLI. |
--project | No | No description supplied by the CLI. |
--dataset | No | No description supplied by the CLI. |
--blog-url | No | No description supplied by the CLI. |
--author | No | PERSON_ID=SANITY_AUTHOR_ID. |
--site | No | No description supplied by the CLI. |
--user | No | No description supplied by the CLI. |
--wordpress-com | No | No description supplied by the CLI. |
--wpcom-address | No | No description supplied by the CLI. |
--token-stdin | No | Read the CMS token/password from one stdin line; never echoes it. |
Examples
Run in your terminal with the intended organization selected.
recala cms connect Exit codes: 0 OK, 1 ERROR, 2 USAGE, 3 NOT_AUTHENTICATED, 4 FORBIDDEN, 5 NOT_FOUND, 6 CONFLICT, 7 INVALID, 8 RATE_LIMITED, 9 UNAVAILABLE, 10 CONFIRMATION_REQUIRED, 11 PAYMENT_REQUIRED.
API commands share the CLI’s HTTP error mapping. Read human and JSON output rules.