Configuration reference (AER 2.31)¶
- File storage
- Web server
Anaconda Repository will load configuration files with the extension
from the following locations:
$PREFIX is the location where Anaconda Repository was installed.
Files are loaded from these directories in order, with later files overriding earlier files. Files are loaded from each directory in alphabetical order.
If an environment variable ANACONDA_SERVER_CONFIG is set with the path of a configuration file, this file is loaded after the three already listed. Its settings will override any conflicting settings in the earlier files.
Each configuration setting variable can have its value set with the
anaconda-server-config --set command, or by editing a configuration file.
For example, you can set a value named VALUE_ONE to 50 by adding this to a configuration file:
Or you can set a value named VALUE_ONE to 50 with this command:
anaconda-server-config --set VALUE_ONE 50
A regular expression that defines the allowable user names.
For example, this setting specifies that user names will contain only lowercase letters and the period, plus, and minus characters (
NOTE: The default value for
^[a-z0-9_][a-z0-9_-]+$ which translates to: at least one alphanumeric character or underscore, followed by zero or more alphanumeric, dash or underscore characters.
NOTE: Escape any extra instances of the single quote character
\', and do not use the slash and ampersand characters
& which have special meanings in URLs.
NOTE: If USER_REGEX is changed and the server is restarted, existing usernames that do not match the new USER_REGEX will not cause errors.
Anaconda Repository uses MongoDB as the database backend.
A MongoDB connection URI used to connect to the MongoDB database server. It can be used to configure the hostname and port, as well as database authentication.
The MongoDB database where Anaconda Repository will store data used for asynchronous processing.
Anaconda Repository can serve package contents from a local file-system, or from Amazon Web Services Simple Storage Service (AWS S3).
The storage mechanism to use. Valid choices are
fs (for file-system storage) or
s3 (for AWS S3 storage).
The absolute path to a directory where Anaconda Repository will store all uploaded packages, if configured to use file-system storage.
When this option is set, Repository stores the files by full paths and not just
by hashes. This way a tensorflow file uploaded by the user Bob will be stored
NOTE: If you rename a user or transfer a file to a different user, the file location on the storage does not change, so the storage path does not always contain the current file owner and their user name.
The name of an AWS S3 bucket where Anaconda Repository will store uploaded packages, if configured to use AWS S3 storage.
You can identify the name of your bucket by the
<bucket> in your
The S3 region that the bucket is located in. The available regions can be found in the Amazon AWS documentation.
The name and port number of the server. This option is required for subdomain support.
If set to
true, Anaconda Repository will serve
conda package from a separate subdomain.
SERVER_NAME: anaconda.srv:8080 subdomains: true
Allows access to conda packages at
As a cross-site scripting (XSS) protection, notebook content can be served from a separate domain name. If this option is configured, Anaconda Repository will only serve rendered notebooks from this domain.
Anaconda Repository can serve content over HTTPS, using user-provided SSL certificates.
ssl_options: certfile: /etc/anaconda-server/server.crt keyfile: /etc/anaconda-server/server.key PREFERRED_URL_SCHEME: https
The preferred scheme that will be used to generate URLs. Set this to
https if HTTPS is configured.
gunicorn: timeout: 60 workers: 5
The number of seconds that a worker is allowed to process a request for, before being forcefully terminated. Defaults to 120.
The method Anaconda Repository will use to authenticate users. Valid choices are
NATIVE (for built-in authentication),
KERBEROS (for Kerberos) and
Options for configuring LDAP authentication and group synchronization.
LDAP: URI: ldap://ldap.server BIND_DN: cn=Anaconda Repository,cn=Users,dc=example,dc=com BIND_AUTH: Pa55w0rd USER_SEARCH: base: cn=Users,dc=example,dc=com filter: sAMAccountName=%(username)s KEY_MAP: name: cn OPTIONS: OPT_NETWORK_TIMEOUT: 60 OPT_TIMEOUT: 60
Anaconda Repository can be configured to send email for various reasons, including to reset forgotten usernames and passwords. Email can be sent using SMTP protocol, or through Amazon Web Services Simple Email Service (AWS SES).
The username to authenticate against the SMTP server before attempting to send email.
The password to authenticate against the SMTP server before attempting to send email.
If set to
true, Anaconda Repository will send email with AWS SES. To authenticate to AWS,
the server should be configured with
an appropriate IAM role,
or have credentials specified in a
Boto configuration file.
If set to
true, Anaconda Repository will allow different users to share the same email or secondary email.
The prefix that Cloudera parcels are generated with. Defaults to
The distributions that Cloudera parcels are generated for. Defaults to
['el5', 'el6', 'el7', 'lucid', 'precise', 'trusty', 'wheezy', 'jessie', 'squeeze', 'sles11', 'sles12'].
For example, if you only wish to support Ubuntu:
PARCEL_DISTRO_SUFFIXES: - lucid - precise - trusty
The Anaconda Repository accounts that environments installed with the
bundled Anaconda distributions will pull packages from.
For example, to add an additional
DEFAULT_CHANNELS: - anaconda - r-channel - custom
The maximum size (in bytes) of the
repodata.json requests cache. Set to
0 to disable
caching. Default: 1Gb. When the maximum size is reached, the 10 least recently used entries of the cache are