Laydebug

Env and secrets

What self-hosters and Action integrators need to configure.

API

NamePurpose
LAYDEBUG_PROJECT_API_KEYRaw project key (hashed at rest)
BETTER_AUTH_SECRETBetter Auth secret (≥32 chars)
BETTER_AUTH_URLPublic API URL (HTTPS in production)
DATABASE_URLPostgres (required in production)
SUPABASE_URL / SUPABASE_SECRET_KEYStorage signing
SUPABASE_STORAGE_BUCKETDefault laydebug-state
GITHUB_ISSUE_TOKEN / GITHUB_REPOOpen issues (owner/name)
GITHUB_CLIENT_ID / GITHUB_CLIENT_SECRETOptional GitHub OAuth for a future console
ALLOW_INSECURE_LOCAL_ADAPTERSPGlite + memory storage (forbidden in production)

Integrator Action secrets

NamePurpose
OPENAI_API_KEY / OPENROUTER_API_KEY / ANTHROPIC_API_KEYSuggested-fix models
SUPABASE_URL / SUPABASE_SECRET_KEYDownload consented snapshots
TRIAGE_APK_URL / TRIAGE_APK_SHA256Explicit APK (checksum optional)
EXPO_TOKENFallback: latest finished EAS Android build

Website clients use the same tRPC/HTTP contract with x-laydebug-key. There is no web SDK in v1.

On this page