@ricsam/r5d-worker 0.0.36 → 0.0.38
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 +5 -1
- package/dist/cjs/main.cjs +234 -525
- package/dist/cjs/managed-paths.cjs +158 -0
- package/dist/cjs/package.json +1 -1
- package/dist/cjs/workspace-sync.cjs +653 -0
- package/dist/mjs/main.mjs +239 -523
- package/dist/mjs/managed-paths.mjs +116 -0
- package/dist/mjs/package.json +1 -1
- package/dist/mjs/workspace-sync.mjs +608 -0
- package/dist/types/main.d.ts +0 -50
- package/dist/types/managed-paths.d.ts +15 -0
- package/dist/types/workspace-sync.d.ts +74 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -10,7 +10,7 @@ r5d-worker --version
|
|
|
10
10
|
The worker uses the existing `r5dctl` config file and accepts `R5D_WORKER_TOKEN` or `R5D_API_KEY`. Project checkouts are managed under:
|
|
11
11
|
|
|
12
12
|
```text
|
|
13
|
-
~/.r5d/projects/<namespace
|
|
13
|
+
~/.r5d/projects/<namespace>/<project>/<branch-name>
|
|
14
14
|
```
|
|
15
15
|
|
|
16
16
|
Web shells and agent shell commands receive a server-issued `r5dctl` credential automatically. The credential is scoped to the signed-in user and revoked when the shell or command finishes, so commands such as `r5dctl auth status` do not require a separate login on the worker host.
|
|
@@ -19,6 +19,10 @@ When the user has signed in with GitHub, web shells and agent commands also rece
|
|
|
19
19
|
|
|
20
20
|
Visible branch checkouts are the user/agent workbench. Their `origin` remains the connected GitHub repository for manual Git work. r5d internal sync git metadata lives separately under `~/.r5d/sync`; when a worker connects, every idle registered branch is force-synchronized from that internal remote. The same destructive sync can be requested for a live worker from User Settings.
|
|
21
21
|
|
|
22
|
+
Branch names managed by r5d use lowercase letters, numbers, internal hyphens, and slash-separated segments, for example `ft/esm-support`. They may contain at most 45 characters. On the first start after upgrading to the nested checkout layout, the worker atomically moves each unambiguous legacy `<namespace>-<project>` directory to `<namespace>/<project>`. If both paths exist, it preserves both and stops with recovery instructions.
|
|
23
|
+
|
|
24
|
+
The nested-layout release is a breaking worker/server cutover. Run `bun run workspace:checkout-preflight` against the production database, stop and upgrade workers to the required version, deploy the matching server, and then reconnect workers. Older workers are rejected before WebSocket upgrade rather than receiving an incompatible manifest.
|
|
25
|
+
|
|
22
26
|
Worker labels are mandatory and unique per user. Choose labels that describe host capabilities, such as `macos`, `linux`, `ios`, or `ec2-build`.
|
|
23
27
|
|
|
24
28
|
`r5d-worker start` keeps a lightweight supervisor process attached to the launching terminal or service. When both r5d CLIs are updated from User Settings, the connected runtime verifies the installed versions, exits with a reload signal, and the supervisor reconnects using the new worker package. Updates only run while the worker has no active commands or shells.
|