What's on this page

• Environment variables
• CLI option

Override configuration

The configuration can be overridden without editing the configuration file, through environment variables or a CLI option.

Environment variables

The configuration can be overridden through environment variables.

At startup, Cecil also attempts to load a .env file from the current site path (the current working directory, or the <path> argument if provided).

• If the .env file does not exist, Cecil continues normally.
• Variables already defined by the shell/system are preserved.

Each environment variable name must be prefixed with CECIL_ and the configuration key must be set in uppercase. Nested keys are separated with _ (e.g.: CECIL_PAGES_DIR sets pages.dir), so keys that contain an underscore can't be set this way. Boolean-like values (true/false, 1/0, yes/no, on/off) are converted to booleans.

For example, the following command sets the website’s baseurl:

export CECIL_BASEURL="https://example.com/"

You can store the same value in a .env file at your project root:

CECIL_BASEURL="https://example.com/"
CECIL_TITLE="My Cecil site"

CLI option

You can combine multiple configuration files with the --config option of the build and serve commands:

php cecil.phar build --config config-1.yml,config-2.yml

The files are merged from left to right, after the main configuration file: a scalar value is replaced by the last one defined, maps are merged key by key, lists of values are replaced (or adjusted with a map of booleans), output formats are merged by name and other lists of entries (e.g. menus) are concatenated.

---