Multiple envs for non-package project

[corey-dawson]

Hello,

I want to use poetry to manage package dependencies for my non package project .I have two components in my project folder; api and ui. I want to do a separate env for each component

myproject
|--api
   |-api.py  # fast api
|--ui
   |--ui.py  # python shiny

In my original thought, i tried to cd into each the api folder and the ui folder and poetry init. creating a poetry toml definition in each folder and being able to switch environments by changing directories from ./myproject/api and ./myproject/ui. However, i cannot get my second folder to create and switch to a a different poetry environment. One possible issue is that i have i have virtual envs in-project set to true.

I really want to ask for any guidance or best practices on managing two sets up code within a single project folder. My goal is to containerize each folder in its own docker image, and want to keep independent dependencies for the ui and api. Any direction would be helpful

[dexhunter]

One possible issue is that i have i have virtual envs in-project set to true.

virtualenvs.in-project = true fits your api/ui layout: each folder can have its own .venv. If the api environment was still active when you moved into ui, though, Poetry can keep using it. Changing directories doesn't deactivate the environment. Use exit to leave a poetry shell, or deactivate if you sourced its activation script.

Keep a separate pyproject.toml and poetry.lock in each folder, and put package-mode = false under [tool.poetry] in both before installing. That suits the two non-package apps and gives each Docker image its own dependency set. With your in-project setting already enabled and no environment active, run poetry -C api install and poetry -C ui install from myproject. You can then select either app with poetry -C api run ... or poetry -C ui run ... from that same shell.

One caveat for environments you've already created: enabling the in-project setting doesn't move an existing cached environment into .venv.