stroblme 53916d869b Clients take a flow's id or key: one resolver in the SDK, id first, explicit id:/key:, a warning for reads and a refusal for changes when a name means two flows, deleted flows found by their last key; sync creates by POST, retries a create race through the drift checks and reports the id; MCP gets create_flow and resolves every flow argument with the caller's token; displays show flow_name; an engine from before ids is named as such

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

..

assets

Publish the documentation site: docs.fluksio.com

2026-08-22 05:55:34 +02:00

code

Clients take a flow's id or key: one resolver in the SDK, id first, explicit id:/key:, a warning for reads and a refusal for changes when a name means two flows, deleted flows found by their last key; sync creates by POST, retries a create race through the drift checks and reports the id; MCP gets create_flow and resolves every flow argument with the caller's token; displays show flow_name; an engine from before ids is named as such

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

concepts

Clients take a flow's id or key: one resolver in the SDK, id first, explicit id:/key:, a warning for reads and a refusal for changes when a name means two flows, deleted flows found by their last key; sync creates by POST, retries a create race through the drift checks and reports the id; MCP gets create_flow and resolves every flow argument with the caller's token; displays show flow_name; an engine from before ids is named as such

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

getting-started

Image builds with uv 0.13.6; follow-redirects 1.16.2 and seroval 1.6.12; getting started covers Docker on Raspberry Pi OS and Compose 2.24

2026-11-01 10:59:51 +01:00

interface

Flows and dashboards are created by POST under an issued or superuser-pinned id; PUT only updates; deleted flows leave a tombstone with their key; the controller stores by id and runs by key, hooks live under /hooks/<flow id>; a key with state or queued work behind it is refused until cleared

2026-11-02 17:41:23 +01:00

reference

Flows and dashboards are created by POST under an issued or superuser-pinned id; PUT only updates; deleted flows leave a tombstone with their key; the controller stores by id and runs by key, hooks live under /hooks/<flow id>; a key with state or queued work behind it is refused until cleared

2026-11-02 17:41:23 +01:00

stylesheets

Make documentation standalone and generalize examples

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

index.md

Docs: x86 and arm64, Raspberry Pi included; one container in the start pages

2026-10-16 14:56:08 +02:00

llms.txt

A node's worker label is worker, so a device is only a paired one

2026-10-16 16:56:05 +02:00