@samyx/preview-stacks-ui 0.2.1 → 0.2.2
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 +6 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -13,15 +13,15 @@ This one is richer — dashboards, tabs, live-following logs, keyboard navigatio
|
|
|
13
13
|
cost of being a second artefact. So it is opt-in:
|
|
14
14
|
|
|
15
15
|
```bash
|
|
16
|
-
|
|
17
|
-
pstack build-image --ui # generates an nginx Dockerfile around it
|
|
16
|
+
pstack build-image --ui # nginx around this package, fetched from npm inside the build
|
|
18
17
|
pstack init --ui advanced
|
|
19
18
|
```
|
|
20
19
|
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
20
|
+
Nothing to install on the host: the package ships `dist/` already compiled, and the generated
|
|
21
|
+
Dockerfile `bun add`s it *inside* the build — the same trick `pstack build-image` uses for the
|
|
22
|
+
control image. This package being a BUILD-time input is the whole point; requiring it on the host
|
|
23
|
+
too once turned an optional UI into a boot failure. (`apps/ui/Dockerfile` still exists and builds
|
|
24
|
+
from source; that is what CI uses, and what you want when developing the UI itself.)
|
|
25
25
|
|
|
26
26
|
Docker images are not published yet. When they are, this becomes a `docker pull` and
|
|
27
27
|
`PSTACK_UI_IMAGE=<registry>/…`.
|