Windmill.dev and Requirements.txt: How to Manage Dependencies in the cloud?
It seems that whenever I switch from editing locally in VS Code to using the cloud-based editor (windmill.dev), the system attempts to automatically infer and manage the required libraries. This process modifies the app.script.lock file, leading to inconsistencies when I pull the changes back to my local environment.
While I have a requirements.txt file locally to specify the project dependencies, I'm unsure how to integrate or utilize it within the windmill.dev environment.
For instance, the "phidata" library consistently causes issues. Since I import it in my Python code using "from phi.", the system seems to misinterpret it as the "phi" library instead of "phidata".
2 Replies
?
Are you facing the same issue? normally what you should do its generating metadata before pushing to windmill with the command:
wmill script generate-metadata
That will generate the required lockfiles of your deps Every time you add something to the requirements you need to make sure that all the lockfiles are updated If you are using vscode extension to run the script locally make sure to turn the use current lockfile so windmill dont infer them You can also use uv to run the scripts locally if you dont want to use vscode windmill extension
That will generate the required lockfiles of your deps Every time you add something to the requirements you need to make sure that all the lockfiles are updated If you are using vscode extension to run the script locally make sure to turn the use current lockfile so windmill dont infer them You can also use uv to run the scripts locally if you dont want to use vscode windmill extension
