Generic over your config model
ConfigSource
config port
generic config loading and templated content packs — the seal that validates what runs
Scarab is the org's config & template expertise: a generic config loading port (ConfigSource<T>/ConfigFormat<T> + a Discovery spec, generic over the consumer's serde model) and a templated content plane (type: template tamias packs rendered by a sandboxed MiniJinja engine).
Every repo was copy-pasting the same config-discovery dance — explicit path → $<NAME>_CONFIG → ./<name>.<ext> → ~/.config/<name>/ — and templated dotfiles/config packs had no shared mechanism. Scarab generalizes both once, behind ports, so consumers keep only their Config type.
type: template pack model/driver/engine.| You want to… | Go to |
|---|---|
| Load your first typed config | Tutorial |
| Do a task (custom discovery, layered configs, template packs) | How-to |
| Understand the design (ports, planes, boundaries) | Explanation |
| Look up a trait, type, or pack field | Reference |