GETTING STARTED

Configuration

Understand the settings that connect EveryOS to your host.

API configuration

The API configuration lives at /etc/everyos/config.yaml. Values resolve in order: environment variables, YAML, then built-in defaults. Unknown keys or invalid values fail with a startup error. The example is for access through a local HTTPS reverse proxy; replace the example origin.

YAML
server:
  host: 127.0.0.1
  port: 7470
  trustedProxies: [127.0.0.1]
  publicOrigins: ["https://everyos.example.com"]

Apply changes

After editing the root-owned configuration, restart the API and check its service status. Generic defaults bind to loopback; the verified installer enables IPv4 network access only for a fresh configuration. Upgrades retain existing bindings.

Bash
sudo systemctl restart everyos-api.service

Keep data and keys together

Application data is in /var/lib/everyos; agent policy is in /etc/everyos/agent.yaml. Preserve secret keys with your backups. Host-file access also requires explicit permissions and compatible systemd policies; adding a path to configuration alone does not grant access.

Based on EveryOS v0.1.38

View source · configuration.md