Configuration reference
Tally reads literal environment settings. Keep its public HTTPS origin, browser address, and listening port consistent so sessions, CSRF checks, password reset links, and upgrades use the same address. For certificate setup, follow HTTPS in the installation guide.
Files and directories#
| Location | Contents |
|---|---|
~/.local/lib/godel-tally | Executable, launcher, uninstall script, and runtime helpers. |
~/.config/godel-tally/tally.env | Saved configuration and credentials, readable only by the installing user (0600). |
~/.local/share/godel-tally | Private native database data, TLS files, logs, container ownership records, and upgrade state. |
Set TALLY_INSTALL_DIR, TALLY_CONFIG_DIR, and TALLY_DATA_DIR to absolute paths before first installation to override these locations. XDG configuration and data roots are respected. Use the same custom configuration directory for updates and uninstall.
The saved file contains KEY=value lines, not shell commands. Do not add shell quotes, export, or variable substitution. Edit it with a text editor and restart Tally. Keep TALLY_SECRET_KEY stable and backed up: it protects saved connector and email credentials.
Ports and addresses#
| Setting | Default | Purpose |
|---|---|---|
TALLY_URL | https://localhost:8443 | Exact public origin; no path or trailing slash. |
TALLY_HTTP_BIND | 127.0.0.1:8443 | Production UI and API listener. Use installer --port to change it. |
TALLY_POSTGRES_PORT | 5433 | Managed PostgreSQL host port; choose before provisioning. |
TALLY_CLICKHOUSE_PORT | 8124 | Managed ClickHouse HTTP host port; choose before provisioning. |
TALLY_UPGRADE_BIND | 127.0.0.1:8789 | Private upgrade runtime listener; do not expose it publicly. |
Managed database ports must be 1024–65535. Existing database URLs determine their own ports. Changing only a saved managed database port does not reconfigure an already-created container or database server; plan such changes explicitly.
Configuration reference#
The repository's .env.example documents runtime, database, retention, email, registry, and development settings. Production installation generates credentials; development defaults are for local use.
Settings saved in the console may take precedence over environment defaults, notably email delivery. Credentials belong in the protected server configuration, never in NEXT_PUBLIC_* variables or committed files.