Currently, when users create an environment using conda-store, it is not automatically available for use in both the Terminal and Jupyter Notebook. This creates inconvenience and inefficiency as users have to manually configure their environments for each use case.
We need to ensure that newly created environments are automatically accessible for users in both ecosystems when they spin up a new lab server.
For reference, a similar functionality is implemented in Nebari (linked below). However, conveniently conda-store group environments seems to be already present on the user terminal so changes on this regard doesn't seem to be required (e.g catching the groups object as in the Nebari's implementation )
Feature description
Currently, when users create an environment using conda-store, it is not automatically available for use in both the Terminal and Jupyter Notebook. This creates inconvenience and inefficiency as users have to manually configure their environments for each use case.
We need to ensure that newly created environments are automatically accessible for users in both ecosystems when they spin up a new lab server.
For reference, a similar functionality is implemented in Nebari (linked below). However, conveniently conda-store group environments seems to be already present on the user terminal so changes on this regard doesn't seem to be required (e.g catching the
groups
object as in the Nebari's implementation )Reference: Nebari Environment Setup
Current Configuration Example:
Value and/or benefit
Users will be able to access and experiment with their conda-store environments.
Anything else?
No response