> For the complete documentation index, see [llms.txt](https://docs-lunar.earthly.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-lunar.earthly.dev/configuration.md).

# Configuration

- [lunar-config.yml](https://docs-lunar.earthly.dev/configuration/lunar-config.md): Reference for lunar-config.yml — the central configuration file defining hub connection, catalogers, domains, components, collectors, initiatives, and policies.
- [About images](https://docs-lunar.earthly.dev/configuration/lunar-config/images.md): Configure default container images for collectors, policies, and catalogers in lunar-config.yml, with override precedence rules.
- [catalogers](https://docs-lunar.earthly.dev/configuration/lunar-config/catalogers.md): Define the catalogers section of lunar-config.yml — scripts that synchronize domain and component metadata from external systems.
- [catalogers/hooks](https://docs-lunar.earthly.dev/configuration/lunar-config/cataloger-hooks.md): Configure cataloger hooks in lunar-config.yml — triggers like cron schedules or repository events that determine when catalogers run.
- [domains](https://docs-lunar.earthly.dev/configuration/lunar-config/domains.md): Define the domains section of lunar-config.yml — hierarchical groupings that organize related components for ownership and policy targeting.
- [components](https://docs-lunar.earthly.dev/configuration/lunar-config/components.md): Define the components section of lunar-config.yml — repositories or monorepo subdirectories that Lunar monitors with metadata and tags.
- [collectors](https://docs-lunar.earthly.dev/configuration/lunar-config/collectors.md): Define the collectors section of lunar-config.yml — scripts that run on CI, code, or cron triggers to gather component metadata.
- [collectors/hooks](https://docs-lunar.earthly.dev/configuration/lunar-config/collector-hooks.md): Configure collector hooks in lunar-config.yml — triggers like CI commands, code events, or cron schedules that determine when collectors run.
- [initiatives](https://docs-lunar.earthly.dev/configuration/lunar-config/initiatives.md): Define the initiatives section of lunar-config.yml — groupings of policies around shared goals or compliance requirements.
- [policies](https://docs-lunar.earthly.dev/configuration/lunar-config/policies.md): Define the policies section of lunar-config.yml — rules that Lunar evaluates against components to enforce standards and check health.
- [on (tag matching)](https://docs-lunar.earthly.dev/configuration/lunar-config/on.md): Reference for the on field in lunar-config.yml — tag-matching expressions used by collectors, policies, and initiatives to target components.
- [Validating your config](https://docs-lunar.earthly.dev/configuration/lunar-config/validation.md): Validate lunar-config.yml at commit/PR time — before merge — with a Hub-less dry run that runs the same checks the Hub does, plus a generated JSON Schema.
- [lunar.yml](https://docs-lunar.earthly.dev/configuration/lunar-yml.md): Reference for lunar.yml, the optional per-repository file that configures a single component's owner, domain, branch, tags, and CI pipelines.


---

# 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 dynamically by asking a question.

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

```
GET https://docs-lunar.earthly.dev/configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.