Configuration

!!! tip 'Centralized management' Configure production keys via the Admin Console or your secrets manager; do not store secrets in repo or plain text.

!!! note 'Structure' Use environment variables for runtime-only settings and persisted config for tunable platform behavior.

!!! warning 'Config drift' Ensure configuration is consistent across environments: mismatched retention or key settings may cause compliance gaps.

Global configuration table (complete)

Examples: environment snippets

# (1)
# Example: load configuration using pydantic BaseSettings
from pydantic import BaseSettings
class Settings(BaseSettings):
    app_env: str
    database_url: str
    class Config:
        env_file = '.env'

// (1)
// Example: load config via process.env
const config = {
  dbUrl: process.env.DATABASE_URL,
  storageBackend: process.env.STORAGE_BACKEND || 's3'
}

# (1)
export APP_ENV=development
# Prefer Postgres by default
export DATABASE_URL='postgresql+asyncpg://vivified:changeme@localhost:5432/vivified'
# RAG uses Redis by default when available
export REDIS_URL='redis://localhost:6379/0'
# Tests remain hermetic unless TEST_DB_URL overrides
# export TEST_DB_URL='sqlite+aiosqlite:///:memory:'

1. Prefer a secrets manager for production KMS and DB credentials

mermaid graph LR Env[Environment Vars] --> App ConfigStore --> App App --> Services Services --> Audit

Per-service configuration comparisons

!!! note 'Versioning & migrations' For config fields that are schema-related, use versioned keys and migration tooling. Avoid in-place changes without migrations.

??? note 'Advanced: dynamic flags' Some flags may be toggled at runtime via the Admin Console; use feature flags for experimental behavior.