perplexity-multi-env-setup

Configure Perplexity across development, staging, and production environments.Use when setting up multi-environment deployments, configuring per-environment secrets,or implementing environment-specific Perplexity configurations.Trigger with phrases like "perplexity environments", "perplexity staging","perplexity dev prod", "perplexity environment setup", "perplexity config by env".

⭐939stars🔀114forks📁View on GitHub🕐Updated Jan 11, 2026⬇️1downloads

When & Why to Use This Skill

The Perplexity Multi-Environment Setup skill streamlines the configuration and deployment of Perplexity API integrations across development, staging, and production environments. It focuses on implementing professional-grade environment isolation, secure secret management using tools like AWS Secrets Manager and HashiCorp Vault, and robust environment detection logic to ensure application stability and security throughout the software development lifecycle (SDLC).

Use Cases

  • Setting up isolated API configurations to prevent development tests from affecting production data or consuming production quotas.
  • Automating the retrieval of environment-specific secrets from AWS Secrets Manager, GCP Secret Manager, or HashiCorp Vault for secure API access.
  • Implementing environment guards and safety checks to block high-risk operations (like data deletion) in non-production environments.
  • Configuring CI/CD pipelines to dynamically inject the correct Perplexity credentials and feature flags based on the deployment target.
  • Establishing a standardized configuration structure (base, dev, staging, prod) for scalable and maintainable AI-powered applications.
nameperplexity-multi-env-setup
description|
allowed-toolsRead, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*)
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Perplexity Multi-Environment Setup

Overview

Configure Perplexity across development, staging, and production environments.

Prerequisites

  • Separate Perplexity accounts or API keys per environment
  • Secret management solution (Vault, AWS Secrets Manager, etc.)
  • CI/CD pipeline with environment variables
  • Environment detection in application

Environment Strategy

Environment Purpose API Keys Data
Development Local dev Test keys Sandbox
Staging Pre-prod validation Staging keys Test data
Production Live traffic Production keys Real data

Configuration Structure

config/
├── perplexity/
│   ├── base.json           # Shared config
│   ├── development.json    # Dev overrides
│   ├── staging.json        # Staging overrides
│   └── production.json     # Prod overrides

base.json

{
  "timeout": 30000,
  "retries": 3,
  "cache": {
    "enabled": true,
    "ttlSeconds": 60
  }
}

development.json

{
  "apiKey": "${PERPLEXITY_API_KEY}",
  "baseUrl": "https://api-sandbox.perplexity.com",
  "debug": true,
  "cache": {
    "enabled": false
  }
}

staging.json

{
  "apiKey": "${PERPLEXITY_API_KEY_STAGING}",
  "baseUrl": "https://api-staging.perplexity.com",
  "debug": false
}

production.json

{
  "apiKey": "${PERPLEXITY_API_KEY_PROD}",
  "baseUrl": "https://api.perplexity.com",
  "debug": false,
  "retries": 5
}

Environment Detection

// src/perplexity/config.ts
import baseConfig from '../../config/perplexity/base.json';

type Environment = 'development' | 'staging' | 'production';

function detectEnvironment(): Environment {
  const env = process.env.NODE_ENV || 'development';
  const validEnvs: Environment[] = ['development', 'staging', 'production'];
  return validEnvs.includes(env as Environment)
    ? (env as Environment)
    : 'development';
}

export function getPerplexityConfig() {
  const env = detectEnvironment();
  const envConfig = require(`../../config/perplexity/${env}.json`);

  return {
    ...baseConfig,
    ...envConfig,
    environment: env,
  };
}

Secret Management by Environment

Local Development

# .env.local (git-ignored)
PERPLEXITY_API_KEY=sk_test_dev_***

CI/CD (GitHub Actions)

env:
  PERPLEXITY_API_KEY: ${{ secrets.PERPLEXITY_API_KEY_${{ matrix.environment }} }}

Production (Vault/Secrets Manager)

# AWS Secrets Manager
aws secretsmanager get-secret-value --secret-id perplexity/production/api-key

# GCP Secret Manager
gcloud secrets versions access latest --secret=perplexity-api-key

# HashiCorp Vault
vault kv get -field=api_key secret/perplexity/production

Environment Isolation

// Prevent production operations in non-prod
function guardProductionOperation(operation: string): void {
  const config = getPerplexityConfig();

  if (config.environment !== 'production') {
    console.warn(`[perplexity] ${operation} blocked in ${config.environment}`);
    throw new Error(`${operation} only allowed in production`);
  }
}

// Usage
async function deleteAllData() {
  guardProductionOperation('deleteAllData');
  // Dangerous operation here
}

Feature Flags by Environment

const featureFlags: Record<Environment, Record<string, boolean>> = {
  development: {
    newFeature: true,
    betaApi: true,
  },
  staging: {
    newFeature: true,
    betaApi: false,
  },
  production: {
    newFeature: false,
    betaApi: false,
  },
};

Instructions

Step 1: Create Config Structure

Set up the base and per-environment configuration files.

Step 2: Implement Environment Detection

Add logic to detect and load environment-specific config.

Step 3: Configure Secrets

Store API keys securely using your secret management solution.

Step 4: Add Environment Guards

Implement safeguards for production-only operations.

Output

  • Multi-environment config structure
  • Environment detection logic
  • Secure secret management
  • Production safeguards enabled

Error Handling

Issue Cause Solution
Wrong environment Missing NODE_ENV Set environment variable
Secret not found Wrong secret path Verify secret manager config
Config merge fails Invalid JSON Validate config files
Production guard triggered Wrong environment Check NODE_ENV value

Examples

Quick Environment Check

const env = getPerplexityConfig();
console.log(`Running in ${env.environment} with ${env.baseUrl}`);

Resources

Next Steps

For observability setup, see perplexity-observability.