@siteoshq/cli 1.4.0 → 1.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +15 -1
- package/dist/cli.js +446 -89
- package/dist/cli.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# SiteOS CLI
|
|
2
2
|
|
|
3
3
|
`@siteoshq/cli` exposes one `siteos` binary for Auth, common Projects, Pulse, Cookie, Forms,
|
|
4
|
-
Search, Trace, SEO and Integrations. This source prepares version 1.
|
|
4
|
+
Search, Trace, SEO and Integrations. This source prepares version 1.6.0; publishing is a separate release.
|
|
5
5
|
Node.js 22 or newer is required.
|
|
6
6
|
|
|
7
7
|
## Install and authenticate
|
|
@@ -267,3 +267,17 @@ answers from the working database, retaining only a reserved-key tombstone. That
|
|
|
267
267
|
reused. Shared Environment credentials remain active for other forms. Sync refuses archived/deleted
|
|
268
268
|
keys and never removes forms missing from a local manifest. Backups follow deployment retention;
|
|
269
269
|
they are not an in-app restore mechanism.
|
|
270
|
+
|
|
271
|
+
### Automatic Forms deployment
|
|
272
|
+
|
|
273
|
+
Generate Forms JSON from the shared host validation schema during build. Install a release-only
|
|
274
|
+
key once with `siteos forms deployment-key issue --environment production --install --json`.
|
|
275
|
+
Store `SITEOS_FORMS_DEPLOYMENT_KEY` in the CI secret store and configure explicit
|
|
276
|
+
`SITEOS_FORMS_PUBLIC_URL`. Keep the submission credential on the website server.
|
|
277
|
+
|
|
278
|
+
Run `siteos forms deploy --manifest .siteos/forms/manifest.json --json` before routing traffic to a
|
|
279
|
+
new release. This needs no interactive Auth or local Project state and publishes atomically.
|
|
280
|
+
Definitions include a generated SHA-256 `sourceExportId`; runtime sends it as `contractVersion`.
|
|
281
|
+
A changed field requires a normal build/release, not a second hand-edited validation schema.
|
|
282
|
+
`forms deployment-key list|revoke` manages release keys; submission keys cannot publish.
|
|
283
|
+
See the SiteOS Forms skill for the portable generator and version serialization contract.
|