Skip to content

scarabconfig & template expertise

generic config loading and templated content packs — the seal that validates what runs

What it is ​

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).

Why ​

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.

Boundary ​

  • Owns: config discovery + formats, the type: template pack model/driver/engine.
  • Doesn't own: secret values (cuora), distribution (tamias), releases (tarsi).

Where to go next ​

You want to…Go to
Load your first typed configTutorial
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 fieldReference