stroblme d4a1b1db47 History is kept by flow id: runs, cascades, rollups and events file the id in their flow column and nodes as <flow id>.<node>, the API answers flow plus flow_name and shows and takes nodes as <key>.<node>; events carry flow_id from the moment they are published; run queue items, the stage cache and cached curves keep ids and keys apart; endpoints, the brain graph, device bindings and search name the id to open

2026-11-02 19:01:19 +01:00

..

agents.md

Getting started: own settings go in compose.override.yml, uv waits 120 s for a download

2026-10-29 21:35:50 +01:00

api.md

History is kept by flow id: runs, cascades, rollups and events file the id in their flow column and nodes as <flow id>.<node>, the API answers flow plus flow_name and shows and takes nodes as <key>.<node>; events carry flow_id from the moment they are published; run queue items, the stage cache and cached curves keep ids and keys apart; endpoints, the brain graph, device bindings and search name the id to open

2026-11-02 19:01:19 +01:00

cli.md

Flows and dashboards get ids: the store is addressed by id with a key index, the first start gives every document its key as id, fluksio store migrate --dry-run and ls; the rename routes are gone

2026-11-02 16:54:11 +01:00

connectors.md

fluksio requires fluksio-worker 0.2.x: the 0.1 range left the 0.2.0 wheels unresolvable, and publish stopped on it

2026-11-01 13:47:01 +01:00

nodes.md

SDK: artifacts work outside a node, run --follow prints status and queue waits, fluksio cancel

2026-10-28 08:07:35 +01:00

workers.md

Make documentation standalone and generalize examples

2026-10-25 14:43:20 +01:00