Skip to content
EON Path
Configuration

Configuration

Configuration surfaces

EON Path’s components are configured differently depending on how they’re deployed:

  • The server daemon (eonpath-server) is configured through an environment file, /etc/eonpath/server.env, read by its systemd unit. A small number of less common settings are only available as command-line flags. See Server.
  • The desktop and mobile clients are configured through a YAML file, eonpath.conf, that lists the servers and endpoints you connect to. See Client.
  • The API server (eonpath-api) is configured through its own environment file, /etc/eonpath/api.env, covered in the server install guide since it ships alongside the server daemon.

File locations

ComponentConfiguration fileState directory
eonpath-server/etc/eonpath/server.env/var/lib/eonpath/
eonpath-api/etc/eonpath/api.env/var/lib/eonpath/api/
Desktop client~/.config/eonpath/eonpath.conf (Linux/Windows) or ~/eonpath.conf (macOS)OS keyring (auth tokens), ~/.config/eonpath/

After editing a server-side environment file, restart the corresponding systemd service to apply the change:

sudo systemctl restart eonpath-server
sudo systemctl restart eonpath-api

Format notes

  • Environment files (server.env, api.env) use KEY=value lines, parsed by systemd’s EnvironmentFile directive. Values are not quoted. Lines starting with # are comments.
  • eonpath.conf is a YAML file. It’s read and (when you change settings in the client UI) rewritten by the application, so hand edits are preserved but comments are not.

See Server and Client for the full key reference, or API for the REST management API and the VPN authentication protocol.