Drop --token from the hand-started worker examples

The worker reads FLUKSIO_WORKER_TOKEN itself; on the command line the
token shows in ps. The --token row in the options table says so.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013GAeg4Jo6xjZzjwy9QDWMQ
This commit is contained in:
2026-10-07 09:35:00 +02:00
co-authored by Claude Opus 5.5
parent cb2a6315c9
commit 5eeeb08be4
8 changed files with 8 additions and 15 deletions
+1 -1
View File
@@ -43,7 +43,7 @@ A machine that should only *run nodes* for an engine elsewhere installs less:
```sh ```sh
pip install fluksio-worker pip install fluksio-worker
fluksio-worker --url wss://api.fluksio.com/api/v1/workers/attach --token "$TOKEN" --labels gpu FLUKSIO_WORKER_TOKEN=… fluksio-worker --url wss://api.fluksio.com/api/v1/workers/attach --labels gpu
``` ```
## Getting started ## Getting started
+1 -2
View File
@@ -231,8 +231,7 @@ agent's own parser: it is the same program `fluksio-worker` installs, so the
two are interchangeable: two are interchangeable:
```sh ```sh
fluksio worker --url wss://api.${DOMAIN}/api/v1/workers/attach \ fluksio worker --url wss://api.${DOMAIN}/api/v1/workers/attach --labels gpu
--token "$FLUKSIO_WORKER_TOKEN" --labels gpu
``` ```
See [Remote workers](workers.md). See [Remote workers](workers.md).
+1 -2
View File
@@ -16,7 +16,6 @@ pip install fluksio-worker
fluksio-worker \ fluksio-worker \
--url wss://api.${DOMAIN}/api/v1/workers/attach \ --url wss://api.${DOMAIN}/api/v1/workers/attach \
--token "$FLUKSIO_WORKER_TOKEN" \
--labels gpu,cuda12 \ --labels gpu,cuda12 \
--python /opt/torch-venv/bin/python --python /opt/torch-venv/bin/python
``` ```
@@ -29,7 +28,7 @@ driver in order to run a training step. An engine host already has it, and
| Option | Default | What it does | | Option | Default | What it does |
|---|---|---| |---|---|---|
| `--url` | **required** | `wss://…/api/v1/workers/attach` | | `--url` | **required** | `wss://…/api/v1/workers/attach` |
| `--token` | `$FLUKSIO_WORKER_TOKEN` | the credential, minted on the engine | | `--token` | `$FLUKSIO_WORKER_TOKEN` | the credential, minted on the engine; on the command line any user of the machine reads it from `ps`, so prefer the variable |
| `--name` | this host's name | sent along; the worker list shows the token's name | | `--name` | this host's name | sent along; the worker list shows the token's name |
| `--labels` | the token's | comma-separated; must match the labels the token was minted with | | `--labels` | the token's | comma-separated; must match the labels the token was minted with |
| `--python` | this interpreter | the interpreter node code runs on | | `--python` | this interpreter | the interpreter node code runs on |
-1
View File
@@ -270,7 +270,6 @@ pip install fluksio-worker
fluksio-worker \ fluksio-worker \
--url wss://api.${DOMAIN}/api/v1/workers/attach \ --url wss://api.${DOMAIN}/api/v1/workers/attach \
--token "$FLUKSIO_WORKER_TOKEN" \
--labels gpu,cuda12 \ --labels gpu,cuda12 \
--python /opt/torch-venv/bin/python --python /opt/torch-venv/bin/python
``` ```
+3 -4
View File
@@ -161,11 +161,10 @@ nothing of yours, so a container is always this case.
`pip install fluksio-worker` into the environment the training code runs `pip install fluksio-worker` into the environment the training code runs
in, and node code runs on it: `--python` defaults to the interpreter the in, and node code runs on it: `--python` defaults to the interpreter the
agent was started with. agent was started with. It reads its token from `FLUKSIO_WORKER_TOKEN`.
```sh ```sh
fluksio worker --url ws://127.0.0.1:8000/api/v1/workers/attach \ fluksio worker --url ws://127.0.0.1:8000/api/v1/workers/attach --labels gpu
--token "$WORKER_TOKEN" --labels gpu
``` ```
Then give the node `device="gpu"`; see [Remote workers](../code/workers.md). Then give the node `device="gpu"`; see [Remote workers](../code/workers.md).
@@ -469,7 +468,7 @@ alongside the store's own. `--dry-run` prints all of this and uploads nothing;
```sh ```sh
fluksio worker --url ws://127.0.0.1:8000/api/v1/workers/attach \ fluksio worker --url ws://127.0.0.1:8000/api/v1/workers/attach \
--token "$WORKER_TOKEN" --labels local --python "$(which python)" --labels local --python "$(which python)"
``` ```
Then give the node `device="local"`. Then give the node `device="local"`.
+1 -2
View File
@@ -258,13 +258,12 @@ curl -X POST https://api.${DOMAIN}/api/v1/workers/tokens \
The labels are signed into it, so the worker can repeat them with `--labels` The labels are signed into it, so the worker can repeat them with `--labels`
but not change them. but not change them.
On the other machine: On the other machine, with that token in `FLUKSIO_WORKER_TOKEN`:
```sh ```sh
pip install fluksio-worker pip install fluksio-worker
fluksio-worker \ fluksio-worker \
--url wss://api.${DOMAIN}/api/v1/workers/attach \ --url wss://api.${DOMAIN}/api/v1/workers/attach \
--token "$WORKER_TOKEN" \
--labels shed,gpio \ --labels shed,gpio \
--parallel 2 --parallel 2
``` ```
-1
View File
@@ -9,7 +9,6 @@ pip install fluksio-worker
fluksio-worker \ fluksio-worker \
--url wss://api.example.com/api/v1/workers/attach \ --url wss://api.example.com/api/v1/workers/attach \
--token "$FLUKSIO_WORKER_TOKEN" \
--labels gpu,cuda12 \ --labels gpu,cuda12 \
--python /opt/torch-venv/bin/python --python /opt/torch-venv/bin/python
``` ```
+1 -2
View File
@@ -3,8 +3,7 @@
Point it at the engine on the box with the GPU and it dials in:: Point it at the engine on the box with the GPU and it dials in::
pip install fluksio-worker pip install fluksio-worker
fluksio-worker --url wss://api.example.com/api/v1/workers/attach \\ fluksio-worker --url wss://api.example.com/api/v1/workers/attach --labels gpu
--token "$FLUKSIO_WORKER_TOKEN" --labels gpu
Install it into the environment the training code already runs in and node Install it into the environment the training code already runs in and node
code runs on that: ``--python`` defaults to the interpreter this was started code runs on that: ``--python`` defaults to the interpreter this was started