Skip to main content

Configuring conda-store

The conda-store server has two types of config.

  • server configuration config, eg. url for database endpoints, redis endpoints, port to run on, etc.
  • application settings config, eg. the default namespace, default conda command, default packages to install in environments, etc.

The server configuration is always specified in the conda-store configuration file.

There are two options to set the application settings config. These are through:

  • the conda-store configuration file. See the available options in the configuration options doc
  • the conda-store admin console. Available at <conda_store_url>/admin

There are multiple levels which settings config can be applied to conda store.

  • deployment defaults (controlled by the config file)
  • global defaults (controlled by the admin console)
  • namespace defaults (controlled by the admin console)
  • environment default (controlled by the admin console)

The most specific settings config will take precedence over the more general setting. For example, if the conda_command is specified in all four settings config levels, the most specific, environment settings config will be applied.

note

Since the deployment defaults are of lowest precedent when settings are being generated, it is likely that they will be overridden by another by another level, for example the global defaults.

So, it is recommended that users change global defaults from the admin console.

The full list of application settings config is described in the settings pydantic model.