onepipeline-ui 0.11.0 → 0.11.1

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.
Files changed (2) hide show
  1. package/README.md +7 -3
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -9,12 +9,16 @@ and no binary. The read API it talks to ships separately as
9
9
  npm install onepipeline-ui
10
10
  ```
11
11
 
12
- Serve `node_modules/onepipeline-ui/dist` from any static file server, and put the read
13
- API behind the same origin at `/api` and `/healthz`:
12
+ The read API of the same release already carries this bundle: `onepipeline-api serve
13
+ --runs-root ./runs --ui` serves it at `/` beside the API, with nothing to install
14
+ beyond the command. This package is the bundle on its own, for serving it from
15
+ somewhere else — any static file server with the read API behind the same origin at
16
+ `/api` and `/healthz`, or the API itself pointed at it:
14
17
 
15
18
  ```sh
16
19
  npx onepipeline-api-cli serve --runs-root ./runs # the API, on 127.0.0.1:8765
17
- npx serve node_modules/onepipeline-ui/dist # the view
20
+ npx serve node_modules/onepipeline-ui/dist # the view, from a static server
21
+ npx onepipeline-api-cli serve --runs-root ./runs --ui --ui-dist node_modules/onepipeline-ui/dist
18
22
  ```
19
23
 
20
24
  The app declares no schema, event name, or API path of its own: every payload it reads
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "onepipeline-ui",
3
- "version": "0.11.0",
3
+ "version": "0.11.1",
4
4
  "description": "The DAG Observatory: the browser view of onepipeline runs, built and ready to serve.",
5
5
  "keywords": [
6
6
  "ui",