Running Server: settings, backups, updates

Settings

Server reads its settings from environment variables, or from a corexar.conf file. The full, generated list is docs/CONFIGURATION.md in the platform repository; the common ones are on the Configuration page of this site. The application checks all settings when it starts and stops with a list of everything wrong, rather than one error at a time.

What to back up

• The PostgreSQL database (a dump) and the media bucket (MinIO or S3).
• The secrets, above all ENCRYPTION_PEPPER: without it encrypted collections cannot be read, and it must never be changed once data is encrypted.
• For Home: the data folder.

Updating

Server: pull the new images and start them (docker compose pull, then docker compose up -d). Database migrations run automatically on start. Home: download the new archive and replace the application; the data folder is untouched.

What protects the installation

• Brute-force protection: failed sign-ins, password changes, recovery requests and unlock attempts are counted per address and per user, and the blocked party is the one guessing, never the account being guessed.
• Sessions can be revoked at once; a banned or deleted account loses its access immediately.
• Cross-origin access (CORS) is closed unless you list websites that may call the API.
• Optional Redis shares counters and revoked sessions between several instances; without it they live in the process memory.
• E-mail (SMTP) enables invitations by mail, password recovery, confirmation of new accounts and security notices; without it none of these are sent.