Multi-Environment Setup

May 30, 2026 | 5 min read

Environment-Specific Config Files

Pyvorin supports per-environment config overrides via environment variables:

# Development
export PYVORIN_THIN_API_BASE_URL=http://localhost:8000
export PYVORIN_THIN_MOCK_MODE=true

# Staging
export PYVORIN_THIN_API_BASE_URL=https://staging-api.pyvorin.com

# Production
export PYVORIN_THIN_API_BASE_URL=https://api.pyvorin.com
export PYVORIN_THIN_TELEMETRY_ENABLED=true

Docker Compose Example

services:
  app-dev:
    environment:
      - PYVORIN_THIN_MOCK_MODE=true
  app-prod:
    environment:
      - PYVORIN_THIN_API_BASE_URL=https://api.pyvorin.com
      - PYVORIN_THIN_LICENSE_KEY=${PYVORIN_LICENSE_KEY}

Config Precedence

  1. Environment variables (highest)
  2. Config file (thin_config.json)
  3. Built-in defaults (lowest)

Secrets Management

  • Never commit thin_config.json to version control.
  • Use Docker secrets, Kubernetes secrets, or CI variables for license keys.
  • The config file is JSON — easy to template with Ansible, Chef, or Puppet.