Configure deployment services and review their status
Understand service credentials, configuration overrides, and when a backend restart is needed.
On this page
Configure the database, JWT, administrator credentials, API domains and provider keys in your deployment environment. Website settings shows provider configuration status and lets you maintain non-secret sender information. Existing installations with database overrides retain compatibility until the operator explicitly migrates those values.
The operator console does not edit provider credentials. Existing database overrides are retained for compatibility; move them to your deployment secret configuration through an explicit operator-controlled migration before removing them.
Where the settings come from
New installations use deployment configuration for provider credentials. Website settings maintains public identity, support contacts and non-secret sender details. Existing provider overrides keep their previous precedence until explicitly migrated.
When changes apply
Public branding and article publication refresh through the website cache, usually within one minute of subsequent visits. Sender or deployment credential changes require a backend restart; a configured badge does not prove a successful connection.
What saving verifies
Status reports configuration, not external API permissions, email delivery or successful charges. Verify delivery and test payments in an isolated test environment. The local preview never activates external email or payments.
# First boot only; also configure your database, JWT, admin credentials and domains.
APP_AUTH_ENABLED=true
APP_AUTH_EMAIL_ENABLED=false
APP_AUTH_EMAIL_DEBUG=false
APP_AUTH_GOOGLE_ENABLED=false
APP_AUTH_GITHUB_ENABLED=false
APP_EMAIL_PROVIDER=none
APP_BILLING_ENABLED=false