.env.test

# ============================================================================
# Tale Platform - Test Environment Configuration
# ============================================================================
# Minimal .env for running container e2e tests in isolation.
# DO NOT use these values in production.

# Domain (required by all services)
HOST=tale.local
SITE_URL=https://tale.local

# TLS
TLS_MODE=selfsigned

# Security Secrets (test-only throwaway values)
BETTER_AUTH_SECRET=test-secret-do-not-use-in-production-1234567890
ENCRYPTION_SECRET_HEX=0000000000000000000000000000000000000000000000000000000000000000

# API Keys (test-only, services won't make real calls)
OPENAI_BASE_URL=http://localhost:9999/mock/v1
OPENAI_API_KEY=test-key-not-real
OPENAI_MODEL=test-model
OPENAI_FAST_MODEL=test-model
OPENAI_CODING_MODEL=test-model
OPENAI_EMBEDDING_MODEL=test-model
OPENAI_VISION_MODEL=test-model
EMBEDDING_DIMENSIONS=1536
CRAWLER_EMBEDDING_DIMENSIONS=1536

# Database - DB_ vars are used by the db entrypoint wrapper to set POSTGRES_*.
# DB_NAME is intentionally NOT set here: the db Dockerfile defaults it to `tale`
# for the postgres server, while rag/crawler entrypoints fall through to their
# own default (`tale_knowledge`) — the database where init-scripts/03 installs
# the `vector` and `pg_search` extensions. Setting DB_NAME globally via env_file
# would leak `tale` into rag/crawler and race with ParadeDB's bootstrap loading
# `vector` into `tale`, which fails on slower runners (e.g. ubuntu-latest).
DB_PASSWORD=test_password_e2e
DB_USER=tale

# Also set POSTGRES_ vars directly for the PostgreSQL healthcheck in compose.yml
POSTGRES_USER=tale
POSTGRES_DB=tale
POSTGRES_PASSWORD=test_password_e2e

# Convex
INSTANCE_SECRET=0000000000000000000000000000000000000000000000000000000000000000
INSTANCE_NAME=tale_platform