Connection information for Redis for build logs caching

The URI at which to access the database, including any credentials.

The default, configurable tag expiration time for time machine. Defaults to `2w`.

Configuration for storage engine(s) to use in Quay. Each key is a unique ID for a storage engine, with the value being a tuple of the type and configuration for that engine.

The preferred storage engine(s) (by ID in DISTRIBUTED_STORAGE_CONFIG) to use. A preferred engine means it is first checked for pullig and images are pushed to it.

The URL scheme to use when hitting Quay. If Quay is behind SSL *at all*, this *must* be `https`

The URL at which Quay is accessible, without the scheme.

The options that users can select for expiration of tags in their namespace (if enabled)

Connection information for Redis for user event handling

If true, pulls in which the pull audit log entry cannot be written will still succeed. Useful if the database can fallback into a read-only state and it is desired for pulls to continue during that time. Defaults to False.

The types of avatars to display, either generated inline (local) or Gravatar (gravatar)

The URL of the announce endpoint on the bittorrent tracker

The bittorent piece size to use. If not specified, defaults to 512 * 1024.

If specified, contact information to display on the contact page. If only a single piece of contact information is specified, the contact footer will link directly.

A list of client IDs of *Quay-managed* applications that are allowed to perform direct OAuth approval without user approval.

The list of storage engine(s) (by ID in DISTRIBUTED_STORAGE_CONFIG) whose images should be fully replicated, by default, to all other storage engines.

If TLS is supported, but terminated at a layer before Quay, must be true.

Whether to enable conversion to ACIs. Defaults to False

Whether or not to rotate old action logs to storage. Defaults to False

Whether the v2/ endpoint is visible. Defaults to True

Whether to allow anonymous users to browse and pull public repositories. Defaults to True

Whether to enable support for App repositories. Defaults to False

Whether to enable support for repository mirroring. Defaults to False

Require HTTPS and verify certificates of Quay registry during mirror. Defaults to True

Whether to support Bitbucket build triggers. Defaults to False

Whether to allow using Bittorrent-based pulls. Defaults to False

Whether to support Dockerfile build. Defaults to True

Whether users and organizations are allowed to change the tag expiration for tags in their namespace. Defaults to True.

Whether users can directly login to the UI. Defaults to True

Whether to support GitHub build triggers. Defaults to False

Whether GitHub login is supported. Defaults to False

Whether to support GitLab build triggers. Defaults to False

Whether Google login is supported. Defaults to False

Whether users being created must be invited by another user. Defaults to False

Whether to allow for "namespace-less" repositories when pulling and pushing from Docker. Defaults to True

Whether emails are enabled. Defaults to True

If set to true, autocompletion will apply to partial usernames. Defaults to True

Whether sessions are permanent. Defaults to True

Whether to proxy all direct download URLs in storage via the registry nginx. Defaults to False

If set to true, the _catalog endpoint returns public repositories. Otherwise, only private repositories can be returned. Defaults to False

If set to true, build logs may be read by those with read access to the repo, rather than only write access or admin access. Defaults to False

Whether non-encrypted passwords (as opposed to encrypted tokens) can be used for basic auth. Defaults to False

Whether to require invitations when adding a user to a team. Defaults to True

If the security scanner is enabled, whether to turn of/off security notificaitons. Defaults to False

Whether to turn of/off the security scanner. Defaults to False

Whether to automatically replicate between storage engines. Defaults to False

Whether super users are supported. Defaults to True

Whether to allow for team membership to be synced from a backing group in the authentication engine (LDAP or Keystone)

Whether users can be created (by non-super users). Defaults to True

Whether to collect and support user metadata. Defaults to False

Configuration for using GitHub (Enterprise) as an external login provider

Configuration for using GitHub (Enterprise) for build triggers

Configuration for using Gitlab (Enterprise) for external authentication

Configuration for using Google for external authentication

If specified, the e-mail address used as the `from` when Quay sends e-mails. If none, defaults to `support@quay.io`.

The SMTP password to use when sending e-mails.

The SMTP port to use. If not specified, defaults to 587.

The SMTP server to use for sending e-mails. Only required if FEATURE_MAILING is set to true.

The SMTP username to use when sending e-mails.

If specified, whether to use TLS for sending e-mails.

Maximum allowed size of an image layer. Defaults to 20G

If a namespace is defined in the public namespace list, then it will appear on *all* user's repository list pages, regardless of whether that user is a member of the namespace. Typically, this is used by an enterprise customer in configuring a set of "well-known" namespaces.

If specified, the long-form title for the registry. Defaults to `Red Hat Quay`.

If specified, the short-form title for the registry. Defaults to `Red Hat Quay`.

The endpoint for the security scanner

The number of seconds between indexing intervals in the security scanner. Defaults to 30.

Quay usernames of those users to be granted superuser privileges

If team syncing is enabled for a team, how often to check its membership and resync if necessary (Default: 30m)