Name the directory where micromamba stores named environments under .daicrc (bed6bc28) · Commits · DAIC / docs-experimental

content/en/tutorials/python/index.md

+5 −3

Original line number	Diff line number	Diff line
		@@ -447,13 +447,15 @@ If you see an import error, check that biopython was added to `pixi.toml`.
		$ "${SHELL}" <(curl -L micro.mamba.pm/install.sh)
		```

		The installer asks where to put the binary and the environments. Keep both out of the cluster home:
		The installer asks four questions. Keep the binary and the prefix out of the cluster home, and accept the defaults for the other two:
		```
		Micromamba binary folder? [~/.local/bin] ~/linuxhome/.local/bin
		Init shell (bash)? [Y/n]
		Configure conda-forge? [Y/n]
		Prefix location? [~/micromamba] ~/linuxhome/.mamba
		```

		These match what `.daicrc` configures: `~/linuxhome/.local/bin` is on your `PATH`, and `MAMBA_ROOT_PREFIX` points to `~/linuxhome/.mamba`, so named environments are stored under `~/linuxhome/.mamba/envs`.
		These match what `.daicrc` configures: `~/linuxhome/.local/bin` is on your `PATH`, `MAMBA_ROOT_PREFIX` points to `~/linuxhome/.mamba`, and `CONDA_ENVS_PATH` points to `~/linuxhome/.conda/envs`, which is where named environments are stored. `micromamba info` lists the directories in use.

		To keep an environment in project storage instead, for example to share it with your group, create it by path with `-p` rather than by name:

		@@ -477,7 +479,7 @@ $ micromamba activate pytorch-env
		```shell-session
		$ micromamba env list
		Name Active Path
		pytorch-env * /home/netid01/linuxhome/.mamba/envs/pytorch-env
		pytorch-env * /tudelft.net/staff-homes-linux/n/netid01/.conda/envs/pytorch-env

		$ micromamba deactivate
		```