stroblmeandClaude Opus 5 0a018fb698 Stop and start a flow without rebuilding anything ...

A stopped flow's nodes are built like any other flow's — being stopped
means having no subscriptions, schedules or webhooks, not being absent —
so a toggle only ever needed the lifecycle call and the gate that goes
with it. It was doing a whole-pipeline rebuild instead, which on a
populated installation is every node in every flow reconnecting.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01StpRc2C6au1WJ1EUU7fsfu

2026-08-23 18:35:28 +02:00

..

connector-wheels

Record the connectors and what is still read-only

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

fluksio

Stop and start a flow without rebuilding anything

2026-08-23 18:35:28 +02:00

scripts

Keep the engine's state in SQLite, not Postgres

2026-08-21 22:19:45 +02:00

tests

Stop and start a flow without rebuilding anything

2026-08-23 18:35:28 +02:00

.dockerignore

Rename the import package app to fluksio

2026-08-21 21:48:05 +02:00

.gitignore

Rename the import package app to fluksio

2026-08-21 21:48:05 +02:00

alembic.ini

Rename the import package app to fluksio

2026-08-21 21:48:05 +02:00

Dockerfile

Split the worker into a distribution of its own

2026-08-21 21:54:10 +02:00

pyproject.toml

Add the fluksio CLI: serve, enroll, worker

2026-08-21 22:51:13 +02:00