Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow customizing the conda directories #158

Merged
merged 2 commits into from
Oct 13, 2023
Merged

Allow customizing the conda directories #158

merged 2 commits into from
Oct 13, 2023

Conversation

enasca
Copy link
Member

@enasca enasca commented Sep 25, 2023

Moves the default conda directories away from user homes so that they can be placed on the appropriate storage, e.g. local raid or cached nfs.

The new default for the package cache is node-global rather than user-specific.

@enasca
Copy link
Member Author

enasca commented Sep 25, 2023

Still untested.

@enasca enasca force-pushed the conda-env-default-dir branch from 62d8969 to 8e78c7f Compare October 12, 2023 08:39
@enasca
Copy link
Member Author

enasca commented Oct 12, 2023

I'm reverting to one variable for both environments and packages. Putting the env directory and the package directory on different filesystems seems risky.

Environments and packages from the mamba installation directories
are included if the conda env root is changed.
@enasca enasca merged commit 1ad96fc into main Oct 13, 2023
@enasca enasca deleted the conda-env-default-dir branch October 13, 2023 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant