# YAML reference

> Every key of every YAML file a DRE project uses, generated from the JSON Schemas.

A DRE project is YAML and SQL files. Each kind of YAML file has a reference page that lists every key with its type, default and meaning. The pages are generated from the same [JSON Schemas](https://getdre.com/docs/editor-setup/) that give editors autocomplete, so they can’t miss a key.

File

What it holds

Reference

`dre_project.yml`

The project: default profile and output, variables, week settings, folder config

[dre\_project.yml](https://getdre.com/docs/reference-project/)

`reports/**/*.yml`

A report: queries, output, destinations, Sets, templates

[Report YAML](https://getdre.com/docs/reference-report/)

`sets.yml`

Named variants a report can run as

[sets.yml](https://getdre.com/docs/reference-sets/)

`schedules.yml`

Named schedules your orchestrator fires

[schedules.yml](https://getdre.com/docs/reference-schedules/)

`timings.yml`

Named timings that schedules share

[timings.yml](https://getdre.com/docs/reference-timings/)

`profiles.yml`

Connections: sources and destinations (kept outside the project)

[profiles.yml](https://getdre.com/docs/reference-profiles/)

`dependencies.yml`

Plugin packages and macro packages

[dependencies.yml](https://getdre.com/docs/reference-dependencies/)

`lookups/<name>.yml`

The config of a lookup file

[Lookup config](https://getdre.com/docs/reference-lookups/)

The options of each format and destination (for example `delimiter`, or an email’s `to`) are documented with their plugins in [Plugins](https://getdre.com/docs/plugins/); that reference comes from the plugins themselves.

For editor autocomplete and validation, see [Editor setup](https://getdre.com/docs/editor-setup/).

[Edit page](https://github.com/get-dre/dre/edit/master/docs/yaml-reference.md)

[Previous  
Building from source](https://getdre.com/docs/building-from-source/)[Next  
Editor setup](https://getdre.com/docs/editor-setup/)