Configuration

Pedestal uses late binding to configure these values, so that it is possible to customize Pedestal’s behavior to the operating environment: anything from local developer to final production.

Pedestal will search a series of sources for a value that identifies the var; these are in a specific order, with an eye towards making it possible to override the value at runtime for testing or production, as that is often a need for these subsystems.

The intent is that a Pedestal application will typically include a pedestal-config.edn on the classpath (packaged with the application’s sources or compiled classes, typically stored in resources); the pedestal-test-config.edn will only be on the classpath during local testing (typically, stored in test-resources).

When necessary, these values can be overrridden when deployed to a staging or production deployment using environment variables or JVM system properties.

The contents of pedestal-config.edn (and pedestal-test-config.edn) are EDN maps.

The keys are the JVM property converted to a keyword (for example, :io.pedestal.log.overrideLogger).

The value can be either a qualified symbol, or a string that is converted to a qualified symbol.

Once a symbol is obtained from a configuration source, it is resolved to a Clojure Var. Each use of configuration has its own interpretation of the Var.

The following section list the current configuration values; each heading identifies the JVM system property, then the equivalent environment variable.