-
Notifications
You must be signed in to change notification settings - Fork 111
Closed
Labels
area: integration/conda-storeneeds: discussion π¬Needs discussion with the rest of the teamNeeds discussion with the rest of the teamtype: enhancement π
πΌNew feature or requestNew feature or request
Description
Nebari now has the capability to have git-based conda environments (currently defined in the nebari_config.yaml) and environments created by end users through the conda-store UI after installation. The user created environments are stored in a database. Conda-Store also has fairly rich namespace features.
Several questions come up.
- Should Nebari continue to support git based environments in the nebari-config.yaml
- Should we point to another git repo/folder that just contains a collection of environment.yaml files
- Should this functionality actually move to conda-store
One of the main advantages of git based environments is having a set of curated default environments that are available immediately after install. Also currently, due to a lack of a robust backup/restore system, environments in the conda-store database are not fully/easily reproducible across a reinstall of conda-store.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area: integration/conda-storeneeds: discussion π¬Needs discussion with the rest of the teamNeeds discussion with the rest of the teamtype: enhancement π
πΌNew feature or requestNew feature or request
Type
Projects
Status
Done πͺπΎ