Node Config Defaults
Overview
Node config defaults are inheritable settings that provide baseline behavior for nodes. They are supplied by ancestors (and service/platform) and are resolved by a mechanism similar to that of service config config.
- Inheritance mechanism: see inheritable config flow
- Operational (final) config: see operational config flow
- Folder overview for config flows: see meshnode config flows
Common default settings (examples)
- Flow versioning: on/off (whether abstract flows create
_vN/snapshots on weave) - Distribution syntaxes: preferred serializations (e.g., TriG, JSON‑LD)
- Resource pages and fragments: enable page/fragment generation; template and stylesheet selection
- Aggregated distributions: on/off for generating top-level rollups
- Rights & provenance defaults: copyright/licensing/attribution/delegation policies (applied at snapshot time)
These defaults apply when a node does not specify the setting in its operational config flow; “most specific wins” from parent → service → platform (see inheritable config flow for precedence).
Minimal guidance
- Keep defaults lightweight; override at the node only when needed
- Prefer repository‑level templates/css in
_assets/for consistency (see assets tree) - Review defaults when moving/embedding meshes to ensure expected publication behavior
Backlinks