OXYGENHUB

README: a Windows runner, and flow runner update 731413202557

refs #83, #85
Author
Andy McCall @andymccall <[email protected]>
When
· 2026-10-26 02:42 UTC
Signature
◈ sealed by Andy McCall
Hash
731413202557f69748d8ab3e6d1dc6cb7e353853598277aff48c173f1a947a92
Depends on
a083cc802892 fc10d9e80383
Depended on by
4dd392d16454 494a1b9a8ac2
In bookmarks
main
In tags
v0.4.0 v0.5.0 v0.5.1 v0.5.2 v0.5.3
Edits
2 atoms, 0 tree operations, 1 file

Browse the tree at this change

modified README.md +16 −0
…
48 unchanged lines
49 49
under `/home/claude/flow` (keeping the previous files as `.prev`), re-pins
50 50
`flow-init` in `flow.toml` and restarts the `flow-runner` service.
51 51
52 +
## A Windows runner
53 +
54 +
A Windows machine runs WASM jobs (the other tiers are Linux's). Each
55 +
release carries `flow-windows-x86_64.exe` (from the `dist` job):
56 +
57 +
    flow.exe --home C:\flow runner register https://oxygenhub.io --token flowreg_… --name win-1 --label windows
58 +
    flow.exe --home C:\flow runner
59 +
60 +
The token comes from the hub (Admin › Runners, or `POST /api/v1/user/runner-token`
61 +
for a runner of your own repositories). A pipeline sends it work with a
62 +
`runtime "wasm"` sandbox and `runs-on "windows"`. To keep it running, a
63 +
Task Scheduler task at start-up with that command (restarting on failure)
64 +
does. What a Windows runner does not do yet: report load and kernel, update
65 +
itself, or drain when Windows stops it (oxygenflow#83).
66 +
52 67
## Commands
53 68
54 69
    flow check                 # validate .flow/pipeline.kdl, print jobs and the pipeline hash
…
2 unchanged lines
57 72
    flow rootfs list
58 73
    flow hash FILE             # BLAKE3, for pinning in flow.toml
59 74
    flow runner                # claim and run jobs for the hub in flow.toml
75 +
    flow runner update --from FILE [--dry-run]   # install a new flow build in place of this one (spec §11.5.3)
60 76
61 77
## A Flow home
62 78
…
50 unchanged lines