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
- Stored in Key Vault and auto-loaded at runtime
- Or specified directly as env vars
Integration Configuration
Telegram
Discord
Slack
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
.envfile 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
- Never commit secrets - Use
.gitignorefor.envfiles - Use Key Vault in production - Don’t store secrets in env vars
- Separate configs per environment - dev, staging, production
- Validate on startup - Fail fast if config is incorrect
- Document all variables - Maintain configuration documentation
- Use defaults wisely - Provide sensible defaults
- Environment-specific overrides - Allow per-environment customization