- 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.
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.
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 30.
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
Anaconda Repository can be configured to send email after launching kapsels. 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.
The prefix that Cloudera parcels are generated with. Defaults to