Configuration Reference¶

Privitty Edge is configured via environment variables or CLI flags. Priority (highest wins):

CLI flag  >  Environment variable  >  Built-in default

Environment variables¶

Variable	Required	Default	Description
`PRIVITTY_PROFILE`	Yes (first run)	—	Gateway display name; local part used during provisioning
`PRIVITTY_LISTEN`	No	`127.0.0.1:7200` (binary) / `0.0.0.0:7200` (Docker `CMD`)	HTTP listen address
`PRIVITTY_ACCOUNTS`	No	`accounts` (binary) / `/var/lib/privitty` (Docker)	Persistent data directory
`PRIVITTY_SERVER`	No	`chat.privittytech.com`	Privitty relay hostname
`PRIVITTY_LICENSE_URL`	No	—	License delivery URL — activates on first start if no `.lic` file yet
`RUST_LOG`	No	`info`	Log level: `error`, `warn`, `info`, `debug`, `trace`

CLI equivalents¶

Flag	Env var
`--profile`	`PRIVITTY_PROFILE`
`--listen`	`PRIVITTY_LISTEN`
`--accounts`	`PRIVITTY_ACCOUNTS`
`--server`	`PRIVITTY_SERVER`
`--license-url`	`PRIVITTY_LICENSE_URL`
`--cors`	(no env var — CLI/CMD only)

Docker-specific settings¶

Inside a container, always set:

PRIVITTY_LISTEN=0.0.0.0:7200
PRIVITTY_ACCOUNTS=/var/lib/privitty

Mount a volume at /var/lib/privitty for persistence.

Enable CORS for web-based HMIs by overriding the container command:

command: ["--listen", "0.0.0.0:7200", "--accounts", "/var/lib/privitty", "--cors"]

Reference config file¶

The image includes /etc/privitty/privitty-edged.toml as an operator reference. The daemon does not parse this file at runtime — it documents the available settings.

Mount your own copy for on-site documentation:

-v /host/my-config.toml:/etc/privitty/privitty-edged.toml:ro

Persistent data layout¶

Everything under PRIVITTY_ACCOUNTS (typically /var/lib/privitty):

Path	Content
`privitty.lic`	License JWT
`device.uuid`	Stable device identifier
`license_server.txt`	License server base URL
`activation.json`	Activation metadata
`accounts/`	SQLite database, keys, blobs (internal)

Warning

Treat this directory as sensitive. It contains cryptographic keys. Restrict filesystem permissions and back up regularly.

Connectivity states¶

Query with get_connectivity (see Curl Cookbook):

Value	Meaning
`0`	Not configured
`1–1999`	Not connected
`2000–2999`	Connecting
`3000–3999`	Connected (working)
`4000+`	Fully connected

CLI client settings¶

The privitty-edge CLI connects to the daemon via:

Flag	Env var	Default
`--endpoint`	`PRIVITTY_ENDPOINT`	`http://127.0.0.1:7200`

When running CLI via docker exec, the default endpoint (127.0.0.1:7200) works because exec runs inside the same network namespace as the daemon.