The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

I'm new to dagster and I'm wondering how to handle virtual environments possible across code locations? Is that something that is done? How is that setup or structured if its something that is a good practice?

You can think about each code location as its own virtual environment - they're usually deployed as separate docker containers

I'm wondering if this is the solution <https://dagster.slack.com/archives/C066HKS7EG1/p1706149224229199?thread_ts=1706146159.370139&amp;cid=C066HKS7EG1>

That's kind of just how code locations work. It sort of just depends on how you deploy Dagster. If you deploy it using any of the container-based deployments then you'll build different containers for each code location, which isolates their dependencies from each other

If you deploy Dagster all on the same machine without any container isolation (generally this isn't what you'd want for a production deployment), then yeah you'll need to do something similar to what Scout suggested