Documentation menu

Deployment Configuration

Configure device selection, presentation, input, and fonts at their owning startup boundaries.

A deployment supplies the settings that let Hera choose devices and construct its services. herad translates those values into explicit server, renderer, and input configuration, while some subsystems read additional startup-only environment settings. Set them before launching each participating process so initialization sees a consistent configuration.

Output Devices

Use HERA_DRM_NODE to choose the DRM display node and HERA_RENDER_NODE to choose the render node. If a particular output mode is required, HERA_DRM_MODE supplies a request such as 1920x1080@60. The selection code still checks that request against available modes and the output's admitted configuration.

A requested output still needs compatible routing, planes, formats, and driver support. Treat a mode-selection failure as a startup capability issue rather than a client layout problem.

Presentation Behavior

The renderer selects its storage path from device capabilities when HERA_PRESENT_MODE is auto. Setting it to zero or cpu requests that path explicitly, with aliases documented in the selection implementation. A forced zero-copy request fails if the device lacks required extensions, making an unsupported configuration visible at startup.

HERA_RENDER_AHEAD=1 enables triple buffering through daemon configuration. It changes available in-flight storage; it does not make active scanout images immediately reusable.

For output diagnostics, enable the renderer's profile overlay with HERA_PROFILE_OVERLAY=1; displaying damage outlines also requires the build's damage-overlay feature. The separate HERA_PRECISE_TIMER=1 setting selects the daemon's precise timer option when timing experiments need it.

Input Configuration and Shell Identity

Input discovery begins in the directory selected by HERA_INPUT_DIR. Keyboard interpretation can be configured with HERA_XKB_LAYOUT, together with HERA_XKB_VARIANT and HERA_XKB_OPTIONS when a layout is explicitly supplied. For cursor diagnostics, HERA_DEBUG_CURSOR=1 enables the server's debug cursor behavior.

HERA_SHELL_UID sets the configured shell user identity used by privileged shell policy. It is part of the deployment's trust configuration, not an application preference.

The ordinary daemon boolean parser accepts 0, 1, false, and true for its boolean settings. The precise-timer setting is handled separately and is enabled specifically by 1.

Font Registration

Supply HERA_FONT_REGISTRY with the path to a JSON registration manifest and HERA_FONT_PATH with the configured fallback face when needed. Paths within the manifest are resolved relative to that file. Registrations, including load failures, are cached after their first load, so prepare the assets and environment before startup.

Use identical manifests and bytes in client shapers and the server. Keep app-owned assets and licenses in apps/<app>/assets/ and app-specific launch scripts in apps/<app>/scripts/.

Logging Configuration

The daemon initializes tracing with RUST_LOG filtering. Release builds compile out routine tracing below the workspace's configured maximum level, so raising a runtime filter cannot restore an event removed at compile time.

See performance and troubleshooting for diagnostic use.

Source Reference

The following files in the Hera checkout define the behavior described on this page.

  • apps/herad/src/config.rs
  • apps/herad/src/main.rs
  • crates/renderer/src/present/selection.rs
  • crates/font/src/registry.rs
  • Cargo.toml