Configuration

Non-secret settings (public URL, CORS, ports, TTLs) live in config.toml — the installer puts it in your install directory and compose mounts it. Secrets stay in .env. Settings resolve in this order:

1. EDDYTOR__SECTION__KEY env override (e.g. EDDYTOR__SERVER__PUBLIC_URL=https://app.example.com)
2. $EDDYTOR_CONFIG_FILE path
3. ./eddytor.toml
4. /etc/eddytor/config.toml
5. Built-in defaults

The shipped config.toml documents every section and field inline. Restart the containers after editing — config is read at boot.

Required env

The installer generates all of these into .env for you. In compose, persist the secrets volume — losing the encryption key means losing every stored secret.

CORS

server.cors.allowed_origins is an allowlist of origin patterns — literal, or glob via * (multi-level, matches across dots):

[server.cors]
allowed_origins = [
  "https://app.example.com",   # exact
  "https://*.example.com",     # any subdomain
  "http://localhost:*",        # any localhost port (dev)
]
allow_credentials = true

TLS

Eddytor's binaries speak plaintext everywhere, and TLS is terminated at the edge: a reverse proxy or load balancer (Nginx, Envoy, ALB, Traefik, Caddy) in front of the server's :8080, or a service mesh in Kubernetes. Set server.public_url to the HTTPS hostname your edge serves. There is no internal cert mesh to manage.

Email (SMTP)

Magic-link sign-in sends a link by email. With no SMTP configured (the default), links are written to the server logs instead — fine for a solo operator, but to let teammates log in set EDDYTOR_SMTP_HOST, _PORT, _USER, _PASS, _FROM in .env (SES SMTP, Postfix, Mailgun, …).