INBUXA_RECOVERY_ADMIN and INBUXA_WEBMAIL_CLIENT_SECRET can come instead from a file that INBUXA_RECOVERY_ADMIN_FILE or INBUXA_WEBMAIL_CLIENT_SECRET_FILE names, such as a mounted Kubernetes or Docker secret, so a secret never has to sit in the environment, where anything that can read the process's environment or the pod spec sees it. The relay's INBUXA_RELAY_JOIN_TOKEN takes _FILE the same way. The file's trailing newline is dropped. Both forms set, or a file that can't be read or is empty, stops the server as it starts (boot checks every one), naming the variable and the path, never the secret. The rule lives in types::branding::secret_env_var, its core a pure function the unit tests drive; SECRET_ENV_VARS lists the variables it covers.