The one place every Hyper configuration value is read.
Configuration is layered, highest priority first:
/etc/hyper/config.exs— runtime app env, unprivileged node only. The right place for secrets loaded at boot./etc/hyper/config.toml— static, shared withhyper-suidhelper. Anything that influences a root process lives here so the two sides can never drift.- Compile-time
config/config.exs— performance fine-tuning. - Built-in defaults.
Each value names which of these layers it may be read from. Privileged tool
paths and the helper-shared [jails] table are config.toml-only, so the
unprivileged config.exs can never override a root-impacting path.
Read values through the focused submodules — Hyper.Cfg.Tools,
Hyper.Cfg.Dirs, Hyper.Cfg.Jails, Hyper.Cfg.Budget, ... — never reach for
Application.get_env or Hyper.Cfg.Toml directly.