evernote-multi-env-setup

# Evernote Multi-Environment Setup ## Overview Configure separate development, staging, and production environments for Evernote integrations with proper isolation, configuration management, and environment-aware client factories. ## Prerequisites - Multiple Evernote API keys (sandbox for dev/staging, production for prod) - Environment management infrastructure - CI/CD pipeline (see `evernote-ci-integration`) ## Instructions ### Step 1: Environment Configuration Files Create per-environment config files that define the Evernote endpoint, sandbox flag, rate limit settings, and logging level. ```javascript // config/environments.js const configs = { development: { sandbox: true, apiUrl: 'https://sandbox.evernote.com', rateLimitDelayMs: 0, // No throttle in dev logLevel: 'debug' }, staging: { sandbox: true, apiUrl: 'https://sandbox.evernote.com', rateLimitDelayMs: 100, logLevel: 'info' }, production: { sandbox: false, apiUrl: 'https://www.evernote.com', rateLimitDelayMs: 200, logLevel: 'warn' } }; module.exports = configs[process.env.NODE_ENV || 'development']; ``` ### Step 2: Environment Variables Define environment-specific `.env` files. Each environment uses its own API key and token. The `EVERNOTE_SANDBOX` flag controls which Evernote endpoint the SDK connects to. ```bash # .env.development - sandbox with dev token EVERNOTE_SANDBOX=true EVERNOTE_DEV_TOKEN=S=s1:U=... # .env.production - production with OA...