# Configuration Within ColdBox

ColdBox allows for a programmatic approach via the `ColdBox.cfc` configuration object. So let's look at how the ColdBox loader looks at your configuration:

1. Is there a `logBox` variable defined in the configuration?
   * **False**:
     * Does a `LogBox.cfc` exist in the application's `config` folder?
       * **True**: Use that CFC by convention to configure LogBox
       * **False**: Continue to next point
     * Configure LogBox with default framework settings (`coldbox.system.web.config.LogBox`)
   * **True**:
     * Have you defined a `configFile` key?
       * **True**: Then use that value to pass into the configuration object so it can load LogBox using that configuration file (CFC)
       * **False**: The configuration data is going to be defined inline here so process it

So the configuration DSL is exactly the same as you have seen in before with the only distinction that you can add a `configFile` key that can point to an external configuration file (CFC).


---

# 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://logbox.ortusbooks.com/master/usage/logbox-in-a-coldbox-application/configuration-within-coldbox.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.