This website requires JavaScript.
Explore
Help
Sign In
Fluksio
/
app
Watch
0
Star
0
Fork
0
Code
Issues
Pull Requests
Actions
Packages
Projects
Releases
Wiki
Activity
Files
d4a1b1db477553a86a259af8fbfcc578a100971d
app
/
backend
/
fluksio
/
api
T
History
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
..
routes
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
__init__.py
Rename the import package app to fluksio
2026-08-21 21:48:05 +02:00
deps.py
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
main.py
Panels become devices: per-device documents in the flow repo, a Devices tab
2026-10-16 15:48:36 +02:00
socket_auth.py
Make documentation standalone and generalize examples
2026-10-25 14:43:20 +01:00