Skip to main content

Overview

Praxos is configured primarily through environment variables. This guide covers all available configuration options.

Core Configuration

Environment

Server

Database Configuration

MongoDB

Azure Cosmos DB

Message Queue

Azure Service Bus

Redis (Alternative)

LLM Configuration

Portkey (Gateway)

OpenAI

Google Gemini

Secrets Management

Azure Key Vault

When using Key Vault, individual secrets can be:
  • Stored in Key Vault and auto-loaded at runtime
  • Or specified directly as env vars

Integration Configuration

Telegram

Discord

Slack

WhatsApp

Google Services

Microsoft 365

Notion

Trello

Dropbox

Feature Flags

Performance Tuning

Worker Configuration

Caching

Rate Limiting

Timeouts

Logging Configuration

Log Levels

Log Destinations

Security Configuration

CORS

API Security

Data Protection

Monitoring

Metrics

Health Checks

Azure Application Insights

Scheduled Tasks

Browser Configuration

Webhook Configuration

Time Zone

Example Configurations

Development

Staging

Production

Configuration File (.env)

Create a .env file:

Loading Configuration

From Environment

From Azure Key Vault

Validation

Praxos validates configuration on startup:

Troubleshooting

Configuration Not Loading

  • Check .env file exists
  • Verify file is in correct directory
  • Check for typos in variable names
  • Ensure proper file permissions

Secrets Not Found

  • Verify Azure Key Vault URL is correct
  • Check authentication credentials
  • Ensure secrets exist in Key Vault
  • Verify secret names match

Connection Errors

  • Validate connection strings
  • Check network connectivity
  • Verify firewall rules
  • Test credentials

Best Practices

  1. Never commit secrets - Use .gitignore for .env files
  2. Use Key Vault in production - Don’t store secrets in env vars
  3. Separate configs per environment - dev, staging, production
  4. Validate on startup - Fail fast if config is incorrect
  5. Document all variables - Maintain configuration documentation
  6. Use defaults wisely - Provide sensible defaults
  7. Environment-specific overrides - Allow per-environment customization

Next Steps

Kubernetes Deployment

Deploy to Kubernetes

Requirements

Review requirements

Quickstart

Local development setup