Modules resolve the manifest with uv pip compile before syncing, so listed packages bring their dependencies

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WgBfkm4rCmtd1T4vHWjEPx
This commit is contained in:
2026-10-15 17:06:20 +02:00
co-authored by Claude Opus 5.5
parent 356b0331bf
commit 50e6c033f1
4 changed files with 98 additions and 44 deletions
+4 -5
View File
@@ -32,11 +32,10 @@ the flow repository. Using references keeps credentials out of saved flows.
packages and Python version. There are two setups:
- **Managed environment:** Docker uses a separate node environment. A
superuser edits **Requirements** and presses **Apply**. Packages are synced
with `uv pip sync`; deleting a requirement removes it. Sync installs only
what is listed, so list the dependencies too, for example the output of
`uv pip compile`. The manifest is versioned with the flows, and successful
installs refresh the workers.
superuser edits **Requirements** and presses **Apply**. The list is resolved
with `uv pip compile` and synced with `uv pip sync`, so each package brings
its dependencies and deleting a requirement removes it. The manifest is
versioned with the flows, and successful installs refresh the workers.
- **Adopted environment:** a fresh pip installation inside your own virtual
environment can use that environment for nodes too. Modules is read-only.
Install dependencies there with pip or uv, then sync or restart Fluksio.