Multiple code locations in Dagster OSS with shared code (resources, utils)

[tspencerdata]

Hi all,
I’m looking for some guidance on repo structure best practices in Dagster OSS.

Context:

• I have multiple code locations, each of which requires its own Python environment
• I have a set of shared utilities, resources that are used across all code locations.

Current repo structure (simplified):

dagster_OSS/
├─ analytics/ # code location 1 (unique env)
│ ├─ defs/
│ ├─ lib/
| └─ pyproject.toml
├─ data_engineering/ # code location 2 (unique env)
│ ├─ defs/
│ ├─ lib/
│ ├─ resources/ # shared resources
│ ├─ utils/ # shared utilities
| └─ pyproject.toml
├─ deploy_files/
├─ workspace.yaml # defines the code locations
└─ pyproject.toml

Each code location may need libraries that would clash with others, so isolation is important. But I also want to avoid duplicating the shared utils/ and resources/ code across locations.

What’s the recommended way to structure repos when you need per-location env isolation but also shared code?