# Environment Variables

## Cement Environment Variables

### CEMENT\_LOG

Parsed by the core framework, and extensions early on in runtime (before `App` is fully loaded). Triggers low-level framework logging, and toggles `App.Meta.framework_logging`.

Values: 

* `0`
* `1`

Usage:

```
export CEMENT_LOG=1
```

{% hint style="info" %}
This variable was introduced in Cement v3.0.8, and deprecates the previous setting [`CEMENT_FRAMEWORK_LOGGING`](https://docs.builtoncement.com/pages/BKKRWDUkncx4bT2liT3U#3.0.8-1).
{% endhint %}

### CEMENT\_FRAMEWORK\_LOGGING

Deprecated in 3.0.8 in favor of [CEMENT\_LOG](#cement_log) (same usage).

## Overriding App Configuration

Out of the box, Cement supports overriding application configuration settings by environment variables.

Configuration:

```yaml
myapp:
  foo: bar
```

The above configuration would be overridden by the `$MYAPP_FOO` environment variable.

```
export MYAPP_FOO=not-bar
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.builtoncement.com/environment-variables.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.