Korieo Community Docs

Configuration

Configure environment variables, database access, authentication, repository integration, and local settings.

Environment variables

Start with placeholders and replace values only when the corresponding service is ready. Do not commit secrets or share environment files in public issue reports.

DATABASE_URL=
AUTH_SESSION_SECRET=
TOKEN_ENCRYPTION_KEY=
NEXT_PUBLIC_SUPABASE_URL=
NEXT_PUBLIC_SUPABASE_ANON_KEY=
NEXT_PUBLIC_APP_URL=http://localhost:3000
AUTHZ_MODE=mock
DEV_AUTH_BYPASS=true
GITHUB_TOKEN=
GITHUB_OWNER=
GITHUB_REPO=

Database configuration

Set DATABASE_URL to the approved local database connection string. Confirm the database exists, migrations have been applied if required, and the app user has the expected permissions.

Authentication configuration

Set AUTH_SESSION_SECRET, TOKEN_ENCRYPTION_KEY, NEXT_PUBLIC_SUPABASE_URL, and NEXT_PUBLIC_SUPABASE_ANON_KEY for the supported auth/session flow. For local mock evaluation, use AUTHZ_MODE=mock with DEV_AUTH_BYPASS=true and the DEV_AUTH_* values your workspace needs. Redirects and generated links should use NEXT_PUBLIC_APP_URL matching the URL used in the browser.

Repository integration configuration

If GitHub integration is enabled, configure GITHUB_TOKEN, GITHUB_OWNER, and GITHUB_REPO for the repository you are evaluating. Use the minimum token permissions needed for the workflows you are evaluating.

Local development settings

Use local-only secrets, local database credentials, and a local NEXT_PUBLIC_APP_URL while evaluating Korieo. Restart the development server after changing environment variables.

Production settings

Production deployment details are not finalized in these starter docs. Before deploying beyond local evaluation, confirm supported hosting, database, authentication, backup, monitoring, and security requirements with the Korieo team.