@siteoshq/cli 1.1.0 → 1.2.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 +39 -2
- package/dist/cli.js +518 -23
- package/dist/cli.js.map +1 -1
- package/package.json +19 -20
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 and Integrations. This source prepares version 1.
|
|
4
|
+
Search, Trace and Integrations. This source prepares version 1.2.0; publishing is a separate release.
|
|
5
5
|
Node.js 22 or newer is required.
|
|
6
6
|
|
|
7
7
|
## Install and authenticate
|
|
@@ -20,6 +20,24 @@ The one-time token is secret. Only `auth complete` receives it. The durable sess
|
|
|
20
20
|
privately in `~/.siteos/auth.json`. Product commands exchange it for short-lived, audience-bound
|
|
21
21
|
grants; the durable session never reaches a product endpoint.
|
|
22
22
|
|
|
23
|
+
## Hosted origins
|
|
24
|
+
|
|
25
|
+
CLI 1.2.0 defaults to `https://app.siteos.sh` for Auth and every service. Existing credentials
|
|
26
|
+
and repository bindings retain their selected origin; sign in again when moving installations.
|
|
27
|
+
Never copy private state between production and staging.
|
|
28
|
+
|
|
29
|
+
For the separate SiteOS staging installation, set all four overrides before authentication:
|
|
30
|
+
|
|
31
|
+
```sh
|
|
32
|
+
export SITEOS_AUTH_BASE_URL=https://siteosapp.xui.se
|
|
33
|
+
export SITEOS_PULSE_API_URL=https://siteosapp.xui.se
|
|
34
|
+
export SITEOS_FORMS_PUBLIC_URL=https://siteosapp.xui.se
|
|
35
|
+
export SITEOS_SEARCH_PUBLIC_URL=https://siteosapp.xui.se
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
These select the SiteOS installation. A Project's Production or Staging Environment is a separate,
|
|
39
|
+
project-level selection inside that installation.
|
|
40
|
+
|
|
23
41
|
## Select one Project
|
|
24
42
|
|
|
25
43
|
From the website repository:
|
|
@@ -141,7 +159,7 @@ Organization and tracked Pulse slug agree. It leaves the original file untouched
|
|
|
141
159
|
## Origins and errors
|
|
142
160
|
|
|
143
161
|
`SITEOS_AUTH_BASE_URL` selects the shared application origin for common Projects and all service
|
|
144
|
-
commands using that context (default `https://
|
|
162
|
+
commands using that context (default `https://app.siteos.sh`). The legacy service flows retain
|
|
145
163
|
`SITEOS_PULSE_API_URL`, `SITEOS_FORMS_PUBLIC_URL` and `SITEOS_SEARCH_PUBLIC_URL` overrides. Runtime
|
|
146
164
|
integration uses its service's configured public URL and scoped credential.
|
|
147
165
|
|
|
@@ -165,3 +183,22 @@ pnpm --dir packages/cli pack:check
|
|
|
165
183
|
```
|
|
166
184
|
|
|
167
185
|
`pack:check` creates the publishable tarball locally. It does not publish the package.
|
|
186
|
+
|
|
187
|
+
## Cookie verification
|
|
188
|
+
|
|
189
|
+
CLI 1.2.0 adds `cookie schema`, `cookie validate --input draft.json`,
|
|
190
|
+
`cookie regions resolve --country GB --source published` and `cookie restore --input restore.json`.
|
|
191
|
+
Restore changes the draft only. Validation makes no write and reports a stale draft version.
|
|
192
|
+
|
|
193
|
+
From the selected website repository, run `siteos cookie verify --json` or
|
|
194
|
+
`siteos cookie verify --url /pricing --browser webkit --json`. Install the matching local browser
|
|
195
|
+
when requested with `npx playwright@1.61.1 install chromium` or `npx playwright@1.61.1 install webkit`.
|
|
196
|
+
The check opens fresh contexts, exercises the public consent API and reports request origins and
|
|
197
|
+
storage names without values, query strings, request bodies or authenticated sessions. These are
|
|
198
|
+
real visits; normal installation/aggregate signals may be recorded. Reports remain local.
|
|
199
|
+
|
|
200
|
+
A report records the revision, runtime, observed Edge location, scenario scope and 24-hour expiry.
|
|
201
|
+
`passed` exits 0; `needs-review` and `failed` exit 1. Unknown origins/storage require classification.
|
|
202
|
+
The check covers one route and a bounded observation window, not hidden first-party/server-side
|
|
203
|
+
tracking, every delayed interaction, visual accessibility or legal compliance. Repeat after
|
|
204
|
+
website/publication changes and preserve a separate GTM Tag Assistant check where applicable.
|