acocodes
12/16/2024, 9:50 AMvenv
and`deploy.py` where deployments are defined via <http://flow.to|flow.to>_deployment()
. Projects may also have their own .env
. Example:
root/
├── main.py
├── project_A/
│ ├── venv/
│ ├── deploy.py
│ ├── .env
├── project_B/
│ ├── venv/
│ ├── deploy.py
├── project_C/
│ ├── venv/
│ ├── deploy.py
Currently main.py
serves the deploy.py
files all at once using ThreadPoolExecutor
, but we're getting job fails or crashes whenever projects are scheduled close to each other. The projects themselves only contain fairly simple Python scripts so we have no work pools set up. Any suggestions to improve this that works on Windows?Bianca Hoch
12/16/2024, 11:23 PM