stroblmeandClaude Opus 5
dfa0d44589
A tag is the only thing that is a version. Between two of them the tree is a build nobody released, and until now it went on claiming to *be* the release it came after — which is how 0.1.4 came to name both the build before the per-node digest and the build after, with the mismatch messages unable to tell them apart. `+dev` is a local version: it says "0.1.4, plus changes", it does not have to guess what the next release will be numbered, and PyPI refuses one, so a dev build cannot be published by accident. `scripts/release.sh` in the workspace root writes it after each tag; this is that commit, by hand, for the release that predates it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A9Hdrmf2cwNABCnE5x9UJa
fluksio-worker
Runs Fluksio nodes on a machine the engine cannot reach — a GPU box, a cluster node, anything behind a NAT. It dials out to the engine over one authenticated websocket, so nothing has to be exposed here.
pip install fluksio-worker
fluksio-worker \
--url wss://api.example.com/api/v1/workers/attach \
--token "$FLUKSIO_WORKER_TOKEN" \
--labels gpu,cuda12 \
--python /opt/torch-venv/bin/python
--python is the interpreter node code runs on, which is how this machine keeps
its own wheels without the engine ever installing them. Mint a token from the
engine with POST /api/v1/workers/tokens.
Linux and macOS.
License
Copyright (C) 2026 Melvin Strobl — GNU Affero General Public License v3.0 or later. Running a modified version over a network obliges you to offer its users the corresponding source (AGPL §13).