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 \
--labels gpu,cuda12 \
--python /path/to/node-venv/bin/python
Replace the address and interpreter path with your own. Create a token on the
engine with POST /api/v1/workers/tokens and set FLUKSIO_WORKER_TOKEN before
starting the worker. See the worker guide
for the commands.
--python selects the environment holding your node dependencies. Omit it to
use the worker's own interpreter. The token fixes the worker's name and labels;
--labels may repeat those labels but cannot change them.
Engine and worker must use compatible protocols. Upgrade the engine first, then its workers.
A plain ws:// address is refused unless the engine is on this machine, since
the token and node secrets would cross the network in clear; --insecure
allows it on a network you trust.
Requires Python 3.12 or newer on Linux or 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).
Metadata
Release files for fluksio-worker 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| fluksio_worker-0.2.0.tar.gz | 30.4 kB | Without provenance | Details for fluksio_worker-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fluksio_worker-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for fluksio_worker-0.2.0-py3-none-any.whl |
Total release size: 62.9 kB
Release files / fluksio_worker-0.2.0.tar.gz
| Download URL | fluksio_worker-0.2.0.tar.gz |
|---|---|
| Size | 30.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b60223c252c2fb0098fc6c29b2f11bc68997f31b1dbe5ff4374a86025574e3e2
|
|
BLAKE2b-256 checksum How to use checksums |
393f9d574cd22c951f2f32b277425f1eda08c95b11a051714d1219c2d9de8045
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / fluksio_worker-0.2.0-py3-none-any.whl
| Download URL | fluksio_worker-0.2.0-py3-none-any.whl |
|---|---|
| Size | 32.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b7bcb4af4cc7240a59dbb0169ac7764a271cd93726e680a5b4778f74df9a51b
|
|
BLAKE2b-256 checksum How to use checksums |
52732a80e1b8075c8d31154199b423586e1e52b6bb455d567d48ad02d0064617
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for fluksio-worker 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.