Use case: project on network drive, used from different machines

[m-albert]

Thanks for this amazing tool, which I'm starting to use more and more. I wanted to quickly share a problem / use case I encountered. Probably I'm using pixi wrongly and there's already a solution to this.

Setup

Consider the following setup:

• the project folder is on a network drive
• code is run from different machines which mount this network drive

In order to save the environments locally on the different machines (which can run different platforms), I use detached-environments to save the environments on each machine under ~/.pixi/envs.

Problem

After installing an environment on the first machine, it seems that pixi creates links from /.pixi/envs to the environment under ~/.pixi/envs (machine 1). Therefore, if I try to install an environment on machine 2 it tries to follow the simlink found under ~/.pixi/envs.

What seems to work for me is to specify different environments for each machine and use them separately, e.g. pixi install -e machine1:

[environments]
machine1 = []
machine2 = []

Question

Probably I'm using pixi wrongly: Is there a more straightforward way of using pixi in the described setup?

[Hofer-Julian]

Hey @m-albert, thanks for your interest in pixi.

This use case, is something our community is already exploring. You might also be interested in the discussion in this Discord thread

[m-albert]

Thank you @Hofer-Julian!