Files

T

stroblme 42ea2e50ac Export FLOWS and build from the top-level fluksio package

A test of the declarations had to import them from fluksio.sdk while the
guide teaches `from fluksio import ...`. The worker's inert module gets the
same two names so a module importing them still loads inside a node.

2026-09-16 16:44:47 +02:00

fluksio_worker

Export FLOWS and build from the top-level fluksio package

2026-09-16 16:44:47 +02:00

LICENSE

License the workspace under AGPL-3.0-or-later

2026-08-24 11:53:54 +02:00

pyproject.toml

Back to development

2026-09-02 22:48:40 +02:00

README.md

Say the licence on the two pages PyPI will show

2026-08-24 12:51:53 +02:00

README.md

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.