Configure multi-environment setup for Evernote integrations.
Use when setting up dev, staging, and production environments,
or managing environment-specific configurations.
Trigger with phrases like "evernote environments", "evernote staging",
"evernote dev setup", "multiple environments evernote".
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.
Define environment-specific .env files. Each environment uses its own API key and token. The flag controls which Evernote endpoint the SDK connects to.
EVERNOTE_SANDBOX
# .env.development - sandbox with dev token
EVERNOTE_SANDBOX=true
EVERNOTE_DEV_TOKEN=S=s1:U=...
# .env.production - production with OAuth
EVERNOTE_SANDBOX=false
EVERNOTE_CONSUMER_KEY=prod-key
EVERNOTE_CONSUMER_SECRET=prod-secret
Step 3: Environment-Aware Client Factory
Build a factory that creates properly configured Evernote clients based on the active environment. Include validation that production never uses sandbox tokens.
Step 4: Docker Compose for Local Development
Define services for the app, Redis (caching), and a webhook receiver (ngrok or localtunnel) in docker-compose.yml. Mount .env.development as environment file.
Step 5: Health Check Endpoint
Create a /health endpoint that verifies Evernote API connectivity, reports the active environment, and checks cache availability.
For observability setup, see evernote-observability.
Examples
Three-environment setup: Development uses sandbox Developer Token for instant testing. Staging uses sandbox OAuth for integration testing. Production uses production OAuth with full rate limiting and monitoring.
Docker local dev: Run docker compose up to start the app with Redis caching and ngrok for webhook testing, all preconfigured for the sandbox environment.
