Configuration

There is no settings database and no config file besides the two .env files and the mail templates. Everything an instance needs is an environment variable read once at startup, which makes an instance reproducible from its .env and its database.

The single exception is the login background image, which an admin uploads from /admin/settings and which is stored in the main S3 bucket, not in configuration.

Page	Covers
Server configuration	The server’s .env, group by group: application URLs and secret, database, storage, mail, cloud sync, PIM.
Client configuration	The client’s build-time variables: API endpoint and brand colours.
Email templates	The mailconfig.json format, the seven templates and the variables each can use.
Branding	Everything that changes the look: app name, colours, login background, logo and favicon.

The exhaustive table with defaults is Environment variables. Provider setup (Dropbox app, Azure registration, SMTP, buckets) is in Integrations.

Caution

Two defaults are safe on a laptop and dangerous on a server: APP_SECRET (signs every session token) and the MinIO credentials in MAIN_S3_URL / ASSETS_S3_URL. Change both before exposing an instance.