Configuration

The Python Settings model is the field reference; deployment credentials remain private.

Configure from the code

Use .env.example and Settings for providers, state paths and device transports. Home Assistant HUD overrides and an SSH target configure connections but do not prove reachability.

Optional integrations require their own dependencies, credentials and account scopes. Check the active process configuration rather than assuming an edited file was loaded.

Browser separation

HUD_GATEWAY_ORIGIN configures the development broker. Do not put root or provider credentials in VITE-prefixed values, which can enter browser code.

Consent requires updated brain, gateway and frontend routes. Reads can still work against an older deployment while approvals remain unavailable.

Generated field reference

The Settings reference page lists every annotated field, its declared type and environment names or aliases directly from config.py. It deliberately excludes loaded values and defaults so no owner configuration is published. Process-specific gateway variables remain documented by their implementation.

Implementation sources

Repository paths below describe the implementation. They do not certify a running deployment or a configured external account.

  • src/mushegh/config.py
  • .env.example
  • clients/hud-spatial/vite.config.ts

Subsystem directory · HUD guide · Verification and known limits