Skip to content

values.emporium.yaml File

At its heart, an app is a Helm chart that contains a unique values.emporium.yaml file. This file delineates how Emporium should configure your app and what inputs it needs from the user. It serves as a template for the values fed into helm install.

Available Variables

This section lists all variables available within values.emporium.yaml.

VariableDescription
.Emporium.NameThe name of the app instance, input by the user in the Emporium UI.
.Emporium.AnnotationsAnnotations for ingresses, configured automatically by Emporium.
.Emporium.UserSupplied.[your-variable-name]User-supplied values, specified by the @userSupplied syntax.

DNS Integration

The following variables are provided by the DNS integration.

VariableDescription
.Emporium.Integrations.DNS.HostnameHostname for the application, input by the user in the Emporium UI. (eg. myapp.funupupu.io)
.Emporium.Integrations.DNS.ZoneDNS Zone of the deployment. (eg. funupupu.io)
.Emporium.Integrations.DNS.SubdomainSubdomain of the application (eg. myapp)

OIDC Integration

The following variables are provided by the OIDC integration.

VariableDescription
.Emporium.Integrations.OIDC.ClientIDOIDC client id
.Emporium.Integrations.OIDC.ClientSecretOIDC client secret
.Emporium.Integrations.OIDC.ConfigurationEndpointOIDC configuration endpoint (/.well-known/openid-configuration)
.Emporium.Integrations.OIDC.IssuerOIDC issuer

Storage Integration

The following variables are provided by the storage integration.

VariableDescription
.Emporium.Integrations.Storage.ClaimsMap of storage claims.
.Emporium.Integrations.Storage.Claims.[Key].NameName of the storage claim identified by [Key].
.Emporium.Integrations.Storage.Claims.[Key].StorageClassStorage class of storage claims.
.Emporium.Integrations.Storage.Claims.[Key].CapacityCapacatiy of the storage claim (e.g. 100Gi or 2Ti).

Email / SMTP Integration

The following variables are provided by the smtp integration.

VariableDescription
.Emporium.Integrations.SMTP.HostSMTP hostname, configured by the user in the Emporium UI.
.Emporium.Integrations.SMTP.PortSMTP port, configured by the user in the Emporium UI.
.Emporium.Integrations.SMTP.UsernameSMTP username, configured by the user in the Emporium UI.
.Emporium.Integrations.SMTP.PasswordSMTP password, configured by the user in the Emporium UI.
.Emporium.Integrations.SMTP.FromSMTP from email address, configured by the user in the Emporium UI.
.Emporium.Integrations.SMTP.ReplyToSMTP reply to email address, configured by the user in the Emporium UI.

User Supplied Variables

All variables in the form of .Emporium.UserSupplied.[your-variable-name] will have to have a corresponding @userSupplied definition.

Check out the @userSupplied documentation for a more detailed explanation.

Integrations

Emporium discovers automatically which integrations an app references in it's values.emporium.yaml file. It will render the install screen based on the used integrations and ´@userSupplied´ values.

For example, if an app uses the SMTP / Email integration, Emporium will render a dropdown menu where users can select an email account.

Rendering Process

The following diagram illustrates the process how values.emporium.yaml is used to install an app in your cluster.

null