@edgehero/pi-dispatch-admin 2.0.0 → 2.1.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 +6 -0
- package/dist/index.mjs +86715 -144584
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -58,6 +58,12 @@ container runtime guarantees is declared in
|
|
|
58
58
|
[`docs/backends.md`](https://github.com/edgehero/pi-dispatch/blob/main/docs/backends.md), and
|
|
59
59
|
`pi-dispatch doctor --live` reads it back from real containers.
|
|
60
60
|
|
|
61
|
+
**Where it runs.** On any Linux server or VM you control, or your own Mac or Windows machine with Docker
|
|
62
|
+
Desktop: the worker is a long running process beside a container runtime on the same host. Serverless
|
|
63
|
+
platforms, hosted sandbox services and a container daemon on another machine are not supported. pi-dispatch
|
|
64
|
+
itself needs no AI key; the provider key is for pi inside each job. The details are in the
|
|
65
|
+
[main README](https://github.com/edgehero/pi-dispatch#where-it-can-run).
|
|
66
|
+
|
|
61
67
|
Spend is checked before a container starts, so a runaway or a junk trigger costs a refusal, not a bill.
|
|
62
68
|
The job image ships Playwright and Chromium, so a flow can build a frontend, screenshot it and iterate.
|
|
63
69
|
|