# Complete native TOML examples

See the [complete configuration reference](../../docs/configuration.md) for all
fields, types, defaults and constraints. Copy a file into your deployment
directory and prepare trusted TALs in its input/ directory. The fixed example
also needs a valid, matching ripe.cer. No live inputs are bundled here.

| File | Purpose |
| --- | --- |
| [validate-minimal.toml](validate-minimal.toml) | Minimal automatic TA; built-in defaults |
| [validate-full.toml](validate-full.toml) | Common/validate settings, strict completion, successful publication |
| [validate-fixed.toml](validate-fixed.toml) | Fixed TA certificate |
| [daemon-all5.toml](daemon-all5.toml) | Five automatic TAs, continuous operation |
| [daemon-three.toml](daemon-three.toml) | Five automatic TAs, three cycles with independent state |

For example, copy validate-full.toml to /srv/panda/validate.toml and prepare
/srv/panda/input/ripe.tal:

```bash
panda-rpki validate --config /srv/panda/validate.toml --check-config
panda-rpki validate --config /srv/panda/validate.toml --print-config
panda-rpki validate --config /srv/panda/validate.toml
```

Paths are relative to the configuration file. Automatic mode refreshes the TA
certificate, never the TAL. Uncomment ta or constraints only after preparing the
corresponding files. Omitted constraints still discovers a same-stem file when
one exists.

Full/daemon examples explicitly choose require-complete=true and
run-timeout-secs=1800; built-in defaults are false and 0. Use the
[Docker examples](../../docker/examples/README.md) for container paths.