> For the complete documentation index, see [llms.txt](https://cachebox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cachebox.ortusbooks.com/5.x-1/configuration/cachebox-configuration/cachebox-dsl.md).

# CacheBox DSL

In order to create a simple data CFC, just create a new CFC with one required method on it called `configure()`. This is where you will define the caching configuration data structure in a structure called `cacheBox` in the `variables` scope:

```javascript
**
* A CacheBox configuration data object
*/
component{

    function configure(){
        cacheBox = {

        };
    }
}
```

The cacheBox structure can be configured with the following keys:

| Key               | Type   | Required | Default                                         | Description                                                                                                                                                                                                                                                          |
| ----------------- | ------ | -------- | ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| logBoxConfig      | string | false    | `cachebox.system.cache.config.LogBox`           | The instantiation or location of a LogBox configuration file. This is only for standalone operation.                                                                                                                                                                 |
| scopeRegistration | struct | false    | `{enabled=true,scope=application,key=cacheBox}` | A structure that enables scope registration of the CacheBox factory in either server, cluster, application or session scope.                                                                                                                                         |
| defaultCache      | struct | true     | ---                                             | The configuration of the default cache which will have an implicit name of default which is a reserved cache name. It also has a default provider of CacheBox which cannot be changed.                                                                               |
| caches            | struct | true     | `{}`                                            | A structure where you can create more named caches for usage in your CacheBox factory.                                                                                                                                                                               |
| listeners         | array  | false    | `[]`                                            | An array that will hold all the listeners you want to configure at startup time for your CacheBox instance. If you are running CacheBox within a ColdBox application, this item is not necessary as you can register them via the main ColdBox interceptors section. |


---

# 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://cachebox.ortusbooks.com/5.x-1/configuration/cachebox-configuration/cachebox-dsl.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.