Configuration

Local configuration documented

The current Compose file contains deliberate local-development defaults. Shared and production installations must not reuse those credentials or network assumptions.

Application URLs

• APP_URL identifies Katra Server.
• CLIENT_URL identifies the browser-facing Client.
• SANCTUM_STATEFUL_DOMAINS must contain the trusted Client and Server hosts used by cookie authentication.
• Reverb allowed origins contain host patterns rather than complete URLs.

Data and queues

• PostgreSQL is selected with DB_CONNECTION=pgsql.
• Redis backs cache, sessions, and queues.
• Horizon runs in a separate worker service.
• Scout uses Meilisearch for derived full-text indexes.

Realtime

Katra Server publishes to Reverb inside the service network. Katra Client receives the browser-facing Reverb host, port, scheme, and application key. The Reverb application secret stays server-side.

Meeting media

• LIVEKIT_URL is the Server-to-LiveKit control endpoint.
• LIVEKIT_PUBLIC_URL is the signaling URL supplied to authorized participants.
• The LiveKit API key and secret stay server-side.
• Shared environments require trusted HTTPS/WSS, an externally reachable advertised address, and proven direct UDP plus TURN fallback.

Mail

The local environment sends mail to Mailpit and does not relay it externally. A shared installation must configure a real mail transport without logging invitation bearer URLs.

Secrets

Keep secrets and environment-specific configuration outside source control. The static PostgreSQL, Reverb, and LiveKit values in the Compose file exist only for disposable localhost development.

Production secret distribution, rotation, recovery, and credential-leasing guidance remain part of the production deployment roadmap.