> For the complete documentation index, see [llms.txt](https://logbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://logbox.ortusbooks.com/usage/logbox-in-a-coldbox-application/configuration-within-coldbox.md).

# Configuration Within ColdBox

ColdBox allows for a programmatic approach via the `ColdBox.bx` (or `.cfc` for CFML) 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.bx` (or `.cfc` for CFML) exist in the application's `config` folder?
       * **True**: Use that class 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 (class)
       * **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 (class).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://logbox.ortusbooks.com/usage/logbox-in-a-coldbox-application/configuration-within-coldbox.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.