Configure production credentials, storage, networking, and optional services for a Kuest operator site.
Start with the required runtime values, then choose exactly one storage profile. Add network overrides and operational integrations only when your deployment needs them.
If the KUEST_* credentials are missing or invalid, users can browse markets, but trading authentication and Deposit Wallet flows will fail.
Better Auth sessions and encrypted trading credentials.
Generate a random value with at least 32 characters.
CRON_SECRET
Authentication for scheduled sync routes.
Generate a random value with at least 16 characters.
POSTGRES_URL
Runtime database for users, settings, events, markets, and migrations.
Use the PostgreSQL URL supplied by your database provider.
Treat BETTER_AUTH_SECRET as a persistent production secret. Rotating it invalidates existing sessions and can make previously encrypted credentials unreadable.
The application defaults to Kuest services. Set these variables only when routing traffic through a Custom Domain, a private proxy, or another supported runtime endpoint.
Keep package names and HTTP headers exactly as documented by the corresponding API. URL variables make the same integration portable across operator environments.
Send runtime errors from the server and user-facing application to Sentry.
SENTRY_ORG
Identify the Sentry organization for build-time release integration.
SENTRY_PROJECT
Select the project that receives source maps and release artifacts.
SENTRY_AUTH_TOKEN
Authenticate build tooling that uploads releases or source maps.
EVENT_CREATION_SIGNER_PRIVATE_KEYS
Sign recurring or server-scheduled event creation. Accepts comma-separated private keys or a JSON array.
Private keys, Kuest credentials, storage keys, database URLs, and service-role keys must remain server-side. Store them in your hosting provider’s encrypted secret manager.
