env-sync

Environment Manager

Synchronizes environment variables across environments, validates configurations, manages secrets, and sets up development environments.

Purpose

• Sync .env files across environments
• Validate environment variables
• Generate environment documentation
• Secret rotation management
• Docker/container environment setup

Workflow

Phase 1: Environment Selection

1. STOP → "Select environment operation:"

   1. Sync environments - Copy variables between environments
   2. Validate config - Check for missing/invalid variables
   3. Generate template - Create .env.example
   4. Rotate secrets - Update sensitive values
   5. Setup new environment - Initialize from template
   6. Compare environments - Diff between environments
   
   Choose operation (1-6):
   

2. Environment Options

   • STOP → "Include secret values? (y/n):"
   • STOP → "Validate against schema? (y/n):"
   • STOP → "Backup current config? (y/n):"

Phase 2: Environment Discovery

1. Find Environment Files

   # Locate all env files
   find . -name ".env*" -type f | grep -v node_modules
   
   # Common patterns
   .env
   .env.local
   .env.development
   .env.staging
   .env.production
   .env.test
   

2. Parse Environment Variables

   const dotenv = require('dotenv');
   const fs = require('fs');
   
   function parseEnvFile(filepath) {
     const content = fs.readFileSync(filepath, 'utf8');
     return dotenv.parse(content);
   }
   

Phase 3: Environment Validation

Schema Definition

// env.schema.json
{
  "required": [
    "NODE_ENV",
    "PORT",
    "DATABASE_URL",
    "JWT_SECRET"
  ],
  "properties": {
    "NODE_ENV": {
      "type": "string",
      "enum": ["development", "staging", "production"]
    },
    "PORT": {
      "type": "number",
      "minimum": 1000,
      "maximum": 65535
    },
    "DATABASE_URL": {
      "type": "string",
      "pattern": "^(postgres|mysql|mongodb)://.*"
    },
    "JWT_SECRET": {
      "type": "string",
      "minLength": 32
    }
  }
}